Towards the Future Internet A Survey of Challenges and Solutions in Research and Standardization 60 60 24 29 Internet Protocol Version 6 (IPv6) C Stream Control Transmission Protocol (SCTP) C RF RF Features of IPv6 Features of the SCTP Transport Protocol: p ‒ Simple header for efficient processing ‒ Reliable u t e e h n S ‒ Sufficient number of addresses -> better distribution for efficient routing ‒ Connection-oriented t o is ti a n TP er C n o S e P i ‒ Flow Label for easy flow identification -> Quality of Service ‒ Message-oriented t g C t T ex f a n o i ‒ Built-in security: IPsec is mandatory c Security: o s m s o A Challenges for Upper Layers: fr ‒ 4-way handshake on v6 ti IP ra o ig t ‒ Support for IPv6 and IPv4 (dual-stack) -> Migration Path M v4 ‒ Immune against flooding attacks IP ‒ Handling of multiple addresses -> Multi-Homing Path Redundancy by Multi-Homing g ‒ Handling of prefix changes -> Mobility n ‒ 1 association, n paths i m Deployment: ‒ Still works if up to n-1 paths break o H - i t ‒ Supported by all major operating systems ‒ Path monitoring by heartbeats l u ‒ Usable via tunnelling over IPv4, some providers already provide it directly! ‒ Fine-granular configuration M ss re og ‒ Per-association congestion control Pr n i Flow Routing rk g o Multi-Streaming n W i m Key Assumption of Classical Internet Routing: ‒ Up to 65,536 streams via single association a e r t ‒ Router memory is scarce and expensive => Stateless Packet Routing ‒ Useful e.g. for VoIP/multimedia trunks S - i t l ‒ ... but recent hardware is powerful and memory inexpensive! ‒ No head-of-line blocking u M New Approach: Flow Routing! Optional Extensions ‒ Per-flow state for routing ‒ Add-IP – Add/remove network addresses during association runtime ‒ May be used for QoS mechanisms Support for IPv6 prefix changes Our Idea for a Simple QoS Mechanism: Upgrade IPv4-only -> IPv4/IPv6 -> IPv6 only – without interrupting associations! Support for mobile endpoints ‒ Overload handling procedure: ‒ PR-SCTP – Timeout for retransmission (similar to UDP, but with congestion control!) Focus packet discard on “selected flows” Full quality for all other flows! ‒ Secure-SCTP – Built-in per-stream/per-message encryption and authentication ‒ Application: Delivery of multimedia content to broadband customers (e.g. DSL) Deployment: SCTP is available for all major operating systems now! Network Layer Transport Layer The Future Internet Session Layer Application Layer ! t d! rs r s fi da s 's n re F ta g T s ro IE er P he y Services using Reliable Server Pooling in Reliable Server Pooling T La k n or io W ss A Generic, Application-Independent Framework for Se SCTP-based Mobility SS7 and VoIP ‒ Server pool management and RSerPool Terminology Communication between two mobile endpoints: ‒ Session handling ●Pool Element (PE): Server RSerPool as lightweight address lookup service to support simultaneous “break before make” handovers! ●PE ID: Unique ID of PE Symmetric Scenario Key Features ● ●Pool Handle: Unique ID of pool GK PEs using MGC pool ●MGC PEs using GK Pool ‒ Lightweight ●Handlespace: Set of pools ●Registrar (PR) Pool management ‒ Real-Time ●Pool User (PU): Client ‒ Scalable ‒ Extendable RSerPool Protocols ‒ Simple ●ASAP (Aggregate Server Access Protocol) ●ENRP (Endpoint Handlespace Redundancy Protocol) “Make before Break”: New network available when old one gets unreachable Under Standardization by the IETF “Break before Make”: Old network gets unreachable before access to new one ‒ Reference implementation developed by us! Battlefield Networks Server Selection ‒ RFCs coming soon! Web Server Pools Application Development IPFIX Architecture with Availability in Mind Load Balancers RSerPool usage for ●Collector selection ... ●Failover support Real-Time Distributed Computing Overhead reduction by caching Protocol Stack Failover Support Simple and efficient Observation Point delivers statistics data to Collector. Limited local Usage of SCTP for storage capacity! ●Multi-homing RSerPool usage for ●Mobility support ●Server selection A Proof of Concept: ●Address handling ●Failover support Our RSerPool prototype demo system ●Security against DoS Flow Routing SCTP Reliable Server Pooling Our Contributions Open Source Prototype Implementation SCTPLIB Research Open Source Prototype Implementation RSPLIB Evaluation, Optimization and Improvement ‒ Novel approach for a simple QoS mechanism Evaluation, Optimization and Improvement for real-time multimedia content delivery to ‒ Path management of multi-homed associations broadband customers Various Contributions to Major IEEE Conferences ‒ Security Contributions to Standardization Contribution of Results into IETF Standardization Contribution of Results into IETF Standardization ‒ IETF (Flow Identification) ‒ 4 Working Group Drafts ‒ Secure-SCTP extension (Individual Submission) University of Duisburg-Essen ‒ 6 Individual Submissions To be RFCs soon! ‒ ITU-T (QoS Signalling) ‒ RFC 3436 (TLS over SCTP) Workshop on Visions of Future Network Generations 2007, Würzburg/Germany Thomas Dreibholz 6 July 2007.