Skip to main content

Requirements of distributed mobility management

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Anthony Chan
Last updated 2012-10-30 (Latest revision 2012-06-14)
Replaced by RFC 7333
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dmm-requirements
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The traditional hierarchical structure of cellular networks has led to deployment models which are heavily centralized. Mobility management with centralized mobility anchoring in existing hierarchical mobile networks is quite prone to suboptimal routing and issues related to scalability. Centralized functions present a single point of failure, and inevitably introduce longer delays and higher signaling loads for network operations related to mobility management. This document defines the requirements for distributed mobility management for IPv6 deployment. The objectives are to match the mobility deployment with the current trend in network evolution, to improve scalability, to avoid single point of failure, to enable transparency to upper layers only when needed, etc. The distributed mobility management also needs to be compatible with existing network deployments and end hosts, and be secured.


Anthony Chan

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)