IPv6 Privacy Extensions (Temporary Address)
What is IPv6 Privacy Extensions (Temporary Address)?
IPv6 Privacy Extensions generate a randomized, temporary interface identifier instead of one derived from a device's MAC address, so the same device looks different on every network and over time. AdminKit's guide on MAC address randomization explains why this replaces the older EUI-64 approach for most traffic today.
By AdminKit team, Netbase JSC · Updated
IPv6 Privacy Extensions, defined in RFC 8981 (also tracked by the IETF Datatracker), let a host generate a temporary IPv6 address with a randomized interface identifier alongside its normal address, instead of deriving that identifier deterministically from the device’s MAC address the way EUI-64 does. RFC 8981 obsoletes the original specification, RFC 4941, published in 2007, but keeps the same underlying goal: an EUI-64-derived address embeds a stable, globally unique hardware identifier that lets a device be correlated across different networks and over time, purely from its address — a risk NIST’s guidelines for secure IPv6 deployment flag directly, recommending privacy addresses as a deployment practice for exactly this reason. A temporary address changes on a regular schedule and per network, breaking that correlation for outbound connections while a device’s stable address still handles incoming connections to any services it runs. Modern operating systems enable temporary addressing by default for general traffic, reserving the deterministic address mainly for cases that need a stable, reachable endpoint. On Linux the behavior is a per-interface setting: the kernel’s IP sysctl documentation describes use_tempaddr, where 1 enables Privacy Extensions but prefers public addresses, a value above 1 prefers temporary addresses, and 0 (disabled) is the kernel’s own default for most devices.
Privacy Extensions apply to a device’s global address; its link-local address is unaffected and keeps working the same way regardless.
IPv6 Privacy Extensions (Temporary Address) is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
Do IPv6 Privacy Extensions replace a device's normal IPv6 address?
No -- a host generates a temporary address alongside its normal one; the stable address still handles incoming connections to any services the device runs.
What problem do IPv6 Privacy Extensions solve that EUI-64 doesn't?
An EUI-64-derived address embeds a stable, globally unique hardware identifier that lets a device be correlated across different networks and over time, purely from its address.
Is RFC 4941 still the current specification for IPv6 Privacy Extensions?
No -- RFC 8981 obsoletes RFC 4941 from 2007, though it keeps the same underlying goal of breaking address-based correlation.
Do IPv6 Privacy Extensions change on a fixed schedule?
Yes -- a temporary address changes on a regular schedule and per network, breaking correlation for outbound connections while leaving the device's stable address unaffected.
Sources
- RFC 8981 -- Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6
- RFC 4941 -- Privacy Extensions for Stateless Address Autoconfiguration in IPv6 (obsoleted)
- IETF Datatracker -- RFC 8981, Temporary Address Extensions for SLAAC in IPv6
- NIST SP 800-119 -- Guidelines for the Secure Deployment of IPv6
- Linux kernel documentation -- IP Sysctl