L4S Integration Efforts in IEEE 802.11 - Subgroup Chairs' Recommendations
Explore the recommendations from subgroup chairs regarding L4S activity integration in IEEE 802.11. Understand the considerations for coordinating and aligning efforts within the 802.11 framework and beyond. Delve into the potential technical changes required for accommodating L4S technology within the existing architecture, emphasizing collaboration with external bodies and subgroup-specific responsibilities.
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
November 2024 Subgroup Chairs recommendation on L4S activity in 802.11 Date: 2024-11-12 doc.: IEEE 802.11-24/1931r0 Authors: Name Mark Hamilton Affiliations Ruckus/CommScope 350 W Java Dr. Address Phone +1-303-818-8472 email mark.hamilton2152@gmail.co m Sunnyvale, CA 94089 Mike Montemurro Alfred Asterjadhi ?? (*) Submission Slide 1 Mark Hamilton, Ruckus/CommScope
November 2024 doc.: IEEE 802.11-24/1931r0 Abstract Joint Recommendations from chairs of ARC, REVmf and TGbn(?)*, on coordination and division of efforts on L4S within 802.11 * TGbn Chair is still reviewing this presentation Submission Slide 2 Mark Hamilton, Ruckus/CommScope
November 2024 doc.: IEEE 802.11-24/1931r0 Noted considerations for L4S integration efforts L4S is an end-to-end facility, and there are already implementations/proof-of-concept work happening on some wired protocols (DOCSIS) and in 3GPP networks. Thus, this effort is likely bigger than 802.11 , and could involve other 802 activities (beyond 802.11) and coordination between 802.11 WG and other 802 activities and activities beyond 802. There appear to be open technical discussions about how L4S (in particular the dual- queuing structure) best fits into 802.11 and/or broader 802 architecture. There are proposals/discussion suggesting that we need to update the MAC SAP, and/or extend the MLME interface, to support the upper-layers needs to accomplish end-to-end L4S. L4S integration into 802.11 could be accomplished with existing MAC/PHY facilities, and such support is desirable to enable the L4S goals in the near term (next few years). On the other hand, L4S integration and implementation might be enhanced through changes to 802.11 faculties that would be appropriate to develop within a MAC/PHY update such as 802.11bn. Thus, it seems that L4S activites are likely appropriate in more than one 802.11 subgroup Slide 3 Submission Mark Hamilton, Ruckus/CommScope
November 2024 doc.: IEEE 802.11-24/1931r0 Subgroup Chairs recommendations Activities that interact with technology beyond 802.11 s scope should be discussed in the ARC SC, to facilitate liaison/coordination with the appropriate external bodies (other IEEE 802 group(s) and/or groups beyond IEEE 802 (for example IETF)). Initial discussion of how to integrate L4S technology into 802.11 (or general 802) architecture, should also be directed to the ARC SC. It is recognized that some aspects of the architecture of L4S may be left up to implementation-specific options, and again might require coordination outside 802.11. Technical changes to IEEE Std 802.11 itself (text changes) should be handled in REVmf, whenever the changes are general (not specific to a particular PHY, or MAC features unique to TGbn), and it should be a goal that changes be kept general in this sense, as much as practicable. TGbn is the correct forum for technical changes to the lower MAC (likely to involve hardware/chip changes) or PHY, including (for example) channel access mechanisms such as any changes to EDCA operation. Submission Slide 4 Mark Hamilton, Ruckus/CommScope
