Re: [STDS-802-11-TGBN] Co-RTWT CR documents submission

The current resolution for #9508 is insufficient for clarification. According to the baseline, in order for a TWT scheduling AP to terminate an existing broadcast TWT, the TWT Setup Command field shall be set to "Reject TWT" and this broadcast TWT should be indicated for as many TBTTs as needed.

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

The current proposed text in 26/0272r1 only addresses the Restricted TWT Parameters Set field modification. So, I think we need to modify the proposed text as below for modification of the TWT Setup Command field to "Reject TWT” to cover the case of Co-RTWT agreement teardown.

If the Co-RTWT coordinating AP modifies the Restricted TWT Parameters Set field and the TWT Setup Command field carried in a broadcast TWT element and corresponding to an R-TWT schedule announced for its BSS (see 35.8.3.1 (Rules for RTWT scheduling AP)), and if the schedule is a coordinated R-TWT schedule with a Co-RTWT coordinated AP, the Co-RTWT coordinating AP should perform a Co-RTWT negotiation to update the Co-RTWT agreement by following the rules defined in 37.14.2.4.2.

NOTE—For example, an Co-RTWT coordinating AP might change the announcement of an R-TWT schedule from active to idle by changing the setting of the Restricted TWT Schedule Info field from 1 or 2 to 0 in the Restricted TWT Parameter Set field and the setting of the TWT Setup Command field to Reject TWT corresponding to the R-TWT schedule and included in a broadcast TWT element carried in the Beacon frame. (#9508)

And, I have one more clarification. If the Co-RTWT coordinating AP modifies the broadcast TWT element when it has a non-zero value of the Broadcast TWT Persistence field, should the Co-RTWT coordinated AP modify the broadcast TWT element accordingly as well? Shouldn’t we add the text related to coordinated AP’s operation (regarding this exception) for this case as well?

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Date: Tuesday, March 3, 2026 at 7:19 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Co-RTWT CR documents submission

[Co-RTWT CR documents: part 5 and part 6 – please review]

Dear members of the Co-RTWT TTT,

Uploaded ‘Co-RTWT part 5’ and ‘Co-RTWT part 6’ first revision, including editorials according to received feedback (tracked changes in different color).

https://mentor.ieee.org/802.11/dcn/25/11-25-1940-01-00bn-lb291-cr-for-cortwt-part5.docx

https://mentor.ieee.org/802.11/dcn/26/11-26-0272-01-00bn-lb291-cr-for-cortwt-part6.docx

Best,

Giovanni

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, February 26, 2026 9:45 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Co-RTWT CR documents submission

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

[Co-RTWT CR documents: part 5 and part 6 – please review]

Dear Alfred and Co-RTWT TTT,

The following CR documents are uploaded on mentor and queued for presentation in the ad-hoc.

Please let me know if you have comments.

Co-RTWT Part 5 (19 CIDs):

4412 4413 4414 4415 4416 6837 6838 6839 6840 7026 9507 9382 10686 10687 10641 11018 5828 7027 12645

https://mentor.ieee.org/802.11/dcn/25/11-25-1940-00-00bn-lb291-cr-for-cortwt-part5.docx

Co-RTWT Part 6 (12 CIDs):

5751 6477 6478 6479 11005 11006 11410 7699 9508 10998 9516 5746

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

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