| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Wook Bong and all, Thanks for the comments. Please see the updated version: https://mentor.ieee.org/802.11/dcn/20/11-20-1276-06-00be-pdt-phy-eht-preamble-eht-sig.docx Regarding something similar as table 27-25, like I commented in the word doc, I will add them later by CR after D0.1. Thanks. regards 于健 Ross Yu Huawei Technologies 发件人: Wook Bong Lee [mailto:wookbong.lee@xxxxxxxxxxx]
Hi Ross, Thanks for your effort. I have following comments. 1.
“For an EHT PPDU sent to multiple users, the EHT-SIG content channel consists of a Common field followed by a User Specific field. For an EHT PPDU
sent to a sinle user, it is TBD. The configuration of the Common field regarding the postion and number of CRC and Tail subfields is TBD for an EHT PPDU sent to multiple users. For an EHT PPDU sent to a single user, it is TBD.” è
It should be EHT MU PPDU throughout the all places whenever it is EHT MU PPDU. è
Types: sinle
à single. postion
à position è
Also, is this true for NDP? Maybe we need to add “For an EHT NDP, it is TBD.” è
Seems yellow highlighted texts are duplicated at least for single user case. In uncompressed mode, single user transmission is allowed? Same for
the last sentence before 34.3.10.7.3. è
Typo: postion
à position 3.
Uncompressed vs. Non-compressed è
Need to have a single term.
4.
In page 4. “All RU Allocation subfields at the same position in each EHT-SIG Common field of the two EHT-SIG content channels are set to TBD4 or
TBD5 value (see Table 34-xx3 (RU Allocation subfield)).” è
Can you delete this? We already have all zero user field with unassigned 242-tone RU. So, I don’t think we need this.
5.
In page 5. “If an RU is an unallocated RU, zero users are allocated to it. Otherwise, ”
è
Can you delete this? Same as 5. 6.
As I mentioned during the call, I think it is useful to have table 27-25 in 11be.
7.
End of page 6 to beginning of page 7. I think we also need MRU for smaller bandwidth in larger bandwidth. For example, 484+242 in 160, and 320 MHz. 8.
“The pre-HE modulated fields (see Figure Ref XX (Timing boundaries for EHT PPDU fields if midamble is not present)) are not transmitted in 20 MHz
subchannels in which the preamble is punctured.” è
Type. pre-HEà
pre-EHT Best regards, Wook Bong Lee From: Yujian (Ross Yu) [mailto:ross.yujian@xxxxxxxxxx]
Hi all, Attached please find the new revision based on Alice and Sameer’s comments offline. All your comments are welcome. Thanks. https://mentor.ieee.org/802.11/dcn/20/11-20-1276-05-00be-pdt-phy-eht-preamble-eht-sig.docx regards 于健 Ross Yu Huawei Technologies 发件人: Yujian (Ross Yu)
Hi Alice, Bin, Sameer and all, As discussed during today’s call, please check if you have any part you want to make it yellow (TBD) before I run the SP next time. https://mentor.ieee.org/802.11/dcn/20/11-20-1276-04-00be-pdt-phy-eht-preamble-eht-sig.docx regards 于健 Ross Yu Huawei Technologies 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 |