UNIVERSITY OF DAYTON

CPS 472/572: Computer Networking

Winter Semester 2003 3 credits

Meets: T,Th 12:00pm - 1:15pm

214 Miriam Hall

Professor: Dr. Jennifer Seitzer Office: 144 Anderson Hall Email: seitzer@udayton.edu Course Web Page: http://homepages.udayton.edu/~seitzer/cps472 Phone: (937) 229-2197 *Office Hours: Monday: 1:30pm – 3:30pm; Tuesday: 10:30 - 11:30am, 3pm-4:00pm;Thursday: 10:30am - 11:30am, 3pm-4:00pm; Friday: 11:30am - 1:30pm, or by appointment.

Mailing Address: Dr. Jennifer Seitzer, Assistant Professor Computer Science Department University of Dayton 300 College Park Dayton, OH 45469-2160

*These are tentative and will possibly change due to departmental meetings and other college events as they arise.
Prerequisites:

CPS 470/570 Data Communications.

Catalog Description:

Concepts and goals of computer networks (local-area and long-hauls). Network protocols, analysis, design management. OSI layers, gateways. Network topologies and case studies.

Motivation:

Our study of computer networking will center on the Internet. We will study the underlying hardware and software, the services it offers, and the applications it runs. Some believe that an "internet" is a nominalization; it is an entity that exists by name only. Universal service, the prime goal of an internetwork, exists by deftly combining software and hardware into a virtual network system, where the communication system is an abstraction. The Internet is characterized by its ability to provide universal end-to-end service worldwide.

In this course, we study what is required to make the illusion of an internetwork a reality. We review the functionality of routers, the TCP/IP reference model and its protocols. Interestingly, we will study the TCP/IP model from the top down. We will start by studying the application level. This is the level of current growth in networking. Many recent innovations such as video and audio streaming take place at the application level. We will study the underlying paradigm of client-server interaction, and how transport level protocols realize this. We will learn how to code clients and servers as well as spend some time looking at E-mail, FTP, and World Wide Web clients and servers. We will perform socket programming in both C++ and Java, and then discuss some of the underlying activities at the network and data link levels. We will culminate our pursuits by exploring some advanced topics of networking including network simulation, multimedia networking, network security, and network management.

Objectives:

· To acquire a general knowledge of networking parlance. This includes the plethora of of terms and acronyms that permeate the field.

· To have the following programming skills:

· to program clients and (iterative and concurrent) servers that work together in C++

· to write a web server and client in Java

· to simulate packet reassembly from fragments and fragments of fragments

· to successfully use and program the networking simulation tool OPNET

· To understand the intricacies and complexity of translating location identifiers including DNS names, IP addresses, and physical addresses

· To compare and contrast the underlying transmission techniques of multimedia networking with data networking

Subject Matter (Tentative list and schedule of coverage):

Week	Topics	Readings
1 – 1/7/2003, 1/9/2003	Introduction; Application Layer	Chapter 1 ; Sections 2.1
2 -- 1/14/2003, 1/16/2003	HTTP, Email, FTP	Sections 2.2, 2.3, 2.4
3 -- 1/21/2003	Domain Name System	Sections 2.5
No Thursday, 1/23/03 class Monday Schedule followed at UD
4 -- 1/28/2003, 1/30/2003	Socket Programming	Sections 2.6-2.8:
Last Day to Withdraw with no record Monday, 1/27/2003
5 – 2/4/2003, 2/6/2003	Transport Level - Reliability	Sections 3.1-3.5
6 -- 2/11/2003, 2/13/2003	Transport Level - Congestion Control	Sections 3.5-3.8
7 -- 2/18/2003, 2/20/2003	Routing	Chapter 4
Midterm #1 -- Tuesday, February 18, 2003
8 -- 2/25/2003, 2/27/2003	Multicast Routing	Chapter 4
9 – 3/4/2003, 3/6/2003	Multimedia Networking - Compression	Sections 6.1-6.5
10 -- 3/11/2003, 3/13/2003	Multimedia Networking - Real Time Protocol (RTP)	Sections 6.6 - 6.10
SPRING BREAK No class 3/18/2003 and 3/20/2003		A good novel J
11--- 3/25/2003 – 3/27/2003	Network Simulation	Notes
Last Day to Withdraw with a record of W Wed., 3/26/2003
12 – 4/1/2003, 4/3/2003	Network Security	Chapter 7
Midterm #2 -- Tuesday, April 1, 2003
13 --4/8/2003, 4/10/2003	Network Management	Chapter 8
14--4/15/2003, 4/17/2003	Wireless and Emergent Networks	Article to be distributed
15 -- 4/23/2003, 4/25/2003	IP Convergence: Voice over IP; Graduate Student Presentations	Handouts
Final Exam: Monday, April 28, 2003	Final Examination-- 12:00-1:15pm MH 214	Comprehensive

Grading Undergraduate Students (Approximate distribution of credit):

Midterm #1 – Tues, February 18, 2003 15 %

Midterm #2 -- Tues, April 1, 2003 15 %

Final Exam – Mon.,April 28, 2003 25 %

Homework and Programming Assignments 38-40 %

In-Class Grade 5-7 %

(includes class participation, pop quizzes, and in-class exercises)
note: these cannot be made up

Grading Graduate Students (Approximate distribution of credit):

Midterm #1 – Tues, February 18, 2003 12 %

Midterm #2 -- Tues, April 1, 2003 12%

Final Exam – Mon., April 28, 2003 25 %

Homework and Programming Assignments 29-31 %

Graduate Assignment 15 %

In-Class Grade 5-7 %

(includes class participation, pop quizzes, and in-class exercises)
note: these cannot be made up

Required Text: Computer Networking A Top-Down Approach Featuring the Internet
By, James F. Kurose and Keith W. Ross ISBN: 0-201-47711-4

Other Helpful Text : Computer Networks Third Edition, By, Andrew Tanenbaum;

ISBN 0-13-349945-6.

Graduate Student Project

Graduate students are required to produce a final project for the course. This entails choosing a topic of computer networking not presented in class (or extending what was presented in class) and doing the following:

1. read at least two articles on the topic

2. write a short term paper (10 pages) in your own words describing the topic

3. write a software program or hardware project (such as a simulation) demonstrating some aspect of the topic

4. present your paper in a 10-15 minute Powerpoint presentation to the class

5. demonstrate your simulation or demonstration object to the class in a 5-10 minute demo

6. Submit term paper, Powerpoint slides, simulation/demonstration object

Policy on Makeups, Missed and Late Work:

1. Late Work: Work will usually be accepted late and recorded as such. Work is due at the beginning of class. A 10% penalty is applied for every class day the assignment is late. No work will be accepted after solutions have been given out, or after the assignment has been graded and returned.

2. Make-ups: Tests are expected to be taken on the test date. Any make-ups must be established with me ahead of time. There are no make-ups for in-class pop quizzes, exercises, or participation. To get these points, you must come to class.

3. Attendance: Students are expected to come to class. If a class must be missed, however, students are responsible for all material, assignments, and announcements made during class. For this reason, you are encouraged to find a colleague with whom you can communicate to share such important information.

Programming Conduct Rules:

¨ Programming assignments are dispensed to reinforce concepts presented in class. Good programming skills comprise a fundamental component of being a computer scientist. Your code should be generated by you, by hand; it should not be automatically generated by a code generator or wizard (such as that provided by Microsoft Visual 6.0). Assignments in this class are short enough to write by yourself. As I am trying to endow in you the fundamental techniques and algorithms of computer networking, no graphical user interface (GUI) is necessary or required to be written. With the network simulation tool, the GUI will be provided.

¨ Students may share ideas in composing programs, but may not code them together. There is no sharing of code, only ideas. Any collaborative work should be acknowledged in the comments. Plagiarizing code will result in a zero for the program.

Email Communication and Class Computer Accounts:

· Email: I prefer to conduct communication through email. My email address (as indicated above) is seitzer@.udayton.edu. Please feel free to write me anytime. I try to check my email many times through the day. If you do not have an email account, I ask that you get one. Student email accounts can be acquired from the Systems Administrator. For information, you may call (937)229-3858.

· Lab Work and Programs: Programming assignments may be written using the platform of your choice in any lab of your choice so long as the system on which you are working has an operational C, C++, or Java compiler. Network simulation assignments must be done in the computer science labs housed in Anderson Hall 131 and 133 where the OPNET Modeler software is loaded.

Course Web Page:

· The course has its own web page that can be found at URL http://homepages.udayton.edu/~seitzer/cps472. You are responsible for consulting this page regularly. Most handouts, class notes, and other communications will be posted on this page.

· Additionally, the textbook has a web page. Class Slides, helpful hints, and ideas can be procured at the URL http://www.awl.com/kurose-ross

Class Email List:

· Along with web page postings, I regularly send my classes email via the respective Class Email List. To get on the email list, send me an empty email message to
seitzer@udayton.edu with the following subject: 472 Class Email List if you are enrolled in CPS 472. Send a message with the subject 572 Class Email List if you are enrolled in CPS 572. This email should be sent during the first week of school.