MN IP reachability for the DMM
draft-xiong-dmm-ip-reachability-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Chunshan Xiong , Liu Jianning | ||
Last updated | 2014-08-15 (Latest revision 2014-02-11) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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:
Abstract
In distributed mobility management (DMM) environment, the mobile node (MN) has more than one IP addresses and can use different IP address to communicate with different hosts. When a new correspondent node (CN) initials an IP session with MN, the CN needs to find and select one of the MN's IP addresses to provide best performance (e.g. with low delay) for the IP session. This draft analyses the existing mechanisms for IP reachability in a distributed mobility management environment, and identifies the key procedures or enhancements to support the routing-optimized IP reachability in a distributed mobility management environment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)