XIA: Efficient Support for Evolvable Internetworking

1. XIA: Efficient Support for Evolvable Internetworking

2. IP: Narrow Waist of the Internet Applications Innovation bothabove and below IP IP But what about IP? Technology Hyeontaek Lim / NSDI '12

3. Proposed -Centric Networking • Service: Serval (This NSDI!) • Content: Named Data Networking • Mobility: MobilityFirst • Cloud: Nebula Problem: Focusing on one communication type may hinder using other communication types, as occurred to IP Can we support heterogeneous communication types on a single Internet architecture? Hyeontaek Lim / NSDI '12

4. Future -Centric Networking • Service, content, mobility, and clouddid not receive much attention before as now • Yet more networking styles may be usefulin the future • E.g., DTN, wide-area multicast, …? Problem: Introducing additional communication types tothe existing network can be very challenging Can we support future communication typeswithout redesigning the Internet architecture? Hyeontaek Lim / NSDI '12

5. Legacy Router May Prevent Innovation Internet “I got a computer withAwesome-Networkingannounced in NSDI 2022!Can I use it right now?” “Ouch, we just replaced all of our routers built in 2012.Can you wait for another10 years for new routers?” Problem: Using a new communication type may requireevery legacy router in the network to be upgraded Can we allow using a new communication type even when the network is yet to natively support it? Hyeontaek Lim / NSDI '12

6. XIA’s Goals and Design Pillars “Principal types” “Fallbacks” Allow usingnew communication types at any point (incremental deployment) Support multiple communication types(heterogeneity) Support future communication types(evolution) Hyeontaek Lim / NSDI '12

7. Principal Types Define your own communication model Hyeontaek Lim / NSDI '12

8. Principals Current Internet XIA IP address Hash of host’s public key 128.2.10.162 Host Service Principal type Future Content 0x8A37037… 0x47BF217… 0xF63C7A4… … Type-specific identifier Hash of service’s public key Hash of content Hyeontaek Lim / NSDI '12

9. Principal Type-Specific Semantics Contact a host Host Service Content 0xF63C7A4… 0x8A37037… 0x47BF217… Use a service Retrieve content Hyeontaek Lim / NSDI '12

10. Principal Type-Specific Processing Commonprocessing Host-specific processing Service-specific processing Output Input Content-specific processing … XIA router • Type-specific processing examples • Service: load balancing or service migration • Content: content caching Hyeontaek Lim / NSDI '12

11. Routers with Different Capabilities • Routers are not required to supportevery principal type • The only requirement: Host-based communication Common Host Common Host Common Host Service Content Host-only router Service-enabled router Content-enabled router Hyeontaek Lim / NSDI '12

12. Using Principal Types that areNot Understood by Legacy Routers? Content-enabled router Content-enabled router Legacy routerwithoutcontent support Want to communicate using content principals Hyeontaek Lim / NSDI '12

13. Fallbacks Tomorrow’s communication types… today! Hyeontaek Lim / NSDI '12

14. Fallbacks: Alternative Ways forRouters to Fulfill Intent of Packet Intent: Retrieve Content Fallback: Contact , who understands request Host Content • What the network does: • With content-enabled routers, use for routing • Otherwise, use for routing (always succeeds) Content Host Hyeontaek Lim / NSDI '12

15. DAG-BasedAddress Your address is more than a number Hyeontaek Lim / NSDI '12

16. DAG (Direct Acyclic Graph)-Based Addressing Enables Fallbacks Packet sender Intent Routing choice Content Host Another routing choice(with lower priority) This host knows how to handle content request Fallback Hyeontaek Lim / NSDI '12

17. DAG Addresses in Packet Header Common fields(Size, Hop limit, …) Including in-packet state for forwarding Destination address For forward path Source address For return path (Extension headers) Payload DAG encoding in paper Hyeontaek Lim / NSDI '12

18. Scoping Using DAG Tier-1 ISP Tier-2 ISP My laptop Echo More specific intent & Better scalability Host Service Domain Domain My laptop Echo Tier-1 ISP Tier-2 ISP Hyeontaek Lim / NSDI '12

19. Service Binding with DAG Initial contact to a service When a particular host should serve subsequent service requests Service Service Host Web service Web service Server #57 “Late binding” Hyeontaek Lim / NSDI '12

20. DAG Allows Nested Fallbacks Content Service Domain Host Strong support for evolvable internetworking Hyeontaek Lim / NSDI '12

21. Can We Forward DAGs Rapidly? Expressive ≠ Expensive Hyeontaek Lim / NSDI '12

22. XIA Software Router’sHigh Forwarding Throughput ≤26% slowdownfor small packetswith 3 fallbacks Click-based implementation on commodity hardware351 K table entries based on a Route Views snapshot Hyeontaek Lim / NSDI '12

23. XIA: eXpressive Internet Architecture • Support for evolvable internetworking • Heterogeneous communication types • Future communication types • Incremental deployment of new communication types • Principal types & fallbacks • DAG-based addressing Hyeontaek Lim / NSDI '12

24. XIA: Enabling Evolution by eXpression Something New • Prototype: github.com/XIA-Project/xia-core • Router, socket, content cache, etc. • Supports LAN, XIA-over-IP, GENI Something Old Hyeontaek Lim / NSDI '12