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
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
