|
CSE 123B, Spring 2003
Communications Software Lectures: TuTh 2:00-3:20pm Cntr 113
Teaching Assistants:
|
Mailing list
Please join the class mailing list by sending e-mail to majordomo@cs.ucsd.edu with subscribe cse123b your_email_address in the message body (where your_email_address is the email address you use for reading mail).
Computer Networks: A Systems Approach, 2nd Edition by Peterson and Davie, published by Morgan Kaufmann, 2000. (errata)
This course covers the design and architecture of network communications software with an emphasis on Internet-based communications technologies. The goal of the course is to provide an appreciation of the fundamental challenges in networking as well as the design approaches and implementations in use today. We will cover, at minimum, the following topics: Internetworking (IP), reliable communication, flow control, congestion control (TCP), intra-domain (RIP, OSPF) and inter-domain routing (BGP), Quality of Service, naming (DNS), Web service (HTTP), load balancing, and network security.
Homeworks are due by the end of class on the day specified. We will reduce homework grades by 20% for each day that they are late. You must hand in a hardcopy of your homework. We will post homework solutions 5 days after they are due.
To complete the projects in this course, you will need the ability to develop software programs using the C language. If you have not used C recently, you may want to refresh your knowledge using one of the many good books on the topic. In particular I recommend the classic, The C Programming Language, by Kernighan and Ritchie.
Project Assignment 1 is out!
Project Assignment 2 is out!
Your grade for the course will be based on your performance on the homeworks, midterm and final exams, and programming projects using the following weights:
Homeworks: 25%
Midterm: 20%
Final: 30%
Projects: 25%
Unless we state specifically otherwise, you are encouraged to collaborate on home and projects. After all, you will learn a lot from your fellow students. However, there can be a fine line between collaboration and cheating. Here is what we expect:
You spend at least 15 minutes on each and every problem, alone before discussing it with others.
You write up each and every solution as your own program or in your own words, and understand your solution fully.
Copying someone else's written homework or programs is cheating, as is copying them from other source (Web, previous years classes, etc.)
I understand that sometimes assignments can be frustrating and that you are all under a lot of pressure. Please come to see me, or one of the TA's if you're having trouble. I have great sympathy for people who try hard. I have no sympathy for cheating. If you're caught cheating, you can expect a serious response on my part (its not worth it).
The academic honesty guidelines outlined by Charles Elkan for CSE 130 apply to this course.