Google Cloud VMs

For the first time, we are providing you with Google Cloud VMs to do your coursework on! This will allow you to develop some networked applications that function over the real internet. We will send information to you about signing up for this credit, and will release a guide and scripts for using Google Cloud at the same time as the first assignment.

VM image for assignments

In past offerings of the course, we instead provided students with a base Ubuntu VM image for Virtualbox. However, it still may be useful in addition to the Google Cloud VMs, for example if you want to test your code locally or without internet access. The image and instructions on how to set it up can be found here.

Academic honesty policy (adapted from Prof. Panda's class)

The short version is: please don't cheat; it makes life difficult for everyone. Instead, use the extra credit or late days, or come talk to the instructor and/or the graders.

In more detail, you must cite any external sources that you make use of for an assignment. External sources include but are not limited to previously published articles, blog posts, ChatGPT output, Stack Overflow or similar sites, conversations with other people, assignment solutions from previous terms, verbatim phrases from the lecture notes, etc. You must provide citations for all work turned in for this class (similar to the acknowledgements section at the bottom of this page or the citations at the end of each lecture note). It is NOT OK to simply paste the assignment question into ChatGPT as a prompt and paste ChatGPT's output as your answer. This policy is not meant to discourage the use of external sources. Instead, it just codifies a standard academic practice.

However, you are responsible for ensuring that you understand any code or written material you turn in for the class. We reserve the right to ask you to explain part or all of your code for any assignment, and failure to adequately explain this will result in a loss in points. Finally, we will investigate any suspected academic misconduct and will report it to the department as required by GSAS policies. We reserve the right to use tools like MOSS to ensure that any code that is submitted is yours. If we find evidence of cheating, we will have to report it. If you're in doubt as to what constitutes cheating, come talk to us.

Office hours

• Anirudh Sivaraman (anirudh@cs.nyu.edu): 3 to 5 pm on Thursdays (Room 408, 60 Fifth Avenue), and by appointment
• Ulysses Butler (ulysses.butler@nyu.edu): 2:15 to 3:15 pm on Wednesday (Room 424, 60 Fifth Avenue), and by appointment
• Daniel Qian (daniel.qian@nyu.edu): 10:30 to 11:30 am on Mondays (Room 444, 60 Fifth Avenue), and by appointment
• Jeff Ma (grader, jm9527@nyu.edu): TBA

Tutoring Sessions

Tuesday: 1:00pm and 4:00pm (Room 446, 60 Fifth Avenue)
Thursday: 4:00pm and 7:00pm (Room 446, 60 Fifth Avenue)
Zoom Link: https://nyu.zoom.us/j/99341925454

Tentative course schedule

Acknowledgements

This class borrows ideas from several sources.

• Keith Winstein's suggestions on reference material for network surveillance and censorship
• Hari Balakrishnan's lecture notes from 6.02 (Fall 2012) at MIT for reliable transport, intradomain routing, ALOHA, and CSMA/CA
• Hari Balakrishnan's lecture notes from 6.829 at MIT for inter-domain routing
• Scott Shenker's slide deck from CS168 (Fall 2017) at UC Berkeley for Internet architecture