The Internet is one of the great technology success stories of the last twenty years. As it has grown, it has been used in ways that the original designers never envisioned and for which the core protocols were never designed. New needs have been met through a variety of ad hoc mechanisms, which have never been integrated into the network architecture, and which, in many cases, violate some of the Internet's central architectural principles. This course will study how the Internet has evolved to meet changing needs and will explore the technical issues that have arisen, as a result of this evolution. It will also explore how the Internet might be restructured to address these issues. The course will be based primarily on published research papers, with reference to standard texts and RFCs for background material.
.
The class will be conducted using a combination of conventional lectures and student-led presentations of selected papers from the research literature. In particular, each Monday class session will involve student presentations of two different papers, and each Wednesday session will involve a lecture from the instructor. The student presentations will be limited to 25 minutes, to allow time for discussion. This means you will need to focus on presenting the most important elements of the paper, rather than presenting every last detail. Student presentations must be mailed to the instructor by 6:00 pm the evening before the presentation. They will be made available on the web site, so that other students can review them before class.
For each of the student-led presentations, several other students will be designated to write critical reviews of the papers. These will be due on the Friday before the paper is to be presented at 6:00 pm, and must be posted as articles to a blog that has been setup for the class. Reviews should be one to two pages long. I suggest you look at the public reviews from recent HotNets conferences and this year's SIGCOMM conference for examples of the kind of reviews I am expecting. However, that I advise you not to read online reviews of any paper that you will be reviewing yourself.
The papers that will be used for the student presentations are listed at the bottom of this page. To sign up to present or review a particular paper, please use this form (there is also a link to the form in the left margin). Each student is expected to give two presentations over the course of the semester (at least one must be before the middle of October) and review six papers (say two per month).
Each week, several students will also prepare short essays on one of several selected topics. Essays should be 3-4 pages long. These are also to be posted to the blog and will be due on Sundays at 6:00 pm. Each student will do three essays over the course of the semester (say one per month). Signups for essays will also be done using the scheduling form.
There will be a final paper due at the end of the semester. This should take the form of a proposal for a novel network architecture or architectural feature. The Hotnets conference is a good source of examples of the kind of work I am looking for here. Each student will also give a short presentation of their final paper. These will be done during finals week.
Students are also expected to post comments to the blog, addressing issues raised in the papers read, the presentations, the reviews, the essays or the comments from other students. Comments to the blog will be evaluated as part of the course grade.
The blog is called Reinventing the Internet. To register on the blog, click on the "Login" link, in the Meta section at the right and then select the "Register" link in the dialog box. Please use your full name as your user name. Once you have registered, you will be able to write articles that will be saved in the blog database and edit them later. You won't be able to post them to actually appear on the blog, but I will do that whenever the deadline for the given review or essay has passed. Your may also post comments to any of the articles on the blog.
In addition to the blog, there is a usenet newsgroup (wu.cse.class.570) that you can access through newsreader.wustl.edu. Please use this for course-specific questions, discussion that is not directly related to the papers, reviews or essays. I will also use it for announcements, so please check it regularly.
Academic integrity. In a course like this, there may be a temptation to "borrow" from existing online sources. Resist such temptations. Instances of plagiarism will be taken very seriously (a failing grade in the course and referral to the academic integrity committee). You may quote others' work if you cite it appropriately, and you may incorporate selected figures from other sources, but only if you cite them.
| Date | Authors | Topic |
| 9-10-2006 | Mike Wilson | Ethernet - a brilliant example of network architecture and evolution |
| 9-10-2006 | Andrew Wan | Ethernet - a modest technology gone bad |
| 9-17-2006 | Niarcas Jeffrey | The Internet protocol suite - a triumph of thoughtful design and engineering |
| 9-17-2006 | Travis Keshav | How the Internet succeeded in spite of IP |
| 9-24-2006 | Harri Thorvaldsson | Cross-layer transparency - the key to matching network performance to application needs |
| 9-24-2006 | Charlie Wiseman | Why well-defined interfaces are essential for enabling networks to evolve and survive |
| 10-1-2006 | Paul Moceri | Telepresence in real and virtual worlds - the next big thing in networked applications |
| 10-1-2006 | Andrew Wan | Why network (in)security will remain the Achilles heel of peer-to-peer and ad hoc nets |
| 10-8-2006 | Nuzhet Atay, Amy Freestone | How overlay networks will make IP irrelevant without actually killing it |
| 10-8-2006 | Brandon Heller | The absurdity of expecting unstructured overlays to improve application performance |
| 10-15-2006 | Sailesh Kumar | The essential role of networks in denial of service attack defense |
| 10-15-2006 | Travis Keshav | The futility of in-network DDoS defenses - it's the computer systems, stupid |
| 10-22-2006 | Niarcas Jeffrey, Brandon Heller | Re-thinking networks for mobility - static endpoints are just a (rare) special case |
| 10-22-2006 | Michela Becchi | The role of the wired infrastructure in wireless nets for enabling services on power-poor devices |
| 10-29-2006 | Paul Moceri, Mike Wilson | The case for strong authentication of network traffic |
| 10-29-2006 | Charlie Wiseman, Harri Thorvaldsson | You'll have to pry address spoofing from my cold, dead, spam-stained hands |
| 11-5-2006 | Amy Freestone, Nuzhet Atay | Making networks smarter - the key to reducing administrative and maintenance costs |
| 11-5-2006 | Mike Wilson | Lord save me from so-called smart networks - building a house of cards on a foundation of sand |
| 11-12-2006 | Niarcas Jeffrey, Michael Roche | Why multi-provider networks with no central control are bad for users |
| 11-12-2006 | Andrew Wan, Nuzhet Atay | How competition among network providers can produce better service for users |
| 11-19-2006 | Travis Keshav, Harri Thorvaldsson | The trouble with Internet naming and the growing abuse of DNS |
| 11-19-2006 | Charlie Wiseman, Michael Roche | The case for a consistent global naming system for all networked objects - real and virtual |
| 11-26-2006 | Paul Moceri, Michela Becchi, Sailesh Kumar | Geographic addressing in WANs to simplify routing and enable new services |
| 11-26-2006 | Brandon Heller | Why geographic addressing has no place in WANs (and maybe not LANs) |
| 12-3-2006 | Michela Becchi, Michael Roche | The case for making multicast a first-class service in the Internet |
| 12-3-2006 | Sailesh Kumar | Why multicast is irrelevant to the Internet |
| Date | Speaker |
| 12-6-2006 | Charlie Wiseman |
| 12-6-2006 | Harri Thorvaldsson |
| 12-11-2006 | Mike Wilson |
| 12-11-2006 | Sailesh Kumar |
| 12-11-2006 | Paul Moceri |
| 12-18-2006 | Niarcas Jeffrey |
| 12-18-2006 | Michael Roche |
| 12-18-2006 | Brandon Heller |
| 12-18-2006 | Michela Becchi |
| 12-18-2006 | Nuzhet Atay |
| 12-18-2006 | Travis Keshav |