1. AERO BGP-Based Routing for Distributed Mobility Management
Fred L. Templin

2. AERO Architecture AERO Virtual Link AERO Clients
NBMA tunnel virtual overlay over connected network routing region
Enterprise networks, operator networks, ISP networks, aviation networks, etc.
Works over any tunnel type, but usually uses UDP Port 8060 (AERO)
Connects Clients, Servers and Relays via tunneling
AERO Clients
Mobile or fixed routers (e.g., analogous to MIPv6 mobile node or PMIP MAG)
PMIP mobile node, or lightweight Client app (cellphones, tablets, laptops, etc.)
Associate with AERO Servers using DHCPv6 and IPv6ND for control signaling
Most mobility events reported to Servers ONLY – not to Relays
Clients can change freely between Servers and receive the *same* service (i.e., Distributed Mobility Management)

3. AERO Architecture (2) AERO Servers AERO Relays
Infrastructure mobility anchors (e.g., analogous to PMIP LMA)
Provide DHCPv6 services to delegate AERO Client Prefixes (ACPs) (mobile prefix)
Keep track of current ACP access network address (track mobility events locally, but DO NOT report localized address changes to Relays)
Engage in BGP routing session with all AERO Relays
Servers ONLY keep track of their associated ACPs and default route everything else through Relays
AERO Relays
Represent the AERO link to the rest of the Internet via one or more AERO Service Prefixes (ASPs) (all ACPs are derived from ASPs)
Engage in BGP routing session with all AERO Servers
Keep track of all ACP-to-Server associations

4. AERO Routing System Internetwork To Internet
AERO Servers discover Clients
Servers publish ACPs using BGP
Relays discover all Client-Server associations
Relays advertise ASPs to Internet
Relays
Internetwork
BGP
Servers
AERO Virtual Link
AERO works with servers in the Internetwork that manage routing information in a way that allows clients to be fully mobile without imparting “churn” in the core routing protocols. This entails a unique tie-in with the core address delegation function.
← Clients →

5. AERO BGP Routing System
AERO link-internal BGP instance – does not interact with the global BGP routing system
All Servers peer with all Relays, but Relays do not peer with each other and Servers do not peer with each other
Servers announce and withdraw ACPs to all Relays – Relays get full topology knowledge
Servers use Relays as default routers via tunneling
AERO Relays do not report anything to Servers (one-way reporting from Servers to Relays)
Servers ONLY need to know about their associated Clients, and not about other Clients

6. AERO Enterprise World View
Boeing Proprietary
AERO Enterprise World View
AERO VPN GW
Internet P7
P12
P11
P10 P9 P8
AERO Link
AERO Relays
AERO Server
AERO Server
AERO Server P6 P1 P5 P2 P3 P4

7. AERO BGP Routing Demo
Servers peer with all Relays
Servers report associated Clients via BGP
Servers only need to know about their associated Clients and not about other Clients
Servers handle Client mobility locally w/o disturbing BGP
Relays discover full topology of Client/Server associations