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

Re: [STDS-802-11-TGBN] NOTE1 in 11-26/1760

Hello Romain,

My comment was that the NOTE being added included details that are not defined in the current draft as normative text. The NOTE actually reads more of normative text rather than a clarification.

Regards,
Minyoung 

On Wed, Sep 16, 2026 at 2:51 PM GUIGNARD Romain <Romain.Guignard@xxxxxxxxxxxx> wrote:

Hello Minyoung,

 

You asked to defer my CIDs that were resolved in document 11-26/1760 regarding TXSPG. However, your concern was not clear to me.

The specification states:

"A TXSPG non-AP STA in a P2P group identified by the AID12 field in the User Info field contained in an MU-RTS TXS Trigger frame shall ensure that its PPDU transmission(s) and any expected responses fit entirely within the allocated time for the P2P group."

 

Since only the TXSPG requesting STA knows its AID12 value and the identity of its associated AP, the other non-AP STAs in the P2P group must be informed of both the AID12 and the AP identity in order to determine whether a received MU-RTS TXS Trigger frame applies to their P2P group and, consequently, to comply with the PPDU transmission timing requirement.

Therefore, I do not understand your concern regarding NOTE 1 in document 11-26/1760, as it seems that conveying the AID12 value and the associated AP identity to the peer STAs are necessary for them to satisfy the requirement above and in fact the note seems a minimum to clarify the specification.

Could you please clarify your concern?

 

Best regards,

Romain

 

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