RFC 6496: Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)
In plain English — editorial summary, not part of the RFC
SEcure Neighbor Discovery (SEND) specifies a method for securing Neighbor Discovery (ND) signaling against specific threats. As defined today, SEND assumes that the node sending an ND message is the owner of the address from which the message is sent and/or possesses a key that authorizes the node to act as a router, so that it is in possession of the private key or keys used to generate the digital signature on each message. This means that the Proxy ND signaling performed by nodes that do not possess knowledge of the address owner's private key and/or knowledge of a router's key cannot be secured using SEND. This document extends the current SEND specification in order to secure Proxy ND operation. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6496
- Published
- February 2012
- Authors
- S. Krishnan; J. Laganier; M. Bonola; A. Garcia-Martinez
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6602Bulk Binding Update Support for Proxy Mobile IPv6Current
May 2012
- RFC 7148Prefix Delegation Support for Proxy Mobile IPv6Current
March 2014
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 2014
- RFC 8818Distributed Mobility AnchoringCurrent
October 2020
- RFC 5149Service Selection for Mobile IPv6Current
February 2008
- RFC 6618Mobile IPv6 Security Framework Using Transport Layer Security for Communication between the Mobile Node and Home AgentCurrent
May 2012
- RFC 6636Tuning the Behavior of the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) for Routers in Mobile and Wireless NetworksCurrent
May 2012
- RFC 6705Localized Routing for Proxy Mobile IPv6Current
September 2012
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?