RFC 8981: Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6
In plain English — editorial summary, not part of the RFC
This document describes an extension to IPv6 Stateless Address Autoconfiguration that causes hosts to generate temporary addresses with randomized interface identifiers for each prefix advertised with autoconfiguration enabled. Changing addresses over time limits the window of time during which eavesdroppers and other information collectors may trivially perform address-based network-activity correlation when the same address is employed for multiple transactions by the same host. Additionally, it reduces the window of exposure of a host as being accessible via an address that becomes revealed as a result of active communication. This document obsoletes RFC 4941.
Document record
- Document ID
- RFC8981
- Published
- February 2021
- Authors
- F. Gont; S. Krishnan; T. Narten; R. Draves
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 20
- Also known as
- —
- Obsoletes:
- RFC 4941
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3041 (2001)
- RFC 4941 (2007)
- RFC 8981 (2021)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 9103DNS Zone Transfer over TLSCurrent
August 2021
- RFC 9724State of Affairs for Randomized and Changing Media Access Control (MAC) AddressesCurrent
March 2025
- RFC 9797Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use CasesCurrent
June 2025
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 9458Oblivious HTTPCurrent
January 2024
- RFC 8446The Transport Layer Security (TLS) Protocol Version 1.3Obsoleted
August 2018
- RFC 9781A Concise Binary Object Representation (CBOR) Tag for Unprotected CBOR Web Token Claims Sets (UCCS)Current
May 2025
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?