January 2020 doc IEEE 802 11 200120 r

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 RCM Summary and Way Forward Date: 2020 -01 -14 Authors: Submission Slide 1 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 Abstract Summary of report from RCM TIG and discussion of way forward from RCM ad hoc Submission Slide 2 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 RCM TIG Background: • The Randomization or (relatively) frequent Changing of a device’s MAC address (“RCM”) is becoming prevalent, primarily for purposes of privacy for the user. • This lack of a clear-text, permanent, and unique device identifier has repercussions on 802. 11 network operation, and other services. • The RCM TIG was formed to investigate and recommend next steps in response. • Output report is here: 11 -19/1442 r 9 Submission Slide 3 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 RCM TIG Report Summary TIG findings: • 11 example use cases (see next slide) were identified, where RCM could have impacts on existing systems. • Many of the impacts from RCM are on “upper-layer” protocols and systems, arguably beyond the 802. 11 (or 802) scope. A liaison was sent to WBA (from ARC, prior to RCM TIG) outlining these concerns: (11 -18/1988). • Remedial methods to mitigate the impacts of RCM were identified and reviewed. • Recommendations (summarized): – Future work is needed in 802. 11, resulting in an amendment to the Standard implementing some of the mitigation strategies that are within 802. 11 scope. – There is also clear demand for broader work on privacy issues relating to 802. 11 technologies, that could be explored by a more broadly scoped TIG. Submission Slide 4 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 RCM TIG Report Use Cases • • • Initial infrastructure network connection steering Access control and arrival detection in a home environment Airport security queue measurement Grocery store customer flow analysis Grocery store frequent shopper notifications Infrastructure (home or enterprise) with different SSIDs per band Infrastructure (home or enterprise): probes use RCM, even with associated SSID Rogue detection in infrastructure networks Customer support and troubleshooting Residential wireless gateway with Hotspot Pervasive surveillance Submission Slide 5 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 RCM ad hoc plan - 1 The RCM ad hoc met Tuesday EVE, and proposes the following ways forward: • Develop amendment text on issues directly affecting the operation of MAC and PHY due to random/changing MAC addresses. Such as: – Use case on Initial Infrastructure Connection Steering (section 3. 1) – Use case on Customer Support and Troubleshooting (section 3. 9) • This might include: – – – Recommendations on MAC address change timing? Recommendations on SSID assignments (not per-band)? Other recommendations? Alternative identifier(s) for device identification by trusted networks? Other alternative ways to support steering, surveillance, queue/flow analysis, etc. ? Other standardized methods, perhaps to help facilitate other use cases beyond 802. 11 scope? • Potential venue: Submission – Study Group? Slide 6 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 RCM ad hoc plan - 2 The RCM ad hoc met Tuesday EVE, and proposes the following ways forward (con’t): • Separately, form a new TIG for broader work on privacy issues relating to 802. 11 – See presentations on last slide, etc. Submission Slide 7 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 RCM ways forward • The RCM ad hoc will meet again Thursday AM 1 • Intention is to draft specific recommended actions for the 802. 11 WG, to be discussed and motioned on Friday • Interested individuals, please join us, or let Mark (or others) know your thoughts • Think about the way forward, in preparation for Friday’s discussion and motion Submission Slide 8 Mark Hamilton, Ruckus/Comm. Scope

January 2020 doc. : IEEE 802. 11 -20/0120 r 0 Background documents • RCM TIG report: 11 -19/1442 r 9 • WBA Liaison on MAC randomization impacts: – Liaison from WBA: 11 -18/1579 r 1 – Response from 802. 11 (drafted in ARC): 11 -18/1988 r 2 • Other inputs to RCM TIG: – 11 -19 -0588 -02 -0 rcm-summary-of-discussions-on-randomized-and-changing-macaddresses-2014 -2019. odt – 11 -19 -0851 -00 -0 rcm-p 802 -1 cq-mac-address-assignment-requirements. pptx – 11 -19 -0884 -00 -0 rcm-temporary-addresses. pptx – 11 -19 -1027 -01 -0 rcm-do-not-fear-random-macs. pptx – 11 -19 -1313 -02 -0 rcm-pitfalls-with-address-randomization. pptx – 11 -19 -1314 -02 -0 rcm-privacy-protection-in-wi-fi-analytics-systems. pptx – 11 -19 -1320 -00 -0 rcm-assignment-of-temporary-addresses. pptx Submission Slide 9 Mark Hamilton, Ruckus/Comm. Scope