Mobility API Extension for Distributed Mobility Management

Document Type Expired Internet-Draft (individual)
Last updated 2014-05-09 (latest revision 2013-11-05)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In order to provide an appropriate level of mobility support that a mobile node may require for proper performance of various applications, it is important to enable applications to select addresses that will be managed properly by the mobility management infrastructure. Previous documents have enabled address selection on the basis of certain characteristics such as randomness, temporary usage, scope of validity, and so on. This document proposes new classes of addresses in addition to those already available, to enable an application to receive certain kinds of mobility support.


Dapeng Liu (
Hui Deng (
Charles Perkins (

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