Address Pool based Stateful NCoA Configuration for FMIPv6
draft-jung-mipshop-stateful-fmipv6-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Hee Jung | ||
Last updated | 2003-08-29 | ||
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 DAD procedure for NCoA validation is a burden for achieving the fast MIPv6 handover. The existing stateless and DHCPv6-based stateful NCoA configuration schemes are all concerned with the DAD process at NAR. This document describes an NCoA address pool based stateful NCoA configuration for MIPv6 fast handover (FMIPv6). To reduce the DAD handling time during the handover, the NCoA pools are established at NAR (in the reactive stateful scheme) or PAR (in the proactive stateful scheme). An NCoA pool maintains a list of NCoAs already confirmed by the corresponding NAR. In response to a handover request, the NAR or PAR will allocate a confirmed NCoA to the MN. By the address pool based stateful NCoA configuration, the handover latency can be significantly reduced, and a tunneling for handover can be extended to an NCoA address, instead of NAR.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)