Address Selection for DMM
draft-liu-dmm-address-selection-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Dapeng Liu , DENG Hui , Juan Liu | ||
| Last updated | 2012-09-13 (Latest revision 2012-03-12) | ||
| RFC stream | (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 DMM scenario, it is possible for the MN to have multiple mobility anchor points and corresponding prefixes. In that case, MN needs to know the type of the addresses then it can select the right one for application to use. This document describes a mechnism to extend RA message to carry a flag which can be used to identify the nature of the prefix.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)