|Time:||Tuesday 11:45am-1:25pm, Thursday 2:50pm-4:30pm|
|Instructor Office Hours:||10am-11am Wednesdays |
Location: 613 ISEC
|Teaching Assistants:||Aditya Kulkarni, Gagan Shantha Kumar, Chi Zhang|
|TA Office Hours:||4-5pm Monday (362 WVH), |
7-8pm Wednesday (304 KA)
10am-11am Friday (362 WVH)
|Class Forum:||On Piazza|
The Internet has become an integral part of modern society. We are constantly connected by smart, mobile devices backed by large-scale, cloud-based infrastructure. Thus, it has become critically important for computer scientists to be familiar with the fundamentals of computer networking, and the design principals behind distributed systems that leverage the network. This course will focus on the architecture, algorithms, and protocols of the Internet, as well as key design principals of distributed systems. Topics include local area networking, routing, congestion control, the domain name system, network security, and applications such as distributed key-value stores, peer-to-peer and content distribution networks, and crypto-currencies. This course will be systems oriented, and students will work on hands-on projects to learn how to build and understand Internet applications.
The official prerequisites for this course are CS 3600 or CS 3650. This course is systems oriented, so I expect you to understand the basics of computer architecture and operating systems, and to have experience implementing non-trivial systems-type projects. Basic knowledge of the Unix command line is essential. You should know how to write code using emacs/vim, write a makefile, compile code using makefiles, check for running processes, kill runaway processes, and create compressed archives. Experience with a debugger is recommended.
The class forum is on Piazza. Why Piazza? Because they have a nice web interface, as well as iPhone and Android apps. Piazza is the best place to ask questions about projects, programming, debugging issues, exams, etc. To keep things organized, please tag all posts with the appropriate hashtags, e.g. #lecture1, #project3, etc. I will also use Piazza to broadcast announcements to the class. Bottom line: unless you have a private problem, post to Piazza before writing me/the TA an email.
|Tue. Jan. 9||Intro, History, Network Programming||Beej's Guide|
|Thu. Jan. 11||Network Architecture, Physical Layer||§1.1-1.6, 2.1-2.3||Proj. 1 Out|
|Tue. Jan. 16||Data Link Layer||§2.4-2.8|
|Thu. Jan. 18||Bridging and Switching||§3.1, 3.4||Proj. 1 Due, Hw. 1 Due|
|Tue. Jan. 23||Network Layer||§3.2||Proj. 2 Out|
|Thu. Jan. 25||Intra-domain Routing, Inter-domain Routing||§3.3, §4.1||Hw. 2 Due|
|Tue. Jan. 30||Inter-domain Routing, Transport Layer||§5.1-5.2||Proj. 2 Milestone Due|
|Thu. Feb. 1||Transport Layer||§6.1-6.4||Hw. 3 Due|
|Tue. Feb. 6||No Class: Proffnes goes to Beacon Hill
|Thu. Feb. 8||(Proffnes out with flu)||Hw. 4 Due, Proj. 2 Due, Proj. 3 Out,|
|Tue. Feb. 13||Transport Layer|
|Thu. Feb. 15||NAT, DNS||§9.3||Hw. 5 Due|
|Tue. Feb. 20||Midterm|
|Thu. Feb. 22||Distributed Systems Overview||†5; §9.1||Hw. 6 Due|
|Tue. Feb. 27||Web Architecture, P2P and BitTorrent||†10.1-10.3, 20.6|
|Thu. Mar. 1||P2P and BitTorrent||§9.4; †10.4-10.7||Proj. 3 Due, Proj. 4 Out|
|Tue. Mar. 6||No class (Spring Break)|
|Thu. Mar. 8||No class (Spring Break)|
|Tue. Mar. 13||Nor'easter|
|Thu. Mar. 15||P2P and BitTorrent,
Time and Logical Clocks,
Fault Tolerance and Consensus
|†14;||Hw. 7 Due|
|Tue. Mar. 20||Fault Tolerance and Consensus||Proj. 4 Due, Proj. 5 Out|
|Thu. Mar. 22||Fault Tolerance and Consensus||Hw. 8 Due|
|Tue. Mar. 27||Network Security||§8|
|Thu. Mar. 29||Transport Layer Security|
|Tue. Apr. 3||Transport Layer Security, Bitcoin||Hw. 9 Due|
|Thu. Apr. 5||Bitcoin|
|Tue. Apr. 10||Anonymous Communication|
|Thu. Apr. 12||Overlay Networks?||Hw. 10 Due|
|Tue. Apr. 17||Last Lecture (timely research topics in networking)||Proj. 5 Due|
|Apr. 20||Final Exam: 3:30-5:30pm, location TBD|
I do not require students to get textbooks; everything you need to know for this course can be found in the slides or online. However, a textbook may be useful if you are not totally comfortable with network fundamentals, or if you just want to have a handy reference book. Officially, the networking textbook for the course is:
Computer Networks: A Systems Approach, 5th Edition by Larry Peterson and Bruce Davie, Morgan Kaufmann.
This is denoted by the § symbol in the reading assignments.
There is also a supplement:
TCP/IP Sockets in C by Jeff Donahoo and Ken Calvert, Morgan Kaufmann.
Also recommended, for reference:
Computer Networking: A Top-Down Approach Featuring the Internet. by Jim Kurose and Keith Ross, Addison-Wesley.
We also have an official distributed systems book, although it is not as good as the Peterson/Davie networking textbook:
Distributed Systems: Concepts and Design, 5th Edition by George Coulouris, Jean Dollimore, Tim Kindberg, and Gordon Blair, Pearson.
This is denoted by the † symbol in the reading assignments.
Note that, should you choose to purchase these textbooks, older editions are totally fine.
There will be five programming projects throughout the semester. Programming projects are due at 11:59:59pm on the specified date. You will use a turn-in script to create a compressed archive of the project files, timestamp them, and submit them for grading. These projects require significant design and coding, hence students are recommended to start early!
|Assignment||Description||Due Date||Piazza Tag||% of Final Grade|
|Project 1||Socket Basics||Slides||January 19||#project1||4%|
|Project 2||Building Bridges||Slides||February 9||#project2||14%|
|Project 3||Reliable Transport||Slides||March 2||#project3||10%|
|Project 4||Web Crawling||March 20||#project4||8%|
|Project 5||Distributed Key-Value Store||April 18||#project5||14%|
You will use groups of two people (possibly three, if necessary) to do the projects. I will choose your groups; if you are having trouble with your group, please contact the professor. I will switch groups after project 3. All group members should be involved in all major design decisions, and groups should develop a programming plan that can be effectively parallelized. The course projects are hard, so you will want to distribute work between yourself and your teammate.
Most projects can be programmed in a language of your choice. The only universal requirement is that your projects must compile and run on an unmodified CCIS Linux machine. Notice the stress on unmodified: if you're relying on libraries or tools that are only available in your home directory, then we will not be able to run your code and you will fail the assignment. You are welcome to develop and test code on your home machines, but in the end everything needs to work on the CCIS Linux machines. If you have any questions about the use of particular languages or libraries, post them to Piazza.
This course will have ten homework assignments reviewing concepts in class. Homework assignments are to be done by each student individually. The homework assignments will be graded and handed back to you within a week. Links to the homeworks can be found in the above schedule.
Homework assignments are due at the beginning of lecture on the specified date. Late homework assignments will not be accepted, and slip days may not be used for homeworks (see the late policy, below).
There will be one midterm and one final. All exams will be closed book and closed notes, and computers are not allowed nor is any access to the Internet via any device. The exams will cover material from lectures, readings, and the projects. The final will be cumulative, so review everything!
I do not require students to attend class, and I won't be taking attendance. If you need to miss class for any reason, you don't need to tell me beforehand. However, that said, 5% of your final grade is based on your participation in class (i.e. asking questions) and on Piazza, so it behooves you to attend and speak up.
|Projects (5):||4%, 14%, 10%, 8%, 14%|
|Homeworks (10):||1.5% each|
|Midterm and Final:||15% each|
Each project will include a breakdown of how it will be graded. Some projects may include extra credit components that can boost your grade above the maximum score :)
To calculate final grades, I simply sum up the points obtained by each student (the points will sum up to some number x out of 100) and then use the following scale to determine the letter grade: [0-60] F, [60-62] D-, [63-66] D, [67-69] D+, [70-72] C-, [73-76] C, [77-79] C+, [80-82] B-, [83-86] B, [87-89] B+, [90-92] A-, [93-100] A. I do not curve the grades in any way. All fractions will be rounded up.
In this class, we will use the Coaches Challenge to handle requests for regrading. Each student is allotted two (2) challenges each semester. If you want a project or a test to be regraded, you must come to the professors office hours and make a formal challenge specifying (a) the problem or problems you want to be regraded, and (b) for each of these problems, why you think the problem was misgraded. If it turns out that there has been an error in grading, the grade will be corrected, and you get to keep your challenge. However, if the original grade was correct, then you permanently lose your challenge. Once your two challenges are exhausted, you will not be able to request regrades. You may not challenge the use of slip days, or any points lost due to lateness.
Note that, in the case of projects, all group members must have an available challenge in order to contest a grade. If the challenge is successful, then all group members get to keep their challenge. However, if the challenge is unsuccessful, then all group members permamently lose one challenge.
For programming projects, we will use flexible slip days. Each student is given four (4) slip days for the semester. You may use the slip days on any project during the semester in increments of one day. For example, you can hand in one project four days late, or one project two days late and two projects one day late. You do not need to ask permission before using slip days; simply turn in your assignment late and the grading scripts will automatically tabulate any slip days you have used.
Slip days will be deducted from each group member's remaining slip days. Keep this stipulation in mind: if one member of a group has zero slip days remaining, then that means the whole group has zero slip days remaining.
After you have used up your slip days, any project handed in late will be marked off using the following formula:
Original_Grade * (1 - ceiling(Seconds_Late / 86400) * 0.2) = Late_Grade
In other words, every day late is 20% off your grade. Being 1 second late is exactly equivalent to being 23 hours and 59 minutes late. Since you will be turning-in your code on the CCIS machines, their clocks are the benchmark time (so beware clock skew between your desktop and CCIS if you're thinking about turning-in work seconds before the deadline). My late policy is extremely generous, and therefor I will not be sympathic to excuses for lateness.
It's ok to ask your peers about the concepts, algorithms, or approaches needed to do the assignments. We encourage you to do so; both giving and taking advice will help you to learn. However, what you turn in must be your own, or for projects, your group's own work. Looking at or copying code or homework solutions from other people or the Web is strictly prohibited. In particular, looking at other solutions (e.g., from other groups or prior CS 3700 students) is a direct violation. Projects must be entirely the work of the students turning them in, i.e. you and your group members. If you have any questions about using a particular resource, ask the course staff or post a question to the class forum.
All students are subject to the Northeastern University's Academic Integrity Policy. Per CCIS policy, all cases of suspected plagiarism or other academic dishonesty must be referred to the Office of Student Conduct and Conflict Resolution (OSCCR). This may result is deferred suspension, suspension, or expulsion from the university.
If you have a disability-related need for reasonable academic accommodations in this course and have not yet met with a Disability Specialist, please visit www.northeastern.edu/drc and follow the outlined procedure to request services. If the Disability Resource Center has formally approved you for an academic accommodation in this class, please present the instructor with your "Professor Notification Letter" at your earliest convenience, so that we can address your specific needs as early as possible.
Title IX makes it clear that violence and harassment based on sex and gender are Civil Rights offenses subject to the same kinds of accountability and the same kinds of support applied to offenses against other protected categories such as race, national origin, etc. If you or someone you know has been harassed or assaulted, you can find the appropriate resources here.