<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-6man-enhanced-dad" target="https://datatracker.ietf.org/doc/html/draft-ietf-6man-enhanced-dad-00">
   <front>
      <title>Enhanced Duplicate Address Detection</title>
      <author initials="R." surname="Asati" fullname="Rajiv Asati">
         </author>
      <author initials="H." surname="Singh" fullname="Hemant Singh">
         </author>
      <author initials="W." surname="Beebee" fullname="Wes Beebee">
         </author>
      <author initials="E." surname="Dart" fullname="Eli Dart">
         </author>
      <author initials="W." surname="George" fullname="Wesley George">
         </author>
      <author initials="C." surname="Pignataro" fullname="Carlos Pignataro">
         </author>
      <date month="April" day="10" year="2012" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-6man-enhanced-dad-00" />
   
</reference>
