RFC 6104: Rogue IPv6 Router Advertisement Problem Statement
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6104
- Published
- February 2011
- Authors
- T. Chown; S. Venaas
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4211Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)Updated
September 2005
- RFC 6105IPv6 Router Advertisement GuardUpdated
February 2011
- RFC 6110Mapping YANG to Document Schema Definition Languages and Validating NETCONF ContentUpdated
February 2011
- RFC 6094Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing ProtocolsCurrent
February 2011
- RFC 6092Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet ServiceCurrent
January 2011
- RFC 6087Guidelines for Authors and Reviewers of YANG Data Model DocumentsObsoleted
January 2011
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
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?