1 / 13

Asymmetric Extended Route Optimization (AERO)

Asymmetric Extended Route Optimization (AERO). IETF90 Distributed Mobility Management (DMM) Working Group Fred L .Templin fred.l.templin@boeing.com. AERO History. Developed in the 2008 – 2014 timeframe First Edition published as IETF RFC 6706

werner
Télécharger la présentation

Asymmetric Extended Route Optimization (AERO)

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. Asymmetric Extended Route Optimization (AERO) IETF90 Distributed Mobility Management (DMM) Working Group Fred L .Templin fred.l.templin@boeing.com

  2. AERO History • Developed in the 2008 – 2014 timeframe • First Edition published as IETF RFC 6706 • Second Edition now an Internet draft (draft-templin-aerolink)

  3. AERO Overview • Tunneling of any Internet Protocol (IP) version over any IP network (e.g., IPv6 over IPv6, IPv6 over IPv4, etc) • IPv6 Neighbor Discovery (ND) messaging (control plane) • Mobile Clients; stable Servers/Relays; DHCPv6 server • Clients, Servers and Relays are “neighbors” on a virtual IP link configured over a carrier IP network • Clients get IP prefix delegation for mobile networking • Clients send initial communications through a Server • Client-initiated redirection to discover optimal routes • Relays keep track of Client/Server assignments and serve as gateways to the rest of the Internetwork

  4. AERO LINK Reference Model .-(::::::::) .-(:::: IP ::::)-. +-----------+ (:: Internetwork ::) | DHCPv6 | `-(::::::::::::)-' | Server D | `-(::::::)-' +-----------+ | +--------------+ +------+-------+ +--------------+ |AERO Server S1| | AERO Relay R | |AERO Server S2| | (default->R) | | (A->C; G->E) | | (default->R) | | (A->B) | +-------+------+ | (G->F) | +-------+------+ | +------+-------+ | | | X---+---+-------------------+------------------+---+---X | AERO Link | +-----+--------+ +--------+-----+ |AERO Client B | |AERO Client C | | default->S1) | | default->S2) | +--------------+ +--------------+ .-. .-. ,-( _)-. ,-( _)-. .-(_ IP )-. .-(_ IP )-. (__ EUN ) (__ EUN ) `-(______)-' `-(______)-' | | +--------+ +--------+ | Host D | | Host E | +--------+ +--------+

  5. AERO Innovations • New IPv6 link-local Address Format (the AERO Address) • IPv6 delegated prefix is 2001:db8:1:2::/64 • AERO link-local address is fe80::2001:db8:1:2 • Address and prefix do not change as node moves • AERO route optimization • Uses network trust anchors as intermediaries • Fully supports mobility (mobile networks and routers) • Works over any IPv4 or IPv6 access technologies (e.g., Ethernet, 3G/4G, WiFi, aeronautical links, MANET links, etc.) • AERO Routing System • Servers manage collections of mobile Clients • BGP routing between Servers and Relays • Relays connect AERO link to rest of Internetwork

  6. AERO Virtual Link With AERO Addresses • DHCPv6 server delegates prefixes • Clients configure link-local AERO address DHCPv6 Server Relays and Servers Internetwork AERO Virtual Link fe80:: ← AERO Addresses → fe80::2001:db8:0:1 fe80::2001:db8:0:2 fe80::2001:db8:0:3 ← Clients → ← Clients → 2001:db8:0:1::/64 2001:db8:0:2::/64 2001:db8:0:3::/64

  7. AERO Detailed Message Exchange (1) AERO Client AERO Server DHCPv6 Server DHCPv6 Request DHCPv6 Request DHCPv6 Reply • Create nbr cache entry • Advertise route in BGP DHCPv6 Reply • Assign AERO link-local address • Sub-delegate IPv6 prefix to EUNs Router Solicitation Router Advertisement Data Packets

  8. AERO Node Mobility • Client registers first L2 address with Server • Client moves to second L2 address; informs Server and Correspondents • Client moves to third L2 address; informs Server and Correspondents Correspondent Nodes Server Internetwork AERO Virtual Link fe80:: 192.0.2.65 192.0.2.1 192.0.2.33 fe80::2001:db8:0:1 2001:db8:0:3::/64 2001:db8:0:2::/64 fe80::2001:db8:0:3 fe80::2001:db8:0:2 2001:db8:0:1::/64 Mo b ile Node

  9. AERO Detailed Message Exchange (2) AERO Client AERO Server DHCPv6 Server DHCPv6 Renew DHCPv6 Renew DHCPv6 Reply • Change Client L2 Address DHCPv6 Reply Unsolicited NAs to Correspondents Data Packets

  10. AERO Route Optimization • First packet and “Predirect” to Server • “Predirect” triggers “Redirect” • Subsequent packets direct to target Relays and Servers Internetwork AERO Virtual Link fe80:: ← AERO Addresses → fe80::2001:db8:0:1 fe80::2001:db8:0:2 fe80::2001:db8:0:3 ← Clients → ← Clients → 2001:db8:0:1::/64 2001:db8:0:2::/64 2001:db8:0:3::/64

  11. AERO Detailed Message Exchange (3) AERO Client (A) AERO Server AERO Client (B) Data Packet Data Packet “Predirect” message “Predirect” message • Create nbr cache “accept” entry “Redirect” message “Redirect” message • Create nbr cache “forward” entry Neighbor Solicitation Neighbor Advertisement Data Packets

  12. AERO Routing System • AERO Servers discover Clients • Servers publish associated Clients using BGP • Relays discover all Client-Server associations To Internet Relays Internetwork BGP Servers AERO Virtual Link ← Clients →

  13. AERO Use Cases • AERO for enterprise mobile device users • iPad, iPhone, Android, Windows mobiles • Goal: place AERO handsets with corporate users • AERO for civil aviation: • Airplane as mobile router for its attached networks • On-board device addresses remain stable as aircraft travels • Goal: effective Air Traffic Management • AERO for other uses: • numerous other use cases under investigation

More Related