P802.11aq Waiver Request Introduction

1. P802.11aq Waiver Request Introduction Date: 2018-04-17 Authors: Stephen McCann, BlackBerry

2. Abstract These slides have been produced by the P802.11aq Task Group chair in response to a request from the RevCom chair, Gary Hoffman, “to post a position statement in layman’s terms to the RevCom agenda on why RevCom should consider recommending the waiver for approval”. r1 adds slides #4 - #8 with additional explanatory material. Stephen McCann, BlackBerry

3. RevCom to approve Waiver Request • It is the understanding of the P802.11aq BRC that the final P802.11aq draft does not harm IEEE RAC registries. • The P802.11aq BRC concluded that satisfying the IEEE RAC MCCs will impede the utility of the P802.11aq amendment. • The P802.11aq BRC believes they have given “appropriate consideration and response” to the IEEE RAC MCCs. • IEEE 802 LMSC Sponsor and IEEE 802.11 WG Approvals March 2018 • Approval of the Waiver Request: • IEEE 802.11 WG: 93/0/7, IEEE 802 LMSC Sponsor: 9-3-3 • Approval for forwarding the P802.11aq draft to RevCom: • IEEE 802.11 WG: 99/0/12, IEEE 802 LMSC Sponsor: 11-2-2 Stephen McCann, BlackBerry

4. P802.11aq Draft 14.0 - I 12.2.10 Requirements for support of MAC privacy enhancements MAC privacy enhancements are enabled on a non-AP STA when dot11MACPrivacyActivated is set to true. The STA shall periodically change its MAC address to a random value while not associated to a BSS. The STA shall construct the randomized MAC address from the locally administered address space as defined in IEEE Std 802-2014 and IEEE Std 802c-2017. However, the non-AP STA shall not change its MAC address during a transactional exchange, for example transmitting Public Action frames for preassociation discovery, or during the creation of state on an AP using preassociation capabilities, for example RSN pre-authentication, FT over-the-DS, etc. The smaller the period of MAC address change, down to a single transmitted frame per MAC address, the greater the privacy these enhancements afford. The actual period used when changing a MAC address is implementation dependent and outside the scope of this standard. • At all times, IEEE 802.11aq constructs the randomized MAC address as defined in IEEE Std 802-2014 and IEEE Std 802c-2017 • In pre-association, the frames terminate at the Access Point. Stephen McCann, BlackBerry

5. P802.11aq Draft 14.0 - II 12.2.10 Requirements for support of MAC privacy enhancements … If such a non-AP STA starts any transaction that establishes state bound to a MAC address and might elect to establish an association or establish transaction state with a discovered BSS, it shall check the value of dot11LocallyAdministeredMACConfig and shall configure its MAC address according to the rules of the local address space prior to the start of the transaction. State created with an AP using a prior MAC address, for instance RSN pre-authentication state or FT state established over-the-DS, is bound to the MAC address used when that state was created. Prior to establishing an association to the AP, the non-AP STA shall change its MAC address to the MAC address used when the state was created. • In post-association the device is configured by the network administrator and the device follows the network policy Stephen McCann, BlackBerry

6. P802.11aq Draft 14.0 - III C.3 MIB Detail … dot11LocallyAdministeredMACConfig OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "This is a control variable. It is written by an external management entity or the SME. Changes take effect as soon as practical in the implementation. This attribute identifies an addressing plan to use for when associating with the BSS. 0: local addresses comply with the Structured Local Address Plan (SLAP) as defined in IEEE Std 802c-2017 1: local addresses are constructed according to vendor-specific local address plan. DEFVAL {0} ::= { dot11StationConfigEntry 185 } • The default value of the network policy is the SLAP, when local administered MAC addresses are configured for the network by the network administrator Stephen McCann, BlackBerry

7. IEEE 802c-2017 8.4.1 Concept and overview … While a local administrator may assign addresses throughout the local range, the optional Structured Local Address Plan (SLAP) specifies different assignment approaches in four specified regions of local MAC address space. • The SLAP is optional Stephen McCann, BlackBerry

8. 11aq PRIVACY CONFIGURATION AND NETWORK SELECTION • The following behavior takes place when the STA selects a network and begins to connect. • Assumptions: • An IEEE 802.11 device cannot associate to a BSS/AP that uses local address management unless the device is configured with local address information. • A device cannot configure itself. A network administrator provides the configuration based on the BSS/AP local address policy. There are many existing deployed configuration mechanisms, including Wi-Fi Alliance Passpoint online signup, ActiveSync, Wi-Fi Simple Config, and 3GPP ANDSF. dot11PrivacyActivated FALSE TRUE Default Select Network and use Globally unique MAC address. dot11LocallyAdministeredMACConfig SLAP OTHER Default Select network and use configured MAC address. Configured MAC address is assigned by administrator according to SLAP Select network and use configured local MAC. Configured MAC is assigned by administrator according to local address policy Stephen McCann, BlackBerry

9. Sponsor Ballot Process • During the P802.11aq sponsor ballot • 13 Mandatory Coordination Comments (MCC) were received from IEEE RAC. • Changes were made to the P802.11aq draft in response to the IEEE RAC MCCs received from the IEEE RAC, between October 2017 and January 2018. • The P802.11aq Ballot Resolution Committee (BRC) has not been able to satisfy the IEEE RAC MCCs. • Final Sponsor Ballot results: 99% approval, 1 negative voter, 1 abstain, returns 115 Stephen McCann, BlackBerry

10. The P802.11aq BRC believes they have given “appropriate consideration and response” to the IEEE RAC MCCs. • To the best of their ability the P802.11aq BRC have tried to learn, discuss and engage with the IEEE RAC regarding the MCCs. Invitations to all P802.11aq face-to-face and teleconference meetings have been relayed to the IEEE RAC since September 2017. • The P802.11aq draft 12.0 was modified in October 2017 to resolve issues from the IEEE RAC MCCs. This draft was subsequently updated resulting in a final P802.11aq draft 14.0. • The P802.11aq BRC have created the RevCom Waiver Request: • https://mentor.ieee.org/802.11/dcn/17/11-17-1704-11-00aq-waiver-request-regarding-ieee-rac-comments.ppt Stephen McCann, BlackBerry

11. From the IEEE-SA Standards Board operations manual: (Dec 2016) 5.4.4 Mandatory coordination … Comments from these entities shall be given appropriate consideration and response. At the time of project submittal to the IEEE-SA Standards Board for consideration for approval, the Sponsor shall supply the most recent coordination comments and indicate either acceptance** or a request for a waiver (see 4.2.3.2). ** Note – “acceptance” also includes “acceptance in principle” (Chair opinion) 4.2.3.2 Review of draft standards … Coordination. Mandatory coordination comments shall be addressed. If the Sponsor believes that satisfying specific mandatory coordination comments will impede the utility of the draft standard, appropriate documentation of this position shall be presented to RevCom. Stephen McCann, BlackBerry