| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Boyce, we need to start from somewhere as many have indicated; also with MLO there’s the option of using quieter links. Regards, Payam From: Dibakar Das <dibakar.das@xxxxxxxxx> Hi Boyce, Just wanted to address the concern on pre-11be devices a little bit. In the 6 GHz channel, there are only 11ax STAs. So, the problem may not be as bad.
Regards, Dibakar From: Yangbo (Boyce, 2012 NT Lab) <yangbo59@xxxxxxxxxx>
Hi Chunyu,
Thanks for your contribution and sp As you mentioned in the straw poll text, EHT STAs shall end it’s TXOP. What about pre-EHT STAs? If pre-EHT STAs don’t follow the rules, there would be two problems: 1, EHT STAs are actually have
lower priority than legacy STAs by your SP, which seems not right to me. 2, In a real WLAN network, pre-EHT STAs would be the majority for a long time(According to IDC, Upto 40% of unit shipments in 2019 are 802.11n standard) and those STAs don’t follow any
rules defined by restricted TWT mechanism, which would actually ruin the mechanism.
As to the wording, I suggest you use a more general description for the mechanism like ‘protected session’, ’protected access period’ or ’protected access resource’ instead of ‘restricted
TWT session(s)’ in this straw poll. So this straw poll focus only on the boundary rules. May be you can add another straw poll to ask whether 11be introduce restricted TWT. Regards Boyce Yangbo 发件人:
董贤东
[mailto:0000120bd98e7489-dmarc-request@xxxxxxxxxxxxxxxxx]
Hi, Chunyu, Thanks for initialing this thread, I don’t
object your proposal, but I think we should have a solution for the case
“a TXOP of legacy STA may overlap/partially overlap with the restricted TWT”.
BTW, could you add note in SP, “ a TXOP of a legacy STA overlaps/partially
overlaps with the restricted TWT which is defined in SP2, this will be studied further”. Best Regards Xiandong Dong 发件人: Chunyu Hu <chunyuhu07@xxxxxxxxx>
Hi, all: Based on feedback we collected, we prepared a second version of SP1 and hope to get some early feedback of the WG’s preference: ---------------- Version 1 (current one):
Version 2 (new):
Discussion:
---------------- Feel free to send me or any co-authors an email or reply to this thread. Thank you very much! Chunyu To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 #/******本邮件及其附件含有小米公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential information from XIAOMI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!******/#
To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1 |