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

Re: [STDS-802-11-TGBN] MAC queue (uploaded/ready): Co-RTWT part 7 (26/0743) - 20 CIDs

Hi Pascal,

Thanks a lot for the thoughts and comments.

For revision r1, I considered your text suggestion. Please check the revised text.
For the removal of the example from the resolution table, I am fine, please check r1.

Best,
Giovanni


From: VIGER Pascal <Pascal.Viger@xxxxxxxxxxxx>
Sent: Thursday, April 02, 2026 05:43
To: Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: RE: MAC queue (uploaded/ready): Co-RTWT part 7 (26/0743) - 20 CIDs

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi Giovanni,

 

Thank you for your document.

 

I do not have strong opinion about the modified specification text :

One rematch: maybe “the same R-TWT schedule as the schedule as announced” by Coordinating AP would better be “a R-TWT schedule corresponding to the schedule as announced”.

This is because the TSF are not the same.

 

While I agree there may exist protection mechanism for Co-RTWT in coordinated BSS, I disagree with the example you provide of using Quiet Element for protecting Co-RTWT.

There are several reasons that avoid using Quiet Element to align, in a second BSS,  with a TWT SP of a first BSS :

  • TBTTs in between two BSSs are not aligned in time and may not last the same duration. Furthermore, the Quiet element and the TWT element do not use the same timing reference: the Quiet element is based on the TBTT (hence the beacon frames) while the TWT element is based on the TSF.
  • The Quiet Element is based on a Quiet Period and Quiet Offset fields, set on a number of beacon intervals. But beacon intervals are not mandatorily the same in between the coordinated/ing BSSs.
  • To comply with previous issue, one may further think applying a Quiet Element per TBTT, but this is not possible : As Quiet period is signalled in the beacon frame with a Quiet Count strictly positive, the Quiet Period can be effective only after the next beacon frame. It turns out that the Quiet-based coordination cannot have immediate application in the neighbouring BSS

I  suggest removing the Quiet Element example from the comment resolution tab.

 

Best regards,

Pascal

 

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: mardi 31 mars 2026 19:05
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] MAC queue (uploaded/ready): Co-RTWT part 7 (26/0743) - 20 CIDs

 

BEWARE: This email originated outside of our organization. DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe.
Please report all suspicious emails to the ISS department as an attachment.

 

[Co-RTWT TTT - document ready for presentation]

 

 

Dear Co-RTWT TTT and Alfred,

 

I uploaded the contribution Co-RTWT part 7 resolving the following 20 CIDs:

4907 5826 5827 6750 7975 7976 8150 8362 8364 8367 8368 9340 9383 9504 10992 10994 11402 11403 12109 12258

https://mentor.ieee.org/802.11/dcn/26/11-26-0743-00-00bn-lb291-cr-for-cortwt-part7.docx

 

The document is ready for presentation, @Alfred Asterjadhi, could you please queue it for presentation?

 

To the Co-RTWT TTT, please check resolutions and let me know if you have comments.

 

Best,

Giovanni

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