Hi Alfred , Ross
The TBDs related to MAPC Request/Response frame format (Clause 9) will be resolved as detailed in “Notes” in the table below.
Regards,
Arik
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: יום ו 06 יוני 2025 00:43
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] TGbn Agenda: May To July Telco - Uploaded
Thanks Ross for preparing this table.
Please populate the notes with the CR/PDT submissions that are resolving these TBDs and if the submissions are not yet ready please obtain a DCN number and provide an ETA as to when they will be ready for discussion.
Hi Alfred and all,
I can give a quick update about the current CID status and number of TBDs in today
or next week’s joint call based on the CC sheet r24:
https://mentor.ieee.org/802.11/dcn/25/11-25-0296-24-00bn-ieee-802-11bn-cc50-comments-on-d0-1.xlsx
R24: updated some assignees per offline agreement, added resolutions of more PHY CIDs,
two CIDs are withdrawn by commenter, 1630 CIDs are now with resolutions. Resolutions for PHY (Motion 389, 392; 84 CIDs) are still to be added. About 199 PHY CIDs are without resolutions; 2057 MAC or joint CIDs are without resolutions.
Number of TBDs are also added in a new tab:
Clause
|
Topic
|
PoC
|
TBDs
|
Notes
|
Clause 6
|
|
Yan Li
|
6
|
|
Clause 9
|
9.2.4.6.4 HE variant
|
Liwen Chu
|
2
|
|
9.3.1.22 Trigger frame format
|
Alice Chen
|
18
|
|
9.4.1.85 DPS Operation Parameters
|
Liwen Chu
|
5
|
|
9.4.2.aa1 UHR Operation Element
|
Ming Gan
|
6
|
|
9.4.2.aa2 UHR Capabilities element
|
Ming Gan
|
2
|
|
9.6.7.69 MAPC Request frame format
|
Arik Klein
|
2
|
Resolved in
11-25/0599r13
|
9.6.7.70 MAPC Response frame format
|
Arik Klein
|
2
|
Resolved in
11-25/0599r13
|
9.6.10 Protected Dual of Public Action frame details
|
Jay Yang
|
2
|
|
Clause 37
|
37.5 Prioritized EDCA
|
Dmitry Akhmetov
|
1
|
|
37.6 UHR Acknowledgement Procedure
|
Ming Gan
|
1
|
Ack procedure for ELR
|
37.14 SMD BSS transition
|
Duncan Ho
|
14
|
|
37.15 Power management
|
Liwen Chu
|
17
|
|
37.16 Non-primary channel access (NPCA)
|
Matthew Fischer
|
16
|
|
37.17 Unavailability reporting and parameter updates
|
Laurent Cariou
|
37
|
|
37.20 Padding for an ICF
|
Liwen Chu
|
1
|
|
37.22 Low Latency Indication
|
Mohamed Abouelseoud
|
3
|
|
Clause 38
|
38.3.5 Interference mitigation
|
Shimi Shilo
|
13
|
|
38.3.16.8 Pilot subcarriers
|
Chenchen Liu
|
5
|
|
38.3.22 Coordinated spatial reuse
|
Jason Yuchen Guo
|
1
|
|
Annex C
|
|
Yan Li
|
1
|
|
|
Total
|
|
155
|
|
Please help check if the PoCs are correct or not.
For D0.3, I expect it will be ready for uploading to member area on late Thursday or
Friday, and uploaded to member area either late this week or early next week.
Regards
Ross Jian Yu
于健
Huawei Technologies
Hi MAC team,
Let me know if any of these other docs would benefit from further convergence/discussion, in which case i can move the SP to (possibly)
next Thursday as well:
·
CR/PDT SPs:
·
25/0437 CC D0.1 subclause 37.11
Laurent Cariou [152C SP]
·
25/0538 cc50-cid-1780-discussion-on-npca-switch-back
Chaoming Luo [1C SP]
·
25/0571 CR-MAC-CC50-CIDs 1550,1551
and 1553 Yajun Cheng [3C SP]
·
25/0599 PDT MAC MAPC Sig.
& Protocol Aspects Giovanni Chisci [30C SP]
·
25/0448 PDT MAC on low latency indication
Mohamed Abouelseoud [PDT]
I will post an updated agenda by end of today (ET) so please let me know by then.
Prioritization is based on the number of CIDs/resolved TBDs and as usual SPs on PDT/CRs have priority.
I don't have visibility on other aspects of the discussions, and hence I encourage members to use the reflector so that we can get a sense
of how the discussions are going.
Having said that, I can move this CR to Thursday next week, and schedule SPs that are pending on a similar subject during the same Telco.
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Office #: +1 858 658 5302
Hi Alfred,
I can see that at the top of the CR/PDT SPs, in the agenda document for June 2th there is:
-
25/0437 CC D0.1 subclause 37.11 Laurent Cariou [152C SP]
This contribution was presented 2 times in the Warsaw F2F and SP was run (with several comments voiced and a count requested).
The group did not support the proposed resolutions. I appreciate that anyone can bring an SP for as many time as they wish, but I wonder how easy it is to appear at top of the agenda again when:
-
There is no updated revision of the document, and
-
There have been no discussion about this document in the reflector, and
-
There has been no willingness to discuss how to technically address a number of comments that have been explicitly pointed out to the authors, and
-
There are many other documents that have not had their chance to be presented to the group.
I am not going to be able to attend the call, as it is in an unfriendly to Europe timezone, so I’d
like to use this opportunity to voice my objection to the proposed resolutions. My technical concerns are:
-
I have requested to include a different resolution for CID1751. The authors prefer to remove the CID from the SP list, and bring a separate SP without considering my technical contribution.
-
CID241 is included in the contribution, with a “Reject” resolution. I have voiced a number of times my concern that DUO is limited to non-AP STAs, when in the real world implementations the same coexistence
issues are valid and need addressing beyond non-AP STAs. I also find strange that only this one comment has been selected to go in this list (and get rejected); I am worried that it will be used later as an excuse to reject similar comments other members have
made in CC50.
-
Resolution text marked with tag [#3214] uses terms such as MaxStandaloneDuoBSRP which are not defined in this document or in D0.1/0.2, and there is no cross reference which allow me to find their meaning.
So, I cannot tell if this resolution is acceptable, as I do not understand what limits it will bring to the non-AP STA’s behaviour.
Kind regards,
Michail
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: 28 May 2025 01:12
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] TGbn Agenda: May To July Telco - Uploaded
TGbn agenda for the teleconferences between May and July can be found
here.
Please check that the queues reflect all submissions requests.
--
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
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
![]()
|
--
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
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
--
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
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
|