Re: [Int-area] Some thoughts on draft-yong-intarea-inter-sites-over-tunnels

["Templin, Fred L" <[e-mail]>]

Hi Joe,

AERO was designed to accommodate the orchestration of multiple data links with
dynamically changing properties (cost, performance, availability, mobility, etc.)
while allowing the mobile node to maintain a stable and unchanging IP address
or prefix. Mobile hosts assign a stable and unchanging IP address to the aero0
interface, while mobile routers leave the AERO interface unnumbered and
maintain a stable and unchanging IP prefix that can be used to number
downstream-attached networks and hosts. Again, sorry if you don't like it
but we are finding that this path meets our requirements while honoring
the "tunnels as links" architecture.

One thing to clarify again - AERO is not a routing protocol; it is simply an
adaptation of IPv6 ND on a specific link type, i.e., the AERO link. RFC4861
says that specific link types are to document the operation of IPv6 ND in
IP-over-(foo) documents. AERO is an IP-over-(foo) document.

Thanks - Fred

From: Joe Touch [mailto:[e-mail]]
Sent: Tuesday, December 06, 2016 3:43 PM
To: Templin, Fred L <[e-mail]>; Lucy yong <[e-mail]>; Brian E Carpenter <[e-mail]>; [e-mail]
Subject: Re: [Int-area] Some thoughts on draft-yong-intarea-inter-sites-over-tunnels




On 12/6/2016 3:39 PM, Templin, Fred L wrote:
Hi Joe,

The areas I described are very much wrapped around mobility, and for AERO
mobility is handled through dynamic neighbor cache updates over the AERO
interface. It is very important that these mobility events do not get propagated
into dynamic routing protocols like OSPF, which would clobber low data rate
data links like LDACS and many varieties of SATCOM. Dynamic neighbor cache
updates in the same manner as described in RFC4861 are the method employed
by AERO.

Those can be integrated easily into updates to the IP forwarding table. That need not propagate to other nodes, and the update can be via any routing protocol you want (Aero's or otherwise).

The primary benefit of integration into existing IP forwarding is that you CAN propagate these if you want, and you CAN integrate the impact of those updates into IP forwarding decisions. If you have only one link, that doesn't matter - but it does otherwise.

Joe