Towards a Unified Internet Control Architecture Rolf Winter – Trilogy Project EuroView2008 A Unified Control Architecture Resource Reachability Load-dependent control multipath Re-feedback Traffic engineering Commercial & social control EuroView2008 1 July 21-22, 2008
A Unified Control Architecture Resource Reachability control Trilogy Trilogy Commercial & social control EuroView2008 2 July 21-22, 2008 A slim waist! Data plane Control plane phone email phone email WWW WWW Applications TCP UDP TCP UDP ? Mobility Multicast Trilogy IP Routing IP NAT IntServ IPSec ETH 802.11 ETH 802.11 radio copper fibre radio copper fibre Technologies The Internet “Love handles” New control hourglass architecture! Complexity! EuroView2008 3 July 21-22, 2008
Rest of the talk � What is wrong with the current Internet? � And what not � The Trilogy Approach � Goals � Thrusts � Unified architecture � Joint technical, economical and social control � Illustrations and Examples � Conclusions EuroView2008 4 July 21-22, 2008 What is wrong with the Internet? � The Internet works � Designed as a best effort service infrastructure � Dominant infrastructure today - data, voice, video, TV,… � But the Internet just works! � End user concerns � Security, privacy � Operational (business) concerns � Address spaces, routing limitations, debuggability, 5-nines � Technical challenges � Mobility, security � Lack of experimental opportunities � Experiment at scale (GENI) � New services, new features � Innovation is driven by people and applications (iPhone…) � Problems are fundamental, no more incremental patches EuroView2008 5 July 21-22, 2008
Fundamental challenges � Basic design principles � Architecture changed over 40 years � Mutual evolution of Internet and society � Reconsideration necessary � Critically review principles, check validity � Example: end-to-end principle: middleboxes; Spam/DDoS, … � Derive new / update design principles � Control plane � We know how to forward packets on a router � How do we allocate resources? � Who controls resources – and how? � Absolute control? Delegate control? Coordinate control? EuroView2008 6 July 21-22, 2008 Approach: a unified architecture � Reachability � Inter-domain routing: more Resource functionality, more devices Reachability � Convergence time are too high Control Trilogy � NATs, middleboxes break � Resource Control � End-system based (TCP) � Today abuse Commercial � Multiple TCP flows (p2p) & social � DDoS, Spam control � Commercial/social control � Stakeholders with different interests � Tussle over control Why jointly consider? EuroView2008 7 July 21-22, 2008
Why a unified architecture? Resource users Resource owners Secret??? Unfair ? TCP Skype Obfuscate Multi-conn. Port-selective DPI P2P, IDC Too slow packet dropping (deep packet Inspection) Discriminating Discriminating Tussle over resource control EuroView2008 8 July 21-22, 2008 Lessons � Example is simplified in many ways � Tussle – fight over resources � Among stakeholders � Here: resource owners vs resource users � Can also be among users, etc � Tussles arise at run time � Evolution – hard to predict � Future architecture must be tussle-aware � How? � No cookbook recipe! EuroView2008 9 July 21-22, 2008
Trilogy objective � Original Internet � Internet today � Trilogy goal � Piece of art � Torn by tussles � Embrace! � Beautiful � Ossified � Unified control � Innovative � Patched � Simplicity � Flexibility � At run time EuroView2008 10 July 21-22, 2008 Mapping the parameter space - today ������ ��������� phone email WWW TCP UDP IP ETH 802.11 radio copper fibre ����� �������� � Current Internet architecture maps 1 point in the “tussle” space � Technical, business, social, legal EuroView2008 11 July 21-22, 2008
Mapping the parameter space - future ������ ��������� Applications ? Technologies �������� ����� � Current Internet architecture maps 1 point in the “tussle” space � Technical, business, social, legal � Future must embrace multiple areas EuroView2008 12 July 21-22, 2008 Tussle space: middlebox? End system resources App App Tussle space TCP TCP IP IP IP IP IP MAC MAC MAC MAC MAC PHY PHY PHY PHY PHY Operator resources EuroView2008 13 July 21-22, 2008
Example: resouce usage End system Multiple paths: resources How many? value App App Tussle TCP TCP space IP IP cost MAC MAC PHY PHY Operator resources EuroView2008 14 July 21-22, 2008 Middlebox control - reviewed Resource users Resource owners Secret??? Terms of Unfair ? negotiation TCP Skype Obfuscate Multi-conn. Port-selective DPI P2p, IDC packet dropping (deep packet Too slow Inspection) Discriminating Discriminating EuroView2008 15 July 21-22, 2008
Next steps � Challenges and objectives are clear - but not how to get there! � Our approach � Design principles for a tussle-aware architecture � Where did they occur, and how they were resolved � Lessons learned � Define preliminary architecture (ongoing work) � Tussle-aware � Encorporates novel (technical ideas) � Discuss preliminary architecture with business leaders � Get early feedback � Take feedback to improve approach EuroView2008 16 July 21-22, 2008 Trilogy Conclusions � Develop a unified control reachability architecture for the Future Internet mechanisms � Scalable, dynamic and robust topology discovery, � Operational and business requirements reachability � Develop and evaluate new technical load-dependent, traffic multi-path engineering solutions for key Internet control TRILOGY elements congestion control � Reachability & resource control routing policy re-feedback economic drivers � Assess commercial and social resource control aspects control business � of our architecture & technical solutions � internal & external strategic evaluation www.trilogy-project.eu EuroView2008 17 July 21-22, 2008
Recommend
More recommend
