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

Re: [STDS-802-11-TGBN] Co-BF/Co-SR Trigger frame format discussion

Hi Jason,

 

One comment:

  • Should we clarify how the “CS Required” bit is used ? I assume that bit will be reserved for soliciting CBF PPDU transmission (?)
  • Regarding “More TF” bit, the text says “The More TF field indicates whether or not a subsequent Co-BF Trigger frame is scheduled for transmission. The More TF field is set to 1 if the Co-BF coordinating AP schedules a subsequent Co-BF Trigger frame is the current TXOP, and is set to 0 otherwise.”
    1. Should it be “intends to schedule”  instead of “schedules” ?
  • What is the Duration field in the Trigger frame ? Forgot if that was covered in another doc.

 

Regards,

Dibakar

 

From: Guoyuchen (Jason Yuchen Guo) <000018696e95f088-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, January 15, 2026 9:50 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Co-BF/Co-SR Trigger frame format discussion

 

Hi Yanjun,

 

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.

 

Best,

Jason

 

发件人: Yanjun Sun <yanjunsunstd@xxxxxxxxx>
发送时间: 2026年1月15日 23:26
收件人: Guoyuchen (Jason Yuchen Guo) <guoyuchen@xxxxxxxxxx>
抄送: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBN] Co-BF/Co-SR Trigger frame format discussion

 

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.

 

Thanks,

Yanjun

 

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

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