RFC 8928: Address-Protected Neighbor Discovery for Low-Power and Lossy Networks
In plain English — editorial summary, not part of the RFC
This document updates the IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery (ND) protocol defined in RFCs 6775 and 8505. The new extension is called Address-Protected Neighbor Discovery (AP-ND), and it protects the owner of an address against address theft and impersonation attacks in a Low-Power and Lossy Network (LLN). Nodes supporting this extension compute a cryptographic identifier (Crypto-ID), and use it with one or more of their Registered Addresses. The Crypto-ID identifies the owner of the Registered Address and can be used to provide proof of ownership of the Registered Addresses. Once an address is registered with the Crypto-ID and a proof of ownership is provided, only the owner of that address can modify the registration information, thereby enforcing Source Address Validation.
Document record
- Document ID
- RFC8928
- Published
- November 2020
- Authors
- P. Thubert; B. Sarikaya; M. Sethi; R. Struik
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 29
- Also known as
- —
- Updates:
- RFC 8505
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8929IPv6 Backbone RouterCurrent
November 2020
- RFC 8930On Forwarding 6LoWPAN Fragments over a Multi-Hop IPv6 NetworkCurrent
November 2020
- RFC 8931IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Selective Fragment RecoveryCurrent
November 2020
- RFC 8925IPv6-Only Preferred Option for DHCPv4Current
October 2020
- RFC 8932Recommendations for DNS Privacy Service OperatorsCurrent
October 2020
- RFC 8915Network Time Security for the Network Time ProtocolCurrent
September 2020
- RFC 8947Link-Layer Address Assignment Mechanism for DHCPv6Current
December 2020
- RFC 8948Structured Local Address Plan (SLAP) Quadrant Selection Option for DHCPv6Current
December 2020
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?