Assignments for CSE 588
The purpose of the weekly assignments for this course is two-fold; not
only do they serve as a way of reviewing and enhancing the knowledge you
acquired in lecture, they also prepare you for the following lecture.
Assignments are due every Thursday at the beginning of class.
They are to be submitted by paper.
Eastside students may submit late homeworks by email
(in text, HTML, or Postscript format, either embedded
in the document or using a MIME-attachment) to
cse588-hw@cs.washington.edu
The first few minutes of each class will be dedicated to discussing the
homework.
Final Late Policy:
Turned in at... | Deduction |
Thursday at the beginning of class | 0% |
Everyone is allowed 7 late days total for all homeworks combined. After that | 15% |
If the problem has been discussed in class | 50% |
If the solution has been handed out | 100% |
Special exceptions by arrangement prior to the
deadline. |
Solutions to the Homeworks
Homework #1 solution
Homework #2 solution
Homework #3 solution
Homework #4 solution
Homework #5 solution
Homework #6
Reading:
- Finish chapters 8 and 9 if you haven't already.
- Go back and read section 4.3 (cell switching/ATM).
Exercises
- Do problems 8.8, 8.12, and 8.20.
- Do problems 9.15.
Homework #5
Reading:
Homework #4, due May 8th at the beginning of class
Reading:
- Read sections 4.2, 5.2.3, 5.2.4, 5.3, and 5.5 in the text.
- Read RFC 1058 (RIP) and skim RFCs 1075 (DVMRP) and
1583 (OSPF -- particularly long). RFCs can be obtained at
ftp://ds.internic.net/rfc/rfcNNNN.txt.
RFC 1058
RFC 1075
RFC 1583
- Optional reading in supplemental text: C. Huitema, "Routing in the
Internet", Chapters 4-6 and 11.
Exercises
- Do problems 5.2, 5.12, and 5.13.
For more information on traceroute.
Homework #3, due April 24th at the beginning of class
Reading:
- Read this paper (or PDF format).
- Familiarize yourself with sliding window protocols in Chapter 6.
- Familiarize yourself with big-endian/little-endian in Chapter 7.
- Start looking at Chapter 8.
Exercises
-
We talked about host configuration in class last night, using RARP,
BOOTP and DHCP. These provide a way for the end-system to get an IP
address. What other configuration info besides an IP address does a host
need in order to function, that is, to send/receive IP packets on the net
and to figure out where to send them? What else needs to happen if the
host is acting as a server (e.g. web or ftp) ?
-
IPv6 has 128 bit addresses, up from 32 bits in IPv4. How might these
big addresses be used to solve the problem of host autoconfiguration?
(Assume Ethernet-connected hosts.) What implications would such a
strategy have for the Address Resolution Protocol (ARP) ?
Paper Outline
- Please submit a detailed outline for paper #1.
Submissions should include both a paper copy at the beginning
of class. Please follow this up with an email
version within 24 hours of class.
Remember to use text/plain or text/html for the version you
send by email
(for one thing, so that we can easily edit out your name!).
Homework #2, due April 17th at noon
Reading:
- Continue reading chapters 3 and 4; begin reading chapter 5.
Textbook Exercises
- Chapter 3: 21, 22, 23
- Chapter 4: 1, 2
- Chapter 5: 15
In addition:
- 11111 is 4B/5B's coding for idle. What problems are there with
this scheme? What could be used to fix this problem?
- Some CRC can be used to correct small numbers of errors. Why?
Why do link protocols simply discard frames with incorrect CRCs
rather than attempting correction?
- Why have the powerful error checking (CRC) at the lower layers
and the less powerful checking at the upper layers (Internet
Checksum)
Bonus Question
- In FDDI, when a claim frame is received, a station with a TTRT
equal to the claim may or may not replace the claim frame with
its own. Why not pass it on, knowing that its TTRT requirement
has been satisfied?
Homework #1, due April 10th at noon
Relating to Week 1 (Background) lecture:
- Be familiar with material in Chapter 1
- Textbook exercises for Chapter 1: 6,7,9,15
Preparing for Week 2 (Routing & Switching) lecture:
- Skip Chapter 2 of the text, but be familiar with concepts of
multiplexing/demultiplexing.
- Make sure you're comfortable with protocol layers,
and how each layer's info is encapsulated with new
headers for the next layer.
- Use your favorite web browser to:
- Connect to
www.nwfusion.com
Register to gain admittance (you can use a fake name!)
Search for "Switching Showdown"
Find the link that is the transcript from the CommNet 97
"Switching Showdown" and read it.
- On the same site,
use their "docfinder" feature to lookup and read
Doc # 0691, on "the dark side of switching".
- Connect to
www.rapid-city.com and look on the left for the
link under "Innovative New Category"... "routing
switches". Read their
white paper.
- Thumb through chapters 3 and 4 of the text. Don't need to read
every word, but try to get an idea of what the main topics and
issues are.