RFC 9797: Randomized and Changing Media Access Control (MAC) Addresses: Context, Network Impacts, and Use Cases
In plain English — editorial summary, not part of the RFC
To limit the privacy issues created by the association between a device, its traffic, its location, and its user in IEEE 802 networks, client vendors and client OS vendors have started implementing Media Access Control (MAC) address randomization. This technology is particularly important in Wi-Fi networks (defined in IEEE 802.11) due to the over-the-air medium and device mobility. When such randomization happens, some in-network states may break, which may affect network connectivity and user experience. At the same time, devices may continue using other stable identifiers, defeating the purpose of MAC address randomization. This document lists various network environments and a range of network services that may be affected by such randomization. This document then examines settings where the user experience may be affected by in-network state disruption. Last, this document examines some existing frameworks that maintain user privacy while preserving user quality of experience and network operation efficiency.
Document record
- Document ID
- RFC9797
- Published
- June 2025
- Authors
- J. Henry; Y. Lee
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Topics
- RCM
- Universal MAC address
- Local MAC address
- Locally Administered MAC address
- Personal Device
- Shared Service Device
- Network Functional Entities
- Human-Related Entities
- Over-the-Air (OTA) observers
- Wireless access network operators
- Network access providers
- Over-the-Wired internal (OTWi) observers
- Over-the-Wired external (OTWe) observers
- full trust
- selective trust
- zero trust
- privacy
- Residential settings
- Managed residential settings
- public guest network
- Enterprises with Bring-Your-Own-Device (BYOD)
- Managed Enterprises
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9724State of Affairs for Randomized and Changing Media Access Control (MAC) AddressesCurrent
March 2025
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 9103DNS Zone Transfer over TLSCurrent
August 2021
- RFC 8981Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6Current
February 2021
- RFC 4941Privacy Extensions for Stateless Address Autoconfiguration in IPv6Obsoleted
September 2007
- RFC 9788Header Protection for Cryptographically Protected EmailCurrent
August 2025
- RFC 9781A Concise Binary Object Representation (CBOR) Tag for Unprotected CBOR Web Token Claims Sets (UCCS)Current
May 2025
- RFC 9458Oblivious HTTPCurrent
January 2024
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?