CS636: Internetworking (Spring 2012)

Course Information

TR 10:30am-11:45am
LWSN B134

Instructor:
Douglas E. Comer
email: comer@cs.purdue.edu
phone: (765)494-6009
office: LWSN 1171

Teaching Assistant:
Cheng Cheng
email: chengcheng@purdue.edu
phone: (765)494-0361
office: HAAS 254
office hour: TBD

Textbook:
Required:
Comer, Internetworking with TCP/IP Vol 1: Priciples, Protocols, and Architecture, Prentic-Hall, 5th edition, 2005
Recommended:
Comer, Internetworking with TCP/IP Vol 2: Design, Implementation and Internals Prentic-Hall, 3rd edition, 1999

Course E-mail List:
Course: cs636@cs.purdue.edu
TA: cs636-ta@cs.purdue.edu

Credit Hours:
3

Announcements

Labs/Assignments

Lecture Notes

To better protect the lecture notes, all lecture notes will be posted on Blackboard. You can log into the course's BlackBoard page at https://blackboard.purdue.edu/webct/logon/7957988433221

Outside the lecture period...

Class E-mail Lists

The email list for the class is cs636@cs.purdue.edu. You will need to add your address directly to the list. For those of you who do not happen to know how to add yourselves to the email list, here is the instruction:

mailer add me to cs636

Of course, you have to log in to one of the department Linux boxs first.

Blackboard

Discussion and posting of grades and lecture notes will take place at Blackboard Vista. You can log into the course's BlackBoard page at https://blackboard.purdue.edu/webct/logon/6857039686221.

Purpose

This is a graduate-level course in the design and implementation of internetworks that looks at principles, protocols, and architecture. It covers addressing, binding, routing, layering, architecture of the global Internet, and various associated technologies. The focus is on the TCP/IP Internet Protocol Suite, but we will consider design alternatives. The goals are:

  1. to acquaint students with major internet protocols, their features, details and functionality,
  2. to introduce students to the literaure, and
  3. to show students priciples and abstractions underlying desing choices, and how tradeoffs affect the overall system.

Grading Policy:

Students will read the text, RFCs, and other pertinent literature, and build working systems that implement the protocols and forweard IP datagrams among multiple networks. A grade will be assigned as follows:

Class participation, homework assignments and quizzes 5%
System programming projects 80%
Examination(s) 15%

Labs and Policies:

We will use the XINU operating system for the programming labs. The XINU lab is located in the HAAS Building Room 257.

Getting your CS account.

Students can get their CS account information on-line. Go to CS homepage, use the ITaP login and password in the upper right-hand corner. This will take you to a page where you agree to the access and usage policies, and then get your CS login and initial password. You also use the same site for doing mid-semester reviews, evaluations, etc. If you have signed up but don't have an account, please contact the accounts@cs.purdue.edu alias.

Academic Dishonesty

We wish to foster an open and collegial class environment. At the same time, we are vigorously opposed to academic dishonesty because it seriously detracts from the education of honest students. Because of this, we have the following standard policy on academic honesty, consistent with Purdue University's official policy.

It is permissible to discuss a general method of solution with other students, or to make use of reference materials in the library or online. If you do this, you will be expected to clearly disclose with whom you discussed the method of solution, or to cite the references used. Failure to do so will be considered cheating or plagiarism. The use of "method of solution" means a general discussion of technique or algorithm, such as one would reasonably expect to occur standing in front of a whiteboard, and precludes the detailed discussion of code. Specifically, looking at another student's code on his/her computer monitor is NOT allowed.

Unless otherwise explicitly specified, all code that is submitted is to be entirely each student’s own work. Using any code or copying any assignment from others is strictly prohibited without advance prior permission from the instructor. This includes the use of code others have submitted in the past.

All students work is their own unless they are assigned team work. Students who do share their work with others are as responsible for academic dishonesty as the student receiving the material. Students are not to show work to other students, in the class or not. Students are responsible for the security of their work and should ensure that printed copies are not left in accessible places, and that file/directory permissions are set to be unreadable to others (e.g. use "chmod -R 700 *" from your home directory). If you need assistance protecting your work, please contact the TA or the instructor.

Students who encourage others to cheat or plagiarize, or students who are aware of plagiarism or cheating and do not report it are also participating in academically dishonest behavior.

Be aware that we will use a software tool called MOSS to check for copying among submitted assignments. Additionally, the instructor and TA will be inspecting all submitted material to ensure honesty.

Any case of academic dishonesty will be dealt with by a severe grade penalty in the overall class grade and referral to the office of the Dean of Students.

Campus Emergencies:

In the event of a major campus emergency, course requirements, deadlines, and grading percentages are subject to changes that may be necessitated by a revised semester calendar. If such unusual circumstances arise, students may determine any such changes by contacting their instructors via email or phone, and checking the course web page for updates.

Emergencies and campus closings will be announced on local media and on the main Purdue University WWW site http://www.purdue.edu. Individuals may subscribe to an SMS text announcement service. Other details are on the Purdue emergency preparedness site.