CMSC 417-201 (Fall 2001)

CMSC 417-201 (Fall 2001)

Professor:	TAs:
Dr. Jeff Hollingsworth	Feng Peng	Seungjoon Lee
4161 AV Williams	AV Williams	AV Williams
(40) 5-2708
hollings@cs.umd.edu	pengfeng@cs.umd.edu	slee@cs.umd.edu
Office Hours:	Office Hours:	Office Hours:
Tu 10:45 - 12:00	M 11:00 - 1:00	Tu 3:30-5:30
W 10:00-11:00	Th 1:00 - 3:00	Th 3:30-5:30

Class URL: http://www.cs.umd.edu/~hollings/cs417/f01/

You are expected to check the class web page on a regular basis (at least weekly).

Catalog Description:

Computer networks and architectures. The OSI model including discussion and examples of various network layers. A general introduction to existing network protocols. Communication protocol specification, implementation, and measurement.

Objective:

An understanding of how computers communicate with each other through wires, fiber optics, and air.

Prerequisites: CMSC 311, CMSC 330, (CMSC 251 Strongly Suggested)

Topics Covered (in approximately the order we will cover them):

· Introduction to data communications

· Concurrency and Multi-threading

· Routing and congestion control algorithms

· Internetworking

· Transport protocols

· The physical layer

· Framing, error detection and correction

· Channel allocation

· Network security and administration

· Applications (SMTP, HTTP, NNTP)

Required Course Text:

Computer Networks 3^rd Edition, Tanenbaum, Prentice Hall 1996.

Pthreads Programming, Nichols, Buttlar, and Farrell, O’Reilly & Associates 1996.

Programming Projects:

The class will include a substantial programming project to provide hands on experience in writing, debugging, and measuring networking protocols. The projects will be done individually.

Grading:

Final Exam	30%
Midterms (two - each worth 12.5%)	25%
Homework	10%
Programming Assignments	35%

The instructor reserves the right to fail, regardless of overall numeric score, students who do not submit a good faith attempt to complete all programming assignments.

Re-grade policy. All requests to change grading of homework, programming projects, or exams must be submitted in writing (typed) within one week of when the assignment was made available for pickup. Requests must be specific and explain why you feel your answer deserves additional credit. A request to re-grade an assignment can result in the entire assignment being re-evaluated and as a result the score of any part of the assignment may be increased or lowered as appropriate.

Grades will be assigned using the traditional A-F scale and no +/- grades will be used.

Exams:

Midterm #1 – Tuesday, Oct 9 (in class)

Midterm #2 – Thursday, Nov 8 (in class)

Final - Monday, Dec 17 (10:30-12:30 pm)

Any schedule conflicts involving these dates must be reported to Dr. Hollingsworth by Thursday September 6th.

Academic Integrity:

All work that you submit in this course must be your own; unauthorized group efforts will be considered academic dishonesty. See the Undergraduate Catalog for definitions and sanctions. Academic dishonesty is a serious offense that may result in suspension or expulsion from the University. In addition to any other action taken, the grade “XF” denoting “failure due to academic dishonesty” will normally be recorded on the transcripts of students found responsible for acts of academic dishonesty. Sharing of code on programming assignments is a form of academic dishonesty.

Late Policy:

No late homework or programming assignments will be accepted. If you are unable to complete a programming assignment due to illness or family emergency, please see Dr. Hollingsworth as soon as possible to make special arrangements.