1 / 1

Problem with Status Quo Internet fundamentally designed for host-to-host communication

SYN. SR@g. 2. 3. SYN. SYN. AS 1. flowID. DNS. f C1. f S1. srvID. Service System α. addr. 1. 4. SYN. a1. a3. A Service Access Layer, at Your Service. ASR. X. s C. s S. Register Z. Resolve Z. f C2. f S2. SR@f. SR @e. a2. a4. 3. 1. Y. Z. Net 4. AS 2. Host C.

john
Download Presentation

Problem with Status Quo Internet fundamentally designed for host-to-host communication

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. SYN SR@g 2 3 SYN SYN AS 1 flowID DNS fC1 fS1 srvID Service System α addr 1 4 SYN a1 a3 A Service Access Layer, at Your Service ASR X sC sS Register Z Resolve Z fC2 fS2 SR@f SR @e a2 a4 3 1 Y Z Net 4 AS 2 Host C Host S SR SR Internet David Shue, MatveyArye, PremGopalan Erik Nordström, Steven Y. Ko, Michael J. Freedman, Jennifer Rexford Princeton University Address b 4 Address a SR SR 5 SYN-ACK 6 ACK Y Z AS 3 Z 2 Address c Address d 1 a SRC 1 1 1 a a a X e DST Serval(Service Access Layer) for IP networks X X X X X b f g Wide-area Service Resolution 2 b SRC Application Client DST 1 a Transport Service Access Server Network New Layering Model Service Instance Link Network Router (Authoritative) Service Router • Problem with Status Quo • Internet fundamentally designed for host-to-host communication • But users want services, agnostic of hosts • Existing ad-hoc solutions are inadequate • Baroque combo of layer-7 switching, HTTP redirection, DNS with short TTLs, IP anycast, VIP/DIP load balancers, ARP spoofing, … • Service-Centric Architecture • From topology-dependent addresses to topology-independent service names • Multiplicity: Of replicas, paths, interfaces, ... • Dynamism: Of replicas, paths, interfaces, … • Service-level anycastfor stateful connections to service instances, associated IP addresses can change over time as replicas join, move, fail, … • Applications • Replicated web services • Content distribution networks • Distributed storage services • Environments • VM-based cloud platforms • Legacy enterprise applications • Mobile users and devices Serval Features Serval Resolution: Successive Refinement • Support for dynamism and multiple interfaces • Communication on serviceIDsthat are resolved to IPs • Transport demux on flowIDs,multi-home/path support • Service Access Layer (SAL) establishes and maintains connections, maps flowIDs to (changing) IPs • Transparent flow redirection upon migration / failover with in-band signaling Components Implementation Demo • Service table maps serviceIDs to IP addrs of resolvers, services • Without local service router, default rule broadcasts on local segment • Ad-hoc mode allows Serval to operate w/o infrastructure, can be used for bootstrapping • Service Access Layer • (Un)registers services & hosts with net • New division of labor between layers • Transport protocols do data delivery • SAL manages connections • Service Router • Resolves serviceID→instance address • Service routers form resolution overlay • DNS can be leveraged for wide-area • Serval end-host stack • BSD sockets API with PF_SERVAL • Binds to serviceIDs instead of IP/port • Datagram and stream sockets • Kernel and user-space versions • Network elements • Overlay of service routers • Support for anycast and extensible header processing connect(X) 1 4 Client SYN-ACK X X SYN 3 SYN 4 SYN-ACK Service table 2

More Related