Hi Alfred,
Can you please queue the following SPs to the MAC queue:
- Do you agree to add the following to the 11bn SFD:
- An NPCA STA shall not switch to the NPCA PC if its intra-BSS NAV is non-zero.
Supporting doc: 25/416r0
- Do you agree to add the following to the 11bn SFD:
- An NPCA AP may advertise an NPCA Disabled Subchannel Bitmap that indicates the subchannels that are punctured when an NPCA STA operates on the NPCA Primary channel.
- The NPCA Disabled subchannel Bitmap shall satisfy the following requirements:
- The puncturing pattern indicated by the NPCA Disabled Subchannel Bitmap is a valid non-OFDMA puncturing pattern as defined in 36.3.2.1
- A 20 MHz subchannel indicated as punctured in the Disabled Subchannel Bitmap of the EHT Operation element (if any) is also indicated as punctured in the NPCA Disabled Subchannel
Bitmap.
- if the AP advertises an NPCA Disabled Subchannel Bitmap and UHR NPCA STA transmits a PPDU on the NPCA primary channel, the UHR NPCA STA shall follow the same rules as 35.15.2
except that instead of Disabled Subchannel Bitmap it shall use the most recently exchanged NPCA Disabled Subchannel Bitmap.
- If the AP does not advertise an NPCA Disabled Subchannel Bitmap, a UHR NPCA STA shall follow the rules defined in 35.15.2.
Supporting doc: 25/416r0
Do you agree to add the following to the 11bn SFD:
- define a procedure for a DPS non-AP STA to indicate, during the DPS enablement procedure, an ICF-required field, where:
–
If ICF-required is set to 0, the DPS Assisting AP shall initiate frame exchanges with a DPS STA by sending an ICF if it intends to transmit to the DPS STA in HC mode (i.e. the DPS Assisting AP may
exchange frames with the DPS STA without being required to send an ICF as long as the frames use parameters consistent with the STAs’ LC mode)
•
ICF-required set to 0 is only allowed if the DPS STA is not operating on an eMLSR link
–
If ICF-required is set to 1, the DPS Assisting AP shall initiate any frame exchange with a DPS STA by sending an ICF (i.e., the DPS Assisting AP can not exchange any frames with the DPS STA unless
they are preceded with an ICF)
A DPS Assisting
AP shall support operation with a DPS STA that has set ICF-Required to 0 or 1
Supporting doc: 25/415r0
Thanks,
Laurent
From: Binita Gupta <bingupta.ieee@xxxxxxxxx>
Sent: Tuesday, March 11, 2025 7:44 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] TGbn Agenda for March F2F
Hi Alfred,
Could you please queue the following harmonized SP on L4S Support for Thu AM1 agenda.
SP:
Do you
agree to define in 11bn an optional
mechanism for L4S support on the AP as below?
- Define an MLME primitive that provides congestion notification from the MAC layer to the higher layer at the AP, to enable
the upper layer to mark ECN bits on subsequent packets
for L4S congestion signaling.
- Enhance the MA-UNITDATA.request primitive to provide an
indication whether the MSDU carries the packet of L4S flow
- TBD on whether and how AP’s L4S capability is advertised.
NOTE 1 - This SP proposal is a further refinement of L4S-related SPs (39.2, 39.3) presented during Nov’24 Vancouver meeting’s TGbn MAC session 1791r1.
NOTE 2 - The
conditions and criteria based on which the MAC layer determines to signal L4S congestion experienced notification to the upper layer is implementation specific and is outside the scope of this specification.
NOTE 3 – DCN 25/0459r0 shows a Proposed Draft Text (PDT) corresponding to this SP
Supporting documents: 24/0399, 24/0384, 24/0818, 25/459
Hello all,
The initial agenda for the March F2F meeting can be found here.
I plan to upload a revised version that contains the queues up to date (until tomorrow, Saturday, 5:00pm PT) and a preliminary
spread of the submissions in each session following the usual per-topic arrangement. To make sure that the queues are stable by then, please send me the submission requests by tomorrow, Saturday 5:00pm PT).
After that, I will upload the revised version with all received contributions and send the final call for submissions with the usual Sunday deadline.
--
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Office #: +1 858 658 5302
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: 90-92 route de la Reine, 92100 Boulogne, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|