Computer Science 125
Computer Networks
Syllabus -- Fall 2007

Professor: Mike Erlinger
Office: Olin 1258b
Phone: x-18912
E-mail: mike@cs.hmc.edu

Lecture Times: Tuesday & Thursday, 1:15
Lab Times: Wednesday, 8:30-10:00 PM
Meeting Place: TG 206 & Beckman 105

Graders:: Class
Lab TAs:: Chris, Max
Secretary: Joyce Greene, Olin 1258, 621-8225

Course Description

Computer Networks covers the principles of computer networking especially protocols, analysis techniques for computer networking, and analysis of networking models. The course has a significant laboratory requirement. The course prerequisite is CS 105 Computer Systems.

Course Text

I did order texts through Huntley Bookstore, but as usual the numbers may not be correct. There is a link to Amazon off the course page. There are obviously other places to purchase books, e.g., bookpool.com, so do what is best for you.

Computer Networks, A System Approach, 3rd/4th Edition, by Larry Peterson & Bruce Davie Morgan Kaufmann, ISBN 1-55860-832-X. Buy the book from Amazon.com

Other Related Texts

UNIX Network Programming: The Sockets Networking API, 3rd Edition - by W. Richard Stevens, Bill Fenner, Andrew M. Rudoff Prentice Hall, ISBN: 0-13-141155-1-X. Buy the book from Amazon.com
TCP/IP Illustrated, Volume 1: The Protocols by W. Richard Stevens, Addison-Wesley, ISBN 0-201-63346-9 Buy the book from Amazon.com
Internetworking with TCP/IP Vol 1: Principles, Protocols, and Architecture, Fourth Edition. by Douglas Comer, Prentice Hall, ISBN 0-13-018380-6. Buy the book from Amazon.com

What Is This Course About?

There are many ways to approach the subject of computer networks. In early years, the course was centered on the material in Comer's books - an analysis of the individual protocols in the TCP/IP protocol stack. Besides protocol particulars, the current text, Peterson and Davie, considers computer networking from a systems perspective, investigating some of the systems questions related to the general concept of networking (protocols are still a significant undertaking). Peterson and Davie are still strongly oriented towards TCP/IP, but their presentation has a more global view of the interaction of various protocols. I plan on teaching the course at 3 levels: My lectures WILL ASSUME that you have read related material from one of the above books or other material (e.g., RFCs) and that you thus come to class with questions and some knowledge. I hope to start each lecture section with some questions and concepts that you should be thinking about.

Requirements and Grades

I have no idea as to the best approach to encourage you to submit material on time, except to use the calendar and laboratory to control your activities.

Also, I will use the class to grade some projects, hwks, and abstracts. Thus, you will also be responsible for critical evaluation of your classmates' work.

Make sure to read the late policy. There will be only ONE exam - a final. Based on past experience, the final is the primary grade determinate. The relative weighting scheme will be as follows:

Abstracts: and Hwks : 25%
Projects : 25%
Labs : 25%
Tests : 25%

Laboratory

The laboratory aspect of this course continues under development. The various Web pages will be updated as the semester progresses. They include not only course development work, but also network investigation.

Project

The project aspect of this course is focused on a broad view of networking and networking systems. There are obviously many other possible project areas, but I want to stick with the restrictions as specified on the page.

Collaboration Policy

Collaboration is encouraged. This means that you may discuss approaches to solving problems with anyone in the class, including myself and the graders. However, copying solutions from any source (person or book) is disallowed. All students are expected to conduct themselves in accordance with the Harvey Mudd Honor Code. If you have any questions about what is appropriate or inappropriate collaboration, please talk to Me.

Web Page

Obviously you should check the Web page periodically. My plan is to keep it updatedly weekly, i.e., by Friday night the next week should be complete and subsequent weeks partially completed. Things way out may move, but they do show you direction. NOTE: I usually updated the Calendar first, so it should be your primary source.

List of Topics

Mike Erlinger

Last Modified Thursday, 17-Jan-2008 13:52:28 PST