Announcements
-
Prof. Ware is out of town September 6th - September 13th at a conference, Prof. Kevin Webb will lead lecture and lab. No OH on Monday or Thursday.
-
Most announcements will be on EdSTEM.
Class Info
Class: Monday/Wednesday, 10:30 AM - 11:45 AM, Science Center L26
Professor: Dr. Ranysha Ware
Office: Martin 338
Office hours: Monday 3:00 PM - 4:30 PM (Martin 328), Thursday 10:00 AM - 11:00 AM (Martin 338)
Q&A Forum: EdSTEM
GitHub: Swarthmore GitHub Enterprise
Grades: Grades will be posted on Moodle and Gradescope
Textbook: Accessible via TAP+ on Moodle
Weekly Lab Sessions: Martin 113
Section A |
Tuesday 1:05 - 2:35 |
Welcome to CS 43. This course will introduce fundamental ideas in computer networks. The structure of this course may be different from many other CS courses at Swarthmore. We’ll be using a teaching model called peer instruction, which places a strong emphasis on classroom discussion and student interaction.
The course is composed of the following:
-
Readings: The readings serve as a first exposure to new topics, where students learn the basics of the material.
-
Class meetings: The classroom material will cover the difficult concepts and facilitate student discussions.
-
Labs: Several lab programming assignments (mostly in C) explore various aspects of network applications.
-
Quizzes: Biweekly quizzes (closed-book) will cover the material from the previous 2 weeks.
-
Final exam: The final exam (closed-book) will cover the material from entire course and labs.
Materials
iClicker (Required)
iClickers: This course will use iClickers to facilitate feedback and discussion during class. For many upper level courses including CS 43, clicker will commonly be used in class. Clickers may be purchased at the college bookstore or online. Please register your device as soon as you get it. You must register to get points for class participation. We will begin using clickers for credit at the start of week 2!
Textbook (Required)
Computer Networking: A Top-Down Approach by Kurose and Ross. ISBN-13: 978-9356061316 We will be using the Eigth Edition. The electronic version of the textbook is available via the course Moodle page.
Other Resources
Links that are related to the course may be posted here.
Learning Goals & Outcomes
By the end of the course, we hope that you will have developed the skills to:
-
Refine C programming skills in the context of systems design, development, and debugging.
-
Classify network functionality into the appropriate abstraction layer.
-
Characterize the behavior of popular network applications and protocols (HTTP, SMTP, DNS, etc.).
-
Construct distributed applications using various concurrency models.
-
Design and analyze network application protocols.
-
Identify the role of transport protocols in providing reliability and high performance.
-
Implement routing algorithms and analyze routing protocols.
-
Compare and contrast switching and forwarding platforms.
-
Test and debug networked applications.
Lab Schedule
Please familiarize yourself with the course’s partnership expectations before starting the lab. See the lab policy for details.
All labs are due 11:59 pm ET on the due dates shown. Labs are due on Monday evenings.
Weeks | Lab Topic | Out | Due |
---|---|---|---|
1 |
Tue Sep 2 |
Mon Sep 8 |
|
2-3 |
Tue Sep 9 |
Mon Sep 22 |
|
4-5 |
Lab 2: A Concurrent Web Server |
Tue Sep 23 |
Mon Oct 6 |
6-7 |
Lab 3: Talking to DNS |
Tue Oct 7 |
Mon Oct 27 |
8-10 |
Lab 4: Designing a Jukebox Protocol |
Tue Oct 28 |
Mon Nov 17 |
11-12 |
Lab 5: Reliable Transport |
Tue Nov 18 |
Mon Nov 24 |
Quiz Schedule
Quizzes are closed book and will be about 20 minutes covering the content from the previous 2 weeks. See the quiz policy for details.
Week | Quiz Topic | Date |
---|---|---|
3 |
Quiz 1: Covers topics from weeks 1-2 |
Wed Sep 17 |
5 |
Quiz 2: Covers topics from weeks 3-4 |
Wed Oct 1 |
7 |
Quiz 3: Covers topics from weeks 5-6 |
Wed Oct 22 |
9 |
Quiz 4: Covers topics from weeks 7-8 |
Wed Nov 5 |
11 |
Quiz 5: Covers topics from weeks 9-10 |
Wed Nov 19 |
13 |
Quiz 6: Covers topics from weeks 11-12 |
Wed Dec 3 |
Class Schedule
This is a tentative schedule; it may change as we go. You should read the assigned sections before class to prepare for class discussion points. All readings refer to the Kurose and Ross textbook unless otherwise indicated (e.g., there’s a link to some other source).
To access the recordings, you’ll need to be signed in to your @swarthmore.edu Google account.
Week | Date | Topic & In-class Worksheets | Readings & Videos | Labs & Quizzes |
---|---|---|---|---|
1 |
Sep 1 |
Labor Day |
||
Sep 2 |
Couse Introduction [slides] Please complete Assignment 0 before class. |
Optional: K&R: 1.1 |
Lab 0 (due Sep 8) |
|
Sep 3 |
Protocols, Layering and The Application Layer: HTTP [post-class slides] [worksheet] |
1. K&R: 1.1, 1.5 |
||
2 |
Sep 8 |
The Application Layer: HTTP Sockets |
1. K&R 2.1.1, 2.1.2, 2.1.5 2. K&R 2.2.1, 2.2.2, 2.2.3 3. Try Telnet! |
|
Sep 9 |
Lab 1 (due Sep 22) |
|||
Sep 10 |
The Application Layer: Socket Programming: Concurrency & Non-blocking I/O |
|||
3 |
Sep 15 |
The Application Layer: HTTP and Performance Cntd. |
K&R: 2.1 and 2.2 |
|
Sep 16 |
Lab 1 Cntd. |
|||
Sep 17 |
Quiz 1: Covering Week 1-2 topics The Application Layer: TCP Sockets |
2. Concurrent Web Servers 3. Addressing Sockets 4. Putting it all together: TCP Web Servers] |
Quiz 1 |
|
4 |
Sep 22 |
The Application Layer: Distributed Systems and The DNS Protocol |
Optional Reading: 1. Your Coffee Shop Does not use two-phase commit |
|
Sep 23 |
Lab 2 (due Oct 6) |
|||
Sep 24 |
The Application Layer: Domain Name System |
|||
5 |
Sep 29 |
DNS and Email |
1. K&R: 2.4 |
|
Sep 30 |
Lab 2 Ctnd. |
|||
Oct 01 |
Quiz 2: Covering Week 3-4 topics |
1. K&R 2.5 2. K&R 2.6 |
Quiz 2 |
|
6 |
Oct 6 |
P2P and BitTorrent |
K&R 2.3, 2.5, 2.6 |
|
Oct 7 |
Lab 3 (due Oct 26) |
|||
Oct 8 |
BitTorrent Cntd. |
|||
Fall Break |
||||
7 |
Oct 20 |
DHTs and CDNs |
K&R 2.6 |
|
Oct 21 |
Lab 3 Cntd. |
|||
Oct 22 |
Quiz 3: Covering Week 5-6 The Transport Layer: Transport Services and UDP |
1. K&R 3.1, 3.2, 3.3 |
Quiz 3 |
|
8 |
Oct 27 |
The Transport Layer: Reliable Transport and TCP |
K&R 3.5.1 to 3.5.4 |
|
Oct 28 |
Lab 4 (due Oct 6) |
|||
Oct 29 |
The Transport Layer: Flow and Congestion Control |
K&R 3.4.3, 3.4.4, 3.6 |
||
9 |
Nov 3 |
The Transport Layer Contd. |
Same readings as above. |
Quiz 4 |
Nov 4 |
Lab 4 Ctnd. |
|||
Nov 5 |
Quiz 4: Covering Week 7-8 topics The Network Layer: Introduction |
K&R 4.1, 4.2.1, 4.3.1 |
Quiz 4 |
|
10 |
Nov 10 |
The Network Layer Contd. |
Same readings as above |
|
Nov 11 |
Lab 4 Ctnd. |
|||
Nov 12 |
The Network Layer: IP Glue: DHCP, NATs, IPv6, ICMP |
K&R 4.3.2, 4.3.3, 4.3.4, 5.6 |
||
11 |
Nov 17 |
The Network Layer: IP Glue: DHCP, NATs, IPv6, ICMP |
||
Nov 18 |
Lab 5 (due Nov 24) |
|||
Nov 19 |
Quiz 5: Covering topics from Week 9-10 The Network Layer: Intradomain Routing, and Traffic Management |
K&R 5.1, 5.2, 5.3 |
Quiz 5 |
|
12 |
Nov 24 |
The Network Layer: Intradomain Routing Cntd. and IPv6, NATs, ICMP |
K&R 4.3.3, 4.3.4, 5.6 |
|
Nov 25 |
Lab 5 Cntd. |
|||
Nov 26 |
The Network Layer: BGP: Border Gateway Protocol and Policies |
K&R 5.4 |
||
13 |
Dec 1 |
Link Layer |
K&R 6.1 - 6.4 |
|
Dec 2 |
TBD |
|||
Dec 3 |
Quiz 6: Covering topics from Week 11-12 TBD |
Quiz 6 |
||
14 |
Dec 8 |
TBD |
||
Dec 9 |
Thursday Schedule |
|||
Dec 10 |
Friday Schedule |
|||
Final Exam: TBD |
Assessment Policies
Class Policy and Participation
Your class participation grade will be based on the following:
-
Pre-class reading quizzes: (5%) This course will have readings and pre-recorded class videos you are required to review before class. A short (open book) quiz in the format of a Google Form (link in the class schedule) will be due at the beginning of class before each lecture. These quizzes are graded for correctness.
-
In-class worksheets and poll: (5%) In class we will break into smaller discussion groups and go over 10-15 minute discussion questions that take a deeper look at the class material. You are expected to actively participate in your smaller discussion groups. We will also complete polls throughout lecture. Worksheets and polls are not graded for correctness.
Quiz Policy
Starting Week 3, quizzes (closed-book) are given at the beginning of class every other Wednesday. Arrive promptly to ensure you do not lose time on the quiz. Quizzes will cover the topics from the previous 2 weeks and will typically be 20 minutes. If you need to miss a quiz, contact Prof. Ware as soon as possible, and please see the Absence Policy.
Lab Policy
This course features regular lab assignments that account for the largest component of your course grade. Lab attendance is required by all students, unless you have already completed and submitted the lab assignment for the week.
Lab Due Dates
Lab assignments will typically be assigned during the lab sections on Tuesday will generally be due by midnight on Monday 1-2 weeks later. The assignments for this course are designed to expose you to real-world systems. They are probably going to be more complex than most other course related work. You are strongly encouraged to start early! If you can get in the habit of starting early you will be much better off.
Lab Partnerships
For this course, there will be 1 individual lab, and 5 paired labs. You may choose your own lab partner for each lab, there will be a Edstem post to record your choice the week before the lab is out. If you have not chosen a lab partner by Friday the week before, one will be assigned to you partner for you.
Working with Partners: For partnered lab assignments, you should follow these guidelines:
-
The expectation is that you and your partner are working together side by side, virtually, for most, if not all, of the time you work on partnered lab assignments. You and your partner should work on all aspects of the project together: initial top-down design, incremental testing and debugging, and final testing and code review.
-
If you are pair programming, where one of you types and one of you watches and assists, then you should swap roles periodically, taking turns doing each part. There may be short periods of time where you each go off and implement some small part independently. However, you should frequently come back together, talk through your changes, push and pull each other’s code from the git repository, and test your merged code together.
-
You should not delete or significantly alter code written by your partner when he or she is not present. If there is a problem in the code, then meet together to resolve it. If there is any issue with the partnership, please contact Prof. Ware.
Partnerships where partners work mostly independently rarely work out well and rarely result in complete, correct and robust solutions. Partnerships where partners work side-by-side for all or most of the time tend to work out very well.
You and your partner are both equally responsible for initiating scheduling times when you can meet to work together, and for making time available in your schedule for working together.
Absence / Assignment Extension Policy
To help with cases of minor illnesses, or other short-term time limitations, we will drop your three lowest reading and participation grades. You are still responsible for the material, and you should review any missed materials via the class recordings as soon as you can.
Each student may use up to 2 late days for the semester, no questions asked. Late days do not apply to reading quizzes, participation grades. A late day is a considered a full 24-hours (i.e., 15 minutes late is the same as 23 hours late). In the case of labs, late days are counted against all lab partners.
In the rare case in which only one partner has unused late days, the partnership can use the late days, barring a consistent pattern. If you continuously find yourself needing late days on the assignment, please reach out to your Professor to discuss this.
To use your extra time, you must email your professor after you have completed the lab and pushed to your repository. You do not need to inform anyone ahead of time. When you use late time, you should still expect to work on the newly-released lab during the following lab section meeting. The professor will always prioritize answering questions related to the current lab assignment.
If you feel that you need an extension on an assignment or that you are unable to attend class for two or more meetings due to a medical condition (e.g., extended illness, concussion, hospitalization) or other emergency, you must contact the dean’s office and your instructors. Faculty will coordinate with the deans to determine and provide the appropriate accommodations.
Grading
Grades will be weighted as follows:
40% |
Lab assignments - 5 (8% each) |
30% |
Quizzes - 5 (5% each) |
20% |
Final Exam |
10% |
Class Participation (5% reading, 5% in-class) |
Inclusion Statement
Diversity, inclusion, and a mutual sense of belonging are all core values of this course. All participants in this course must be treated with respect by other members of the Swarthmore CS community. We must all strive, students and faculty both, to never make anyone feel unwelcome or unsafe in any way. Violations of these principles are viewed as unacceptable, and we take them very seriously. If you ever feel discriminated against or otherwise excluded, no matter how minor the offense, we encourage you to reach out to Prof. Ware or campus non-discrimination contacts.
How to Succeed in CS 43
-
Attend class.
Class attendance is mandatory. In class, we will do a deep dive into the more challenging details of the material. Example case-studies in class will directly contribute to your ability to complete labs and quizzes. -
Do the required readings/listen to videos before you come to class.
In-class group participation will carry grades, so please come prepared with your readings and videos. This will make for an interesting and lively debate in class. -
Ask questions if you don’t understand.
-
This means both during class and while doing lab assignments.
-
This class continually builds on previous material, so if you don’t understand something one week, it will continue to be a problem the next week, and the week after that, and so on.
-
If you need help, ask your classmates (make sure you have read the "Academic Integrity" section below first), post on {edstemurl}[EdStem], or come talk with me during my office hours.
-
-
Start the lab assignments early.
-
The assignments for this course are designed to expose you to real-world systems. They are probably going to be more complex than most other assignments from earlier courses.
-
Get in the habit of starting early you will be much better off. If you get stuck on a lab issue early (i.e., not two hours before it is due), there will be time to look for help.
-
In addition, if you start early enough, you can take a break, go do something else, and come back later. I find I always have at least a few new ideas when I come back to a problem after a break. If you wait until the last minute, you can’t do this.
-
-
Completing your labs.
The only effective way to learn the material and consistently do well in the labs is to get into the regular habit of: Discussing the top-down design of your code with your lab partner, before you start coding. Writing descriptive function comments as you go along. ** Incrementally coding and testing with GDB and Valgrind.
+ This process, will make you a sought after computer scientist once you graduate.
-
Attend CS43 Labs.
Lab Attendance is mandatory, and the labs constitute the largest portion of your grade. You should be there! -
Seek help early and often.
Because course material builds on previous material, it is essential to your success in this class that you keep up with the course material. If you are having difficulty with a programming assignment, if you didn’t follow something covered in class, if you feel you need some extra help understanding or practicing some of the course material, or if you just want to discuss something from a class, an assignment, or the text, please come to office hours.
Academic Integrity
Academic honesty is required in all your work. Under no circumstances may you hand in work done with (or by) someone else under your own name. Your code should never be shared with anyone; you may not examine or use code belonging to someone else, nor may you let anyone else look at or make a copy of your code. This includes, but is not limited to, obtaining solutions from students who previously took the course or code that can be found online. You may not share solutions after the due date of the assignment or make them publicly available anywhere (e.g. public GitHub repository).
Discussing ideas and approaches to problems with others on a general level is fine (in fact, we encourage you to discuss general strategies with each other), but you should never read anyone else’s code or let anyone else read your code. All code and written homeworks you submit must be your own with the following permissible exceptions: code distributed in class, code found in the course text book, and code worked on with an assigned partner. In these cases, you should always include detailed comments that indicates on which parts of the assignment you received help, and what your sources were.
Use of or consultation with generative AI (e.g., chatGPT or GitHub CoPilot or other variants) is considered to be unauthorized collaboration with another source and is a violation of our academic integrity policy.
Failure to abide by these rules constitutes academic dishonesty and will lead to a hearing of the College Judiciary Committee. According to the Faculty Handbook:
The spirit of this policy applies to all course work, including code, homework solutions (e.g., proofs, analysis, written reports), and exams. Please contact Prof. Ware if you have any questions about what is permissible in this course.
Exam Integrity
Students must strictly adhere to the following policy, which applies to all quizzes and exams taken in a Computer Science course at Swarthmore:
Exam takers must place all non-essential items at the front of the room (or other designated area). Unless otherwise permitted, students may not have any electronic devices or course materials in their possession during the entirety of the exam. This includes cell phones, tablets, laptops, smart watches, course notes, articles and books, among others. These items should be placed at the front of the room near the proctor. If you need to leave the room during the exam, you must obtain permission from an instructor first. Any non-permitted discussion or aide in regards to exam material will result in immediate forfeiture of the exam and a report to the College Judiciary Committee. Please discuss any concerns or accommodations with your instructor prior to starting the exam.
Academic Accommodations
If you believe you need accommodations for a disability or a chronic medical condition, please visit the Student Disability Services website for details about the accommodations process. Since accommodations require early planning and are not retroactive, contact Student Disability Services as soon as possible. You are also welcome to contact Prof. Ware privately to discuss your academic needs. However, all disability-related accommodations must be arranged, in advance, through Student Disability Services.
To receive an accommodation for a course activity you must have an official Accommodations Letter and you need to meet with Prof. Ware to work out the details of your accommodation at least two weeks prior to any activity requiring accommodations.
You are also welcome to contact Prof. Ware, privately to discuss your academic needs. However, all disability-related accommodations must be arranged, in advance, through Student Disability Services