Instructor: Jinkun Geng (jinkun.geng@nyu.edu)
TAs: Hrithik Samala (hs5828@nyu.edu) and Qiutong Men (grader, qm2017@nyu.edu)
This course will introduce students to computer networks, using today's
Internet as an example. Topics covered include socket programming, routing,
forwarding, reliable transmission, congestion control, and medium access
control. The course will involve a good deal of programming in Python.
Familiarity with programming, algorithms, and basic probability is expected.
Prerequisites: Computer Systems Organization (CSCI-UA 201), Basic Algorithms
(CSCI-UA.0310), and Discrete Mathematics (Math UA 120); or permission of the
department.
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.
| Week | Monday | Wednesday | Assignment |
|---|---|---|---|
| Week 1 | Jan 19 MLK Day |
Jan 21 Class overview |
|
| Week 2 | Jan 26 Packet Switching and Network Modeling |
Jan 28 DNS |
Assignment 1 Published on Gradescope |
| Week 3 | Feb 2 TCP and UDP |
Feb 4 TCP and UDP (Cont.) |
|
| Week 4 | Feb 9 TCP Congestion Control |
Feb 11 Intra-Domain Routing |
Assignment 2 Published on Gradescope, online instructions here |
| Week 5 | Feb 17 Inter-Domain Routing |
Feb 18 Packet Forwarding |
|
| Week 6 | Feb 23 Packet Queuing and Scheduling |
Feb 25 NAT and IPv6 |
|
| Week 7 (Midterm) | Mar 2 Midterm Review |
Mar 4 Midterm Exam |
|
| Week 8 | Mar 2 Data Link Layer I |
Mar 4 Data Link Layer II |