EECS 3214 M, Winter 2020
Computer Network Protocols & Applications
Lecture Schedule: T and R, 10:00 - 11:30, LSB 05
Instructor: Natalija Vlajic
E-mail: vlajic @ cse.yorku.ca
Office Hours: Tuesday, 13:00 - 14:00, LAS 2047
TA Office Hours: Friday, 12:00 - 13:30, LAS 3017
Textbook and Recommended Resources
Course Schedule (Week-by-week Topics Covered, Notes, Required Reading, Assignments)
Late Assignments and Missed Midterm
||Topic / Notes
/ Important Dates
||T, Jan 7
|R, Jan 9
||Packet vs. Circuit Switching - part 1||Kurose - Sections 1.1, 1.2, 1.3
||T, Jan 14
vs. Circuit Switching - part 2
Layered Architecture - part 1
Kurose - Sections 1.5
|R, Jan 16
||Layered Architecture - part 2||-||-
||T, Jan 21
Slides on Layered Architecture
Layered Architecture - part 3
|R, Jan 23
||Network Layer / IP - part 1||Kurose - Sections 4.3||
||T, Jan 28
||Network Layer / IP - part 2||-||-|
|R, Jan 30
Packet (Queueing) Delay - part 1
| Kurose - Sections
Kurose - Sections 1.3
(due date Feb 13)
||T, Feb 4
||Packet (Queueing) Delay - part 2||-||-||
|R, Feb 6
Addressing and Subnetting - part 1
||Kurose - Section 4.3.3
||T, Feb 11
Addressing and Subnetting - part 2
Network Address Translation (NAT)
Kurose - Section 4.3.4
|R, Feb 13
||Unicast Routing - part 1||Kurose - Sections 4.2 and 5.1 - 5.4|
Week (Feb 15 - Feb 21)
||T, Feb 25
(due date Mar 12)
|R, Feb 27
Routing - part 2
||T, Mar 3
|Kurose - Section 5.6||
|R, Mar 5
||TCP basics - part 1||Kurose - Sections 3.2, 3.3.1, 3.3.2, 3.5.1, 3.5.2, 3.5.6|
||T, Mar 10
basics - part 2
TCP flow control - part 1
|Kurose - Sections
3.5.3, 3.5.4, 3.5.5
|R, Mar 12
||TCP flow control - part 2||-||-||Mar 13 - last day to drop courses|
||T, Mar 17
flow control - part 3
TCP congestion control
Kurose - Sections 3.6, 3.7
(due date Mar 26)
|R, Mar 19||Socket
Programming - part 1
|Kurose - Sections 2.7|
||T, Mar 24
Programming - part 2
|R, Mar 26||DNS
|Kurose - Sections 2.4||Assignment
(due date April 7)
||T, Mar 31
Protocol - part 1
|Kurose - Sections 2.2|
|R, Apr 2
Protocol - part 2
Fri, April 24, 9:00
"Computer Networking: A Top-Down Approach Featuring the Internet", J. F. Kurose and K. W. Ross, Addison Wesley, 2018, 7th edition.
"Computer Networks: A Systems Approach - Network Simulation Experiments Manual", E. Aboelela, Morgan Kaufmann, 2012, 3rd edition. (optional)
Recommended Reading Material
"Computer Networks: A Top-Down Approach", B. A. Forouzan, F. Mosharraf, McGraw Hill, 2012. Excellent book!
"Data Communications and Networking", B. A. Forouzan, McGraw Hill, 2013, 5th edition. Excellent book!
"TCP/IP Protocol Suite", B. A. Forouzan, McGraw Hill, 2009, 4th edition. Excellent book!
"Data and Computer Communications", W. Stallings, Prentice Hall, 2014, 10th edition.
"Computer Networks: A Systems Approach", L. L. Peterson, B. S. Davie, Morgan Kaufmann, 2012, 5th edition.
"Learning Network Programming with Java", R. Reese, Packt Publishing, 2015.
"Java Network Programming", E. R. Harold, O'Reilly Media, 2013, 4th edition.
"The TCP/IP Guide", Charles M. Kozierok.
Riverbed Modeler (Academic Edition)
Prerequisites: General Prerequisite.
This course focuses on the higher-level network protocols, security issues, network programming, and applications. Topics covered include networking basics; queuing fundamentals; network layer protocols including ICMP, DHCP and ARP multicasting; transport layer UCP and TCP, sockets and socket programming; application layer protocols including HTTP and DNS; multimedia; security; VOIP.
16% 4 Lab Assignments (4% each)
9% Java Socket Programming Project
35% Midterm Exam
40% Final Exam
Late Assignments and Missed Midterm
Late assignments will not be accepted, unless a prior arrangement is made with the instructor.
Makeups of missed midterm exams are only possible in extremely exceptional situations (such as verifiable medical emergencies) or by arrangement well prior to the exam, provided there is an extremely compelling reason.
"The Department takes the matter of academic honesty very seriously. Academic honesty is essentially giving credit where credit is due. And not misrepresenting what you have done and what work you have produced. When a piece of work is submitted by a student it is expected that all unquoted and uncited ideas and text are original to the student. Uncited and unquoted text, diagrams, etc., which are not original to the student, and which the student presents as their own work is considered academically dishonest."
For more see: Department of Computer Science Academic Honesty Guidelines