Sign in
Version 5.13.0, 2015-03-25
Report a bug

Mobility API Extension for Distributed Mobility Management

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-05-09 (latest revision 2013-11-05)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

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


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)