Operational Neighbor Discovery Problems
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 12
- Abstract
- In IPv4, subnets are generally small, made just large enough to cover the actual number of machines on the subnet. In contrast, the default IPv6 subnet size is a /64, a number so large it covers trillions of addresses, the overwhelming number of which will be unassigned. Consequently, simplistic implementations of Neighbor Discovery (ND) can be vulnerable to deliberate or accidental denial of service (DoS), whereby they attempt to perform address resolution for large numbers of unassigned addresses. Such denial-of-service attacks can be launched intentionally (by an attacker) or result from legitimate operational tools or accident conditions. As a result of these vulnerabilities, new devices may not be able to "join" a network, it may be impossible to establish new IPv6 flows, and existing IPv6 transported flows may be interrupted. This document describes the potential for DoS in detail and suggests possible implementation improvements as well as operational mitigation techniques that can, in some cases, be used to protect against or at least alleviate the impact of such attacks. [STANDARDS-TRACK]
- Publication Date
- 2012-03-01
- Status Note
- Informational
- DOI
10.17487/RFC6583- Link
- https://doi.org/10.17487/RFC6583
- Author(s)
- Igor GashinskyJoel JaeggliWarren Kumari
Latest version of IETF RFC 6583
Document Versions — IETF RFC 6583
-
▶ IETF RFC 6583 (2012-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 4861 [Active*]
- IETF RFC 4862 [Active*]
- IETF RFC 6164 [Active*]
Bibliographic Reference(s)
- IETF RFC 4732 [Active*]
- IETF RFC 5157 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6583.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6583, Operational Neighbor Discovery Problems. Available at https://doi.org/10.17487/RFC6583
Snippet:
IETF RFC 6583, Operational Neighbor Discovery Problems. Available at https://doi.org/10.17487/RFC6583
HTML (ISO 690 compliant)
Preview:
IETF RFC 6583, Operational Neighbor Discovery Problems. Available at https://doi.org/10.17487/RFC6583
Snippet:
<span class="citation"><cite>IETF RFC 6583</cite>, Operational Neighbor Discovery Problems. Available at <a href="https://doi.org/10.17487/RFC6583" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6583</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6583, Operational Neighbor Discovery Problems
doi: 10.17487/RFC6583
url: https://doi.org/10.17487/RFC6583
doi: 10.17487/RFC6583
url: https://doi.org/10.17487/RFC6583
Snippet:
<li> <cite id="bib-rfc6583">IETF RFC 6583</cite>, Operational Neighbor Discovery Problems <span class="doi">10.17487/RFC6583</span> </li>
Referenced By
- IETF RFC 7048 [Active*]
- IETF RFC 7066 [Active*]
- IETF RFC 7421 [Active*]
- IETF RFC 7707 [Active*]
- IETF RFC 9131 [Active*]