Using Neighbor Caceh Entry for Duplicate Address Detection
draft-hoon-mobileip-undad-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jae-Hoon Kim | ||
| Last updated | 2003-10-20 | ||
| 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
The Duplicate Address Detection (DAD) procedure detailed by Neighbor Discovery Protocol (NDP) requires nodes to wait for a quantified time interval during which the configured address is checked for duplication in the connected link. This delay affects normal communication in a Mobile Node (MN) during the DAD time interval thereby hampering Fast Handoff. The expected use of Mobile IP on a wide scale and the need for a minimal time delay during the handoff process require alternate mechanisms for overcoming the DAD time interval. This draft presents a mechanism wherein the Access Router's (AR) Neighbor Cache Entry (NCE) is used to minimize the delay associated with the DAD procedure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)