RFC 7527: Enhanced Duplicate Address Detection
In plain English — editorial summary, not part of the RFC
IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are discussed in Appendix A of RFC 4862. That specification mentions a hardware-assisted mechanism to detect looped back DAD messages. If hardware cannot suppress looped back DAD messages, a software solution is required. Several service provider communities have expressed a need for automated detection of looped back Neighbor Discovery (ND) messages used by DAD. This document includes mitigation techniques and outlines the Enhanced DAD algorithm to automate the 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, this document automates resolving a specific duplicate address conflict. This document updates RFCs 4429, 4861, and 4862.
Document record
- Document ID
- RFC7527
- Published
- April 2015
- Authors
- R. Asati; H. Singh; W. Beebee; C. Pignataro; E. Dart; W. George
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7513Source Address Validation Improvement (SAVI) Solution for DHCPCurrent
May 2015
- RFC 7550Issues and Recommendations with Multiple Stateful DHCPv6 OptionsObsoleted
May 2015
- RFC 7554Using IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the Internet of Things (IoT): Problem StatementCurrent
May 2015
- RFC 7556Multiple Provisioning Domain ArchitectureCurrent
June 2015
- RFC 7558Requirements for Scalable DNS-Based Service Discovery (DNS-SD) / Multicast DNS (mDNS) ExtensionsCurrent
July 2015
- RFC 7559Packet-Loss Resiliency for Router SolicitationsCurrent
May 2015
- RFC 7561Mapping Quality of Service (QoS) Procedures of Proxy Mobile IPv6 (PMIPv6) and WLANCurrent
June 2015
- RFC 7563Extensions to the Proxy Mobile IPv6 (PMIPv6) Access Network Identifier OptionCurrent
June 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?