survivable and disruption tolerant networking
TRANSCRIPT
![Page 1: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/1.jpg)
James P.G. SterbenzSurvivable and Disruption Tolerant Networking
Issues, Challenges, and Research Directions
James P.G. SterbenzLancaster University Computing Department, UK
University of Massachusetts Department of Computer Science, [email protected]+1 508 944 3067
http://www.sterbenz.org/jpgs/sumowin
Rajesh KrishnanBBN Technologies, USA
© 2003–2004 James P.G. Sterbenz7 February 2005Supported in part by DARPA contracts F30602-99 C-0131, N66001-97-D-8622 NASA contract NAS3-99175
![Page 2: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/2.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 2
James P.G. Sterbenz
Survivability & Disruption ToleranceAbstract
This presentation surveys the issues and challenges in enhancing network survivability and providing application-to-application disruption tolerance, with emphasis on mobile wireless and long-delay communication. Conventional fault tolerance methods are necessary but not sufficient for survivability, since failures due to a coordinated attack are not random. Interlayer awareness (knobs and dials) is required for lower layers to convey their state upward, and for users and upper layers to exert influence downward.
A systematic approach is required on three levels:1. Survivable network architectures that:
• establish and maintain survivable topologies that strive to keep the network connected even under attack• design for communication in challenging environments in which the path from source to destination is not wholly
available at any given instant in time; this requires new routing and forwarding mechanisms• the use of technology to enhance survivability such as adaptive networks and satellites
2. End-to-end (transport) protocols that are able to deal with weak, intermittent, and episodically connected and asymmetric channels, and are able to properly respond to channel-induced errors.
3. Adaptive applications that rely on knobs and dials from the network through the application to allow the user to influence the behaviour of the application based on network conditions, to best deal with and mask disruptions and delay.
We describe some of the issues and potential research directions to address each of these areas, and briefly present some example research projects.
![Page 3: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/3.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 3
James P.G. Sterbenz
Survivability & Disruption Tolerance Outline
• Introduction to survivability and disruption tolerance– definitions, motivation, threats– environment: wireless, mobility, latency– challenges and assumptions
• Survivability and disruption tolerance strategy– network survivability
1. maintain survivable connectivity when possible2. survivable communication even when not connected3. technologies to enhance survivability
– end-to-end survivability and disruption tolerance– disruption-tolerant user-controlled adaptive applications
• Summary
![Page 4: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/4.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 4
James P.G. Sterbenz
Survivability & Disruption Tolerance Definitions
Survivability is the capability of a systemto fulfill its mission in a timely manner,
even in the presence of attacks or failures [CMU SEI]
Disruption toleranceis the ability for end-to-end applications to operate
even when network connectivity is not strong(weak, episodic, or asymmetric)
and the network is unableto provide stable end-to-end paths [JPGS]
![Page 5: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/5.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 5
James P.G. Sterbenz
Survivability & Disruption Tolerance Motivation and Threats
• Network & applications should remain operational– when the network is under attack– particularly critical and lifeline services
note: we can’t depend on the Internet for this today• Attacks against the physical infrastructure
– natural disasterse.g. hurricanes, earthquakes, ice storms, tsunami, floods
– targetted attacks (terrorism or warfare)• Attacks against protocol and software infrastructure
– recreational crackers: denial of service– industrial espionage and sabotage– cyber-terrorism and information warfare
![Page 6: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/6.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 6
James P.G. Sterbenz
Communication EnvironmentImpact of Wireless Channel
• Open channel subject to attack– eavesdropping
• network and traffic analysis– interference
• jamming and denial of service– injection of bogus signalling and control messages
• Weak, intermittent, and episodic connectivity– limited bandwidth of shared medium– time-varying available bandwidth
• noise, weather (latter for free-space laser as well as RF)– episodic connectivity
• channel fades between bit errors & failed links in consequence• difficult to achieve routing convergence
![Page 7: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/7.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 7
James P.G. Sterbenz
Communication EnvironmentImpact of Mobility
• Dynamic nodes and topologies– changing links, clustering, and federation topology– difficult to achieve routing convergence
• Control loop delay– mobility may exceed ability of control loops to react
• QOS
1
![Page 8: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/8.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 8
James P.G. Sterbenz
Communication EnvironmentImpact of Mobility
• Dynamic nodes and topologies– changing links, clustering, and federation topology– difficult to achieve routing convergence
• Control loop delay– mobility may exceed ability of control loops to react
• Impacts QOS– changes in inter-node distance
• requires power adaptation• changes density and impacts degree of connectivity
– latency issues (routing optimisations temporary)
2
![Page 9: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/9.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 9
James P.G. Sterbenz
Communication EnvironmentImpact of Mobility
• Dynamic nodes and topologies– changing links, clustering, and federation topology– difficult to achieve routing convergence
• Control loop delay– mobility may exceed ability of control loops to react
• Impacts QOS– changes in inter-node distance
• requires power adaptation• changes density and impacts degree of connectivity
– latency issues (routing optimisations temporary)
3
![Page 10: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/10.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 10
James P.G. Sterbenz
Communication EnvironmentImpact of High Latency
• Long inter-application delay– long path (c) or store-and-forward queueing– appears to be a disruption for interactive applications– latency masking techniques mitigate: caching, prefetching
• but don’t always help
• Severely impacts transport and network protocols– signalling latencies dominate (at high data rates) – very long control loops
• long delays may cause data transfer to stall (window-based)• wrapped sequence number spaces
– high-bandwidth-×-delay products• real-time reaction to many bits in flight difficult or impossible• massive buffering required for error control
![Page 11: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/11.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 11
James P.G. Sterbenz
Survivability & Disruption ToleranceAssumptions and Challenges1
• Problem cannot be solved at physical and link layers– assume that best physical, MAC, link techniques in use– diminishing returns on further research
• Strong connectivity will not always be achievable– economics and policy preclude connectivity everywhere
• faraday cages for security• caves• nomadic hunters in northern Sweden; search and rescue in UK
• Network / security infrastructure may be unavailable– node failure or overrun (capture)– radio silence or jammed channel (enemy, cracker, DDOS)– compromised node software
![Page 12: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/12.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 12
James P.G. Sterbenz
Survivability & Disruption Tolerance Assumptions and Challenges2
• Very long delay inevitable in some scenarios– path (speed of light) latency
• satellite links• interplanetary (and intergalactic?) Internet
– object transmission delay• large objects over modest data rates• weakly connected and congested links
– store-and-forward over episodically connected paths• Security and survivability are not binary choices
– level of security must be traded against resource cost …• limited node power• limited channel bandwidth
… based on application requirements and user desires
![Page 13: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/13.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 13
James P.G. Sterbenz
Survivability & Disruption Tolerance Requirements and Goals
• Survivability goals for network– resistance to attack– recognition when attack has occurred– recovery from attack after occurrence– refinement in future response to attack
• Disruption tolerance goals for applications– access to information by the user or application
• e.g. Web browsing
– maintenance of end-to-end communication association• e.g. video- or teleconference
![Page 14: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/14.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 14
James P.G. Sterbenz
Survivability & Disruption Tolerance Beyond Fault Tolerance and Cryptography
• Fault models do not hold under malicious attack– we cannot assume independence and random failures– therefore, fault tolerance is necessary, but not sufficient
• Cryptography does not ensure survivability– threat of traffic flow analysis leading to attack
• when data encrypted control (signalling, headers) typically not• signal processing can extract information from encrypted data
– control plane and physical infrastructure attacks• unauthenticated signalling• unencrypted packet headers
![Page 15: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/15.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 15
James P.G. Sterbenz
Survivability & Disruption Tolerance Mobile, Wireless, and High Latency
• Traditional communication models– are not survivable even in wired network
• redundancy not geographically diverse
– adapt to episodic connectivity as faults …… that must be recovered
• Are not survivable…– when mobility exceeds reactivity of traditional control loops– when channel conditions don’t allow end-to-end path– with links highly asymmetric or unidirectional– when routing protocols rarely or never converge
![Page 16: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/16.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 16
James P.G. Sterbenz
Survivability & Disruption Tolerance Attacking the Problem
• New way of thinking needed– expect challenging channel environments– expect and exploit mobility– expect, mask, and adapt to high latency
• Attack problem at all levels1 robust physical channels2 robust links and survivable MAC3 survivable networks4 disruption tolerant end-to-end protocols7 adaptive user-controlled applications
• Need– interlayer awareness and control (knobs and dials)– intelligent resource & constraint tradeoffs (P, M, B, E, L)
![Page 17: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/17.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 17
James P.G. Sterbenz
Survivability & Disruption Tolerance Network Survivability
• Introduction to survivability and disruption tolerance• Survivability and disruption tolerance strategy
– network survivability1. establish & maintain survivable connectivity when possible2. survivable communication even when not connected3. technologies to enhance survivability
– end-to-end survivability and disruption tolerance– disruption-tolerant user-controlled adaptive applications
• Summary
![Page 18: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/18.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 18
James P.G. Sterbenz
Survivable ConnectivityNetwork Establishment
• Establishment of network structure and connectivity– secure auto-configuration and self-organisation– all infrastructure protocols and signalling must be
• secure and resistant to attack• authenticated
– use infrastructure when available …• name servers• PKI, CA…
– … but don’t depend on it: take local actions when necessary
• Maintain connectivity when practical– without sacrificing other requirements
![Page 19: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/19.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 19
James P.G. Sterbenz
Network Self-OrganisationNeighbour Discovery
• Nodes emit beacons to announce their presence– known frequencies and codes used for announcements
• Establishes set of directly reachable nodes
![Page 20: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/20.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 20
James P.G. Sterbenz
Network Self-OrganisationLink Formation
• Pairwise negotiation of link formation– interested nodes answer beacons– exchange identification, node and link characteristics– layer 2 connectivity structure
• Maintain link adjacencies– e.g. keepalive messages
![Page 21: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/21.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 21
James P.G. Sterbenz
Network Self-OrganisationSelf-Organisation and Federation
leaderless cluster abstractionor peer group leader
• Communicating nodes self-organise into federations– address acquisition– hierarchical cluster formation and leader election
• based on administrative concerns, security, role/task based
– bootstrap routing topology
![Page 22: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/22.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 22
James P.G. Sterbenz
Network Self-OrganisationTopology Optimisation and Maintenance
• Topology maintenance of federations– merge/split
• group mobility, dynamic coalitions
– heal partition
![Page 23: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/23.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 23
James P.G. Sterbenz
Network Self-OrganisationTopology Optimisation and Maintenance
leave then join
• Topology maintenance of nodes– node mobility– leave/join from/to federation– resolution to identifier vs. topological address reassignment
![Page 24: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/24.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 24
James P.G. Sterbenz
Survivable ConnectivityEstablishment and LPD
• Low probability of detection (LPD)– low transmission power to limit detection– stealthy network is more resistant to attack …
… but stealth makes legitimate communication difficult
![Page 25: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/25.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 25
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission Power
1
![Page 26: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/26.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 26
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity
2
![Page 27: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/27.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 27
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity
3
![Page 28: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/28.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 28
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity
4
![Page 29: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/29.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 29
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity
5
![Page 30: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/30.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 30
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity
6
![Page 31: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/31.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 31
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity• partitioned islands
7
![Page 32: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/32.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 32
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity• partitioned islands
8
![Page 33: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/33.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 33
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity• partitioned islands
9
![Page 34: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/34.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 34
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity• partitioned islands
10
![Page 35: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/35.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 35
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity• partitioned islands
11
![Page 36: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/36.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 36
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity• partitioned islands
12
![Page 37: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/37.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 37
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
• Transmission power– low:
• no connectivity• partitioned islands
13
![Page 38: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/38.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 38
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
14
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected
![Page 39: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/39.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 39
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
15
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected
![Page 40: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/40.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 40
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
16
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
![Page 41: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/41.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 41
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
17
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
![Page 42: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/42.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 42
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
18
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
![Page 43: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/43.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 43
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
19
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 44: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/44.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 44
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
20
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 45: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/45.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 45
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
21
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 46: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/46.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 46
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
22
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 47: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/47.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 47
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
23
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 48: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/48.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 48
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
24
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 49: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/49.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 49
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
25
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 50: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/50.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 50
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
26
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth
![Page 51: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/51.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 51
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Transmission Power
27
• Transmission power– low:
• no connectivity• partitioned islands
– sufficient• connected• biconnected
– excessive• lack of stealth• highly connected:
self jamming“parking lot problem”
![Page 52: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/52.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 52
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Adaptive Power
• Adaptive transmission power– each node adjusts– control number of neighbors:
degree of connectivity
• Biconnected graph– single link cut avoids partition
• May be more stealthy– in cases of lower transmission power
• Omnidirectional antennæ
![Page 53: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/53.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 53
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Directional Antennæ
• Directional antennæ focus– transmission into sector– increase spatial reuse
• Reduced transmission– with better connectivity
• Increased complexity in:– antenna design– node discovery– MAC protocols (steering)– mobility tracking
1
![Page 54: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/54.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 54
James P.G. Sterbenz
Survivable ConnectivityTopological Connectivity: Directional Antennæ
• Directional antennæ– focus transmission into sector– increase spatial reuse
• Reduced transmission power– with better connectivity
• Increased complexity in:– antenna design– node discovery– MAC protocols (steering)– mobility tracking
• Increased stealth– assuming receiver locations known 2
![Page 55: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/55.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 55
James P.G. Sterbenz
Network Survivability StrategySurvivable Communication
• Introduction to survivability• Survivability strategy
1. establish/maintain survivable connectivity when possible2. survivable communication even when not well connected
– expect weak and episodic connectivity– expect and exploit mobility
3. technologies to enhance survivability
• Summary
![Page 56: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/56.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 56
James P.G. Sterbenz
Communication BackgroundNetwork Layer Service and Interfaces
• Network layer 3 is above link layer 2– addressing : network layer identifier for end systems (hosts)– forwarding : transfers packets hop-by-hop
• using link layer services• network layer responsible for determining which next hop
– routing : determination of path to forward packets– signalling : messages to control network layer behaviour– traffic management : management of traffic and congestion
• Network layer service to transport layer (L4)– deliver TPDUs to destination transport entity
![Page 57: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/57.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 57
James P.G. Sterbenz
Communication BackgroundForwarding vs. Routing
• Forwarding transfers packets hop-by-hop– each switch (router) makes decision on which link to send– forwarding table (generally) used to make decision– forwarding is per packet decision– [analogy: determining which exits to take on a drive]
• Routing determines the path to take– routing algorithm [lecture R] independent of forwarding– forwarding table entries populated by routing– routing is (generally) not done per packet– [analogy: planning trip from source to destination]
Forwarding and routing are very different
![Page 58: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/58.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 58
James P.G. Sterbenz
Communication BackgroundFast IP Datagram Switch Architecture
• Routing– loads prefix table
• Input processing– packet classification – IP lookup
• Switch fabric– port interconnection
• Output processing– packet scheduling
input processing
management routing and signalling
switch fabric
classify
output processing
output scheduling
link
headerupdate
prefixesinput
processor
link
prefixesinput
processor
link
output scheduling
link
switch fabric control
![Page 59: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/59.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 59
James P.G. Sterbenz
Non-Survivable CommunicationRouting Convergence and Mobility
• Current routing algorithms assume eventual stability– converge to stable communication paths– complete end-to-end path must exist at some point in time– link outage treated as fault that must be repaired
• Moderate mobility is tolerated as a topology change
![Page 60: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/60.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 60
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
source
destination
• Among possible links
1
![Page 61: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/61.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 61
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• Among possible links– network is formed– biconnected if possible
2
![Page 62: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/62.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 62
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• Among possible links– network is formed– biconnected if possible
3
![Page 63: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/63.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 63
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
silent
interference oreavesdropping
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
4
![Page 64: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/64.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 64
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
5
![Page 65: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/65.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 65
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
• Routing algorithms recompute and converge
6
![Page 66: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/66.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 66
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
• Routing algorithms recompute and converge– (complete) source → destination path exists
7
![Page 67: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/67.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 67
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
• Routing algorithms recompute and converge– (complete) source → destination path exists– data can be transferred along path (as long as stable) 8
![Page 68: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/68.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 68
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
• Routing algorithms recompute and converge– (complete) source → destination path exists– data can be transferred along path (as long as stable) 9
![Page 69: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/69.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 69
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
• Routing algorithms recompute and converge– (complete) source → destination path exists– data can be transferred along path (as long as stable) 10
![Page 70: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/70.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 70
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
• Routing algorithms recompute and converge– (complete) source → destination path exists– data can be transferred along path (as long as stable) 11
![Page 71: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/71.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 71
James P.G. Sterbenz
Non-Survivable CommunicationEventual Stability: Wait for Complete Path
• While interference or suspected eavesdropping…– routing can’t converge on a source → destination path
• Routing algorithms recompute and converge– (complete) source → destination path exists– data can be transferred along path (as long as stable) 12
![Page 72: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/72.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 72
James P.G. Sterbenz
Survivable CommunicationRouting Convergence
• Need to assume weak and episodic connectivity– routine occurrence for which network is designed
• Survivable communication: eventual connectivity– communicate as far as possible, whenever possible– hold data when necessary (store-and-forward)
• deflection when necessary (buffer limitations)
– schedule transmission for optimum LPI/LPD and energy– optimise for eventual stability when possible
• avoid store-and forward avlidance– when stable path is available
• cut-through switches
![Page 73: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/73.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 73
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
directionalxmit only
silent
interference
omnixmit
source
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing
1
![Page 74: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/74.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 74
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible
2
![Page 75: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/75.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 75
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
3
![Page 76: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/76.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 76
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
directionalxmit only
silent
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
4
![Page 77: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/77.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 77
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
5
![Page 78: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/78.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 78
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
6
![Page 79: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/79.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 79
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
7
![Page 80: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/80.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 80
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
8
![Page 81: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/81.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 81
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
9
![Page 82: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/82.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 82
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interferenceinterference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
10
![Page 83: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/83.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 83
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
11
![Page 84: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/84.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 84
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
12
![Page 85: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/85.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 85
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
13
![Page 86: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/86.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 86
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
14
![Page 87: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/87.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 87
James P.G. Sterbenz
Survivable CommunicationEventual Connectivity
interference interference
• Multiple interferences or suspected eavesdroppers– prevent an end-to-end path from ever existing– transfer data as far as possible– store-and-forward when necessary
15
![Page 88: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/88.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 88
James P.G. Sterbenz
Survivable CommunicationExpect Mobility
• Routing and forwarding expect mobility– use location and trajectory information when available– direct information to expected location
![Page 89: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/89.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 89
James P.G. Sterbenz
Survivable CommunicationExpect Mobility
destination
source
• Routing and forwarding expect mobility• Use location/trajectory information where available
– unicast when predictable (e.g. planetary or racetrack UAV)
1
![Page 90: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/90.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 90
James P.G. Sterbenz
Survivable CommunicationExpect Mobility
destination
source
• Routing and forwarding expect mobility• Use location/trajectory information where available
– unicast when predictable (e.g. planetary or racetrack UAV)
2
![Page 91: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/91.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 91
James P.G. Sterbenz
Survivable CommunicationExpect Mobility
destination
source
• Routing and forwarding expect mobility• Use location/trajectory information where available
– unicast when predictable (e.g. planetary or racetrack UAV)– multicast to area of expected location (spray routing)
3
![Page 92: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/92.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 92
James P.G. Sterbenz
Survivable CommunicationExpect Mobility
destination
source
• Routing and forwarding expect mobility• Use location/trajectory information where available
– unicast when predictable (e.g. planetary or racetrack UAV)– multicast to area of expected location (spray routing)
4
![Page 93: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/93.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 93
James P.G. Sterbenz
Survivable CommunicationExpect Mobility
destination
source
• Routing and forwarding expect mobility• Use location/trajectory information where available
– unicast when predictable (e.g. planetary or racetrack UAV)– multicast to area of expected location (spray routing)
• cluster may have inherent broadcast or epidemic routing 5
![Page 94: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/94.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 94
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
• Position node/antenna for survivability– use trajectory information when available– exert control on movement of other nodes
• Node can carry data as they move– store-and-haul data without radiating transmissions – transit areas of no channel connectivity
![Page 95: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/95.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 95
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
source
• Multiple interferences or suspected eavesdroppers
1
![Page 96: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/96.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 96
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Multiple interferences or suspected eavesdroppers
2
![Page 97: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/97.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 97
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Multiple interferences or suspected eavesdroppers
3
![Page 98: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/98.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 98
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
movesteer
• Move nodes and steer antenna around interference
4
![Page 99: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/99.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 99
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
movesteer
• Move nodes and steer antenna around interference
5
![Page 100: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/100.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 100
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference
6
![Page 101: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/101.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 101
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference
7
![Page 102: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/102.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 102
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference
7
![Page 103: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/103.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 103
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference
8
![Page 104: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/104.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 104
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
• Move nodes and steer antenna around interference
9
interferenceinterference
![Page 105: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/105.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 105
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference
10
![Page 106: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/106.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 106
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference
11
![Page 107: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/107.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 107
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
store-and-haul
• Move nodes and steer antenna around interference• Mobile nodes haul data without radiating
– interference and adversary node avoidance– transit disconnectivity
12
![Page 108: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/108.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 108
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
store-and-haul
• Move nodes and steer antenna around interference• Mobile nodes haul data without radiating
– interference and adversary node avoidance– transit disconnectivity
13
![Page 109: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/109.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 109
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference• Mobile nodes haul data without radiating
– interference and adversary node avoidance– transit disconnectivity
14
![Page 110: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/110.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 110
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
interferenceinterference
• Move nodes and steer antenna around interference• Mobile nodes haul data without radiating
– interference and adversary node avoidance– transit disconnectivity
15
![Page 111: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/111.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 111
James P.G. Sterbenz
Survivable CommunicationExploit Mobility
• Move nodes and steer antenna around interference• Mobile nodes haul data without radiating
– interference and adversary node avoidance– transit disconnectivity
16
interferenceinterference
![Page 112: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/112.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 112
James P.G. Sterbenz
Survivable CommunicationAdjust Data Transfer to Knowledge
• Opportunistic …– epidemic routing protocols– transfer data when links are available and nodes reachable
… but scoped and scheduled to: – reduce load while maintaining probability of delivery– reduce offered load to network while maintaining goodput
• Exert control on:– node and subnetwork movement– protocol and parameter choices– layer 2 connectivity and layer 3 federation topology
Opportunistic worst case bound; exploit knowledge to improve
![Page 113: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/113.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 113
James P.G. Sterbenz
Survivable CommunicationAdjust Data Transfer to Environment
• Cut-through (when stable path available)– lowest latency for nodes that are capable– exploit “traditional” physical layer techniques
• Store-and-forward– immediate when link available to next node & empty queues– move data burst to other nodes for load balancing
• Store and forward with scheduled transfer – wait until link available to next node– new physical layer opportunities for burst transfer
• Store-and-haul data
Design for eventual connectivity, optimize for eventual stability
![Page 114: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/114.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 114
James P.G. Sterbenz
Network Survivability StrategySurvivability Technologies
• Introduction to survivability• Survivability strategy
1. establish/maintain survivable connectivity when possible2. survivable communication even when not connected3. technologies to enhance survivability
– adaptive and agile networking– satellite and airborne nodes
– end-to-end disruption tolerance– user controlled adaptive applications
• Summary
![Page 115: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/115.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 115
James P.G. Sterbenz
Survivability TechnologiesAdaptive and Agile Networking
• Adaptive networking at all layers– physical layer transmission and coding
• beamform, waveform, and frequency agility– MAC protocols and parameters– network routing, signalling, and addressing
• geographical, topological, and characteristics-based– end-to-end protocols
• Enabled in systematic manner by– software radios, DSPs, and agile wideband RF tranceivers– active networking technology
• protocols and algorithms dynamically provisioned• don’t need to standardise a network and MAC protocol
– but rather a framework for negotiation
![Page 116: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/116.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 116
James P.G. Sterbenz
Survivability Technologies DARPA Active Node Architecture
MAAs
MEE
NodeOS
switch fabric
EEs
AAs AAs AAs
linkMAC
physicaltransmit
linkMAC
physicalreceive
![Page 117: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/117.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 117
James P.G. Sterbenz
Survivability Technologies Mobile Wireless Active Node Architecture
MAAs
MEE
NodeOS
switch fabric
EEs
AAs AAs AAs
linkMAC
physicaltransmit
linkMAC
physicalreceive
dynamicprotocol/algorithm
loading
dynamicenvironment sensing
andwaveform/code/MAC
receiver selection
![Page 118: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/118.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 118
James P.G. Sterbenz
Survivability TechnologiesSatellites and Airborne Nodes
• High altitude vehicles (satellites and airborne nodes)– less subject to line-of-sight obstructions– less susceptible to attack
• Large transmission footprint– inherent broadcast– connect disconnected islands
• inter-island relay
– mitigates node mobility• transparent within
footprint
![Page 119: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/119.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 119
James P.G. Sterbenz
Survivability Technologies Airborne Information Dissemination
• Broadcast information dissemination– routing and topology updates– name services– certificates and CRLs
• Datacycle– supports radio silence– resists traffic analysis
disconnected island radio silent nodes
datacyclebroadcast
![Page 120: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/120.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 120
James P.G. Sterbenz
Survivability TechnologiesSatellites and Airborne Nodes
• Disadvantages– expensive and infrequent deployment– difficult to upgrade satellites
• software upload• space shuttle mission for hardware & transmitter replacement
– high transmission power required for uplink• mitigated by directional spot beam to known location
– satellite– racetrack-path UAV (unpiloted aerial vehicle)
![Page 121: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/121.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 121
James P.G. Sterbenz
Survivability & Disruption ToleranceEnd-to-End Survivability & Disruption Tolerance
• Introduction to survivability and disruption tolerance– definitions, characteristics– assumptions, requirements
• Survivability and disruption tolerance strategy– network survivability
1. maintain survivable connectivity when possible2. survivable communication even when not connected3. technologies to enhance survivability
– end-to-end survivability and disruption tolerance– disruption-tolerant user-controlled adaptive applications
• Summary
![Page 122: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/122.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 122
James P.G. Sterbenz
E2E Survivability and DTInternet Transport Protocols
• Current transport protocols assume– strongly connected stable end-to-end paths– symmetric path– reliable medium
• TCP and SCTP– combined feedback error+flow+congestion control
• reliable ACK stream required for self-clocking
– unable to discriminate channel loss from congestion• congestion indicated by loss (switch drops)• channel loss results in throttling source
– wrong response in uncongested network
![Page 123: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/123.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 123
James P.G. Sterbenz
E2E Survivability and DTKnobs and Dials
dials knobs
transport protocol
ganged
interrupt/upcall polled
network
service requirements
network and channel
characteristics
• Transport protocols should interact with network– dials feed back topology and path characteristics– knobs influence lower layer parameters and behaviour– example: error control based on loss characteristics
![Page 124: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/124.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 124
James P.G. Sterbenz
E2E Survivability and DTAsymmetric Paths
• Asymmetric channels result from– asymmetric transmission power
• intentional (LPD) or available power– antenna characteristics and directionality– terrain and location
• Unidirectional channels result from – asymmetric transmission power– radio silence
• Path connectivity may be episodic• Asymmetric and unidirectional E2E
– concatenation of channels– forward and reverse may follow different paths
![Page 125: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/125.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 125
James P.G. Sterbenz
E2E Survivability and DTAsymmetric End-to-End Paths
• Asymmetric end-to-end path challenges– how to find best paths through network– how to characterise entire path
strong symmetric
strong asymmetric
weak symmetric
episodic symmetric
episodic asymmetric
strong unidirectional
episodic unidirectional
![Page 126: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/126.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 126
James P.G. Sterbenz
E2E Survivability and DTBidirectional Paths
• Bidirectional path required for– pairwise synchronisation
• signalling messages
– bidirectional data communication• application issue
– closed-loop feedback control• ACKs for reliable data transfer• even if data transfer unidirectional
![Page 127: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/127.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 127
James P.G. Sterbenz
E2E Survivability and DTOpen Loop Control
• Survivability with asymmetric channels needs: – open-loop control– with feedback only when necessary
• Open-loop rate control– congestion feedback from
network only when necessary
![Page 128: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/128.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 128
James P.G. Sterbenz
E2E Survivability and DTOpen Loop Error Control
• Open-loop error control: FEC– unreliable transfer
• optional per link FEC
– quasi-reliable transfer• FEC for probabilistic reliability
– reliable transfer• requires bi-directional path• infrequent adaptive selective ACKs• distinct from:
– flow control (E2E) – congestion control
note: SCTP does none of this
![Page 129: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/129.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 129
James P.G. Sterbenz
E2E Survivability and DTEnd-to-End Transport Mechanisms
• Flow control– rate that receiver can accept– purely end-to-end
• Congestion control– rate that network can accept without congesting– network feedback to end systems
• Error control– retransmission of corrupt and lost packets– link and network-based error characteristics– application-dependent reliability requirements
![Page 130: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/130.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 130
James P.G. Sterbenz
E2E Survivability and DTExplicit Loss/Congestion/Delay Discrimination
• Absence of expected packet or ACK arrival– three distinct and unrelated causes:
1. Congestion: packet dropped in network– congestion control: queue overflow (tail drop)– congestion avoidance: intentional packet drop
2. Corruption: packet lost or delivered corrupted– channel error causing bit errors
3. Delay: packet arrival later than expected– store-and-forward delays in disruption tolerant network– long path
• speed-of-light delay in delay-tolerant network• very long path around disruption
![Page 131: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/131.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 131
James P.G. Sterbenz
E2E Survivability and DTDiscrimination and Explicit Notification
• Discrimination and proper response essential:– congestion ⇒ back off– corruption ⇒ retransmit– delay ⇒ wait or
retransmit via lower delay path
• Explicit notification– ECN: explicit congestion notification– ELN: explicit loss notification (due to corruption)– ELN cannot be determined from ECN (and vice versa)
• packet that first causes congestion may then be corrupted
![Page 132: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/132.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 132
James P.G. Sterbenz
E2E Survivability and DTError Control Mechanisms
• Mechanisms– observation that error has occurred (detection)– notification of error– decision on what response to take– action to correct error
• Taxonomy of mechanisms– each mechanism may have different implementations…
…(e.g. E2E vs. HBH)……but they are frequently related
• ETEN: explicit transport error notification
![Page 133: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/133.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 133
James P.G. Sterbenz
ETEN TaxonomyDeterminism and Granularity
• Determinism– deterministic (take action based on specific corruptions)– probabilistic (e.g. throttle source x% of the time)
• Granularity– PETEN: per packet response– CETEN: cumulative error rate response
• Control feedback …• Control locus …• Control band …• Control direction …
![Page 134: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/134.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 134
James P.G. Sterbenz
ETEN Taxonomy Control Feedback
ACK
sender Nn
sender n N
senderFEC
• Closed loop feedback from notifier nodes {n,N}– (N)ACK from end system or switch (e.g. congestion drop)
• Open loop– Unreliable or FEC for statistical reliability, rate control
• Hybrid open + closed loop– FEC for statistical reliability + (N)ACKs as needed
![Page 135: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/135.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 135
James P.G. Sterbenz
ETEN Taxonomy Control Locus
ETEN
sender N
• End-to-end– no changes to network infrastructure
ETEN
sender n Nnn n
• Some hop-by-hop– deployed as needed (e.g. optional n at wireless access links)
ETEN
sender N NNN N
• All hop-by-hop (N indicates required notifier functionality)
– deployment challenges: impractical for Internet as a whole
![Page 136: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/136.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 136
James P.G. Sterbenz
ETEN Taxonomy Control Band
ETENsender Nn
ACK/ETEN
• In-band– ETEN information carried by packets; options:
• corrupted packets not dropped but marked (violates RFC 1812)• carried by subsequent packets in flow (header field or option)
• Out-of-band– ETEN signalling messages
• may be forward or backward
ETENsender Nn
![Page 137: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/137.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 137
James P.G. Sterbenz
ETEN Taxonomy Control Direction
ETEN
sender Nn
• Backward– ETEN messages returned by switches
• out-of-band unless inserted in reverse flow• requires HBH ETEN
ETENsender Nn
• Forward– ETEN forwarded to receiver; turned back to sender
• may be in- or out-of band• longer delay in response for interactive over high bw-×-delay
![Page 138: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/138.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 138
James P.G. Sterbenz
ETEN SimulationTCP with Oracle ETEN
• TCP Oracle ETEN– instantaneous notification of corruption-based loss– perfect per packet loss discrimination– perfect response: retransmit rather than throttle
• if loss within RTO
– upper bound of possible benefit for bulk traffic• does not cause immediate retransmission:
would matter for transactions but not for bulk transfer
• Simulation– ns-2 FullTcpSack– 536B segments, 30 min. runs
![Page 139: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/139.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 139
James P.G. Sterbenz
ETEN SimulationTCP with Oracle ETEN
LTN:250ms 1-way1.5Mb/s
single flow
30 min. run536B segment2400 seg window
1.E+03
1.E+04
1.E+05
1.E+06
1.E-11 1.E-10 1.E-09 1.E-08 1.E-07 1.E-06 1.E-05
Bit Error Rate
Goo
dput
[B/s
]
OracleSACK
![Page 140: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/140.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 140
James P.G. Sterbenz
ETEN SimulationTCP with Oracle ETEN
1.E+03
1.E+04
1.E+05
1.E+06
1.E-11 1.E-10 1.E-09 1.E-08 1.E-07 1.E-06 1.E-05
Bit Error Rate
Goo
dput
[B/s
]
OracleSACK
LTN:250ms 1-way1.5Mb/s
competing:4×UDPCBR 0.25Mb/son/offexp mean 0.5s
30 min. run536B segment2400 seg window
![Page 141: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/141.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 141
James P.G. Sterbenz
Survivability & Disruption ToleranceUser-Controlled Adaptive Applications
• Introduction to survivability and disruption tolerance– definitions, characteristics– assumptions, requirements
• Survivability and disruption tolerance strategy– network survivability
1. maintain survivable connectivity when possible2. survivable communication even when not connected3. technologies to enhance survivability
– end-to-end survivability and disruption tolerance– disruption-tolerant user-controlled adaptive applications
• Summary
![Page 142: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/142.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 142
James P.G. Sterbenz
Disruption Tolerant ApplicationsAdaptive with Knobs and Dials
dials knobs
application
ganged
interrupt/upcall polled
network path
QOS & service requirements
end-to-end path
characteristics
• Applications should adapt to and mask disruptions– dials provide feedback from end-to-end paths (& network)– knobs influence transport and network behaviour
• Delay translucency (not transparency)
![Page 143: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/143.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 143
James P.G. Sterbenz
Disruption Tolerant ApplicationsCommunication Association
• Recall: disruption tolerance goals for applications– information access by the user or application– end-to-end communication association
• Applications should adapt to path conditions– adaptive within modes
• e.g. frame rate and resolution based on available bandwidth
– adaptive between modes• e.g. video → audio → chat → messaging → email
• Driven by user preferences– e.g. tradeoff between frame rate and resolution
![Page 144: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/144.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 144
James P.G. Sterbenz
Disruption Tolerant ApplicationsInformation Access
• Recall: disruption tolerance goals for applications– information access by the user or application– end-to-end communication association
• User experience highly dependent on response time– interactive information access
• subsecondtargetresponse time
• 100 msidealresponse time
Latency [s]
Util
ity o
f Res
pons
e
real-time
Tr=0.1
interactive
deadline
Tr=1.0
best-effort1
0
![Page 145: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/145.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 145
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM Latency-Aware Web Browser
• Distributed information access– access information from remote locations– Web provides most common infrastructure
• web browser as client• HTTP as protocol
• WVM (Web VADE MECUM)– knobs and dials– user bahaviour emulation– prototype: Mozilla on Linux using IBM Research WBI toolkit
![Page 146: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/146.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 146
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM Knobs and Dials
• Dials– past response time tr history*– weak link connectivity (instantaneous rate ri to lighthouse)*– object size from server metadata– average end-to-end delay li + ls via probes to server– cached freshness* * implemented in prototype
• Knobs: application and user
server
WVM client lighthouse
wireline network
rs ri
ls li weak link
node
![Page 147: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/147.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 147
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM Dials – GUI
• Link color gives high level {fast, old, slow, unknown}
• Status bar indicates global and per link details– past response time– dynamic adjustment of weak link to lighthouse
![Page 148: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/148.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 148
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM User Influence Knobs
• Fetch action– left click: default
• get cached if available• profile based action
– right click gives options:• fetch definitive
refresh window whendefinitive copy arrives
• nonblocking fetchdefinitive copy in new window when available
• View menu selection– allows display of unmodified page (un-munge HTML)
![Page 149: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/149.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 149
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM Prototype Information Flow
userprofile
HTTP get
RTT, bw, connectivity
request
user
request editorset $ parms
store statistics
pass contentre-color URLs
response editor
browser local $
netprotstack
$Web
update
(miss ∨ old)∧ fetch
hitinfo +metadata
![Page 150: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/150.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 150
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM Proxy States
StronglyConnected
Dis-connected
WeaklyConnected
• serve from network and cache• aggressive preload and refresh
• serve from cache and network• controlled refresh and preload
• serve only from cache
• profile (all states)
states based on CODA
![Page 151: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/151.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 151
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM Profile and User Emulation
• All user requests pass through WVM• WVM builds a user-specific WVM-ProfileGraph
– tracks and represents user Web access pattern– nodes are URLs accessed; directed edges for traversal
• URL priority limits cache life and refresh bandwidth– nodes and edges fade using a decay formula
• Autonomic user emulation– graph is automatically traversed when fully connected– graph slowly/selectively traversed when weakly connected– cache kept fresh even when user away from client– cache is as fresh as possible after state change {weak|disc}– coarse-grained learning possible (e.g. daily schedule)
![Page 152: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/152.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 152
James P.G. Sterbenz
Disruption Tolerant ApplicationsExample: WVM Profile Graph
![Page 153: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/153.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 153
James P.G. Sterbenz
Survivability & Disruption ToleranceSummary
• Introduction to survivability and disruption tolerance– definitions, characteristics– assumptions, requirements
• Survivability and disruption tolerance strategy– network survivability
1. maintain survivable connectivity when possible2. survivable communication even when not connected3. technologies to enhance survivability
– end-to-end survivability and disruption tolerance– disruption-tolerant user-controlled adaptive applications
• Summary
![Page 154: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/154.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 154
James P.G. Sterbenz
Survivability & Disruption Tolerance Summary
• Attack problem at all levels:– physical, MAC, and link robustness and agility– network survivability– end-to-end survivability and disruption tolerance– disruption-tolerant user-controlled adaptive applications
• Beyond fault tolerance and crypto• Design for survivability and disruption tolerance
– expect challenging communication channel environment– expect and exploit mobility– expect, adapt, and mask high latency with user influence– interlayer awareness and control (knobs and dials)– intelligent resource & constraint tradeoffs (P, M, B, E, L)
![Page 155: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/155.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 155
James P.G. Sterbenz
Survivability & Disruption Tolerance Primary References
Available from http://ww.sterbenz.org/sumowinSUMOWIN/DTN
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 Wireless Security Workshop (WiSE) 2002, MobiCom Atlanta, GA, Sep. 2002, pp.31–40.
ETENRajesh 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, Oct. 2004, pp. 343–362.Rajesh Krishnan, Mark Allman, Craig Partridge, and James P.G. Sterbenz, Explicit Transport Error Notification (ETEN) for Error-Prone Wireless and Satellite Networks, BBN Technical Report 8333, Feb. 2002.
WVMJames 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.
Long latencyJames P.G. Sterbenz and Joseph D. Touch, High Speed Networking: A Systematic Approach to High-Bandwidth Low-Latency Communication, John Wiley Networking Council (A. Lyman Chapin technical editor), Apr. 2001
![Page 156: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/156.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 156
James P.G. Sterbenz
Survivability & Disruption Tolerance Acknowledgements
• DARPA– Doug Maughan* (SUMMOWIN)
– Rob Ruth* (GloMo)
– Jean Sholtz* (WiaB)
• NASA– William Ivancic
• UMass– Jim Kurose
• Lancaster University– David Hutchison
some of this work performed atBBN Technologies
• BBN– Mark Allman*
– Alden W. Jackson
– Ram Ramanathan
– Tushar Saxena*
– Martha Steenstrup*
– Fabrice Tchakountio
* former affiliation
![Page 157: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/157.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 157
James P.G. Sterbenz
Survivability & Disruption Tolerance Recent Presentation Venues
28 Apr 2004 Boston University18 Jun 2004 KTH, Stockhom, Sweden1 Oct 2004 Universität Tübingen, Germany2 Dec 2004 Lancaster University, UK
16 Dec 2004 University of Kansas (abridged)7 Feb 2005 Lancaster University, UK
![Page 158: Survivable and Disruption Tolerant Networking](https://reader030.vdocument.in/reader030/viewer/2022020703/61fb2f3e2e268c58cd5b27b0/html5/thumbnails/158.jpg)
7 February 2005 Survivable and Disruption Tolerant Networking 158
James P.G. Sterbenz
End of Foils