1 / 26

A Global Name Service for a Highly Mobile Internetwork

A Global Name Service for a Highly Mobile Internetwork. Abhigyan Sharma, Xiaozheng Tie, Hardeep Uppal , Arun Venkataramani, David Westbrook, Aditya Yadav. Internet is mobile-unfriendly. IP 2. Internet. Wassup !. IP 1. Jill’s IP ???. IP 3. Jack. Jill. Jill. Jill.

keely-erickson
Download Presentation

A Global Name Service for a Highly Mobile Internetwork

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. A Global Name Service for a Highly Mobile Internetwork Abhigyan Sharma, Xiaozheng Tie, HardeepUppal, Arun Venkataramani, David Westbrook, Aditya Yadav

  2. Internet is mobile-unfriendly IP2 Internet Wassup! IP1 Jill’s IP ??? IP3 Jack Jill Jill Jill

  3. Internet is mobile-unfriendly Internet Mobile-to-mobile communication & push notifications Redundant effort by app developers! Jack Jill

  4. Outline • Approaches to handle mobility • Limitations of DNS • Design of a global name service • Evaluation • Related work

  5. Indirection-based routing Indirection router e.g. Mobile IP, i3 Internet Wassup! Triangle routing Large data path stretch Jack Jill Jill

  6. Name-based routing Internet Wassup! Large data-path stretch Large routing tables Jack Jill

  7. Global name-to-address resolution Name service Jill’s IP? IP1 IP2 Internet Wassup! No data path stretch Wassup! IP1 IP2 No routing table enlargement Jack Jill Jill

  8. Outline • Approaches to handle mobility • Limitations of DNS • Design of a global name service • Evaluation • Related work

  9. DNS Limitation 1: TTL Caching Domain name system (DNS) IP1 TTL=5 min Jill’s IP? IP2 Internet Wassup! IP1 Mobile is unreachable for TTL duration Jack Jill Jill

  10. DNS Limitation 2: Static placement = Authoritative name server NS = Client NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS NS Update propagation cost NS Managed DNS provider, e.g., Dyn, Ultra DNS, DNS Made Easy Centralized authoritative name server NS NS Very high cost to achieve low latencies globally Number of replicas

  11. DNS Limitation 3: Hierarchical names Flat names impact scalability of DNS root name servers

  12. Outline • Approaches to handle mobility • Limitations of DNS • Design of a global name service • Evaluation • Related work

  13. Four types of mobility Global name service (GNS) Pre-connect mobility Jill’s IP? IP2 IP1 Connection established IP2 Jack Jill

  14. Four types of mobility Global name service (GNS) Pre-connect mobility Jill’s IP? Jill’s IP? IP1 IP2 IP1 Connect-time mobility Connection established IP2 Jack Jill

  15. Four types of mobility Global name service (GNS) Pre-connect mobility IP1 Connect-time mobility Individual mobility IP2 Connection reestablished e.g., TCP Migrate, ECCP, MSocket Jack Jill

  16. Four types of mobility Global name service (GNS) Pre-connect mobility GNS IP1 Connect-time mobility GNS Jill’s IP? IP2 Individual mobility Simultaneous mobility GNS IP2 Connection reestablished Jack Jill IP3

  17. Global name service architecture • Jill’s iPhone • 88789678ab12c, X • 128.119.101.32, 32.245.87.98 Certificate search engine Name certification service Auspice name resolution service images.google.com • 32.245.87.98 Name certification Name resolution Auspice deployable as managed DNS provider

  18. Auspice’s demand-aware placement Number of replicas = c * (read rate)/(write rate) 11% Replicas G 4% A 0% K F 17% 0% C B 0% J 0% H 0% Vote % E 30% 0% I 0% L D 35% Name server X

  19. Auspice’s control plane design Control plane 2 1 1 3 3 G • Collect stats • - read rate • - write rate • - geo-distribution • Compute new replicas • Reconfigure replicas A K F C B J H 1 1 E I L D

  20. More on Auspice design • Consistency of name records • Support for expressive name records

  21. Outline • Approaches to handle mobility • Limitations of DNS • Design of a global name service • Evaluation • Related work

  22. Experiment setup • Testbed: 16 server cluster emulating 80 name servers and 80 local name servers • Workload: 90% highly mobile names with strong geo-locality of requests. 10% low mobility names based on Alexa dataset

  23. Placement schemes comparison

  24. Simultaneous mid-connection mobility … and other experiments. See paper.

  25. Related work • Naming services: Grapevine, Clearinghouse • DNS enhancements: CoDoNS, DMap • Placement algorithms: Volley

  26. Conclusion Complete solution to Internet mobility Auspice name resolution service msocket library A new way to write mobile apps

More Related