• Assignment #7 Addendum, Updated 04/28 @ 12:41
• Programming Assignment, Design Due Wed 23^rd
• AES encrypt/decrypt object file and header file
• Final Exam Fri 2^nd 1:00 p.m.
• See “Topics” for reading assignments
• A note about taking notes

Session	Activity	Reference
#1 - Jan 8	Course overview	Syllabus & Course Materials, Topics
#2 - Jan 13	Network requirements	Topics
#3 - Jan 15	Internet architecture	Topics
#4 - Jan 22	Simplex Server	Topics
#5 - Jan 27	Simplex Client	Topics
#6 - Jan 29	Network performance	Topics
#7 - Feb 3	Network performance, L1 - Physical layer	Topics
#8 - Feb 5	Git tutorial, Markdown tutorial	Assignment #2
#9 - Feb 10	Modulation & Encoding, L2 - Data link	Topics
#10 - Feb 12	Error detection, Error correction	Topics, Assignment #1, Assignment #3
#11 - Feb 17	Test #1
#12 - Feb 19	Network toolbox	Assignment #4
#13 - Feb 24	Flow control algorithms, L2 Sliding window	Topics
#14 - Feb 26	L2 Sliding window, Ethernet IEEE 802.3	Topics
#15 - Mar 3	Ethernet IEEE 802.3, Token ring, FDDI	Topics
#16 - Mar 5	Bluetooth, 802.11 WiFi, Cellular	Topics
#17 - Mar 10	Switching (forwarding)	Topics
#18 - Mar 12	L3 responsbilities, Forwarding in L3	Topics, Assignment #5, Config File Parser
#19 - Mar 17	Switch fabrics, Logical router architecture	Topics
#20 - Mar 19	Test #2
#21 - Mar 31	Routing protocols	Topics
#22 - Apr 2	Routing protocols	Topics
#23 - Apr 7	No class	Assignment #6
#24 - Apr 9	L3 - IP addressing	Topics
#25 - Apr 14	Subnetting, Supernetting, CIDR	Topics
#26 - Apr 16	IPv4 helper protocols, IPv6	Topics
#27 - Apr 21	Test #3
#28 - Apr 23	L4 - end-to-end, UDP, TCP	Topics
#29 - Apr 28	TCP improvements & extensions, Congestion control	Topics

I'm often asked about posting my lecture notes on the class web site.

1. Taking notes during class is, in my opinion, a vital part of the learning process. Hearing what is said, thinking about the material, and writing (in your own words) what we are discussing each session serves to reinforce the learning process. In fact, I think it is useful to take notes from your textbooks as well. The process really speeds up learning and increases retention.
   
2. My notes are an extreme shorthand designed to guide me during class. They do not contain everything I say in class or write on the board/computer. My notes are, at best, a skeleton listing of the topics we've covered. Your notes should be more detailed than mine, after all, I already know the material.
   
3. Finally, it would be much easier for me not to write anything on the board or computer. The reason I do these things is to allow you to reflect on what is being discussed, write appropriate notes, and ask questions. Writing key phrases and facts on the board/computer is designed to slow me down and allow you time to write your notes. Everything we discuss in class is possible exam material whether I write it down or not (i.e. you should be writing it down).

So, I don't believe posting my lecture notes is in your best interest. I feel it is important for you to take your own notes during class.

However, I will do the following:

• post a list of the topics we've covered each session,
• post selected links to reference materials I use,
• post the chapter and page numbers for each session.

These will be posted on the class web site for each session.

• Syllabus
• CS Collaboration policy
• CS 440 Code Style Guide
• UNIX/Linux shell cheatsheet
• Vim cheatsheet
• Git cheatsheet
• Markdown cheatsheet