Rogue IPv6 Router Advertisement Problem Statement
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 16
- Abstract
- When deploying IPv6, whether IPv6-only or dual-stack, routers are configured to send IPv6 Router Advertisements (RAs) to convey information to nodes that enable them to autoconfigure on the network. This information includes the implied default router address taken from the observed source address of the RA message, as well as on-link prefix information. However, unintended misconfigurations by users or administrators, or possibly malicious attacks on the network, may lead to bogus RAs being present, which in turn can cause operational problems for hosts on the network. In this document, we summarise the scenarios in which rogue RAs may be observed and present a list of possible solutions to the problem. We focus on the unintended causes of rogue RAs in the text. The goal of this text is to be Informational, and as such to present a framework around which solutions can be proposed and discussed. This document is not an Internet Standards Track specification; it is published for informational purposes.
- Publication Date
- 2011-02-01
- Status Note
- Informational
- DOI
10.17487/RFC6104- Link
- https://doi.org/10.17487/RFC6104
- Author(s)
- Tim ChownStig Venaas
- Keyword(s)
- Registration Authority, Rogue RA
Latest version of IETF RFC 6104
Document Versions — IETF RFC 6104
-
▶ IETF RFC 6104 (2011-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- Ward, N., "IPv6 Autoconfig Filtering on Ethernet Switches", Work in Progress, March 2009. EXTERNAL
- Droms, R. and T. Narten, "Default Router and Prefix Advertisement Options for DHCPv6", Work in Progress, March 2009. EXTERNAL
- IETF RFC 2684 [Active*]
- IETF RFC 3056 [Active*]
- IETF RFC 3315 [Superseded*]
- IETF RFC 3736 [Superseded*]
- IETF RFC 3971 [Active*]
- IETF RFC 4191 [Active*]
- IETF RFC 4192 [Active*]
- IETF RFC 4861 [Active*]
- IETF RFC 4862 [Active*]
- IETF RFC 5533 [Active*]
- IETF RFC 6105 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6104.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 6104, Rogue IPv6 Router Advertisement Problem Statement. Available at https://doi.org/10.17487/RFC6104
Snippet:
IETF RFC 6104, Rogue IPv6 Router Advertisement Problem Statement. Available at https://doi.org/10.17487/RFC6104
HTML (ISO 690 compliant)
Preview:
IETF RFC 6104, Rogue IPv6 Router Advertisement Problem Statement. Available at https://doi.org/10.17487/RFC6104
Snippet:
<span class="citation"><cite>IETF RFC 6104</cite>, Rogue IPv6 Router Advertisement Problem Statement. Available at <a href="https://doi.org/10.17487/RFC6104" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6104</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6104, Rogue IPv6 Router Advertisement Problem Statement
doi: 10.17487/RFC6104
url: https://doi.org/10.17487/RFC6104
doi: 10.17487/RFC6104
url: https://doi.org/10.17487/RFC6104
Snippet:
<li> <cite id="bib-rfc6104">IETF RFC 6104</cite>, Rogue IPv6 Router Advertisement Problem Statement <span class="doi">10.17487/RFC6104</span> </li>
Referenced By
- IETF RFC 6105 [Active*]
- IETF RFC 6343 [Active*]
- IETF RFC 6980 [Active*]
- IETF RFC 7113 [Active*]
- IETF RFC 7610 [Active*]
- IETF RFC 8106 [Active*]