Enhanced Duplicate Address Detection
draft-hsingh-6man-enhanced-dad-04
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Carlos Pignataro , Eli Dart , Hemant Singh , Rajiv Asati , Wes Beebee , Wesley George | ||
Last updated | 2013-05-10 (Latest revision 2012-01-05) | ||
Replaced by | draft-ietf-6man-enhanced-dad | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-6man-enhanced-dad | |
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
Appendix A of the IPv6 Duplicate Address Detection (DAD) document in RFC 4862 discusses Loopback Suppression and DAD. However, RFC 4862 does not settle on one specific automated means to detect loopback of Neighbor Discovery (ND of RFC 4861) messages used by DAD. Several service provider communities have expressed a need for automated detection of looped backed ND messages used by DAD. This document includes mitigation techniques and then outlines the Enhanced DAD algorithm to automate detection of looped back IPv6 ND messages used by DAD. For network loopback tests, the Enhanced DAD algorithm allows IPv6 to self-heal after a loopback is placed and removed. Further, for certain access networks the document automates resolving a specific duplicate address conflict.
Authors
Carlos Pignataro
Eli Dart
Hemant Singh
Rajiv Asati
Wes Beebee
Wesley George
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)