Re: [STDS-802-11-TGBN] LB291 CR MU Operation revision uploaded now (26/3

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Hi Xiangxin,

Thank you for your comments and editorial changes

The editorial changes have been applied

Regarding your comments, please see my responses below

If you look at D1.4, the reference 37.4.2.4 in the sentence has been removed

This is a similar condition for the intra-BSS NAV in the baseline

Best Regards,

Hongwon

From: 顾祥新 (Xiangxin Gu) <000046f9987a2d10-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, April 15, 2026 2:27 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] LB291 CR MU Operation revision uploaded now (26/354r7)

Hi Hongwon,

Thank you for the discussion.

Please find my comments and editorial changes attached.

BR,

Xiangxin Gu

Institute of Communication Technology

From: yuxin.lu <eeluyx@xxxxxxxxx>
Sent: Wednesday, April 15, 2026 10:40 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] LB291 CR MU Operation revision uploaded now (26/354r7)

Hi Hongwon,

Thanks for initiating the discussion.

Following up on the resolution of CID 11184, the following paragraph implies that the BSS_COLOR parameter (if it exists) in the Co-TDMA TB ICR sent by the polled AP is set to the BSS color of the coordinating AP.

In this case, I assume the non-AP STAs associated with the polled AP would classify the PPDU carrying this ICR as an inter-BSS PPDU if they only decode the PHY preamble. Do we need to clarify this NAV setting explicitly?

A [홍이1] polled AP that responds to a Co-TDMA TB ICF sets the TXVECTOR parameters as defined in 37.4.2.3.2 (TXVECTOR parameters for UHR TB PPDU response to Trigger frame), where the rules related to a UHR non-AP STA also apply to a polled AP.

On Wed, 15 Apr 2026 at 09:39, hongwon.lee <hongwon.lee@xxxxxxx> wrote:

Hi All,

Thank you for the discussion during CC yesterday. I would like to have an offline discussion regarding deferred CIDs 7622 and 1184

We have two discussion points so far
Regarding the issue related to setting the NAV, Sanket raised a concern about unexpected same AP ID in a BSRP Trigger frame from another Coordinating Co-TDMA AP
To address the issue, I removed the exception in 37.2.1, "Setting and resetting the NAV with BSRP Trigger frame and BSRP NDP Trigger frame (#11691)," and added the exception only for Co-TDMA in 37.4.3

Here, I added one more condition related to TA of the Co-TDMA coordinating AP
Together with the exception added in 26.2.4, I hope CID 7622 can be resolved

Regarding “37.4.3 MU operation for Multi-AP Coordination,” I changed the title to “37.4.3 MU operation for Coordinated Time Division Multiple Access (Co-TDMA) Multi-AP Coordination” to clarify that this subclause applies only to Co-TDMA
Please see attached CR doc(rev9)

Please feel free to reach out if you have any comments or questions

Best Regards,
Hongwon

From: hongwon.lee <hongwon.lee@xxxxxxx>
Sent: Monday, April 13, 2026 4:59 PM
To: 'STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx' <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-11-TGBN] LB291 CR MU Operation revision uploaded now (26/354r7)

Hi All,

I would like to inform you that LB291 CR MU operation – part6(26/354r7) rev7 has been uploaded to the mentor

Please feel free to reach out if you have any comments or questions

Best Regards,
Hongwon
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

Best Regards,

Yuxin

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