Visual RFC.
ALL RFCs / RFC 4862
Read the RFC ↗
RFC 4862 / PROTOCOL MECHANISMS

Check a tentative address for duplicates

02

Duplicate Address Detection uses Neighbor Discovery before assigning a tentative unicast address.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 5.4 ↗
RFC 4862 · § 5.4EXAMPLE
3 / 3
Check a tentative address for duplicatesDuplicate Address Detection uses Neighbor Discovery before assigning a tentative unicast address.tentative addressmulticast groupDAD NS · source ::no source-link-layer optionconflicting advertisementDo not assign duplicate addressDAD is required as specified, not proof against every attack
03
A conflicting advertisement stops assignment of that address.

A conflicting advertisement stops assignment of that address.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 2462RFC 4862 Appendix C

The revision recommends Duplicate Address Detection for all unicast addresses rather than relying on an earlier link-local-only check.

Read the updated RFC section ↗
KEY POINT

A DAD solicitation uses the unspecified source address and omits the source-link-layer-address option.

  • A DAD solicitation uses the unspecified source address and omits the source-link-layer-address option.
  • A detected duplicate must not be assigned to the interface.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Form a tentative link-local address
  2. Check a tentative address for duplicates
  3. Combine an advertised prefix and identifier
  4. Track preferred and valid lifetimes
  5. Renumber without an instant cutover

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗