Securing Neighbor Discovery Proxy: Problem Statement
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 22
- Abstract
- 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.
- Publication Date
- 2010-07-01
- Status Note
- Informational
- DOI
10.17487/RFC5909- Link
- https://doi.org/10.17487/RFC5909
- Author(s)
- Jean-Michel CombesSuresh KrishnanGreg Daley
- Keyword(s)
- SEND, Secure Neighbor Discovery
Latest version of IETF RFC 5909
Document Versions — IETF RFC 5909
-
▶ IETF RFC 5909 (2010-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 3775 [Superseded*]
- IETF RFC 3971 [Active*]
- IETF RFC 3972 [Active*]
- IETF RFC 4291 [Active*]
- IETF RFC 4306 [Superseded*]
- IETF RFC 4389 [Active*]
- IETF RFC 4861 [Active*]
- IETF RFC 4862 [Active*]
Bibliographic Reference(s)
- Kempf, J. and C. Gentry, "Secure IPv6 Address Proxying using Multi-Key Cryptographically Generated Addresses (MCGAs)", Work in Progress, August 2005. EXTERNAL
- IETF RFC 3756 [Active*]
- IETF RFC 3963 [Active*]
- IETF RFC 5213 [Active*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5380 [Active*]
- IETF RFC 5568 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5909.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5909, Securing Neighbor Discovery Proxy: Problem Statement. Available at https://doi.org/10.17487/RFC5909
Snippet:
IETF RFC 5909, Securing Neighbor Discovery Proxy: Problem Statement. Available at https://doi.org/10.17487/RFC5909
HTML (ISO 690 compliant)
Preview:
IETF RFC 5909, Securing Neighbor Discovery Proxy: Problem Statement. Available at https://doi.org/10.17487/RFC5909
Snippet:
<span class="citation"><cite>IETF RFC 5909</cite>, Securing Neighbor Discovery Proxy: Problem Statement. Available at <a href="https://doi.org/10.17487/RFC5909" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5909</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5909, Securing Neighbor Discovery Proxy: Problem Statement
doi: 10.17487/RFC5909
url: https://doi.org/10.17487/RFC5909
doi: 10.17487/RFC5909
url: https://doi.org/10.17487/RFC5909
Snippet:
<li> <cite id="bib-rfc5909">IETF RFC 5909</cite>, Securing Neighbor Discovery Proxy: Problem Statement <span class="doi">10.17487/RFC5909</span> </li>
Referenced By
- IETF RFC 6496 [Active*]
- IETF RFC 6957 [Active*]
- IETF RFC 7094 [Active*]