KU EECS 800: Special Topics  
Survivable, Resilient, and Disruption Tolerant Networking

The University of Kansas,
Department of Electrical Engineering and Computer Science,
EECS 800: Special Topics – Survivable, Resilient, and Disruption Tolerant Networking

Instructor

Prof. James P.G. Sterbenz <jpgs@eecs.ku.edu>

Time and Location

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

Description

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


Course Structure and Details

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.

Tentative Schedule

EECS 800 Schedule
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.

1. Introductory Lectures and General Readings

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.

Links

Research Initiatives and Groups

Store-and-Haul Routing
Episodic Internet Access
Interplanetary Internet

Standards and Related Organisations

Conferences and Workshops

Funding Agency Initiatives

2. Focused Readings

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.

Reading List

This reading list will be populated as students choose papers. The current headings suggest potential focus areas.

Background and Overview

[SK+2002]
James P.G. Sterbenz, Rajesh Krishnan, Regina Rosales Hain, Alden W. Jackson, David Levin, Ram Ramanathan, and John Zao,
“Survivable Mobile Wireless Networks: Issues, Challenges, and Research Directions”,
Proceedings of the ACM Wireless Security Workshop (WiSE) 2002 at MobiCom,
Atlanta GA, Sep. 2002, pp. 31–40.
[KS+2003]
John C. Knight, Elisabeth A. Strunk, and Kevin J. Sullivan,
“Towards a Rigorous Definition of Information System Survivability”,
Proceedings of the DARPA Information Survivability Conference and Exposition (DISCEX III),
Washington DC, Apr. 2003, pp. 78–89.

Interplanetary Internet and DTNRG Architecture

[DFS2001]
Why Not Use the Standard Internet Suite for the Interplanetary Internet?,
undated IPNSIG report
available from http://www.ipnsig.org/reports/TCP_IP.pdf.
[AF+2002]
Özgür B. Akan, Jian Fang, and Ian F. Akyildiz, Weilian Su,
“Performance of TCP Protocols in Deep Space Communication Networks“,
IEEE Communications Letters, vol.6 #11, Nov. 2002. pp.478–480.
[F2003]
Kevin Fall,
“A Delay-Tolerant Network Architecture for Challenged Internets”,
Proceedings of the ACM SIGCOMM 2003,
Karlsruhe Germany, Aug. 2003, pp. 27–34.
[AA+2003]
Ian F. Akyildiz, Özgür B. Akan, Chao Chen, Jian Fang, and Weilian Su,
“InterPlaNetary Internet: State-of-the-Art and Research Challenges“,
Computer Networks, vol.43 iss.2, Oct. 2003. pp.75–113.
[CB+2005]
Vinton G. Cerf, Scott C. Burleigh, Robert C. Durst, Kevin Fall, Adrian J. Hooke, and Keith L. Scott,
Delay-Tolerant Network Architecture,
DTN Research Group Ineternet Draft (work in progress),
draft-irtf-dtnrg-arch-03.txt, July 2005.
[EJ2005]
Henrick Eriksson and Patrik Jönsson,
Implementation and Analysis of the Bundling Protocol for Delay-Tolerant Network Architectures,
Luleå University of Technology MSc Thesis 2005:139 CIV,
available from http://epubl.ltu.se/1402-1617/2005/139/LTU-EX-05139-SE.pdf.

Applications

[IP+2002]
Dave Israel, Ron Parise, Keith Hogie, and Ed Criscuolo,
“Demonstration of Internet Technologies for Space Communication”, Proceedings of AIAA SpaceOps 2002,
T5-18, available from http://www.aiaa.org/Spaceops2002Archive/papers/SpaceOps02-P-T5-18.pdf.

Overlays

[YC+2005]
Guang Yang, Ling-Jyh Chen, Tony Sun, Biao Zhou, and Mario Gerla
Ad-hoc Storage Overlay System (ASOS): A Delay-Tolerant Approach in MANETs,
UCLA CSD Technical Report TR050030, 2005,
available from http://www.cs.ucla.edu/%7Ecclljj/publication/2005/UCLA_CSD_TR050030.pdf.

End-to-End Communication and Transport Protocols

[DMT1996]
Robert C. Durst, Gregory J. Miller, and Eric J. Travis,
“TCP Extensions for Space Communications”,
Wireless Networks,
vol.3 #5, Baltzer Science, Netherlands, Oct. 1997, pp. 389–403.
[BR+2003]
Davide Bertozzi, Anand Raghunathan, Luca Benini, and Srivaths Ravi,
“Transport Protocol Optimization for Energy Efficient Wireless Embedded Systems”,
Proceedings of the Design Automation, and Test in Europe Conference and Exhibition (DATE'02),
München, March 2003, pp.706–711.
[KS+2004]
Rajesh Krishnan, James P.G. Sterbenz, Wesley M. Eddy, Craig Partridge, and Mark Allman,
“Explicit Transport Error Notification (ETEN) for Error-Prone Wireless and Satellite Networks”,
Computer Networks,
vol.46, #3, October 2004, pp. 343-362.
[AFA2004]
Özgür B. Akan, Jian Fang, and Ian Akyildiz,
“TP-Planet: A Reliable Transport Protocol for Interplanetary Internet”,
IEEE Journal on Selected Areas in Communication,
vol.22, #2, Feb. 2004, pp.348–361;
[CB+2005]
Keith L. Scott and Scott C. Burleigh,
Bundle Protocol Specification,
DTN Research Group Ineternet Draft (work in progress),
draft-irtf-dtnrg-bundle-spec-03.txt, July 2005

Cross-Layer Optimisations: Knobs and Dials

[SSK2002]
James P.G. Sterbenz, Tushar Saxena, and Rajesh Krishnan,
Latency-Aware Information Access with User-Directed Fetch Behaviour for Weakly-Connected Mobile Wireless Clients,
BBN Technical Report 8340, May 2002.
[SRK2003]
Sanjay Shakkottai, Theodore S. Rappaport, and Peter C. Karlsson,
“Cross-Layer Design for Wireless Networks”,
IEEE Communications,
vol.41 #10, Oct. 2003, pp.74–80.
[KG2004a]
Dzmitry Kliazovich and Fabrizio Granelli,
A Cross-Layer Scheme for TCP Performance Improvement in Wireless LANs,
University of Trento Dept. of Information and Communication Technology technical report DIT-04-025,
available from http://eprints.biblio.unitn.it/archive/00000582/01/DIT-04-025.pdf.
[KG2004b]
Dzmitry Kliazovich and Fabrizio Granelli,
“A Cross-Layer Scheme for TCP Performance Improvement in Wireless LANs”>,
Proceedings of IEEE GLOBECOM 2005,
Dallas, Nov.–Dec. 2004, pp. 840–844.
[KK2005]
Vikas Kawadia and P.R. Kumar,
“A Cautionary Perspective on Cross-Layer Design”,
IEEE Wireless Communications,
vol.12 #1, Feb. 2005, pp. 3–11.

Network Signalling and Control

Network Routing and Forwarding

[VB2000]
Amin Vahdat and David Becker,
Epidemic Routing for Partially-Connected Ad Hoc Networks,
Duke University Technical Report CS-2000-06, July 2000, available from http://issg.cs.duke.edu/epidemic/epidemic.pdf.
[MG+2000]
Sergio Marti, T.J. Giuli, Kevin Lai, and Mary Baker,
”Mitigating Routing Misbehavior in Mobile Ad Hoc Networks“,
Proceedings MOBICOM 2000,
Boston, Aug. 2000, pp. 255–265.
[SLG2001]
William Su, Sung-Ju Lee, and Mario Gerla,
“Mobility Prediction and Routing in Ad Hoc Wireless Networks”,
International Journal of Network Management,
vol.11 iss.1, Jan.–Feb. 2001, pp. 3–30.
[AH+2002]
Baruch Awerbuch, David Holmer, Cristina Nita-Rotaru, and Herbert Rubens,
“An On-Demand Secure Routing Protocol Resistant to Byzantine Failures”,
Proceedings of the ACM Wireless Security Workshop (WiSE) 2002 at MobiCom,
Atlanta GA, Sep. 2002, pp. 21–29.
[HH+2004]
Melissa Ho, Stephen Hailes, Vladimir Dyo, Damir Pavu›in, and Jasper Weener,
Improving Resource Consumption for Epidemic Routing in Intermittent Networks,
available from http://www.melissa.myensim.net/research/epidemic/epidemic.pdf.
[JFP2004]
Sushant Jain, Kevin Fall, and Rabin Patra
“Routing in a Delay Tolerant Network”,
Proceedings of the ACM SIGCOMM 2004,
Portland, Aug. 2003, pp. 145–158.
[LDS2005]
Anders Lindgren, Avri Doria, and Olov Schelé,
“Probabilistic Routing in Intermittently Connected Networks”,
Proceedings First International Workshop on Service Assurance with Partial and Intermittent Resources (SAPIR 2004),
August 2004, Fortaleza, Brazil.
[LC+2005]
Jason LeBrun, Chen-Nee Chuah, and Dipak Ghosal,and Michael Zhang,
“Knowledge-Based Opportunistic Forwarding in Vehicular Wireless Ad Hhoc Networks”,
Proceedings IEEE 61st Vehicular Technology Conference VTC,
Stockholm, May/Jun. 2005.
[MHM2005]
Mirco Musolesi, Stephen Hailes, and Cecelia Mascolo,
“Adaptive Routing for Intermittently Connected Mobile Ad Hoc Networks”,
Proceedings of Sixth IEEE International Symposium on a World of Wireless Mobile and Multimedia Networks (WoWMoM'05),
Messina, Italy, June 2005, pp. 183–189.
[JLW2005]
Evan P.G. Jones, Lili Li, and Paul A.S. Ward,
“Practical Routing in Delay-Tolerant Networks”,
Proceedings of ACM SIGCOMM Workshop on Delay-Tolerant Networking (W-DTN'05),
Philadephia, Aug. 2005, workshops proceedings pp. 237–243.
[AC+2005]
Baruch Awerbuch, Reza Curtmola, David Holmer, Herbert Rubens and Cristina Nita-Rotaru,
“On the Survivability of Routing Protocols in Ad Hoc Wireless Networks”,
Proceedings of SecureComm 2005,
Sep. 2005, available from http://www.cnds.jhu.edu/research/networks/archipelago/publications/ACHNR-SurvivalilityOfRouting-SecureComm2005.pdf.

Autonomic, Programmable, Active, and Cognitive Networks

QOS and Traffic Management

Mobile and Ad Hoc Networking

MAC and Link layers

Security and Information Assurance

Scenarios and Past Failures

9/11

[PB+2003]
Craig Partridge, Paul Barford, David D. Clark, Sean Donelan, Vern Paxon, Jennifer Rexford, and Mary K. Vernon,
The Internet Under Crisis Conditions: Learning from September 11,
National Research Council report 10659, National Acadamies Press, 2003

Central Office Fires

[T1988]
Patrick A. Townson,
“The Great Fire”,
Telecom Digest, vol.8 iss.76, 10 May 1988,
available in comp.dcom.telecom and included in http://massis.lcs.mit.edu/archives/history/fire.in.chicago.5-88

Hurricanes

ISER2005k]
Hurricane Katrina,
Infrastructure Security and Energy Restoration, U.S. Department of Energy,
http://www.oe.netl.doe.gov/hurricanes_emer/katrina.aspx
[CP+2005]
James Cowie, Alin Popescu, and Todd Underwood,
Impact of Hurricane Katrina on Internet Infrastructure,
Renesys report, Sep. 2005, available from http://www.renesys.com/resource_library/Renesys-Katrina-Report-9sep2005.pdf

Power Grid Failures

[MR+2004]
David H. Meyer, Thomas Rusnov, Alison Silverstein, et. al,
Final Report on the August 14, 2003 Blackout in the United States and Canada, U.S.–Canada Power Shystem Outage Task Force, Apr. 2004,
available from https://reports.energy.gov/BlackoutFinal-Web.pdf
[CO+2004]
James H. Cowie, Andy T. Ogielski, BJ Premore, Eric A. Smith, and Todd Underwood,
Impact of the 2003 Blackouts on Internet Communications, preliminary report,
Renesys, Nov. 2003 updated Mar. 2004,
available from http://www.renesys.com/resource_library/Renesys_BlackoutReport.pdf

3. Project

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.


Grades and Academic Integrity

Grading

EECS 800 Grading
weightcomponent
25%midterm exam
20%class participation (other than leading discussions)
20%paper presentation and discussion leadership
35%final project and report

Academic Integrity and Plagiarism

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.1Lynx inspectedW3C AAA Conformance
©2005 James P.G. Sterbenz <jpgs@eecs.ku.edu>