<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-madinas-use-cases" target="https://datatracker.ietf.org/doc/html/draft-ietf-madinas-use-cases-17">
   <front>
      <title>Randomized and Changing MAC Address: Context, Network Impacts, and Use Cases</title>
      <author initials="J." surname="Henry" fullname="Jerome Henry">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="Y." surname="Lee" fullname="Yiu Lee">
         <organization>Comcast</organization>
      </author>
      <date month="December" day="9" year="2024" />
      <abstract>
	 <t>   To limit the privacy issues created by the association between a
   device, its traffic, its location, and its user in [IEEE_802]
   networks, client and client Operating System vendors have started
   implementing MAC address randomization.  This technology is
   particularly important in Wi-Fi [IEEE_802.11] networks due to the
   over-the-air nature 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 MAC address
   randomization purposes.

   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 two existing frameworks to maintain user privacy while
   preserving user quality of experience and network operation
   efficiency.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-madinas-use-cases-17" />
   
</reference>
