| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello Sanket, Thank you for part 3 of CR series on ctdma. If you run an SP on it, please consider deferring the section specified in p.s.
Also, please make a record to update
-
fig. 37.5 since “no ack” for the txop return.
-
No need for “
.. within the allocated time… “ since it is clarified in (#5393,#9909,#10971,#12105) Serhat, while agree on bullet 1, disagreeing on bullet 2. We can discuss offline if available. Thank you, samat
p.s. 4744,#5533,#5956,#6620,#9500,#10973,#10980,#12106)
“ ……
1 if the Co-TDMA coordinating AP explicitly solicits a TXOP return from a Co-TDMA coordinated AP. In this case:
o
The Co-TDMA coordinated AP shall transmit a MAPC TXOP Return frame to the Co-TDMA coordinating AP in the allocated time.
·
0 if the Co-TDMA coordinating AP does not explicitly solicit a TXOP return. In this case:
o
The Co-TDMA coordinated AP may transmit a MAPC TXOP Return frame in the allocated time …. ” From: Serhat Erkucuk <serkucuk@xxxxxxxxxx>
Hi Sanket, Thanks for preparing this CR document. Some of my comments are as follows:
If the "TXOP Return Support=1 & TXOP Return Solicit=0" --> Co-TDMA coordinated AP "may" transmit a TXOP return frame.
If the "TXOP Return Support=0 & TXOP Return Solicit=0" --> Co-TDMA coordinated AP "shall not" transmit a TXOP return frame.
I think this may be somehow complicated from the Co-TDMA coordinated AP perspective as it needs to take two different actions when TXOP Return Solicit=0 (for example, it has to also account
for the TXOP Return Support information received in another frame). I wanted to share my thoughts on the revisions you have made. I think we need to have more discussions on the proposed revisions for the
37.15.2.3.5 TXOP return phase. Thanks, Serhat From: Sanket Kalamkar <000033b8f79f2eb4-dmarc-request@xxxxxxxxxxxxxxxxx> Hi Alfred, I uploaded the CR document 11-25/1957r0 on mentor. Can you please queue it for presentation in MAC? Best, From: Sanket Kalamkar <sankal@xxxxxxxxxxxxxxxx> Hi Alfred, I uploaded the r3 of 11-25/1907. Best, Sanket From: Sanket Kalamkar <000033b8f79f2eb4-dmarc-request@xxxxxxxxxxxxxxxxx> WARNING: This email
originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Uploaded r2 following offline feedback suggesting minor editorial changes and deferred three CIDs. Best, Sanket From: Sanket Kalamkar <sankal@xxxxxxxxxxxxxxxx> I uploaded 11-25/1907r1 to IEEE Mentor to incorporate minor typo corrections. Best, Sanket From: Sanket Kalamkar <000033b8f79f2eb4-dmarc-request@xxxxxxxxxxxxxxxxx> WARNING: This email
originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. I uploaded the CR document 11-25/1907r0 to IEEE mentor. It resolves 35 CIDs. Co-TDMA TTT: your feedback is welcome. Best, Sanket From: Sanket Kalamkar <000033b8f79f2eb4-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, Could you please add the following CR documents to the TGbn MAC agenda?
Best, Sanket From: Liyunbo <00001846a2e5e0c1-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 to the MAC queue:
Regards, Yunbo 发件人: Das, Dibakar [mailto: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 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 |