Hello,
> >
The guidelines seem to be about not having any TBD in the PDT which I understand. That’s why I was suggesting to have some other language to deal with it at a later stage.
>
The guidance is related to any explicit TBD which may appear in PDT.
I don't think just deleting explicit "TBD"s is the solution. You're
still left with an issue that needs to be decided. We should be
honest and leave TBDs in until we have found consensus (even if not
unanimity) on how to proceed.
Thanks,
Mark
--
Mark RISON, Standards Architect, WLAN English/Esperanto/Français
Samsung Cambridge Solution Centre Tel: +44 1223 434600
1 Cambridge Square, Cambridge CB4 0AE Fax: +44 1223 434601
ROYAUME UNI WWW:
http://www.samsung.com/uk
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Thursday, 24 April 2025 00:48
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Feedback on Fairness PDT: 11-25/479r3
Hi Dibakar,
The guidance is related to any explicit TBD which may appear in PDT.
On the subsequent question, my interpretation is that those are technical considerations, which are left to the group to discuss and decide.
Regards,
Alfred
On Wed, Apr 23, 2025 at 4:39 PM Das, Dibakar <dibakar.das@xxxxxxxxx> wrote:
Hi Alfred,
The guidelines seem to be about not having any TBD in the PDT which I understand. That’s why I was suggesting to have some other language to deal with it at a later stage. For example, in 11be time frame the Trigger frame allocation signaling was not specified by draft 1.0; so, we left an imprecise language for the time being.
My question below was in response to following statement from Sanket which seems to be more general than just “TBD”: “So, we need not rush into running a motion on a PDT that contains text which is ambiguous and imprecise.” Does it mean that every PDT associated with a feature X can not have any open items related to feature X before being motioned ?
Regards,
Dibakar
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Wednesday, April 23, 2025 4:08 PM
To: Das, Dibakar <dibakar.das@xxxxxxxxx>
Cc: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] Feedback on Fairness PDT: 11-25/479r3
Hi Dibakar,
We are past the phase of adding TBDs as part of PDTs. The current phase is to resolve TBDs and CIDs from TGbn D0.1. Please refer to item 6. Guideline-Solving TBDs/CRs for TGbn D0.1 of the TGbn guidelines.
Regards,
Alfred
On Wed, Apr 23, 2025 at 2:44 PM Das, Dibakar <dibakar.das@xxxxxxxxx> wrote:
Hi Sanket,
I will ask for the chair guidance here regarding whether we need to clarify every detail in a section before the corresponding PDT being motioned.
I think I am currently following same approach as others to make incremental progress on topics to meet timeline. This PDT document is capturing the group consensus on the motion text. There was a TBD in the motion because this part was not resolved. So, the PDT also has a TBD for that aspect.
Regards,
Dibakar
From: Sanket Kalamkar <sankal@xxxxxxxxxxxxxxxx>
Sent: Wednesday, April 23, 2025 2:14 PM
To: Das, Dibakar <dibakar.das@xxxxxxxxx>; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: Feedback on Fairness PDT: 11-25/479r3
Hi Dibakar,
We have at least two weeks until the May F2F meeting, which can be used to address these issues. So, we need not rush into running a motion on a PDT that contains text which is ambiguous and imprecise.
Do you see a technical concern with the suggested text in my earlier e-mail?
Best,
Sanket
From: Das, Dibakar
Sent: Wednesday, April 23, 2025 12:26 PM
To: Sanket Kalamkar; STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: RE: Feedback on Fairness PDT: 11-25/479r3
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Sanket,
I think we need to make some progress to meet the 11bn draft 1.0 timeline. As such given this text is capturing the motion that passed, we should try to follow what we have done for every other PDT: make progress on the parts that are agreed and work on resolving the details.
If the issue is really about not having a “TBD” we can follow what we have typically done for such issues: have a place-holder/imprecise text for now until the group finds the precise solution.
Regards,
Dibakar
From: Sanket Kalamkar <sankal@xxxxxxxxxxxxxxxx>
Sent: Wednesday, April 23, 2025 11:45 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx; Das, Dibakar <dibakar.das@xxxxxxxxx>
Subject: Feedback on Fairness PDT: 11-25/479r3
Hi Dibakar,
Thank you again for preparing the PDT on the fairness topic. I have a couple of technical concerns as follows:
The current PDT (11-25/479r3) states: "Within a TXOP in which a TXOP owner AP performs either Co-TDMA or TXS mode 2 procedure, the AP shall use at least a TBD portion of the obtained TXOP for data communication with its own associated STAs before sharing the TXOP with other STAs."
1. From a spec language point-of-view, the term "data communication" is ambiguous. So, I suggest the following revision:
"Within a TXOP in which a TXOP owner AP performs either Co-TDMA or TXS mode 2 procedure, the AP shall useat least a TBDa portion of the obtained TXOP for at least one individually addressed frame exchange with its associated non-AP STAsdata communication with its own associated STAsbefore sharing the obtained TXOP with other STAs."2. Suggest not to introduce a new TBD. The above suggestion takes care of it as well. We can always add to the PDT if there is a need to add a specific value later.
If you think we need more offline discussions, we can defer the motion to give us more time to revise the PDT.
Best,
Sanket
From: Das, Dibakar
Sent: Thursday, April 3, 2025 11:07 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] CR MAC Request
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
Hi Alfred,
Please add the following (presented) CR doc to agenda for MAC queue for SP:
https://mentor.ieee.org/802.11/dcn/25/11-25-0479-01-00bn-cr-for-cid-1378.docx
Regards,
Dibakar
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
--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
--
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