Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Kumail, Thanks for sharing your document. I have few questions related to your last revision of your document. I think that some misunderstandings remain.
As Jarkko said before, today the value 4 is already defined for the transmission of latency sensitive data. For me, peer-to-peer traffics are latency sensitive traffic. For sure,
the value 4 need more clarifications about what kind of traffics are allowed to be transmitted. Why do you define a new one ?
This sentence is not clear enough. Do you want to restrict the transmission for P2P traffics only ? If it is, I think that it would be better to define it directly in the table
describing the functionality of each value of the Broadcast TWT Recommendation field.
P2P traffics is also allowed through EDCA mode. Why do you use a “shall” ? P2P traffics is transmitted not only after a MU RTS TXS frame. Globally, the proposed text need more clarifications. Regards Patrice From: Muhammad Kumail Haider <kumail.ieee@xxxxxxxxx>
Hello all, I have updated 11-21/1224 CC 36 CR for Restricted TWT Setup to Rev.4 based on feedback from the group and offline discussions.
Please let me know if there are any further comments/questions. Best regards, Kumail 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 |