15-441 Syllabus

Table of Contents

Course Meetings Lectures:

  • 1:30 - 2:50 Tuesdays and Thursdays in DH 1212

Recitations:

  • Section A: 10:30 - 11:20 Wednesdays in SH 220
  • Section B: 12:30 - 1:20 Wednesdays in SH 220
  • Section C: 3:30 - 4:20 Wednesdays in PH 226A

Course Description

This is an introductory course about computer networks. The emphasis will be on the basic performance and engineering tradeoffs in the design and implementation of computer networks. Students will learn not only what computer networks are and how they work today, but also why they are designed the way they are and how they are likely to evolve in the future. We will draw examples primarily from the Internet. Topics to be covered include: LAN, congestion/flow/error control, routing, addressing, naming, multicasting, switching, internetworking, quality of service, and network security. There will be both written and programming assignments, and a substantial project involving the design and implementation of a complete protocol stack.

-- From the Offical Course Description

Prerequisites

15-213, or equivalent, or permission of instructor

Textbook (Optional)

Peterson and Davie, Computer Netowrks: A Systems Approach/

Web site

The course website is http://www.andrew.cmu.edu/course/15-441-sp07/, contains a tremendous wealth of resources -- check it often!

Course Online Bulletin Board

The course bboard is at academic.cs.15-441 . Please stay up to date on all the postings. Often a question you are about to ask has already been answered on the bboards.

Instructors

Gregory Kesden
Gregory.Kesden@cs.cmu.edu
8020 Wean Hall
(412) 268-1590
Schedule w/Office Hours

Note: Please don't pay too much attention to my office hours. If you want to speak with me, try dropping by. In the past, some students have found it useful to finger me on my workstation, gigo.sp.cs.cmu.edu or the cycle server linux1.gp.cs.cmu.edu.

Sometimes I can be found as gkesden@AIM, gkesden@MSM, or gkesden2@yahoo

All of my phone numbers forward to my cell phone. Please feel free to call any time -- I generally turn it of when inconvenient to answer.

Recitation Instructors

Office hours and locations TBA

  • Section A: Hong Yan (hyan@andrew.cmu.edu)
    • Office Hours: Thursday, 8pm - midnight, WeH 8130
  • Section B: Michael Ashley-Rollman (mpa@andrew.cmu.edu)
    • Office Hours: Sunday 7pm - 9 pm, WeH 5207
  • Section C: Vinay Chaudhary (vjc@andrew.cmu.edu)
    • Office Hours: 8 - 11 P.M Wednesday, Wean 3130
  • Hassan Rom (mrom@andrew.cmu.edu)
    • Office Hours: Tuesday/Thursday 6pm - 8pm, WeH 5200 Windows cluster

Course Attendance

Attendance is expected at all lectures. You are responsible for everything conveyed during class, even if you are absent. The same is true of recitation.

It is suggested that you make friends with your classmates and establish a study group -- these will provide vehicles by which you can discovery the content of any class you might miss. In the event that you miss class, you should contact one of these individuals promptly to ask for help.

The course staff is not responsible to help you with material or procedural announcements from which you opted out by electively missing class.

Need Help?

I can't stress enough that the course staff are dedicated to providing you the highest possible levels of support: inside of the classroom and outside. Please, if you need help, do ask.

To reach the entire course staff, please email
staff-441@cs. This is a great way to get a fast answer to your questions -- I'll be one of us isn't far from the keyboard.

Assignments and Grading

  • Midterm Exam: 15%
    This will be an individual, in-class, written exam.
  • Final Exam: 20%
    This, too, is a traditional paper-and-pencil exam to be administered during the University final exam period.
  • Homework, &c: 15%
    These are out-of-class written assignments. They are usually individual.
  • Projects: 10% + 20% + 20% = 50%
    These are large, out-of-class programming assignments that are completed with a single partner.

Grade Corrections

We try to be very, very careful about scoring your work and maintaining your grades. But, we are human and will make mistakes. If you have any questions about grading, please see any member of the course staff.

If possible, s/he will help you "on the spot". But, if s/he want to discuss the issue with other members of the staff, which does occur in many cases, he or she might make a copy of your work and/or ask you to write down or email your concerns. Please don't be alarmed -- this is just to try to ensure correctness and consistency among staffers, as well as prevent miscommunication. If you are asked to provide a copy of the work or feedback in question, or to provide your concerns in writing or email, you are required to do this before your concern can be addressed.

Please keep copies of all of your graded work, electronic submissions, and electronci feedback, until you receive your final course grade and are satisifed that it is correct. Without the original work and the grading information, it is more difficult and time consuming to correct errors.

In general, grading concerns should be addressed within one (1) weeks. In the special case of the final exam, they should be addressed with one (1) year. The course staff, at its discretion, may refuse to reconsider grades outside of this time period.

Should concerns arise outside of these time periods, but during the semester, please do contact any member of the course staff -- we want to be reasonable and will do our best, within our discretion, to help. Should concerns occur after the end of the semester, please contact the instructor. Or, in the unlikley event that he is no longer at the University, on leave, or otherwise inaccessible, contact an administrator in the Computer Science department.

Students do have the right to appeal final course grades. This can be done informally, beginning with the instructor, and then to the student's academic dean and/or the academic dean in the home department. It can also be done formally using the policy outline in the Academic Regulations.

Collaboration

It is suggested that you form study groups as soon as possible. These groups generally work best if there are between three and five people involved, but sometimes pairs or slightly larger groups can work well. Typically the most effective study groups meet once per week for a few hours, or a couple of times each week for a couple of hours each meeting. For study groups to be effective, each member must work indivudally with the material in-between meetings such that s/he has something to contribute as well as questions to drive the discussion.

Unless otherwise specified, all assignments should be completed individually. In other words, it is okay to collaborate in studying the course material, but the "writing on the page" or the "code in the lab", as examples, should be your own "thought product".

If portions of your indididual assignments have been significantly influenced by someone else, you should prominently give them credit for their contribution. Proper attribution is critically important -- and is an absolute defense against charges of "Academic Dishonesty"

Failure to provide proper recognition for the contributions of others towards any graded work may be, at the discretion fo course staff, considered Academic Dishonesty under the applicable University, School, Department, and/or Intro Group policies.

The Academic Regulations are the only authoritative source for information regarding the University police on Academic Dishonesty, and related procedural matters. But, the following is an informal summary:

  • An instructor can charge a student with academic dishonesty and impose a penalty within the course, including an "R" grade.

  • The instructor informs the University of the charge, where it is recorded. If it is a first-offense, the University takes no further action. If it is not, a University committee is convened. For other than first offenses, the Committee, not the instructor determines the penalty, which can include academic actions such as expulsion or suspension, as well as less-severe actions. The student may appear at this hearing, and the instructor might also ask to appear or be asked to appear.

  • Even on a first offense, the instructor can ask the University to convene a Committee as discussed above. This might be done, for example, in the case of a particularly flagrant case, or under atypical cicumstances.

  • The student has the right to appeal an instructors finding of academic dishonesty. Such an appeal is heard by the same Committee as discussed above. In the event that both the student and faculty member request a Committee, the same Committee will hear both.

  • University procedure provides for the appeal of decisions by the Committee.

  • In the event that the instructor charges a student with Academic Dishonesty, it is suggested that the student consider the totality of the circumstances calmly and rationally and seek advice from the instructor -- as well as third parties, such as the student's advisor, academic dean, or a dean of student affairs. It is may not be in the student's best interest to take a rash action, such as attempting to drop the course.

  • Students who are charge with Academic Dishonesty should be aware that there will be no prejudice against them in the course, beyond the penalty directly imposed, as a result of the charge, or of any appeal.

Late Work

You have five (5) "Late Days" for use on assignments this semester. You can use one day on each of three assignments, three days on one assignment, &c. There are no half days -- an assignment 1 second late requires the use of a full late day.

These late days are not "procrastination days". They are instead designed much like "personal days" at work to handle the little things that come up during the semester: short illnesses, injuries, visiting family or friends, a burst of work in other classes, doctors vists, &c.

The use of these days is completely at your discretion -- but, once they are gone, they are gone. That's it. The course staff cannot give you more. Late work is not accepted, other than through the use of "Late Days".

There is, of course, the possibility that exceptions to this policy will arise. We certainly hope that nothing incapactiating will happen to any of you. But, in the event that there is some major life event including major medical issues, emotional problems, family problems, &c, the course staff stands ready to work with you, as appropriate.

But, because these events are major events that likely will affect more than one class, we refer these circumstances to other University officials, typically academic deans, deans of student affairs, and/or assigned academic advisors.

In the event that you need help of this kind, please see a member of the course staff, and advisor dean, or other appropriate University offical. If you contact us, we'll likely begin by contacting your advisor or dean. But, regardless who you contact first, we'll work together with your academic unit and/or student affairs, and (most importanbtly) you, to do the Right Thing. We are, in fact, here to help.

Please also keep in mind that assignments only count as submitted, if submitted as directed. For example, we don't accept assignments via email or on floppy disk, unless we specifically authorize it. Should you fail to submit an assignment as directed, you will need to use late days to submit it.

o

No Email Attachments

Unless otherwise directed by a member of the course staff, do not send files as attachments via email. For technical reasons, this mode of file transmission is extremely inefficient. Instead, please create a directory within your AFS space, place the file or files into that directory, and give gkesden:staff-100 at least "rl" access. If this doesn't make sense to you -- relax. Just send email to us and ask for instructions for sending us the file(s).

No Email Attachments

Unless otherwise directed by a member of the course staff, do not send files as attachments via email. For technical reasons, this mode of file transmission is extremely inefficient. Instead, please create a directory within your AFS space, place the file or files into that directory, and give gkesden:staff-100 at least "rl" access. If this doesn't make sense to you -- relax. Just send email to us and ask for instructions for sending us the file(s).

Videotaping, audiotaping, still photography prohibited

This policy applies to audio, still video, moving video, and any other recording with a greater fidelity than natural language, manually scribed notes.

No one, other than an appropriately authorized agent of the University or Gregory M. Kesden, may record or tape any classroom activity without the express written consent of Gregory M. Kesden. Unless expressly granted, the authorization to record does not confer any license for viewing or other use. This written consent must be witnessed and notarized.

If a student believes that he/she is disabled and needs to record or tape classroom activities, he/she should contact the Office of Disability Resources. If deemed appropriate by Gregory M. Kesden, the student will be permitted access, for a limited time, and for the single purpose of the permitted student satisfying the written objectives of this course, to a recording created by the University.

Unless given express written consent via a witnessed and notarized document by Gregory M. Kesden, consent is expressly withheld to maintain recordings covered by this policy, regardless of media or format, and regarldess of whether the recording 1st class, "backup", or "cached", beyond the 15th day following the last day of classes of the semester of the recording.

Unless given express written consent via a witnessed and notarized document by Gregory M. Kesden, anyone permitted to record, or access to recordings, under this policy, has the affirmative duty to take all reasonable precautions to ensure that the recordings are not redistributed in any form or otherwise viewable or accessible to those not expressly authorized by Gregory M. Kesden.