RFC 6105: IPv6 Router Advertisement Guard
In plain English — editorial summary, not part of the RFC
Routed protocols are often susceptible to spoof attacks. The canonical solution for IPv6 is Secure Neighbor Discovery (SEND), a solution that is non-trivial to deploy. This document proposes a light-weight alternative and complement to SEND based on filtering in the layer-2 network fabric, using a variety of filtering criteria, including, for example, SEND status. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6105
- Published
- February 2011
- Authors
- E. Levy-Abegnoli; G. Van de Velde; C. Popoviciu; J. Mohacsi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 7113
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6059Simple Procedures for Detecting Network Attachment in IPv6Current
November 2010
- RFC 5909Securing Neighbor Discovery Proxy: Problem StatementCurrent
July 2010
- RFC 4429Optimistic Duplicate Address Detection (DAD) for IPv6Updated
April 2006
- RFC 4076Renumbering Requirements for Stateless Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
May 2005
- RFC 3972Cryptographically Generated Addresses (CGA)Updated
March 2005
- RFC 9131Gratuitous Neighbor Discovery: Creating Neighbor Cache Entries on First-Hop RoutersCurrent
October 2021
- RFC 6104Rogue IPv6 Router Advertisement Problem StatementCurrent
February 2011
- RFC 6110Mapping YANG to Document Schema Definition Languages and Validating NETCONF ContentUpdated
February 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?