Carefully read T. Berners-Lee et al., "The World-Wide Web", reading #20. Prepare for a detailed discussion on the Web's architecture and naming scheme in recitation. Note that the paper uses the term Universal Resource Identifier (URI), but the term Uniform Resource Locator (URL) is used by most browsers today instead. URIs still exist as the union of URLs and Uniform Resource Names (URNs). The difference between those is that URLs are location-dependent, while URNs are not.
If you'd like to read more, the 1996 February issue of DLIB magazine (available only online) has an update on the status of URN proposals and plans, including pointers to each URN scheme currently under active development. See the second article in http://www.dlib.org/dlib/february96/02contents.html.
Reading #20 is essential to your design project. Think of it as an opportunity to get a double benefit: if you do your reading carefully, you can fully participate in section (making a good impression on your instructor) and you'll make progress on your design project!
A special lecture to teach you how to write a paper. Since the paper on the design project is due next week, this lecture can help you greatly in writing your paper.
This is the second and last lecture on naming. Read Saltzer Chapter 5.C, reading #19.
Read "Semantic file systems" (reading #21) by Gifford et al. This paper offers a very powerful way of naming files. Here are some questions you might want to ponder on while reading the paper:
Is the concept of a semantic file system mostly useful when typing commands and doing one-shot shell scripts where the user is available to interactively examine the consequence? Or is there a real use for this feature in writing C programs?
How might caching be used to shorten the time needed to generate a virtual directory lookup?
To give you some more time for your design project, there is no reading report due today.
Today we start a new topic in 6.033: security. As an introduction to security, we will first discuss privacy and security in society. To get prepared, read "Teaching students about responsible use of computers" by Lerman et al., reading #23. (The paper lists Saltzer as the only author, but the official authors are Lerman and Saltzer.) This reading contains only 1 page, so you'll have plenty of time left to work on your design project (due tomorrow!).
The following question was assigned for a reading report last year. You do not have to write a reading report on this question this year, but you might want to think about it.
As an April Fool's day prank, Joe L. User writes a program that takes advantage of a security hole he has discovered in the X window system at Project Athena. The program takes a user's name, finds out from Zephyr where that user is logged in, then opens a full-screen-sized window on that other user's Athena workstation and displays the message "This workstation has crashed. All user files have been lost." Thirty seconds later it displays the message "APRIL FOOL'S! Hah Hah Hah". Unfortunately, Joe stays up all night March 31 doing the reading for 6.033. Finally realizing that it is April 1, Joe races to an Athena workstation, checks and finds that his good friend Ben Bitdiddle is logged in and types the command to target Ben. In his haste (and tiredness!), he mistypes the arguments and the program targets ALL Zephyr-visible users who happen to be logged in at the time. Needless to say, this mistake causes a lot of confusion and floods the Athena consultants and help lines.
Information Systems traces the source of the messages to Joe's account. When confronted, he apologizes profusely and claims it was a mistake. He says that he and Ben have a long running tradition of playing practical jokes on one another. According to Project Athena's Statement of Ethics, what action, if any, should be taken against Joe?
(Lest you think this question is unrealistic, things like this happened to me almost regularly while I was debugging xzewd -- it'd accidentally send zephyrs to random places! ---Eddie Kohler)
System aphorism of the week
A system continues to do its thing, regardless of need.
6.033 Handout 19, issued 3/11/96