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

Re: [STDS-802-11-TGBN] Request agenda time for presenting 26/0744 Co-RTWT Part 8

[Co-RTWT TTT - Part 8 r5 uploaded - please review]


Dear all,

I uploaded r5, where a note has been removed after a comment made during the call on 6/29.
In the meantime, I responded to some clarification questions from members, and I have not received any follow up from the members that requested deferral on Monday.
To those member, I would kindly ask to let me know if they are ok now after their further checking, or otherwise let me know tomorrow so that I have enough time to update and we can make progress on this topic.

https://mentor.ieee.org/802.11/dcn/26/11-26-0744-05-00bn-lb291-cr-for-cortwt-part8.docx
17 CIDs: 4927 5185 7014 7973 8356 8366 8657 9514 9515 10691 11381 11382 11383 11384 12111 12114 12115

@Alfred Asterjadhi could you please schedule SP for this contribution? (Thursday 2 July would be ok)

Best,
Giovanni

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Friday, June 26, 2026 17:41
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Request agenda time for presenting 26/0744 Co-RTWT Part 8

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

[Co-RTWT TTT - Part 8 r4 uploaded - please review]

Dear all,

Just uploaded r4 incorporating offline comments.

https://mentor.ieee.org/802.11/dcn/26/11-26-0744-04-00bn-lb291-cr-for-cortwt-part8.docx
@Alfred Asterjadhi could you please schedule agenda time for this SP?
17 CIDs: 4927 5185 7014 7973 8356 8366 8657 9514 9515 10691 11381 11382 11383 11384 12111 12114 12115

Best,
Giovanni
From: Gaius Yao Huang Wee <yaohuang.wee@xxxxxxxxxxxxxxxx>
Sent: Tuesday, June 23, 2026 19:27
To: Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: RE: Request agenda time for presenting 26/0744 Co-RTWT Part 8

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 the contribution.

One minor editorial comment: there are a few instances of “MAPC requesting AP” which I believe should be changed to “MAPC initiating AP”.


Also, the naming of the “Reference BSSID Flag” field and its meaning doesn’t seem to match that well. How about something like “R-TWT Schedule Owner Flag” field instead?

 

Best regards,
Gaius

 

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, 23 June 2026 8:15 am
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Request agenda time for presenting 26/0744 Co-RTWT Part 8

 

[Co-RTWT TTT - Part 8 r3 uploaded - please review]

 

Dear all,

 

Just presented r3 in the Tgbn call (just contained a fix of a mistake in doc # in CID resolution table, compared to r2)

https://mentor.ieee.org/802.11/dcn/26/11-26-0744-03-00bn-lb291-cr-for-cortwt-part8.docx

 

Some members had questions, that I will address here. Please let me know your thoughts:

 

Comment 1 - @Yong Ho Seok

 

 

This text has been added so that the transmitted will announce the schedule if at least one of the Aps in same set have at least one associated RTWT capable STA.

 

To the best of my understanding, if we do not add this, the condition for the AP that advertises to be advertising (in relation of being the transmitted BSSID of a multiple BSSID set) is unclear.

 

 

Comment 2 - @Shizhenpeng

 

To the best of my understanding, 

  1. The EMCCA BSSID Index field is defined locally in each subclause where it is used, hence definitions are currently independent (see snippets below)
  2. There seems to be no reason to treat value 0 differently from any other value, since the EMCCA leading AP can take any index anyway. Even in the example location (D1,5 p119 L15)), seems disallowing value 0 is unnecessary (also note that Reference BSSID in 37.14.1.6.1 can be any BSSID in the set, since there is a modulo operation)
  3. Even more so for Co-RTWT profile, where requested schedules can definitely belong to the EMCCA leading AP (see proposed text below)

 

All in all, it is currently unclear whether index 0 is reserved for EMCCA leading AP, even if it has to be so, the text in the CORTWT profile needs to allow requesting schedules belonging to any valid BSSID of the EMCCA set, and there is currently no spec text disallowing value 0 as a valid index of the set (or mapping index 0 to EMCCA leading AP, but this is not relevant as noted above)

 

 

Comment 3 - @Liwen Chu

 

Due to time constraints it was not possible to expand on your comment, could you please report here for discussion?

 

 

@Brian Hart (brianh), happy to receive and incorporate your suggestions.

 

 

Best,

Giovanni

 

From: Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>
Sent: Monday, June 22, 2026 12:07
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>; Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>
Subject: Re: Request agenda time for presenting 26/0744 Co-RTWT Part 8

 

[Co-RTWT TTT - Part 8 r2 uploaded - please review]

 

Dear Co-RTWT TTT members,

 

I have uploaded a minor revision, and addition of an author.

https://mentor.ieee.org/802.11/dcn/26/11-26-0744-02-00bn-lb291-cr-for-cortwt-part8.docx

 

Best,

Giovanni

 

 

 

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, June 18, 2026 12:09
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Request agenda time for presenting 26/0744 Co-RTWT Part 8

 

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

[Co-RTWT TTT - Part 8 r1 uploaded - please review]

 

Dear Co-RTWT TTT members,

 

I have uploaded a revision according to offline comments I received (thanks Zhenpeng).

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

 

Best,

Giovanni

From: Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>
Sent: Wednesday, June 10, 2026 22:50
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>; Giovanni Chisci <gchisci@xxxxxxxxxxxxxxxx>; Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Subject: Request agenda time for presenting 26/0744 Co-RTWT Part 8

 

[Co-RTWT TTT - Part 8 uploaded - please review]

 

Dear @Alfred Asterjadhi,

 

Could you please add this document to the agenda?

2026

744

0

TGbn

LB291 CR for CoRTWT Part8

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

Full list (17 CIDs): 4927 5185 7014 7973 8356 8366 8657 9514 9515 10691 11381 11382 11383 11384 12111 12114 12115

 

To the Co-RTWT TTT, please review and let me know if you have any feedback.

 

Best,

Giovanni

From: Giovanni Chisci <00002b657bbbbed7-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, June 04, 2026 16:22
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Reminder: Planning towards July F2F

 

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

Dear @Alfred Asterjadhi,

 

For my part I have the following documents:

 

  1.  

2025

1939

2

TGbn

LB291 CR for CoRTWT Part4
  1.  
    • Queue for SP 25/1939r3 (to be uploaded), 25 CIDs, target agenda slot from Thursday June 11

 

  1.  

2026

744

0

TGbn

LB291 CR for CoRTWT Part8
  1.  
    • Queue for presentation 26/0744r0 (to be uploaded), 18 CIDs, targeting agenda slot from Thursday June 18
  1.  

2026

60

4

TGbn

LB291 CR for ST Part2
  1.  
    • Queue for SP 26/0060r5 (to be uploaded), 27 CIDs, target agenda slot from Monday June 22
  1.  

2026

1171

0

TGbn

LB291 CR for CoRTWT Part9

 

    • Queue for presentation 26/1171r0 (to be uploaded), 5 CIDs, target agenda slot from Thursday June 25

 

Additionally, would kindly request @Yujian (Ross Yu) to update the 25/1772 to reflect current assignments for following CIDs:

  • 6533 8363 8381 10255 10725 to SunHee Baek
  • 10686 to Brian Hart

 

Thank you in advance,

Giovanni

From: Abhishek Patil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, June 04, 2026 15:10
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx <STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx>
Subject: Re: [STDS-802-11-TGBN] Reminder: Planning towards July F2F

 

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

 

Hi Alfred,


Could you please help queue the following documents to the TGbn MAC agenda:

  • 11-25/2365: LB291: CR for CIDs assigned to Abhi - 37.32 - Part 2 (~26 CIDs)
  • 11-26/1169: LB291: CR for CIDs assigned to Abhi - 37.16 - part 3 (~10 CIDs)
  • 11-26/1170: LB291: CR for CIDs assigned to Abhi - 37.32 - Part 3 (~26 CIDs)

 

The contributions will be ready in early July. I will let you know if I have any of them ready sooner.


The above would resolve all the pending CIDs assigned to me.

 

Regards,
Abhi

 

 

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Tuesday, June 2, 2026 10:06 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] Reminder: Planning towards July F2F

 

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

Hello all,

 

Please consider this as a gentle reminder for the deadline below:

"

Please make sure that you send a CR submission request no later than June 5th, 2026, anywhere on earth (AOE)

    • If the submission is not uploaded when the CR submission request is sent then please provide an ETA as to when the CR is ready to be presented (making sure that the CR submission is uploaded at least 24 hours prior to that meeting slot)

"

 

Regards,

 

Alfred

 

On Fri, May 29, 2026 at 8:36 AM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:

Hello all,

 

I am extending the announcement we made during the May 28th meeting and setting some deadlines so that we can plan for the next couple of months.

  • Planning:
    • Prioritization of CRs will continue as usual, except that temporarily expanded the time allocated to MAC normal CR queue to one hour
    • Green tagging will continue as usual, except that-when possible, green tagging will be performed also on CRs from normal MAC queue.
    • Joint meeting slots will continue to dedicate time for prioritized MAC CRs
  • Call for prioritized submissions and submissions from top 40 assignees:
    • There is limited number of CR submissions with ≥10 CIDs.
  • Please submit CRs with ≥10 CIDs so that they can be prioritised
    • There is a limited number of CR submissions from the top 20 assignees.
  • Please submit CRs (preferably with ≥10 CIDs) and send requests/upload them as soon as possible (upload at least 24 hours in advance of the scheduled meeting slot).
  • Alternatively provide ETAs as to when ready to present.

In summary, if you are planning a CR submission (the items below are highly recommended for MAC CR submissions, and advisory for PHY/Joint CR submission): 

  • Please make sure that you send a CR submission request no later than June 5th, 2026, anywhere on earth (AOE)
    • If the submission is not uploaded when the CR submission request is sent then please provide an ETA as to when the CR is ready to be presented (making sure that the CR submission is uploaded at least 24 hours prior to that meeting slot)
  •  Please share the CR submissions with the TGbn group via the reflector as early as possible to seek early feedback from members.

Let me know if you have any questions.

 

Regards,


Alfred

 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe/TGbn Chair,

Qualcomm Technologies Inc.

asterjadhi@xxxxxxxxx

aasterja@xxxxxxxxxxxxxxxx

Cell #:    +1 858 263 9445

Office #: +1 858 658 5302

 

 

--

Alfred Asterjadhi, PhD

IEEE802.11 TGbe/TGbn Chair,

Qualcomm Technologies Inc.

asterjadhi@xxxxxxxxx

aasterja@xxxxxxxxxxxxxxxx

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

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

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