IEEE 802.11be Non-AP MLD Identification Review Nov 2023
Explore the need for non-AP MLD identification in IEEE 802.11be standard, addressing MAC address randomization and changing, proposed standardization paths, and market context updates. Learn about the recommended solutions and standardization options for improving Wi-Fi industry manageability.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 The need for 802.11be non-AP MLD identification Name Jay Yang Affiliations Address Phone email Yang.zhijie@zte.com.cn ZTE YanLi ZTE Yun Li ZTE Bo Sun Sanechips Graham Smith SRTWireless Carol Ansley Cox Kurt Lumbatis ZaiNar Submission Jay Yang al. (ZTE)
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 Introduction The major features of IEEE P802.11bh (Randomized and Changing MAC addresses) is included in latest revision D2.0, with per-11be STAs as the baseline entities. 802.11be has defined a new entity, MLD, in which there s one MLD MAC address and several link MAC addresses. This submission briefly discusses: The supporting RCM and the identification issues on MLD Some recent additional market context for RCM A recommended standardization path for extending Randomized and Changing MAC addresses to support MLD The proposed timeline Submission Slide 2 Jay Yang, et al. (ZTE)
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 The statement of RCM on MLD Both MLD MAC and Link MAC addresses can be randomized changed according to 11be latest draft. One link MAC address may be the same as the MLD MAC address of an MLD. Submission Slide 3 Jay Yang, et al. (ZTE)
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 The identification issue and potential solution on MLD Device ID and IRM schemes proposed by TGbh should be extended to cover different scenarios on MLD . To identify the frames from a certain non-AP MLD with single MAC address. e.g. (ML)probe, MAC address only be carried on MAC header. To identify the frames from a certain non-AP MLD with multiple MAC addresses. e.g., Authentication/Association, MAC addresses are carried on both MAC header and ML element. Submission Slide 4 Jay Yang, et al. (ZTE)
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 Updated Market Context for RCM Wi-Fi industry focuses on 11be technology with the following aspects: Products: Some vendors have already launched several Wi-Fi 7 products. Wi-Fi Alliance: Wi-Fi CERTIFIED 7 Q1 2024. (link: https://www.wi-fi.org/discover-wi-fi/wi-fi-certified-7 ) , based on IEEE 802.11be technology, will be available before the end of Moreover... Few, if any, silicon vendors are interested in taping out a legacy chipset to implement 11bh solution only. With respect to the enhancement of device manageability, the identification issue on non-AP MLD with RCM is still expected to be a pain point for the Wi-Fi industry Therefore We strongly recommend that the 802.11 group addresses the identification issue on non-AP MLD with RCM. Submission Slide 5 Jay Yang, et al. (ZTE)
Nov. 2023 Non-AP MLD with RCM Standardization Options and Recommendation Option Considerations TG bh Incompatible with the 802.11be baseline (according to the timeline) TG me Rev me does not include .11be, would have to wait for the Rev mf time frame to address it as part of a maintenance project TG bi Focus of .11bi is user privacy protection,e.g.,RCM in post-association., a related but separate topic, would disrupt .11bi scope and timeline. TG be Would expand the scope of .11be and likely extend the timeline; workload is already very high Stand Alone New Project With the .11bh work efforts wrapping up, a focused project as a follow on seems to make sense. Need for tight scope and timeline management Doc.: IEEE 802.11-23/2190r0 Recommendation is to develop a PAR and CSD for a standalone Task group for the purpose of standardizing Randomized and Changing MAC addresses for MLD Submission Slide 6
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 A successful case:11az to 11bk WG letter ballot SA letter ballot 802 EC Approvallast meeting PAR approved 2022-9 11az Timeline 2021-11 ........ 2022-09 2022-10-04 2022-11 2015-09 2019-03 ........ 2021-10 smoothly switch 11bk PAR approve and post to EC agenda TGbk first meeting 11bk PAR and CSD discussion 11bk Timeline 2023-01 Submission Slide 7 Jay Yang, et al. (ZTE)
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 The proposed Timeline between 11bh and 11bX WG letter ballot SA letter ballot 802 EC Approvallast meeting PAR approved 11bh Timeline 2024-09 2024-03 2023-05 ........ 2023-11 2021-02 2024-07 smoothly switch 11bX PAR and CSD discussion TGbX first meeting 11bX PAR approve and post to EC agenda 11bX Timeline 2024-11 11bX: Randomized and Changing MAC addresses for MLD (R4M) Submission Slide 8 Jay Yang, et al. (ZTE)
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 THANK YOU Submission
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 reference [1] 802.11 Timeline [2] 11-22-771-70-TGaz Motion compendium [3] 11-22-1070-00-00az-320-MHz-ranging.pptx Submission Slide 10 Jay Yang, et al. (ZTE)
Nov. 2023 Doc.: IEEE 802.11-23/2190r0 SP Do you support TGbh group should develop the PAR and CSD of the project Randomized and Changing MAC addresses for MLD (R4M) Note: the project name can be modified. Submission Slide 11 Jay Yang, et al. (ZTE)
