Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8885
Discuss this RFC: Send questions or comments to the mailing listdmm@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8885
Distributed Mobility Management solutions allow networks to be set upin such a way that traffic is distributed optimally and centrallydeployed anchors are not relied upon to provide IP mobility support.
There are many different approaches to address Distributed MobilityManagement -- for example, extending network-based mobility protocols(like Proxy Mobile IPv6) or client-based mobility protocols (likeMobile IPv6), among others. This document follows the former approachand proposes a solution based on Proxy Mobile IPv6, in which mobilitysessions are anchored at the last IP hop router (called the mobilityanchor and access router). The mobility anchor and access router isan enhanced access router that is also able to operate as a localmobility anchor or mobility access gateway on a per-prefix basis. Thedocument focuses on the required extensions to effectively supportthe simultaneous anchoring several flows at different distributedgateways.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.