Fred, Happy New Year.
I'm not currently tracking rtgwg, so perhaps this is already addressed in discussion of there. (And perhaps I should move dmm@ to bcc...) How does a MNP-bearing node (client) locate candidate s-ASBRs (similarly how does it locate a proxy)? And does the client try to form an eBGP session with the s-ASBR or use something else? I was also not clear on where administrative boundaries are in the various diagrams (though I assumed at least that c-ASBRs are within the MSP-owners administrative domain). Thanks, -Erik On Wed, 2 Jan 2019 at 12:37, Templin (US), Fred L <[email protected]> wrote: > Hello, and Happy New Year, > > We have articulated what is essentially a Distributed Mobility Management > (DMM) > service for the next-generation civil aviation Aeronautical > Telecommunications > Network with Internet Protocol Services (ATN/IPS): > > https://datatracker.ietf.org/doc/draft-ietf-rtgwg-atn-bgp/ > > This work tracks the progress of the International Civil Aviation > Organization > (ICAO), and is a working group item of the IETF RTGWG. > > The way it works is that there is a hub-and-spokes BGP overlay routing > service > that interconnects potentially many mobility anchor points. Each anchor > point is > responsible for mobility management for a constituent set of mobile nodes > (e.g., aircraft), such that the system as a whole supports large-scale DMM. > > We think this document is in the correct home in RTGWG, but I just thought > I would start out the year by sensitizing the DMM community. Any thoughts > or comments are welcome. > > Thanks - Fred > _______________________________________________ > dmm mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmm >
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
