| Hi Jason,
Thank you for accommodating our suggestion during the meeting. I’ve noticed that there were a few more places where the “frame” is present and please help update them in the next version.
As reference, we’re suggesting some text similar to the OMP request define in 11bn as below, which is also a variant of an existing frame. "The UHR OMP request shall be a UHR Link Reconfiguration Request frame with the Type field in the frame set to 3."
On Jan 15, 2026, at 3:58 PM, Guoyuchen (Jason Yuchen Guo) <000018696e95f088-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:
Hi Yanjun, I’m still struggling to understand the issue of the word “frame”, we can also say Co-BF Trigger frame is a variant of BSRP Trigger frame IMHO. Anyway, since it’s an editorial thing, let’s have some more discussion, and we can easily fix it if we decide to make the change. Best, Jason Hi Jason, Thanks for fixing the M-BA part. Regarding comment1, Technically Co-BF Trigger a variant of BSRP Trigger frame, as your current CR clearly says, instead of a new Control frame identified by a type. I concur with you the similar term was misused in many other places throughput 11bn spec and the group needs to start fixing it at some stage and your CR can be a good starting point. The changes also look minor in your CR, as we simply need to remove the “frame” after "Co-BF/SR Trigger”.
I will add “Multi-STA BlockAck”. But I prefer to keep the “frame” there, Co-BF Trigger frame is used a lot in the Co-BF subclause, and it is really a frame. Thank you for your hard work. Please see 3 comments below. 1. As Co-BF Trigger is defined as a variant of BSRP Trigger frame instead of a new frame type, please delete “frame” as follows and propagate the change throughout the CR. “(#8312)9.3.1.22.14.4 Co-BF Trigger frame format A Co-BF Trigger frame is a UHR variant BSRP Trigger frame that has the MAPC Trigger Type field of the Common Info field set to 1. In a Co-BF Trigger frame” 2. Add BlockAck to the list, which is required by DUO, LLI or CFP “— the duration of the MU-BAR Trigger frame sent by the AP + aSIFSTime + the duration of the BlockAck frame or MultiSTA BlockAck sent by the AP’s scheduled STA(s), if the Ack policy of the MPDUs in the transmitted data PPDU is equal to “Block Ack”.” 3. Please apply the similar changes above for the text for Co-SR in the 2nd half of your CR. Dear TGbn members, Please let me know your feedback on doc. 11-26/0023r1 on Co-BF/Co-SR Trigger frame format, thank you! Best, Jason
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 <11-26-0023-01-00bn-lb291-cr-for-co-bf-and-co-sr-trigger-frame-format.docx>
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
|