Distributed mobility management
draft-liu-distributed-mobility-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dapeng Liu , Zhen Cao , Pierrick Seite , H Anthony Chan | ||
| Last updated | 2010-07-10 | ||
| 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
Current mobility solutions generally introduce an anchor point in the network, e.g., HA in MIPv6, LMA in PMIPv6, GGSN in 3GPP. The anchor point is used to maintain the mapping between the stable IP address (e.g., Home address in MIPv6) and the current routable IP address (e.g., CoA in MIPv6). However, one of the trend in mobile network evolution is to "flatten" mobility architecture by confining mobility support in the access network, e.g. at the access routers level, keeping the rest of the network unaware of the mobility events and their support. This document discusses the deployment of current IP mobility mechanisms in such a flat architecture.
Authors
Dapeng Liu
Zhen Cao
Pierrick Seite
H Anthony Chan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)