| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Pooya, The following are the comments from my side:: 1, the TID-to-Link Mapping elements in Beacons of different links will indicates the different start time when the new TID-to-Link mapping will be used. The reason
is that the Switch Count will indicate the TBTTs of different links which are in different times. This is not right. 2, the purpose of changing MU EDCA is not clear to me. 3, it is not clear why TID-to-Link mapping 2 is defined. If the purpose is for supporting low latency traffic, the method other than this is already provided by the
spec. 4, it seems the Mapping Switch Count, Duration, or Mapping Switch Count + Duration transmitted in different links can not give the same start time when the new TID-to-Link
mapping will happen. 5, it makes no sense to have two levels of denying the TID-to-Link mapping request. 6, it is not clear why the non-AP MLD is allowed to use normal EDCA or MU EDCA to transmit frames of a TID in a link where the TID is not mapped to the link.
Best Regards, Liwen From: Pooya Monajemi <00000ef0b9e0aff7-dmarc-request@xxxxxxxxxxxxxxxxx>
Hello all, Opening this thread to discuss 1793, please reply with your comments Many thanks Pooya 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 |