Members Version 03/07 Principal Investigators Prof. David Hutchison Lancaster University Prof. James P. Sterbenz The University of Kansas, Lancaster University Members Chris Edwards Laurent Mathy Andreas Mauthe Andrew Scott David Andrews Weichao Wang Alex Wyglinski Marcus Schöller Paul Smith Manolis Sifalakis Linlin Xie Egemen Cetenkaya Daniel Fokum Abdul Jabbar Justin Rohrer Piyush Upadhyay Related Projects ANA Postmodern TA ResiliNets — Multilevel Resilient and Survivable Networking Initiative InfoLab21 Motivation Society increasingly relies on computer networks in general and the Internet in particular. Consumers rely on networks for access to information and services, personal finance, and for communication with others. The Internet has become indispensable to the routine operation of businesses and to the global economy. The military depends on network centric operations and warfare. Governments depend on networks for their daily operation, service delivery, and response to natural disaster and terrorist attacks. Therefore, we regard resilience and survivability as critical to the future of our network infrastructure. Resilience is the ability of the network to provide and maintain an acceptable level of service in the face of various challenges to normal operation. We aim to engineer a system to protect itself from these challenges and to recognize the impact autonomously if the defence could not isolate the effects. In this case the system services must self-organize themselves to remain accessible whenever possible and degrade gracefully when necessary. As soon as the challenge ended the system must automatically and rapidly recover from degradation to normal operation. To improve future operation of a resilient system, it has to learn from past incidents and refine its operational and defensive mechanism.

ResililNets StrategyResiliNets PrinciplesResiliNets Architecture Principles Service Requirements: need for resilience Normal Behaviour must be specified Threat and Challenge Models Metrics to measure and engineer resilience Resource Tradeoffs determine deployment Complexity understood and reduced Multilevel: layer, plane, network architecture Translucency: abstraction vs. interlevel visibility Trust and Policy relationship Redundancy in space and time Diversity: space, time, medium, and mechanism Self-Organising and Autonomic behaviour Security and Self-Protection State Management alternatives Connectivity and Association Context Awareness Adaptability to the network environment Evolvability to refine future behaviour Axioms: IUER Inevitability of Faults Understand Normal Operations Expect Adverse Events and Conditions Respond to the Adverse Events and Conditions Strategy: D 2 R 2 + DR Phase 1: Real-Time Control Loop – D 2 R 2 Defend challenges and threats to normal operation Detect when adverse event or condition has occurred Remediate effects to minimise the impact Recover to original and normal operations Phase 2: Background – DR Diagnose the fault that was the root cause Refine behaviour for the future D2R2 cycles Multilevel Protocol layer: Functionally composed with cross-layer controls Protocol plane: data, control, management Network architecture and engineering: network elements through topology to global net candidates for other stuff: mechanisms programmable autonomic node realms (compartments) modelling: net ops and service space…