| Hi Jason,
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.
On Jan 14, 2026, at 5:15 PM, Guoyuchen (Jason Yuchen Guo) <000018696e95f088-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:
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
|