RFC 3971: SEcure Neighbor Discovery (SEND)
In plain English — editorial summary, not part of the RFC
IPv6 nodes use the Neighbor Discovery Protocol (NDP) to discover other nodes on the link, to determine their link-layer addresses to find routers, and to maintain reachability information about the paths to active neighbors. If not secured, NDP is vulnerable to various attacks. This document specifies security mechanisms for NDP. Unlike those in the original NDP specifications, these mechanisms do not use IPsec. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3971
- Published
- March 2005
- Authors
- J. Arkko; J. Kempf; B. Zill; P. Nikander
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 56
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 6494Certificate Profile and Certificate Management for SEcure Neighbor Discovery (SEND)Current
February 2012
- RFC 6495Subject Key Identifier (SKI) SEcure Neighbor Discovery (SEND) Name Type FieldsCurrent
February 2012
- RFC 6980Security Implications of IPv6 Fragmentation with IPv6 Neighbor DiscoveryCurrent
August 2013
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5075IPv6 Router Advertisement Flags OptionObsoleted
November 2007
- RFC 5175IPv6 Router Advertisement Flags OptionCurrent
March 2008
- RFC 8161Benchmarking the Neighbor Discovery ProtocolCurrent
May 2017
- RFC 9898Neighbor Discovery Considerations in IPv6 DeploymentsCurrent
November 2025
- RFC 3972Cryptographically Generated Addresses (CGA)Updated
March 2005
- RFC 3963Network Mobility (NEMO) Basic Support ProtocolCurrent
January 2005
- RFC 3957Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4Current
March 2005
- RFC 3993Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent OptionCurrent
March 2005
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?