| 6.033 - Computer System Engineering | Handout 10 - March 2, 2003 |
For recitation, read Saltzer, Reed and Clark, "End-to-End Arguments in System Design" (Reading #10). The paper is in your reading package, and it is also available online. You should also read Isenberg's The Dawn of the Stupid Network.
Today's written assignment is a one-pager summarizing your design
for DP1
The summary should focus on the salient aspects of your
design that address the memory protection and dynamic reallocation
requirements (Section III of DP1).
For fun, think about the following question while reading today's assigned paper (You do not need to hand in an answer.):
A file transfer done using the EFTP protocol described in the Ethernet paper will encounter two error-checking mechanisms. The first is a CRC calculated on the data for purposes of catching errors in the Ether (i.e., errors that occur in transit), and is performed in the Ethernet hardware. The second is another checksum provided as a backup to the (hardware) CRC, as well as for catching errors that occur at the host or destination (but still within the network layer). This check is done as part of the EFTP protocol. Note that the second checksum does not have to be computed, though some value must always be sent. What is the use of these error-checking mechanisms on the basis of the End-to-End argument? Consider the usefulness of each individual checksum as well as the combination of the two. Do you need both checksums?
Yes, we will be having a lecture on Friday this week. A special lecture will be given by the writing program on the subject of writing up your design project. They will present the recommended format for the writeup and give you some tips about how to write a technical paper like the ones we have been reading in class. If you are planning on using your report to pass the Phase 2 requirement, you might find this lecture helpful.
| Go to 6.033 Home Page | Questions or Comments: 6.033-tas@mit.edu
|