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

Re: [STDS-802-11-TGBN] PDT on ICF/ICR and CRF for multiple modes


In the NPCA section for AP, you have a statement that the rules are specified in NPCA, then you have a bullet that says that the AP is not allowed to use RTS or MU-RTS for TXOPs during NPCA, but this contradicts the table agreed to for AP in the consensus document, and it contradicts the existing language in 936rx, both of which allow an MU-RTS to be used in at least some cases.



Matthew Fischer
Nice Guy
Broadcom Inc.
+1 408 543 3370 office


On Thu, Jul 10, 2025 at 10:33 AM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:
Thanks for the careful review, Gaius. Please find attached some responses. I will upload a REV1 shortly that incorporates all changes so far.

PS: I like the idea below.
Regards,

Alfred

On Wed, Jul 9, 2025 at 6:58 PM Gaius Yao Huang Wee <yaohuang.wee@xxxxxxxxxxxxxxxx> wrote:

Hi Alfred,

 

Thanks for your work. I have bunch of mostly editorial comments for your consideration. Please see attached.

 

Regarding “initial response”, I suppose we can still call it “initial Control response” and define it as, e.g., “a frame transmitted in response to an initial Control frame (ICF).”

 

Best regards,
Gaius

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Wednesday, 9 July 2025 3:10 am
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT on ICF/ICR and CRF for multiple modes

 

Thanks Mark. Please find inline.


Regards,


Alfred

 

On Tue, Jul 8, 2025 at 12:06 PM Mark Rison <m.rison@xxxxxxxxxxx> wrote:

Hello Alfred,

 

I think it should be "initial Control frame" not "Initial Control frame"

(except at the start of a sentence/heading/cell/etc.) or "initial control frame".

 [AA] Ack. will apply throughout.

 

Is "initial response frame" defined somewhere?

 

[AA] I am not certain. Will double check.

 

"MU RTS" should be "MU-RTS" throughout.

[AA] Ack. 

 

What are those strange "[2 octets]" etc.?

[AA] Sizes of the fields for the calculation/expectation purposes for UHR.

 

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: Tuesday, 8 July 2025 19:46
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] PDT on ICF/ICR and CRF for multiple modes

 

Hi Michail,

 

Thanks for reviewing. Responses attached (updated version of the draft with incorporated changes will come up in the next few days).

 

Regards,

 

Alfred

 

On Tue, Jul 8, 2025 at 11:21 AM Michail Koundourakis <m.koundou@xxxxxxxxxxxxxxxxxxx> wrote:

Hi Alfred (and all),

 

Please see comments in the attached.

 

Kind regards,

Michail

 

From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: 04 July 2025 01:38
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBN] PDT on ICF/ICR and CRF for multiple modes

 

Hi all,

Please find a PDT that aims at bringing clarity on the ICF/ICR and CRF details when multiple modes are enabled:
- https://mentor.ieee.org/802.11/dcn/25/11-25-1071-00-00bn-pdt-cr-for-icf-icr-details-with-multiple-modes.docx

Since this touches the ICF/ICR of multiple modes I would like to ask for a careful review, especially from the POCs of the respective topics:
- Liwen on DPS and eMLSR
- Laurent on DUO
- Matt on NPCA
- Morteza on DSO
- Po-Kai on CFP (REVmf)
- Mohamed on LLI
- Ming on the CRF (I included some spec text in this doc but I believe it should go in 11-25/0910 so please double check)

PS: ICF/ICRs for MAP related topics are not covered in the above doc.

Thanks in advance for the review and happy 4th of July.

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


 

--

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


 

--

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



--
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


This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature