RFC 5909: Securing Neighbor Discovery Proxy: Problem Statement
In plain English — editorial summary, not part of the RFC
Neighbor Discovery Proxies are used to provide an address presence on a link for nodes that are no longer present on the link. They allow a node to receive packets directed at its address by allowing another device to perform Neighbor Discovery operations on its behalf. Neighbor Discovery Proxy is used in Mobile IPv6 and related protocols to provide reachability from nodes on the home network when a Mobile Node is not at home, by allowing the Home Agent to act as proxy. It is also used as a mechanism to allow a global prefix to span multiple links, where proxies act as relays for Neighbor Discovery messages. Neighbor Discovery Proxy currently cannot be secured using Secure Neighbor Discovery (SEND). Today, SEND assumes that a node advertising an address is the address owner and in possession of appropriate public and private keys for that node. This document describes how existing practice for proxy Neighbor Discovery relates to SEND. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5909
- Published
- July 2010
- Authors
- J-M. Combes; S. Krishnan; G. Daley
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 22
- Also known as
- —
Topics
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 3972Cryptographically Generated Addresses (CGA)Updated
March 2005
- RFC 6105IPv6 Router Advertisement GuardUpdated
February 2011
- RFC 5908Network Time Protocol (NTP) Server Option for DHCPv6Current
June 2010
- RFC 5907Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)Current
June 2010
- RFC 5906Network Time Protocol Version 4: Autokey SpecificationUpdated
June 2010
- RFC 5905Network Time Protocol Version 4: Protocol and Algorithms SpecificationUpdated
June 2010
- RFC 5889IP Addressing Model in Ad Hoc NetworksCurrent
September 2010
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?