Distributed Mobility Management: Current Practices and Gap Analysis
This RFC 7429 was published in 2015
This document analyzes deployment practices of existing IP mobility protocols in a distributed mobility management environment.
It then identifies existing limitations when compared to the requirements defined for a distributed mobility management solution.
RFC 7429 introduction
Existing network-layer mobility management protocols have primarily employed a mobility anchor to ensure connectivity of a mobile node by forwarding packets destined to, or sent from, the mobile node after the node has moved to a different network.
The mobility anchor has been centrally deployed in the sense that the traffic of millions of mobile nodes in an operator network is typically managed by the same anchor.
This centralized deployment of mobility anchors to manage IP sessions poses several problems.
In order to address these problems, a distributed mobility management (DMM) architecture has been proposed.
This document investigates whether it is feasible to deploy current IP mobility protocols in a DMM scenario in a way that can fulfill the requirements as defined in [RFC7333], discusses current deployment practices of existing mobility protocols, and identifies the limitations (gaps) in these practices from the standpoint of satisfying DMM requirements.
The analysis is primarily towards IPv6 deployment but can be seen to also apply to IPv4 whenever there are IPv4 counterparts equivalent to the IPv6 mobility protocols.
Click here to download RFC 7429: TXT format PDF format (coming soon)
Related Request for Comments
©2015 RFC-Base.org - all rights reserved.