Rogue IPv6 Router Advertisement Problem Statement
RFC 6104, “Rogue IPv6 Router Advertisement Problem Statement”, is an Informational document published in February 2011 by T. Chown, S. Venaas. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6104 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6105 IPv6 Router Advertisement Guard
- RFC 6101 The Secure Sockets Layer Protocol Version 3.0
- RFC 6107 Procedures for Dynamically Signaled Hierarchical Label Switched Paths
- RFC 6108 Comcast's Web Notification System Design
- RFC 6109 La Posta Elettronica Certificata - Italian Certified Electronic Mail
- RFC 6110 Mapping YANG to Document Schema Definition Languages and Validating NETCONF Content
- RFC 6097 Local Mobility Anchor Discovery for Proxy Mobile IPv6
- RFC 6111 Additional Kerberos Naming Constraints