MCS-377: Networking (Fall 2006)


We will examine several key challenges of networking, such as application-level interoperability, transport-level congestion control, and network-level routing. For each of these challenges, we will examine the specific response embodied in the current Internet protocol suite and the systems implementing it. However, we will also keep an eye out for the broader possibilities for potential future protocols and systems.

Office hours

I will be available in my office (OHS 303) 10:30-11:20 Mondays and Fridays, 1:30-2:20 Tuesdays and Thursdays, as well as by appointment. Or try your luck: just stop by and see whether my door is open. You may send me electronic mail at or call me at extension 7466. I'll try to put any updates to my office hours on my web page, so check there if in doubt.

World Wide Web

All course materials will be available through my World Wide Web page. The URL for this course is After this syllabus I will give hardcopy handouts only to those students who want them.

Text and readings

The primary text for the course will be Computer Networking: A Top-Down Approach Featuring the Internet, 3rd ed., by James F. Kurose and Keith W. Ross, Addison-Wesley, 2005. You will also read some of the professional literature as part of the homework.


There will be four lab assignments. The due dates for the labs are shown in the syllabus below. We'll meet in the OHS 326 lab as shown in the syllabus.

Attendance is expected for all lab days. (If you turn in a lab report early, you are excused from the remaining days devoted to that lab.) I will excuse up to two absences per student, for any reason. Use yours wisely. If you exceed this allowance, I may reduce your course grade by one letter grade.

Homework assignment policy

I will assign homework problems. You may turn in any individual homework problem whenever you think you have it solved. I will return it to you as quickly as I can, but normally with only an indication of whether it is acceptable or needs more work. The reason why I won't write much on the work I turn back to you is because I would like to talk with you face-to-face. If a problem needs more work, you should treat that as an invitation to come talk with me about it. Once you've done the additional work, you may turn the problem in again. In fact, you may turn in each problem in as many times as you like, until it is marked as acceptable. Your grade for the homework portion of the course will be based on the fraction of homework problems that you eventually did acceptably.

Homework problems may be turned in at any time up until the start of class on October 10th for chapters 1-3, November 13th for chapters 4-5, and December 12th for Chapters 6-8.

Unless I indicate that a particular problem must be done individually, you may work on any problem in a group of two or three students. One copy of the solution produced by the team should be turned in, with all team members names on it. Write "we all contributed fairly to this solution" and have all team members sign under that statement.


There will be two intra-term exams and a final exam. You will be given one and a half hours for each intra-term exam. You will take the first exam on either October 11th or 12th and the second exam on either November 14th or 15th. For each exam, you will be able to sign a test paper out for an hour and a half of your own choice on either of the dates. The final exam will be as scheduled by the registrar. For each test, you may use one 8.5x11 sheet of handwritten notes. (Both sides of the sheet are OK.)

Field trips

On two occasions, we will examine how networking plays out in actual sites. The first one (a warm up) will be an examination of the Gustavus campus network, which we will do during a normal class period. The second one will involve a more extended time period, as we will be driving to HickoryTech in Mankato. Based on polling the class, I have scheduled this for December 5th, departing Olin by college van at 1:30pm.


You are expected to be familiar with the college academic honesty honor code policy, and to comply with that policy. If you have any questions about it, please ask. One specific requirement of that policy is that you write the following in full and sign it on every examination and graded paper:

On my honor, I pledge that I have not given, received, nor tolerated others' use of unauthorized aid in completing this work.

For the purposes of this policy, I am defining "graded papers" to be lab reports but not homework problems. (I still expect you to comply with the honor code on homework problems, just not to write the explicit pledge on them.) When lab reports are co-authored, each co-author should write and sign the pledge.

Late lab assignments

All lab reports are due at the beginning of class on the day indicated. Late reports will be penalized by one ``grade notch'' (such as A to A- or A- to B+) for each weekday late or fraction thereof.

If you are too sick to complete an assignment on time, you will not be penalized. Simply write ``late due to illness'' at the top of the assignment, sign your name and hand it in. Other circumstances will be evaluated on a case-by-case basis.


I will provide you with a letter grade on each lab assignment and test, in addition to the mid-term and final grades, so that you may keep track of your performance. As a guideline, the course components will contribute to your final grade in the proportions indicated below:

Style guidelines

All homework and lab reports should be readily readable, and should not presuppose that I already know what you are trying to say. Use full English sentences where appropriate (namely almost everywhere) and clear diagrams, programs, etc. Remember that your goal is to communicate clearly, and that the appearance of these technical items plays a role in this communication process. Be sure your assignments are always stapled together and that your name is always on them.


If you have a learning, psychological, or physical disability for which a reasonable accommodation can be made, I would be happy to refer you to the college's disability services coordinator, and to cooperate in the accommodation process. It is generally best if this can be done as soon as possible.


This is my best guess as to the rate at which we will cover material. However, don't be shocked if I have to pass out one or more revised syllabi.

9/81.0-1.5Introduction, part 2

9/111.6-1.10Introduction, part 3
9/122.0-2.2Application layer and HTTP
9/142.3-2.4FTP and email

9/182.6P2P filesharing
9/192.7-2.8Socket programming
9/212.9-2.10Programming example
9/22Lab 1

9/253.0-3.3Transport layer and UDP
9/263.4.0-3.4.2Reliable data transfer
9/29Lab 1

10/2No class
10/3No class (Nobel Conference)
10/53.6-3.7.0Congestion control
10/6Guest: Milo MartinLab 1

10/93.7.1-3.8TCP congestion control
10/10Review, catch-up
10/12No class: test schedulable
10/13Lab 2

10/16Lab 2
10/175.0-5.3Link layer
10/205.6-5.7Ethernet boxes and PPP

10/265.8-5.9Link virtualizationLab 2
10/27Lab 3

10/304.0-4.3Network layer and routers
11/24.4.3-4.4.4ICMP and IPv6
11/3Lab 3

11/64.5.0-4.5.1Link-state routing
11/74.5.2-4.5.3Distance-vector routing
11/94.6Internet routingLab 3
11/104.7-4.8Multicast routing

11/13Review, catch-up
11/14No class: test schedulable

11/206.4-6.9Cellular and mobility
11/21No class

11/27Gustavus networking tour
11/308.3-8.4Authentication and integrity
12/1Lab 4

12/4Lab 4
12/5Trip to HickoryTech; leave Olin at 1:30
12/7No class
12/88.5-8.6Key distribution and firewallsLab 4

12/118.7-8.8.1Attacks and secure email
12/128.8.2-8.9More on security

Course web site:
Instructor: Max Hailperin <>