| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Dibakar,
I would like to provide an additional comment. Please note the besides
not supporting the ideas behind comments 6628/10376, which aim to add the additional constraint/restriction to the shared AP to the existing Primary AC rule,
we also do not agree with CR provided in 1934r0 on page 11, quote
“
A data or mangement frame from a coordinated AP during a shared TXOP by Co-TDMA shall belong to the AC_VI or AC_VO access category (#6628, 10376). “ We disagree that management frames need to be AC as this involves enabling QMF (which is not the “interesting” path to go).
The default AC for management frames is AC VO so why to classify it . Thank you, samat From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Samat,
Thank you for your comments.
Regarding #2, I would defer those CIDs for now to have more discussion. Members please share your opinion on these two CIDs.
Regards, Dibakar From: Samat Shabdanov <Samat.Shabdanov@xxxxxxxxxxxx>
Hello Dibakar,
I would like to provide a feedback on
11-25-1934 -CR for MAPC fairness, specifically on
that is flexible for coordinated AP(s) to follow without violating EDCA requirements for the gained TXOP by coordinated APs. Why to revisit now (when we already have 1.0draft) the basic C-TDMA framework what members have discussed intensively at early stages of
C-TDMA development and agreed upon in the past ? C-TDMA is intended for LL traffic, and coordinated APs will prioritize AC VO/VI to serve during the shared portion of TXOP. Ironically, the section on fairness (Section 37.27) on which members spent a good amount of time was discussed/developed to support the current
model (without additional rules/and constraints on coordinated APs). Thank you, samat form mtk From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Alfred,
Please note that I have uploaded
1934r0 to the mentor. All members who are interested in that section please review.
Regards, Dibakar From: Das, Dibakar <dibakar.das@xxxxxxxxx>
Hi Alfred,
Please add the following CR documents to the MAC queue:
Regards, Dibakar From: Arik Klein <0000177967a59511-dmarc-request@xxxxxxxxxxxxxxxxx>
Hello Alfred, Can you please help queue the following CR docs to the TGbn MAC agenda?
Regards, Arik From: Abhishek Patil <0000297b717f2a04-dmarc-request@xxxxxxxxxxxxxxxxx>
Hi Alfred, Can you please help queue the following CR docs to the TGbn MAC agenda? 11-25/1836 LB291: CR for CIDs assigned to Abhi - Part 5 Regards, Abhi From: Abhishek Patil <appatil@xxxxxxxxxxxxxxxx>
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 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 |