Discussion on IEEE 802.11-22/0145r0 STA Identifier - Progress and Challenges
Explore the complexities surrounding the STA identifier in the IEEE 802.11-22/0145r0 document, including debates on privacy, security, and unique identifications. The discussion delves into various viewpoints on identifier control, network vs. device management, uniqueness requirements, and potential solution paths. Join the conversation on addressing new use cases, tracking issues, revisiting conclusions, and advancing solutions for secure identifier usage.
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
January 2022 doc.: IEEE 802.11-22/0145r0 STA identifier way forward Date: 2022-01-20 Authors: Name Mark Hamilton Affiliations Ruckus/CommScope Address 350 W Java Dr. Sunnyvale, CA 94089 Phone +1-303-818-8472 email mark.hamilton2152@gmail.co m Submission Slide 1 Mark Hamilton, Ruckus/CommScope
January 2022 doc.: IEEE 802.11-22/0145r0 Abstract Discussion of the STA identifier topic and a way forward Submission Slide 2 Mark Hamilton, Ruckus/CommScope
January 2022 Discussion of a STA identifier has led to numerous options (and opinions) For example: Agreement that the identifier should be private and secured, but variety of opinions on secured from whom? This includes whether the identifier can/should be shared above layer 2 Is the identifier style/semantics controlled by the device (user) or by the network? The interaction models have not been evaluated, however, such as how a network generated identifier is provided upon leaving and returning later How unique does the identifier need to be/in what scope? The global MAC address abuse came with some assumptions. Etc., etc. Slide 3 doc.: IEEE 802.11-22/0145r0 Submission Mark Hamilton, Ruckus/CommScope
January 2022 doc.: IEEE 802.11-22/0145r0 Discussion of a STA identifier goes in circles How do we make progress? Have we answered these questions in the Issues Tracking section 6 (and if so, are some saying our conclusions should be revisited)? If so, we need contributions to discuss. (We have one, but forced into review before the author said it was ready let s review opinions/contributions, when they re ready.) Are these/are there new use cases that we haven t captured, which generate new/different opinions? If so, we need contributions to discuss, and we need to consider the entire scenario (expand from just a high-level idea), discuss what is in our scope for these use cases, and capture any new criteria. Slide 4 Submission Mark Hamilton, Ruckus/CommScope
January 2022 doc.: IEEE 802.11-22/0145r0 Discussion of a STA identifier is it relevant? An observation: None of the proposed solutions (so far) have made any assumptions about the identifier or its use, other than that it needs to be secured from third party tracking. There is/has been no debate that protection from third parties is a requirement. Deduction: We can make progress on solution(s), and add identifier usage/requirements as a next step, as we get contributions. Submission Slide 5 Mark Hamilton, Ruckus/CommScope
