Skip to main content

Randomized and Changing MAC Address Use Cases
draft-henry-madinas-framework-03

Document Type Replaced Internet-Draft (madinas WG)
Authors Jerome Henry , Yiu Lee
Last updated 2022-01-20 (Latest revision 2021-10-24)
Replaced by draft-ietf-madinas-use-cases
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-madinas-use-cases
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-henry-madinas-framework-03.txt

Abstract

To limit the association between a device traffic and its user, client vendors have started implementing MAC address rotation. When such rotation happens, some in-network states may break, which may affect network efficiency and the user experience. At the same time, devices may continue sending other stable identifiers, defeating the MAC rotation purposes. This document lists various network environements and a set of network services that may be affected by such rotation. This document then examines settings where the user experience may be affected by in-network state disruption, and settings where other machine identifiers may expose the user privacy. Last, this document examines solutions to maintain user privacy while preserving user quality of experience and network operation efficiency.

Authors

Jerome Henry
Yiu Lee

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)