Hi Hank,
The intent is not to disallow requesting R-TWT schedules of APs part of the same MBSSID (this should be allowed, let’s work towards that), but I assume
that we won’t use the B-TWT ID value 31 for it, otherwise if more than one of those are requested, there is ambiguity in referring to them later e.g. if you want to teardown or update the parameters. So perhaps to request an R-TWT schedule on behalf of a non-transmitted
BSSID AP part of the same MBSSID set we need to use a proper B-TWT ID value (not 31) paired perhaps with e.g., the BSSID of that AP.
On your comment ‘In
the baseline, an AP with a transmitted BSSID announces the R-TWT schedule of a nontransmitted BSSID using Broadcast TWT ID equal to 31.’, I think it is more nuanced
that that, see below (from 35.8.3.1):
That said, I am ok deferring this until we understand how this can be resolved.
Thanks,
Giovanni
From: Sung Hyeonjun <hank.sung@xxxxxxxxxxxxxx>
Sent: Tuesday, December 16, 2025 7:15 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx; Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Agenda preparation for TGbn Joint conf calls of December
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Giovanni,
Thanks for your hard work.
I have been reviewing the resolution document(25/1937r3) and had a quick question about CID 9514.
The proposed change in CID 9514 currently limits the Broadcast TWT ID within the tuple to the range of 1 to 30.
|
(#9514)The Broadcast TWT ID field
|
In the baseline, an AP with a transmitted BSSID announces the R-TWT schedule of a nontransmitted BSSID using Broadcast TWT ID equal to 31.
Do you intend to exclude R-TWT schedules of the nontransmitted BSSID from Co-RTWT operations?
May I request you to defer the CID 9514 for further discussion?
Best Regards,
Hank H. Sung
보낸
사람: Giovanni
Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
보낸
날짜: 2025년
12월 12일
금요일
오전 10:21
받는
사람: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
<STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
제목: Re: [STDS-802-11-TGBN]
Agenda preparation for TGbn Joint conf calls of December
Dear Alfred, and CoRTWT/MAPC TTT,
I presented 25/1937 on Monday 18.8 and received some feedback, which has been incorporated in 25/1937r3 uploaded here:
https://mentor.ieee.org/802.11/dcn/25/11-25-1937-03-00bn-lb291-cr-for-cortwt-part2.docx
[31 CIDs]: 4628, 5747, 5748, 6172, 6406, 7696, 7697, 7698, 7965, 7966, 7967, 7968, 7969, 7970, 7971, 7972, 7974, 9513, 9514, 10983, 10986, 10987, 10988, 10989, 10990, 10991, 10995, 10996, 10997,
11415, 12641
The document seems to be stable and I would like to run the SP next week.
I’d kindly ask for a slot on Thursday if possible since I will be in a different time zone and
Thursday 12/18 call would be more friendly.
Thanks,
Giovanni
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Monday, December 8, 2025 7:37 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Agenda preparation for TGbn Joint conf calls of December
WARNING: This email
originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hello all,
Please let me know if there are any CR submissions (from MAC queue) that can be processed quickly during the TGbn Joint calls of this Thursday and that of next week. I am looking for CR docs that have editorial/straightforward
resolutions. If you believe that a CR doc satisfies this criteria then please send me an e-mail.
Regards,
Alfred
--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
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
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