ASSIGNMENT October 22 through October 26, 07
For Tuesday October 23, 07
Read the
"Design and Implementation of Sun Network File System"
by Sandberg, R., D. Goldberg, S. Kleiman, D. Walsh, and B. Lyon, describing
an example of an end-to-end protocol that does more then just provide
reliability.
Address the following question in your one-pager:
What do the designers of NFS mean when they say "stateless" protocol?
If I write my file on a file server, I expect to be able to read it back
someday. Doesn't that mean that the file server maintains state?
Lecture Material:
We continue discussing the end-to-end layer.
In preparation, please read Sections E (flow control) and F (congestion)
of the Networking Chapter.
For Class Discussion, Friday October 26, 07
The discussion today will be on Network Address Translation.
Please read the following papers: "Anatomy: a Look Inside Network
Translations"
by Geoff Huston.
Your suplementary reading is
discussing the problems with NAT.
You may also want to check out these relevant documents.
Address the following question in your one-pager:
-
Recall from lecture/recitations that to increase routing scalability, IP addresses
are hierarchically allocated (i.e., the Internet uses variable-length
"area identifiers"). How does the hierarchical allocation affect the
address shortage problem? Is the IP address space efficiently used?
-
What are the characteristics of a global address? What are the characteristics of a local/private address?
-
Why do global addresses have to be different from local addresses?
What happens if a NAT box advertises a local IP addresses (e.g., 10.*.*.*) to the
rest of the Internet?
Lecture Material:
We will wrap up the end-to-end layer in todays lecture.
In preparation, please make sure you have read Section E of the Network Chapter.
System aphorism of the week
A system continues to do its thing, regardless of need.
CS 146a Handout 7, issued 10/18/07