The University of Kansas,
Department of Electrical Engineering and Computer Science,
EECS 800: Special Topics – Survivable, Resilient, and Disruption Tolerant Networking
Fall 2005
09:30–10:45 Tue. and Thu. in 2002a Eaton
Office hours Tue. and Thu. 11:00–12:00 in 3036 Eaton or by appointment
This seminar will begin with a series of lectures and readings from the literature to introduce the emerging field of survivable, resilient, and disruption-tolerant networks, which aim to remain operational and provide an acceptable level of service in the face of a number of challenges including: natural faults of network components; failures due to mis-configuration or operational errors; attacks against the network hardware, software, or protocol infrastructure; large-scale natural disasters; unpredictably long delay paths either due to length (e.g. satellite and interplanetary) or as a result of episodic connectivity; weak and episodic connectivity and asymmetry of wireless channels; high-mobility of nodes and subnetworks; unusual traffic load (e.g. flash crowds). New approaches, protocols, and algorithms are required at all layers (physical, MAC, link, network, transport, session, application) and at all planes (data, control, management).
With guidance from the instructor and a goal of broad coverage of the field, students will choose an area of interest to pursue in significantly more depth. Papers will be read with findings presented orally to the class and summarised in written form, leading to a project that investigates novel solutions in the chosen area. Simulation is a likely means to execute the project, but other approaches may be considered. Many potential thesis topics lie in this field, and exceptional projects will be encouraged for conference publication.
Prerequisite: EECS 663
This course will consist of three major parts: (1) introductory lectures and general readings, (2) individual topical readings and summaries, and (3) projects. There is no textbook for this course.
| Date | Activity | Required Reading | |
|---|---|---|---|
| 18 Aug | administrivia | ||
| 23, 29 Aug | lecture and discussion – introduction and definitions | [SK+2002, KS+2003] | |
| 29 Aug, 1 Sep | lecture and discussion – scenarios and environment | [F2003] | |
| 1, 6 Sep | lecture and discussion – network layer and architecture | ||
| 6, 7 Sep | lecture and discussion – transport layer and end-to-end communication | [KS+2004] | |
| 8 Sep | past failure paper selection due (verbally in class) | ||
| 8, 15 | lecture and discussion – disruption-tolerant applications | [SSK2002] | |
| 16 Sep | interest area proposal due | ||
| 20 Sep | past failures and scenarios: Katrina, Hinsdale, NE power failure | [T1998, CO+2004] | |
| 22 Sep | past failures and scenarios: 9/11 | [PB+2003] | |
| 11 Oct | past failures and scenarios: Katrina, NE power failure | [CP+2005], scan quickly [MR+2004], browse [ISER2005k] | |
| 13 Oct | fall break | ||
| 18 Oct | mid-term exam (written) | ||
| 20 Oct | project proposal due | ||
| 25 Oct | student presentations: PROPHET | [LDS2005] | |
| 27 Oct | rescheduled | ||
| 1 Nov | student presentations: Interplanetary Internet and DTN routing | [IP+2002, DFS2001], [F2003, JFP2004] | |
| 3 Nov | student presentations: epidemic and resilient routing | [VB2000], [AH+2002] | |
| 8 Nov | student presentations: energy aware transport protocols | [BR+2003] | |
| 10 Nov | student presentations: interplanetary transport protocols | [AFA2004] | |
| 15 Nov | cross layer lecture; student presentations: wireless cross-layer optimisations |
[KK2005, KG2004a] | |
| 16 Nov | student presentations: P2P overlays and epidemic routing | [YC+2005, HH+2004] | |
| 17 Nov | student presentations: knowledge-based opportunistic forwarding and DTN routing | [LC+2005, JLW2005] | |
| 22 Nov | student project status discussion | ||
| 24 Nov | Thanksgiving break | ||
| 7 Dec | student presentations: SCPS-TP and ad hoc routing | [DMT1996, MG+2000] | |
| 8 Dec | student presentation: project status discussion |
||
| Fri 16 Dec | final exam oral project presentations |
This schedule is tentative and will be adjusted based on class enrollment and interests.
The first part of the course will consist of introductory lectures accompanied by general and selected readings in the area of survivable, resilient, and disruption-tolerant networks. Students are expected to complete the introductory readings before the lecture listed in the schedule table – note that class participation is a part of the final grade.
In the second part of the course, students will choose an area of interest to pursue in significantly more depth, with guidance and approval from the instructor. Examples of areas include a protocol layer (e.g. application, overlay, transport; network routing, forwarding, traffic management; MAC, link), protocol plane (e.g data, control and signalling, management), or other aspect (such as security and information assurance). There will be a negotiating phase to match student interests while ensuring diversity and broad coverage among all class members. A one-page proposal of interest area will be due from each student on 8 Sep.; areas will be finalised the following week of classes. Students should feel free to discuss potential areas with the instructor before the proposal deadline.
Each student will be responsible for choosing several papers in their area and will lead the classroom discussions, one or two papers per period tentatively begining 27 Sep. All students will be responsible for reading the chosen paper before the discussion, and will be responsible for contributing to the discussion. . The discussion leader must choose and receive approval for each paper two weeks before the presentation date, and must email presentation materials (.ppt, .pdf, or .ps) to the instructor no later than 48 hours before the beginning of class. Note that this email must begin with the string “[EECS800]” to trigger the instructor's email filtering.
Each student will also be required to provide a written summary of chosen papers, due one week after the presentation date. These summaries will be collected into an informal technical report that (with each student's permission) will be put on the Web and document the findings of this course.
This reading list will be populated as students choose papers. The current headings suggest potential focus areas.
http://www.ipnsig.org/reports/TCP_IP.pdf.draft-irtf-dtnrg-arch-03.txt, July 2005.http://epubl.ltu.se/1402-1617/2005/139/LTU-EX-05139-SE.pdf.http://www.aiaa.org/Spaceops2002Archive/papers/SpaceOps02-P-T5-18.pdf.http://www.cs.ucla.edu/%7Ecclljj/publication/2005/UCLA_CSD_TR050030.pdf.draft-irtf-dtnrg-bundle-spec-03.txt, July 2005
http://eprints.biblio.unitn.it/archive/00000582/01/DIT-04-025.pdf.
http://issg.cs.duke.edu/epidemic/epidemic.pdf.http://www.melissa.myensim.net/research/epidemic/epidemic.pdf.
http://www.cnds.jhu.edu/research/networks/archipelago/publications/ACHNR-SurvivalilityOfRouting-SecureComm2005.pdf.9/11
Central Office Fires
comp.dcom.telecom and included in
http://massis.lcs.mit.edu/archives/history/fire.in.chicago.5-88
Hurricanes
http://www.oe.netl.doe.gov/hurricanes_emer/katrina.aspx
http://www.renesys.com/resource_library/Renesys-Katrina-Report-9sep2005.pdf
Power Grid Failures
https://reports.energy.gov/BlackoutFinal-Web.pdf
http://www.renesys.com/resource_library/Renesys_BlackoutReport.pdf
The final part of the course will consist of each student executing a project that investigates novel solutions in the chosen area. Simulation is a likely means to execute the project, but other approaches may be considered (e.g. analysis or implementation). Project proposals are due in class on 20 Oct., and should include the specific problem or idea to be investigated, planned methodology, and expected outcome.
The project must be completed by the 8 Dec.; written project final reports are due in this class period. Demonstrations are encouraged if appropriate. The final exam will consist of short oral presentations of the project to the entire class.
Many potential dissertation and thesis topics lie in this emerging field; students looking for a topic are encouraged to use this opportunity. Students who complete exceptional projects that receive a grade of A will be encouraged to prepare a paper based on their final report for conference publication, with the help and collaboration of the instructor.
| weight | component |
|---|---|
| 25% | midterm exam |
| 20% | class participation (other than leading discussions) |
| 20% | paper presentation and discussion leadership |
| 35% | final project and report |
All sources in your written work (paper summaries and project final report) must be properly referenced; I consider plagiarism an extremely serious offense that will result in an F for the course in addition to the possibility of more serious sanctions. If you use a source from the literature or the idea of another for your work you must reference it. If you quote or copy a block of text, it must be cited and included in quotation marks (if a sentence or less in length) or in block quote style (if more than a sentence in length). If you paraphrase text (reword a phrase, sentence, or paragraph), you must also quote or blockquote followed by “[paraphrased]” in addition to proper citation.
The USC academic integrity quiz is also useful reading. If you have any doubt, talk to me – inexperience in past writing or coming from an environment where plagiarism was permitted will not be an acceptable excuse for academic misconduct.
Note that a paper that consists mostly of quotes and blockquotes is not likely to receive an acceptable grade, even if properly cited. You are expected to demonstrate your own understanding and knowledge.
I understand that English is not a native language for many students, and while it is important to use the best writing skills you can, you will be far better off submitting your own imperfect English than the work of others. I recommend that you take intermediate notes from which you write your own words. I strongly recommend that you not write in one window while displaying the work of others in another window; this is asking for trouble. “Unintentional” paraphrasing is also not an acceptable excuse for academic misconduct.
Last updated 6 December 2005 –
Valid XHTML 1.1 –
Lynx inspected –
W3C AAA Conformance
©2005 James P.G. Sterbenz
<jpgs@eecs.ku.edu>