1 / 1

Trilogy and 4WARD: Towards a Clean Slate Internet Design

Control plane. Data plane. provide reach-ability. fast converg-ence. POP3. IMAP. SMTP. XMPP. H.323. HTTP. SIP. reachability mechanisms. provide identifiers. SDP. NTP. Telnet. FTP. IRC. security. DNS. topology discovery, reachability. Resource user. Resource provider. XDR.

lynna
Download Presentation

Trilogy and 4WARD: Towards a Clean Slate Internet Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Control plane Data plane provide reach-ability fast converg-ence POP3 IMAP SMTP XMPP H.323 HTTP SIP reachability mechanisms provide identifiers SDP NTP Telnet FTP IRC security DNS topology discovery, reachability Resource user Resource provider XDR ASN-1 XML SMB Diameter multiple path exposure RTCP SSL TLS RTSP RPC ASP RTP load-dependent, multi-path Radius Multi-flows; peer2peer; DDoS traffic engineering Stakeholder behaviours Economicreality scalability Requirements for a Routing Architecture SCTP Market Evolution IKE COPS Multicast Routing TCP UDP TRILOGY DPI; TE OSPF NHRPP RIP GRE E-IGRP DVMRP PIM SM-DM congestion control MIP HIP RSVP Traditional V-model(one variant) IPv4 UserRequirements Validation routing policy economic drivers easy configur-ation EGP IGRP BGP VRRP IGP GGP IGMP MBGP MLD re-feedback Social support for policies IPSec Technical NSIS CIP MPLS SystemRequirements SystemTesting Trilogy: Design for Tussle locality of routing events resource control robust-ness/ stability IP Support 802.X MAC easy deploy-ability 802.11 802.3 802.16 ATM BOOTP ICMP DHCP business Architecture and Design Verification IARP ARP RARP 802. 11x PDH 802.11i 802.1D 802. 3x SDH 802.1x 802. 16x xDSL ISDN 802.21 802.1Q Implementation Unit Testing Legal Business A R D 4 W FDDI Token Ring merge/ network code decode split/ balance code cooperatively join Generic path 1 Generic path 2 Trilogy and 4WARD: Towards a Clean Slate Internet Design Wolfgang Mühlbauer, Roger Karrer, Peter Feil, Anja Feldmann • Clean Slate Internet Design – why? • Many of the design decisions of the Internet were made 4 decades ago. Since then, the Internet and its use have changed as it has changed itself society. However, today, the Internet is out of shape. • An ossified architecture • The Internet architecture is the result of an initial careful design based on well-argued principles and a 4 decade evolution to add additional features. Unfortunately, many of these principles are no longer true (security) or new ones have emerged – technical ones (mobility) as well as economical ones (net neutrality). One thing the Internet lacks is flexibility to efficiently accommodate the new requirements. • Control plane: out of shape • The picture of the Internet hourglass to depict its architecture holds for the data plane. However, it is far from true when we consider the “control plane”. In fact, there is no such thing as an explicit control plane. And second, control protocols had been squeezed into the architecture to fit the layering structure. Therefore, the Internet architecture has significantly extended its waist over the past 40 years. • A clean slate Internet design that searches for novel concepts to build an Internet architecture from scratch is needed to ensure that the Internet is able to address the challenges in the near future. • We at Deutsche Telekom are part of 2 EU FP-7 projects that focus on these challenges: • 4WARD • Triology • Even though the two projects aims at similar goals, they take different approaches and focus on distinct challenges. Trilogy: Re-architecting the Internet Trilogy’s concept is single architecture that is flexible to adapt to the different forces and demands in the Internet – i.e. a tussle-aware architecture. • It identifies 3 fundamental demands that must be consideredjointly in the design of a future Internet architecture • Reachability Mechanisms • Resource Control • Business Aspects • Trilogy is the first project that tries to unify all of them in a clean slate approach • Workpackage 1: Reachability • Establish and control transparent reachability in a scalable, dynamic and resilient manner: • Routing fragility • Growing organizational complexity • Topics include • Routing • Multi-homing • Remote traffic filtering • Workpackage 2: Resource control • Develop and evaluate a unified approach to resource control that is efficient, fair and incentive-compatible: • Utilization • Different fairness metrics • Cheat-proof • Congestion • Storage, battery life, spectrum 4WARD • 4WARD is based on the following technical premises: • Create a new “network of information”, where information objects have their own identity. • Rich communication paths that include mobility, security and QoS over wired and wireless networks • Devise an embedded default-on management capability. • Provide means to support the instantiation and dependable operation of different networks on a single infrastructure in a commercial setting (virtulization). • Develop an integrated framework to represent, design, implement and operate network architectures that all belong to a common family of interoperable network instances. Workpackage 3: Social and commercial control (led by DT) Understand how architectural features allow a controlled behavior, provide flexibility in terms of technical, social and economical outcomes, and interact with business stakeholders outside Triology to get commercial/strategic steer. • Conclusions • A clean slate Internet design • Requires novel concepts with an out-of-box thinking • Needs an experimental facility to experimentally verify that protocols and architectures are viable, scalable and efficient • Offers new technical and economical opportunities for operators, but only for early adopters • For these reasons, DT is involved in the above projects • For further information • Anja Feldmann: Internet Clean Slate Design: what and why? Sigcomm CCR, July 2007 • For more information on the proposals, please contact any of the authors at firstname.lastname@telekom.de.

More Related