Instructor: Carl Hauser, EME 53, 5-6470, mailto:hauser@eecs.wsu.edu
Office Hours: T-Th 11:00-12:00 or make an appointment by e-mail
Teaching Assistant: Jin Ding, Sloan 319, 5-8246, mailto:jding1@eecs.wsu.edu
TA's Office Hours: Monday, 3:30-5:30 or make an appointment by e-mail
Class Meeting Time: MWF 10:10-11:00
Meeting Location: Sloan 9 -- note new location!
Class Web Page: http://www.eecs.wsu.edu/~hauser/CS555
Lab space: Computers in the SNIF Lab, ETRL 301 are available for your
use in programming assignments and projects. Your EECS computer account name is
required in order to set up the lab computers for your access. If you don't
have an EECS unix account you will need to get one and pass it along to the
class TA so she can set it up in the lab. (Information
about EECS accounts)
Computer Networks: A Systems Approach, 2nd Edition, by Larry L. Peterson and Bruce S. Davie. There are several errors in the text. Please visit the errata page and mark corrections in your copy.
Internet RFCs:
An undergraduate course in computer networking. If you have not taken such a course you must be familiar with fundamental networking concepts outlined at the end of this handout.
Protocol design and implementation; proof of protocol properties; network router and switch architectures, routing and switching protocols.
You are required to attend all the lectures. If you miss any of them it is your responsibility to find out what went on during the class and to collect any handouts. However, this will not, in general, be an adequate substitute for having been there. In-class participation will be vital to your success in this course. The class will be highly interactive with many opportunities for participation.
Quizzes and tests are to be your own work. Collaboration and copying will be considered cheating and subject to sanction according to WSU's Academic Integrity Standards ( http://www.studentaffairs.wsu.edu/hb_standards.asp#ac160). The minimum penalty for academic dishonesty is an F in the course. Other possible sanctions include expulsion from Graduate School, revocation of assistantships, etc.
Collaborative work on homework and projects may be allowed and that will be made clear as part of the assignment. My goal in allowing or encouraging collaboration is to enhance your individual learning in the class. Thus, cooperation and collaboration, when permitted, increase your individual responsibility for learning.
At the first class meeting you will receive a folder. After completing the name and contact info form and completing the survey it contains, return it to the file box at the end of class. The folders will be available at each class meeting and you will use them to turn in your work and to receive back your graded work. The folders will accumulate your work over the course of the term. Leave your work in the folder. Prior to the mid-term and final exams, you may take the folder and contents for 1 week for review, but the folders are to be turned in at the beginning of the exam period.
Tests (midterm and final): 30%, Quizzes: 15%, Projects: 30%, Class participation: 10%, Homework: 15%
Tests: There will be three tests including a final.
Homework: Homework will consist of problems based on the lectures and textbook. Some homework problems will require programming. There will be 5-7 home sets during the semester.
Quizzes: There will be 3 quizzes. Quizzes will be announced at the preceding class meeting. It will not be possible to make up a missed quiz, but I will drop up to one quiz grade in computing your final class grade.
Projects: There will be 3 projects. Projects require substantially more programming than a homework problem. You may use the computers in the SNIF lab, ETRL 301, for the projects and programming homework. Any necessary software will be installed on these machines, and accounts for class members established on them by August 31.
Project 1: October 1
Test 1: October 8
Project 2: November 2
Test 2: November 16
Project 3: December 10
Final exam: week of Dec. 17, as scheduled
CptS 455 is a prerequisite for this class. At a minimum, you should know the
following material from the textbook: Chapter 1, Sections 2.1, 2.2, 2.3, 3.1,
and 4.1. In addition you must be able to write single-threaded programs that
use the socket programming model for TCP and UDP communication.