rfc9724v2.txt   rfc9724.txt 
skipping to change at line 317 skipping to change at line 317
discusses privacy considerations in bridged networks. discusses privacy considerations in bridged networks.
As of 2024, two task groups in IEEE 802.11 are dealing with issues As of 2024, two task groups in IEEE 802.11 are dealing with issues
related to RCM addresses: related to RCM addresses:
* The IEEE 802.11bh task group, which is looking at mitigating the * The IEEE 802.11bh task group, which is looking at mitigating the
repercussions that RCM addresses create on 802.11 networks and repercussions that RCM addresses create on 802.11 networks and
related services. related services.
* The IEEE 802.11bi task group, which is chartered to define * The IEEE 802.11bi task group, which is chartered to define
modifications to the IEEE Std 802.11 MAC specification to specify modifications to the IEEE Std 802.11 MAC specification
new mechanisms that address and improve user privacy. [IEEE_802.11] to specify new mechanisms that address and improve
user privacy.
4. Recent Activities Related to MAC Address Randomization in the WBA 4. Recent Activities Related to MAC Address Randomization in the WBA
In the Wireless Broadband Alliance (WBA), the Testing and In the Wireless Broadband Alliance (WBA), the Testing and
Interoperability Work Group has been looking at issues related to MAC Interoperability Work Group has been looking at issues related to MAC
address randomization and has identified a list of potential impacts address randomization and has identified a list of potential impacts
of these changes to existing systems and solutions, mainly related to of these changes to existing systems and solutions, mainly related to
Wi-Fi identification. Wi-Fi identification.
As part of this work, the WBA has documented a set of use cases that As part of this work, the WBA has documented a set of use cases that
skipping to change at line 436 skipping to change at line 437
| designed to minimize disclosure of identifying information. | designed to minimize disclosure of identifying information.
[RFC7844] also indicates that the link-layer address, IP address, and [RFC7844] also indicates that the link-layer address, IP address, and
DHCP identifier shall evolve in synchrony. DHCP identifier shall evolve in synchrony.
6. Taxonomy of MAC Address Selection Policies 6. Taxonomy of MAC Address Selection Policies
This section documents different policies for MAC address selection. This section documents different policies for MAC address selection.
Some OSes might use a combination of multiple policies. Some OSes might use a combination of multiple policies.
| Note about the naming convention used: The "M" in "MAC" is
| included in the acronym but not the "A" from "Address". This
| allows one to talk about a "PVOM address" or "PNGM address".
6.1. Per-Vendor OUI MAC (PVOM) Address 6.1. Per-Vendor OUI MAC (PVOM) Address
This form of MAC address selection is the historical default. This form of MAC address selection is the historical default.
The vendor obtains an OUI from the IEEE. This is a 24-bit prefix The vendor obtains an OUI from the IEEE. This is a 24-bit prefix
(including two upper bits that are set specifically) that is assigned (including two upper bits that are set specifically) that is assigned
to the vendor. The vendor generates a unique 24-bit value for the to the vendor. The vendor generates a unique 24-bit value for the
lower 24 bits, forming the 48-bit MAC address. It is not unusual for lower 24 bits, forming the 48-bit MAC address. It is not unusual for
the 24-bit value to be used as an incrementing counter that was the 24-bit value to be used as an incrementing counter that was
assigned at the factory and burnt into non-volatile storage. assigned at the factory and burnt into non-volatile storage.
skipping to change at line 495 skipping to change at line 492
determine which network has been attached. determine which network has been attached.
6.5. Per-Period Generated MAC (PPGM) Address 6.5. Per-Period Generated MAC (PPGM) Address
This form of MAC address is generated periodically, typically around This form of MAC address is generated periodically, typically around
every twelve hours. Like PNGM addresses, it is used primarily with every twelve hours. Like PNGM addresses, it is used primarily with
Wi-Fi. Wi-Fi.
When the MAC address changes, the station disconnects from the When the MAC address changes, the station disconnects from the
current session and reconnects using the new MAC address. This will current session and reconnects using the new MAC address. This will
involve a new WPA/802.1x session, as well as obtaining (or involve a new Wi-Fi Protected Access (WPA) or 802.1x session, as well
refreshing) a new IP address (e.g., using DHCP or SLAAC). as obtaining (or refreshing) a new IP address (e.g., using DHCP or
SLAAC).
If DHCP is used, then a new DHCP Unique Identifier (DUID) is If DHCP is used, then a new DHCP Unique Identifier (DUID) is
generated so as to not link to the previous connection; this usually generated so as to not link to the previous connection; this usually
results in the allocation of new IP addresses. results in the allocation of new IP addresses.
6.6. Per-Session Generated MAC (PSGM) Address 6.6. Per-Session Generated MAC (PSGM) Address
This form of MAC address is generated on a per-session basis. How a This form of MAC address is generated on a per-session basis. How a
session is defined is implementation-dependent, for example, a session is defined is implementation-dependent, for example, a
session might be defined by logging in to a portal, VPN, etc. Like session might be defined by logging in to a portal, VPN, etc. Like
skipping to change at line 664 skipping to change at line 662
A Quantitative Analysis", Mobile Networks and A Quantitative Analysis", Mobile Networks and
Applications, vol. 10, no. 3, pp. 315-325, Applications, vol. 10, no. 3, pp. 315-325,
DOI 10.1007/s11036-005-6425-1, June 2005, DOI 10.1007/s11036-005-6425-1, June 2005,
<https://doi.org/10.1007/s11036-005-6425-1>. <https://doi.org/10.1007/s11036-005-6425-1>.
[IEEE_802] IEEE, "IEEE Standard for Local and Metropolitan Area [IEEE_802] IEEE, "IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture", IEEE Std 802-2014, Networks: Overview and Architecture", IEEE Std 802-2014,
DOI 10.1109/IEEESTD.2014.6847097, June 2014, DOI 10.1109/IEEESTD.2014.6847097, June 2014,
<https://doi.org/10.1109/IEEESTD.2014.6847097>. <https://doi.org/10.1109/IEEESTD.2014.6847097>.
[IEEE_802.11]
IEEE, "IEEE Standard for Information Technology--
Telecommunications and Information Exchange between
Systems - Local and Metropolitan Area Networks--Specific
Requirements - Part 11: Wireless LAN Medium Access Control
(MAC) and Physical Layer (PHY) Specifications", IEEE
Std 802.11-2020, DOI 10.1109/IEEESTD.2021.9363693,
February 2021,
<https://doi.org/10.1109/IEEESTD.2021.9363693>.
[IEEE_802.11aq] [IEEE_802.11aq]
IEEE, "IEEE Standard for Information technology-- IEEE, "IEEE Standard for Information technology--
Telecommunications and information exchange between Telecommunications and information exchange between
systems Local and metropolitan area network--Specific systems Local and metropolitan area network--Specific
requirements Part 11: Wireless LAN Medium Access Control requirements Part 11: Wireless LAN Medium Access Control
(MAC) and Physical Layer (PHY) Specifications Amendment 5: (MAC) and Physical Layer (PHY) Specifications Amendment 5:
Preassociation Discovery", IEEE Std 802.11aq-2018, Preassociation Discovery", IEEE Std 802.11aq-2018,
DOI 10.1109/IEEESTD.2018.8457463, August 2018, DOI 10.1109/IEEESTD.2018.8457463, August 2018,
<https://doi.org/10.1109/IEEESTD.2018.8457463>. <https://doi.org/10.1109/IEEESTD.2018.8457463>.
 End of changes. 4 change blocks. 
8 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.48.