| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Thanks Jason. Will it be possible to add a Note saying the “HE TP Ack” case is not precluded ? The reason I am asking is if people start to think that the BAR is always sent in separate PPDU and start designing
any optimization or enhancements that depend on that assumption. Ideally, a figure would be clearer since it would capture all possible sequences.
From: Guoyuchen (Jason Yuchen Guo) <guoyuchen@xxxxxxxxxx>
Hi Dibakar, According to the text in this document, the coordinating AP can use the following ACK policies:
I make
“Normal ACK or Implicit BAR”
disallowed to put the duration of the ACK procedure under coordinating AP’s control (rather than decided by the non-AP STA) Best, Jason 发件人:
Das, Dibakar <dibakar.das@xxxxxxxxx> Hi Jason, Thanks for preparing all these docs. For 1871, I quite did not get why the case where the coordinating AP can include the BAR within the CBF DL PPDU is explicitly disallowed. Is it possible to
defer this presentation to tomorrow AM2 or PM1 so I can participate in the discussion ? Regards, Dibakar From: Guoyuchen (Jason Yuchen Guo) <000018696e95f088-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Alfred, Please add the following CR documents to the MAC queue: 11-25-1840-00-00bn-lb291-cr-for-37-15-2-1-1 (49 CIDs) 11-25-1852-00-00bn-lb291-cr-for-37-15-2-1-2-Part I (14 CIDs) 11-25-1870-00-00bn-lb291-cr-for-37-15-2-1-3-Part I (44 CIDs) 11-25-1871-00-00bn-lb291-cr-for-37-15-2-1-3-Part II (36 CIDs) TGbn members, please provide your early feedback so that we can speed up the process. Best, Jason 发件人:
Gaurang Naik <0000305a2f8ce933-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Alfred, Please add the following document to MAC queue. It resolves 38 CIDs.
Thanks Gaurang From: Jay Yang <yang.zhijie@xxxxxxxxxx>
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 put the following CR doc to the MAC agenda?
11-25/1839r0 CR for CIDs on MAPC security part-1 (29 CIDs )
Thanks Best Regards Jay Yang (杨志杰)
Original From:
AbhishekPatil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx> Date:
2025年10月27日 17:19 Subject: Re: [STDS-802-11-TGBN] 11bn LB291 CR request Hi Alfred, Can you please help queue the following CR docs to the TGbn MAC agenda? 11-25/1834 LB291: CR for CIDs assigned to Abhi - Part 3 Regards, Abhi From: Abhishek Patil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx>
WARNING: This
email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hi Alfred, Can you please help queue the following CR doc to the TGbn MAC agenda? Regards, Abhi From: wangkaidong (E) <00004ea939387e7b-dmarc-request@xxxxxxxxxxxxxxxxx>
WARNING: This
email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Hello Alfred, Please help add the CR document to the MAC queue. It resolves 1 CID. Thank you! 23-Oct-2025 ET 2025 1859 0 TGbn 11bn LB291 CR for CID 4983 Kaidong Wang (Huawei ) Best regards, Kaidong Wang From: Fang, Juan <juan.fang@xxxxxxxxx> Hi Alfred, Please help to add following to the PHY queue, it has 8 CIDs .
Thanks, Juan From: Gaurang Naik <0000305a2f8ce933-dmarc-request@xxxxxxxxxxxxxxxxx> Hi Alfred, Pls add the following to the MAC queue. It resolves 15 CIDs .
All, please let me know if you have any feedback. Thanks Gaurang From: Gaurang Naik <gnaik@xxxxxxxxxxxxxxxx> Hi Alfred, Please add the following CR document to the MAC queue. It resolves 23 CIDs .
Thanks Gaurang From: Yujian (Ross Yu ) <00001792b51ef4ea-dmarc-request@xxxxxxxxxxxxxxxxx>
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 CR documents into the queue, it contains 20 editorial CIDs . https://mentor.ieee.org/802.11/dcn/25/11-25-1791-00-00bn-lb291-editorial-comments-part-1.docx regards 于健 Ross Jian Yu Huawei Technologies 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 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 |