Analysis of IPv6 Relocation Delays
draft-vogt-dna-relocation-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Christian Vogt | ||
| Last updated | 2005-07-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
As mobile nodes move to new links, they need to resume their communications in a timely fashion. To communicate, IPv6 nodes need to complete router discovery, address auto-configuration, and other tasks. Unfortunately, this depends on prior completion of the Multicast Listener Discovery (MLD) protocol, introducing a mandatory delay of up to one second. This document discusses where this can be problematic and proposes solutions that can alleviate the problem.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)