CS 536: Data Communication and Computer Networks Spring 2007 http://www.cs.purdue.edu/homes/fahmy/cs536/index.html

Click here for the Reading List page.

• James F. Kurose and Keith W. Ross. Computer Networking - A Top Down Approach Featuring the Internet, 3rd edition, Addison-Wesley, ISBN 0-321-22735-2.
  We will cover parts of Chapters 1 through 9.

• Recommended text: Computer Networks: A Systems Approach. L. Peterson and B. Davie.

• Other Useful Books (some of them available in the library; we will discuss some material from them in class):
  • The Art of Computer Systems Performance Analysis. Raj Jain.
  • Design and Validation of Computer Protocols. Holzmann.
  • Handbook of Wireless Networks and Mobile Computing. Stojmenovic.
  • Internetworking with TCP/IP. Comer.
  • UNIX Network Programming, volumes 1 and 2. Stevens.
  • The Linux kernel.
  • Linux Kernel Internals. Michael Beck et al. Addison-Wesley-Longman, 1998. 2nd edition. ISBN: 0-201-33143-8.
  • Solaris Internals: Core Kernel Architecture. Jim Mauro et al, Sun Microsystems Press, 2001. ISBN: 0-13-022496-0.
  • Solaris Systems Programming. Rich Teer, Pearson Education, 2005. ISBN: 0-201-75039-2.

• Sonia Fahmy, office: LWSN 2142H, e-mail: fahmy@cs.purdue.edu, phone: (765) 49-46183

Office Hours:

• Th 3:20-5 PM, F 1:30-2:20 PM, and by appointment

• Isuru Ranaweera, iranawee@cs.purdue.edu, office: LWSN B116C, office hours: TW 3:25-4:25 PM.

PSO:

Students are strongly encouraged to attend the PSO sessions on Mondays at 1:30 PM in room HAAS 257. PSOs will meet every week (unless otherwise announced), starting Monday January 22nd, 2007.

Prerequisites:

CS 354, CS 422, CS 543, or equivalent courses.

Credit:

03

Click here to access your grades on WebCT.

This course is one of the courses for the Qual I of the CS PhD program.

Policies:

Due Dates

All assignments are due on the dates and times specified. It is the student's responsibility to manage their time so that the assignments can be submitted before the deadline.

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 or written assignments. Specifically, looking at another student's code on his/her computer monitor is NOT allowed.
• Unless otherwise explicitly specified, all written assignments or code that is submitted is to be entirely the students 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. 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 your TA or 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 (http://www.cs.berkeley.edu/~aiken/moss.html) to check for copying among submitted assignments. Additionally, the instructor and TAs will be inspecting all submitted material to ensure honesty.

Class participation and discussions are strongly encouraged. However, please be considerate to others: avoid coming to class late, leaving early, talking to other students, etc. Please turn off your cell phone before the class starts.

Newsgroup:

Questions/comments should be posted on the newsgroup: news:purdue.class.cs536.
Make sure that you check the newsgroup and your e-mail frequently (at least once or twice per day). Do NOT post answers to the assignments, though general clarifications are OK. Complaints about the assignments or the class should NOT be posted to the newsgroup-- instead, they should be e-mailed to the instructor/TAs. The instructor and TAs can be reached by email at cs536-ta@cs.purdue.edu.

Useful Links:

• Networking/OS/DS Tools and Research Links

• A quick introduction to Statistics

• A quick introduction to C++ by Tom Anderson | A quick introduction to C by Steve Holmes