Course Information and Policies
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.
|Professors:||Alan Mislove and Alden Jackson|
|Location and Time:||
Alan: Tuesdays/Fridays 9:50-11:30am, West Village G 108
Alden: Tuesdays/Fridays 1:35-3:15pm, Shillman Hall 305
Alden: Tuesdays/Fridays 3:25-5:05pm, International Village 019
|Professor Office Hours:||
Alan: Tuesdays 1:00-2:00pm via Zoom
|Teaching Assistants:||Aneesh Baskaran, Simon Bass, Ujas Bhadani, Miraj Desai, Rohan Devasthale, Divya Jangid, Wing Kwok, Deepak Nadipelly, Nithin Saripalli, Prajwal Sreenath, Karan Virupakshar|
|TA Office Hours:||Schedule is available as a Google Calendar. All office hours are held virtually via the Khoury Office Hours app.|
|Class Forum:||On Piazza|
Which Section of 3700 Is This?
All of them. There are three sections of CS 3700 in Spring 2022. All three sections will be covering the same material, following the same schedule (roughly), using the same homeworks and projects, and sharing the same TAs.
In accordance with Northeastern policies for Spring 2022, all three sections of CS 3700 will be taught in person. Students are expected to attend classes in person, unless Northeastern changes their policies due to evolving situation with the COVID-19 Delta variant.
All homeworks and projects will be available online, can be completed entirely online, and will be turned in online. More details on homeworks and projects is available below.
Parts of this course will be recorded for educational purposes. These recordings will be made available only to students enrolled in the course, the instructors, and teaching assistants assigned to the course.
Only students who have arranged an accommodation with the Disability Resource Center may use mechanical or electronic transcribing, recording, or communication devices in the classroom. Students with disabilities who believe they may need such an accommodation may contact the Disabilities Resource Center.
COVID-19 Safety and Accommodations
We expect all students to do their utmost to protect the safety of their peers and instructors during these unprecedented times. This includes abiding by all safety guidelines as stated in Northeastern’s COVID-19 policy site.
We will be enforcing mask requirements for all students attending class in person. We will all be wearing masks. Students who arrive to class without a mask will be told to leave until they can procure a mask.
We realize that the ongoing pandemic makes it difficult to predict what will happen in the future, or how events may impact students' ability to attend lectures and/or turn in assignments on time. Recorded lectures will be posted online so that students who cannot attend live lectures may review them later. Students facing hardship that prevent them from completing an assignment on time should contact their professor and explain the situation. All reasonable requests will be honored.
The official prerequisite+ for this course is CS 2510. That said, this course is systems oriented, so we 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, etc. To keep things organized, please tag all posts with the appropriate hashtags, e.g. #lecture1, #project3, etc. We will also use Piazza to broadcast announcements to the class. Bottom line: unless you have a private problem, post to Piazza before writing an email to the TAs or instructors.
We 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.
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.
Note that, should you choose to purchase these textbooks, older editions are totally fine.
There will be six 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 we strongly recommend that students start early!
|Project||Description||Group?||Due Date||% of Final Grade|
|Project 1||Socket Basics||No||Jan. 27||5|
|Project 2||Simple Bridge||Yes||Feb. 3/Feb. 10/Feb. 17||10|
|Project 3||Build a Router||Yes||Mar. 3/Mar. 10||10|
|Project 4||Reliable Transport||Yes||Mar. 24||12.5|
|Project 5||Web Crawling||Yes||Apr. 7||10|
|Project 6||Distributed Key-Value Store||Yes||Apr. 21/May 1||12.5|
Five of the projects (2–6) will be completed in groups. You will form groups of two people (possibly three, if necessary and only with instructor permission) to complete these projects. We will allow you to form your own groups. If you are having trouble finding a partner, post a notice to Piazza.
As you are free to choose your partner(s), we will not be sympathetic to complaints at the end of the semester about how your group-mates did not do any work. If you are having problems with your teammate(s), tell us about it sooner rather than later.
You may switch groups between programming projects. 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(s).
This course will have seven homework assignments reviewing concepts from lecture. Homework assignments are due at 11:59:59pm on the specified date in the schedule. All homeworks are due on Fridays. Links to the homeworks can be found in the schedule. Homeworks will be submitted via Gradescope; the easiest way to access the course Gradescope is via the course’s Canvas page.
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 Khoury College Linux machine. Notice the stress on unmodified: if you’re relying on libraries or tools that are only available in your environment, 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 Khoury College Linux machines. If you have any questions about the use of particular languages or libraries, post them to Piazza.
Participation and Attendance
We do not require students to attend class, and we won’t be taking attendance. If you need to miss class for any reason, you don’t need to tell us beforehand. That said, we like teaching and interacting with students, so please attend class and speak up. We welcome questions and discussion! Note that your participation grade will be based not only on your participation in class, but also on the Piazza forum; please feel free to engage with other students there (but do not simply give out answers to the questions, of course).
We will have two midterms in this class. Both of the exams will be written exams (no coding), and will be take-home. The exams will be “open slides” and “open notes”, but no other assistance will be allowed (no other resources [internet or otherwise], no discussions with classmates, etc). The exams will be handed out in class on the Tuesday of the week, and will be due uploaded to Gradescope by the specified deadline. Students will be given a maximum amount of time they can spend on the exams, and they can choose when and where to take the exam. No slip days can be used on the exams. Any exams submitted after 11:59:59pm on the specified date will be given a 0.
Because the exams are take-home and flexible, any violations of academic integrity during the exams will be handled severely. Students found to have cheated on the exams will be given an immediate 0, and their overall grade in the course will be an F. In other words, students must complete both exams without any academic integrity violations in order to successfully pass the class. Students will be required to sign an honor pledge on their exam attesting to the fact that they did not use any unauthorized aid.
The exam schedule is:
|Exam||Covers||Handed out||Due Date||% of Final Grade|
|Midterm 1||All material before Feb. 18||Feb. 22||Feb. 25||10|
|Midterm 2||All material before Apr. 8||Apr. 12||Apr. 15||10|
|Projects (6)||5%, 10%, 10%, 12.5%, 10%, 12.5%|
|Homeworks (4)||3.75% 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, we 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:
|Numeric Grade||Letter Grade|
We do not curve the grades in any way. All fractions will be rounded up.
Requests for Regrading
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 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 permanently lose one challenge.
Any requests for grade changes must be made within seven days of when the work was returned.
For programming projects, we will use flexible slip days. Each student is given six (6) slip days for the semester. You may use the slip days on any project or homework during the semester in increments of one day. For example, you can hand in one project six days late, or three projects two days late each. 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 Khoury College machines, their clocks are the benchmark time (so beware clock skew between your desktop and Khoury College if you’re thinking about turning-in work seconds before the deadline). My late policy is extremely generous, and therefor we will not be sympathetic 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 students who previously took the course) 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 Khoury College 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.
Accommodations for Students with Disabilities
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 the Northeastern 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.