Scope of TGbh and TGbi in IEEE 802.11-21
Explore the scope and objectives of Task Groups TGbh and TGbi within IEEE 802.11-21 standards. Delve into the delineation of responsibilities and areas of focus to avoid duplication and ensure efficient collaboration.
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
September 2021 doc.: IEEE 802.11-21/1470r0 Scope of TGbh and TGbi Date: 2021-09-09 Authors: Name Mark Hamilton Ruckus/ Affiliations Address Phone +1-303-818-8472 email mark.hamilton2152@gmail.co m 350 W. Java Dr Sunnyvale, CA 94089 CommScope Cox Communications carol@ansley.com Carol Ansley +1-404-229-1672 Submission Slide 1 Mark Hamilton, Ruckus/CommScope
September 2021 doc.: IEEE 802.11-21/1470r0 Abstract Discussion of the scope for TGbh and TGbi. Submission Slide 2 Mark Hamilton, Ruckus/CommScope
September 2021 doc.: IEEE 802.11-21/1470r0 Background Both TGbh and TGbi were started by the RCM TIG and study group, and they have related scope This has resulted in some confusion over which group is appropriate for consideration of some contributions This document is meant for discussion, to try to reach consensus among members of both TGs on how to understand the respective PARs, and what topics will be considered within each group, to help avoid overlap. Submission Slide 3 Mark Hamilton, Ruckus/CommScope
September 2021 doc.: IEEE 802.11-21/1470r0 Scope for 802.11 Both groups have an overall scope defined by the scope of 802.11 itself, of course. Some contributions may need to be considered for whether they are within 802.11 scope. In particular, note that 802.11 as a MAC/PHY Standard limits itself to mechanisms in the MAC/PHY (sub)layers. However, there are situations where a MAC/PHY mechanism is appropriate, even when the mechanism is supporting features or functions at a higher-layer. Examples in the current Standard include: Proxy ARP, FILS HLP Container, Location, TDLS Capability, Venue URL, Civic Location, etc. Both TGs should consider the 802.11 scope when considering a contribution, independently. Submission Slide 4 Mark Hamilton, Ruckus/CommScope
September 2021 doc.: IEEE 802.11-21/1470r0 Scope of TGbh and TGbi Issues that are within TGbh scope, defined by the PAR, paraphrased as: The issue being addressed is a facility or behavior that is disrupted by randomized MAC addresses or MAC addresses that are changing over time, where previously the service functioned based on the assumption of a unique association between a STA and a MAC address. The modifications being proposed do not expose trackable user information to third parties, expose an individual s presence or behavior, or otherwise affect a user s privacy. Issues that are within TGbi scope, defined by the PAR, paraphrased as: The amendment is to specify new mechanisms that address and improve user privacy. Submission Slide 5 Mark Hamilton, Ruckus/CommScope
September 2021 doc.: IEEE 802.11-21/1470r0 Authors derived opinions Randomized/changing MAC addresses were discussed in 802.11aq, and are already being done by many STA devices. There is no need to discuss the value/purpose of RCM, other than to understand its scope of usage. Impacts caused by RCM and mitigations/solutions for those impacts should be discussed in TGbh. Other privacy concerns or enhancements, beyond fixing impacts of RCM , should be discussed in TGbi. Submission Slide 6 Mark Hamilton, Ruckus/CommScope
