CS 456/656: Computer Networks (Fall 2026)


Instructor Mina Tahmasbi Arashloo mina.arashloo@uwaterloo.ca
Lectures Mondays & Wednesdays 4:00PM - 5:20PM
Office Hours Tuesdays, 5:00PM - 6:00PM Only for September - The new time for October onwards will be posted here
Teaching Nesa Abbasimoghaddamniasar nabbasim@uwaterloo.ca
Assistants Amaan Ahmed a477ahme@uwaterloo.ca
Kimiya Mohammadtaheri k4mohamm@uwaterloo.ca
Muhammad Sulaiman m4sulaim@uwaterloo.ca
Mohammad Zangooei mzangooe@uwaterloo.ca

Overview

Modern computer networks are complex distributed systems, with thousands of heterogeneous software and hardware components working together to deliver traffic from sources to destinations. They serve applications that demand much more than basic network connectivity, asking for certain levels of performance and reliability from the network.

In this course, we will discuss the fundamental concepts behind modern computer networks, starting from just a pipe between two endpoints, to a shared infrastructure, to scaling to the entire planet, and networks in the wild today.

Schedule

Following is a tentative schedule of lectures. Details are subject to change depending on how our in-class conversations go.

Dates Lectures Slides Assignments & Project
Introduction
Wed - Sep 9 What is a computer network, and why learn about it?
Part 1: Network as a pipe
Mon - Sep 14 Building networked applications
Wed - Sep 16 What metrics do networked applications care about?
Mon - Sep 21 The transport layer - Introduction
Wed - Sep 23 The transport layer - Dealing with bit errors Fri, Sep 25:
Paper choice due (CS 656)
Mon - Sep 28 The transport layer - Dealing with loss
Wed - Sep 30 The transport layer - Dealing with performance problems
Mon - Oct 5 The TCP protocol Mon, Oct 5:
Assignment 1 released
Wed - Oct 7 The QUIC protocol
Part 2: Network is a shared infrastructure
Mon - Oct 19 How do many endpoints share a network? Mon, Oct 19:
Baseline and extension proposal due (CS 656)
Wed - Oct 21 Finding paths - Part I
Mon - Oct 26 Finding paths - Part II Tue, Oct 27:
Assignment 1 due
Wed - Oct 28 Congestion control - Part I
Mon - Nov 2 Congestion control - Part II
Part 3: Scaling to the whole planet
Wed - Nov 4 Naming Fri, Nov 6:
Assignment 2 released
Mon - Nov 9 Managing scale through aggregation and hierarchies - Part I
Wed - Nov 11 Managing scale through aggregation and hierarchies - Part II Fri, Nov 13:
Project progress report due (CS 656)
Mon - Nov 16 Managing decentralized ownership (BGP) - Part I
Wed - Nov 18 Managing decentralized ownership (BGP) - Part II
Mon - Nov 23 Putting it all together
Part 4: Networks in the wild
Wed - Nov 25 Data center networks and AI infrastructure
Mon - Nov 30 Programmable networks
Wed - Dec 2 Dealing with failures at scale Thu, Dec 3:
Assignment 2 due
Mon - Dec 7 TBD Mon, Dec 7:
Project final report and demo due (CS 656). No extensions possible (per school policy)

Additional Resources

If you are curious to learn more, here is an additional list of resources that will be updated throughout the term.

Books: Papers, blog posts, and platforms: Research papers, blog posts, and platforms related to computer networks. References to these resources will be added to this section throughout the term.

Learning Platforms, Q&A Policy, and Attendance

LEARN: Course announcements, slides, quizzes, and assignments will be posted on LEARN.

Piazza: We will use Piazza for course-related discussions. Piazza is catered to getting you help from classmates, the TAs, and the instructor. Rather than emailing questions to the teaching staff, we encourage you to post your questions on Piazza. When asking questions, please adhere to the course Q&A policy.

Q&A: We strongly encourage you to ask questions about anything in the course – lecture material, quizzes, assignments, etc – and we'd love to have discussions about computer networks! That said, this is a large class. To ensure the teaching team can effectively answer questions, we have put the following policies in place: Attendance: Attendance is not mandatory but we strongly encourage you to attend the lectures. While the slides will be available online, they are mostly intended as teaching aids for the lectures as opposed to detailed lecture notes. As such, they do not necessarily include all the details of the topics discussed in this course.

Assessment

The final grade for the course will be based on the following components:

CS 456 CS 656
Quizzes 10% 10%
Programming Assignments 30% 15%
Project (CS 656) - 15%
Midterm 25% 25%
Final 35% 35%


Quizzes (10%): The goal of quizzes is to help you assess your understanding of the course material, and to help us as your instructors to pinpoint subjects that need extra discussion in the class. Here are the logistics: Programming Assignments - CS 456 (30%): There are two programming assignments, each counting as 15% of your final grade. Here are the logistics: Programming Assignments - CS 656 (15%): You complete one of the two programming assignments, counting as 15% of your final grade. It is your choice which one. In place of the other, you complete the project described below. For the logistics, please see the above text for "Programming Assignments - CS 456".

Project - CS 656 (15%): Students taking CS 656 work individually on a project based on a published research paper related to computer networks. You are expected to reproduce the results about one of the paper's claims using the authors' artifact, evaluate their solution under settings that are different from the paper's, and report and analyze the results. A list of papers with working artifacts will be posted on LEARN. If you would rather work on a paper that has no artifact, you can reimplement it from the paper's description instead of extending it, with the instructor's approval.

Your project grade comes from the final report and the demo. The first three deliverables are not graded on quality, but they are required. Missing each one takes 3% off your final grade for the course. The late policy below applies to these deliverables. The paper you choose and the extension you propose both have to be approved by the instructor. If you miss a deadline, you can still get approval later, at the cost of the penalty above. If you never get approval, your work is still marked, but you take on the risk that what you chose does not meet the requirements, and by then it will be too late to change it.

Late Policy: This applies to programming assignments and to project deliverables. It does not apply to quizzes, which cannot be retaken.

Midterm (25%) and Final (35%) Logistics:

Generative AI: You are accountable for the content and accuracy of all work you submit in this class, including any supported by generative AI.

Recommendations for how to cite generative AI in student work at the University of Waterloo may be found through the Library at this link. Please be aware that generative AI is known to falsify references to other work and may fabricate facts and inaccurately express ideas. GenAI generates content based on the input of other human authors and may therefore contain inaccuracies or reflect biases.

In addition, you should be aware that the legal/copyright status of generative AI inputs and outputs is unclear. Exercise caution when using large portions of content from AI sources, especially images. More information is available from the Copyright Advisory Committee at this link .

Territorial Acknowledgement

The University of Waterloo acknowledges that much of our work takes place on the traditional territory of the Neutral, Anishinaabeg and Haudenosaunee peoples. Our main campus is situated on the Haldimand Tract, the land granted to the Six Nations that includes six miles on each side of the Grand River. Our active work toward reconciliation takes place across our campuses through research, learning, teaching, and community building, and is centralized within the Office of Indigenous Relations.

Faculty of Math's Statement on Mental Health and Diversity

Mental Health Support: The Faculty of Math encourages students to seek out mental health support if needed.

On-campus Resources: Off-campus Resources: Diversity: It is our intent that students from all diverse backgrounds and perspectives be well served by this course, and that students’ learning needs be addressed both in and out of class. We recognize the immense value of the diversity in identities, perspectives, and contributions that students bring, and the benefit it has on our educational environment. Your suggestions are encouraged and appreciated. Please let us know ways to improve the effectiveness of the course for you personally or for other students or student groups. In particular:

Note for Students with Disabilities

AccessAbility Services, located in Needles Hall, Room 1401, collaborates with all academic departments to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum. If you require academic accommodations to lessen the impact of your disability, please register with AccessAbility Services at the beginning of each academic term.

University and Faculty of Math Policy on Academic Integrity

Academic Integrity: In order to maintain a culture of academic integrity, members of the University of Waterloo community are expected to promote honesty, trust, fairness, respect and responsibility. [Check the Office of Academic Integrity for more information.]

Grievance: A student who believes that a decision affecting some aspect of their university life has been unfair or unreasonable may have grounds for initiating a grievance. Please read Policy 70, Section 4. When in doubt, please be certain to contact the department’s administrative assistant who will provide further assistance.

Discipline: A student is expected to know what constitutes academic integrity to avoid committing an academic offence, and to take responsibility for their actions. [Check the Office of Academic Integrity.] A student who is unsure whether an action constitutes an offence, or who needs help in learning how to avoid offences (e.g., plagiarism, cheating) or about “rules” for group work/collaboration should seek guidance from the course instructor, academic advisor, or the undergraduate associate dean. For information on categories of offences and types of penalties, students should refer to Policy 71, Student Discipline. For typical penalties, check Guidelines for the Assessment of Penalties.

Avoiding Academic Offenses: Most students are unaware of the line between acceptable and unacceptable academic behaviour, especially when discussing assignments with classmates and using the work of other students. For information on commonly misunderstood academic offenses and how to avoid them, students should refer to the Office of Academic Integrity's site on Academic Misconduct and the Faculty of Mathematics' site on Academic Integrity.

Appeals: A decision made or penalty imposed under Policy 70, Student Petitions and Grievances (other than a petition) or Policy 71, Student Discipline may be appealed if there is a ground. A student who believes they have a ground for an appeal should refer to Policy 72 - Student Appeals.