1 / 9

Utilizing IPv6 Mobility Support for Enhanced Request Routing in Content Delivery Networks

This research explores the integration of IPv6 mobility support in request routing (RR) for Content Delivery Networks (CDNs), as presented by Arup Acharya and Anees Shaikh at the TJ Watson Research Center. The paper highlights the advantages of using mobile IP mechanisms for RR to direct HTTP requests to proximal servers without overloading DNS systems. Unlike IPv4, where mobility requires mobility agents and results in triangular routing, IPv6's native mobility support facilitates direct connections between mobile clients and servers. This enhances routing accuracy and allows for dynamic management of IP addresses in CDNs, improving overall network efficiency.

meda
Télécharger la présentation

Utilizing IPv6 Mobility Support for Enhanced Request Routing in Content Delivery Networks

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. Using Mobility Support for Request-Routing in IPv6 CDNs Arup Acharya and Anees Shaikh TJ Watson Research Center Presented by Renu Tewari

  2. Request-Routing in CDNs • RR directs client HTTP requests to “proximal” server • In IPv4 CDNs, RR primarily via DNS • Key observation: RR is congruent to IP mobility • use mobile IP mechanisms for redirection • no need to overload DNS • In IPv4, mobility requires deployment of “mobility agents” • existing hosts remain unchanged • however, all packets routed via home agent triangular routing • IPv6 offers native mobility support • support present in any IPv6 node • direct routing between mobiles and correspondents • RR can use mobility mechanisms without modification

  3. 12.100.104.5 (TTL = 0) www.abc.com? www.abc.com? ns.abc.com (TTL = 1d) www.abc.com? 12.100.104.5 DNS Request Routing (IPv4) CDN servers modifiednameserver 63.64.105.4 12.100.104.5 root nameserver local ns client

  4. IPV RR in IPv6 using mobility support • resolve name to an IP address (IPv) IPv6 RR (IPV) origin server DNS server CDN servers www.abc.com? local NS client

  5. home agent src: IPC dest: IPV TCP SYN TCP SYN mobile node correspondentnode IPv6 Request-Routing (cont.) • RR chooses proximal server (IPL) IPv6 RR (IPV) • forwards SYN pkt to IPL in IP-in-IP tunnel f(IPC, IPV) = IPL CDN server (IPL) client (IPC)

  6. src: IPC dest: IPV TCP SYN src: IPL dest: IPC HA: IPV bind upd bindingcache SYN/ACK IPV IPL IPv6 Request-Routing (cont.) • CDN server sendsIPv  IPL mapping to client via a binding update, piggybacked on SYN/ACK IPv6 RR (IPV) • client creates binding cache entry CDN server (IPL) client (IPC)

  7. src: IPC dest: IPL RH: IPV bindingcache HTTP GET IPV IPL IPv6 Request-Routing (cont.) • subsequent client pkts sent to IPL (IPv placed in routing header) • TCP endpoint: < IPc ,IPv> IPv6 RR (IPV) CDN server (IPL) client (IPC)

  8. Additional remarks • IPv6 mobility provides an alternate mechanism for RR • RR policies and metrics must be implemented at the home agent • Functionality similar to DNS, without some problems • IPv6 RR sees actual client address – improved accuracy • CDN server can use lifetime field in binding cache to control duration of binding • Take advantage of large address space in IPv6 • map CDN customers to distinct (virtual) IP addresses • use additional addresses for granular content-based-routing (e.g., streaming, images, etc.)

More Related