IPv6 DAD Optimization Goals and Requirements
draft-park-dna-ipv6dadopt-requirement-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Soohong Daniel Park , Youn-Hee Han | ||
| Last updated | 2004-06-07 | ||
| 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
In order to generate a unique address, IPv6 nodes perform the Duplicate Address Detection (DAD) procedure. Payload packets can not be sent or received before this procedure is complete. In an environment where frequent movements are expected, this delay can be problematic. As the reduction or removal of the delay would be useful, an optimized version of DAD has been proposed. This document suggests the requirements for such "Optimized DAD" protocol as well as considerable solutions.
Authors
Soohong Daniel Park
Youn-Hee Han
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)