Destination Address Selection Analysis for a MONAMI6 MN
draft-jaksa-monami6addr-select-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robert Jaksa | ||
| Last updated | 2006-10-25 | ||
| 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
When a correspondent node (CN) initiates a session with a multi-homed Mobile Node (MN), it should choose the "best" destination address based on the available information about the MN. Presently there is no mechanism allowing the MN to indicate on which interface (i.e., address) a CN may reach it. This draft documents a method whereby the MN may communicate to the CN address selection preferences so that the CN may initiate a session to the desired address (interface) for of the MN. The method is based on the notion of storing address selection preference information for the MN in the DNS.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)