Furthermore, Pg:L::366:34 has description of the capabilities. The relationship with HE MCS NSS Support is missing Change the encoding and definition accoridng to the comment Reject— Resolution of CID15889 applies. "Rx 1024-QAM Support < 242-tone RU Indicates support fro [sic] receiving on a 26-, 52-, and 106-tone RU. [...] An HE STA may transmit an HE PPDU with 1024-QAM on a 26-, 52-, and 106-tone RU to a recipient STA if it has received from the recipient STA an HE Capabilities element with the Rx 1024-QAM Support < 242-tone RU subfield in the HE PHY Capabilities Information field equal to 1; otherwise the HE STA shall not transmit an HE PPDU with 1024-QAM on a 26-, 52-, and 106-tone RU." Does this mean that if the AP sets this to 0, the STA should refuse to transmit 1024-QAM on a 26/52/106-tone RU even if commanded to do so by the AP in the Trigger frame? Add a requirement that an AP that sets Rx Support < 242-tone RU to 0 not request an RU with < 242 tones and 1024-QAM Reject— The comment is already resolved by the following text P:L::366:40 “An HE AP shall not set UL MCS subfield of the User Info field in a Trigger frame to 10 or 11 for a 26-, 52- , or 106-tone RU allocation unless the User Info field is addressed to a HE STA from which the HE AP has received an HE Capabilities element with the Tx 1024-QAM Support < 242-tone RU subfield in the HE PHY Capabilities Information field equal to 1.” Discussion on CID15899 In 11ax D2.0, 1024-QAM was allowed for use on RU sizes > 242-tone RU. This restriction was relaxed in D3.0 by addition of the following capabilities.
CID P.L Comment Proposed Change Resolution Remove the row since it duplicates with the row in P162L59 Change the encoding and definition accoridng to the comment Revised— There exists duplication. TGax Editor: make changes for CID 15891 according to Remove the row since it duplicates with the row in P163L6 Change the encoding and definition accoridng to the comment Revised— exists duplication. TGax Editor: make changes for CID 15892 according to Definition of "Tx Support < RU" in Table is duplicated on line 59 Remove duplication Revised— Refer to resolution of CID15891 Why is "Tx 1024-QAM Support < 242-tone RU" reserved for an AP? Is this for TB only? Clarify Reject— Yes, the capability is for HE TB PPDU. It allows AP to set MCS correctly in the Trigger frame for this non-AP STA. This field is reserved for an AP because Tx properties are not advertised. Name of subfield is "Tx 1024-QAM < RU Support" in Figure 9-589cl. In Table 9-262aa "Tx 1024-QAM Support < 242-tone RU" is used (for one of the duplicate entries) Align names between Figure 9-589cl and Table 9-262aa. Revised— “Tx 1024-QAM Support < RU” is deleted. “Rx 1024-QAM Support < RU” is deleted. Furthermore, some language edits are made. TGax Editor: make changes for CID 16746 according to Name of subfield is "Rx 1024-QAM < RU Support" in Figure 9-589cl. In Table 9-262aa "Rx 1024-QAM Support < 242-tone RU" is used (for one of the duplicate entries) Align names between Figure 9-589cl and Table 9-262aa. Revised— Refer to resolution of CID 16746. 6
PPDU With Compressed SIGB" With Compressed SIGB” is not ambiguous. Furthermore, the description of the capability makes it clear that this capability indicates support for reception of an HE MU PPDU with single RU spanning the entire PPDU BW, using compressed HE-SIG-B. Shouldn't the field name be "Rx Full BW SU RU Using HE MU PPDU With SIGB" As in the comment Reject— The current capability, “Rx Full BW SU Using HE MU PPDU With Compressed SIGB” is not ambiguous. Furthermore, the description of the capability makes it clear that this capability Indicates support for reception of an HE MU PPDU with single RU spanning the entire PPDU bandwidth, using non-compressed format, when its PPDU bandwidth is less than or equal to 80MHz. It seems that HE DL MU PPDU from AP to STA is mandatory. Are you saying that HE MU PPDU with single full BW RU to STA is optional? Clarify it. Reject— No, the capability bits pertain to signalling methods to indicate transmitting a single RU with full BW using an HE MU PPDU, with compressed and non-compressed HE-SIG-B format. 28-19 indicates that HE-SIG-B compression is used if and only if MU-MIMO is being used. Therefore references to compressed HE-SIG-B would be much clearer as references to MU-MIMO (and ditto Change "Rx Full BW SU Using HE MU PPDU With Non-Compressed SIGB" to "Rx Full BW SU Using HE MU PPDU With throughout; change "Rx Full BW SU Using HE MU PPDU With Compressed SIGB" to "Rx Full BW SU Using HE MU PPDU Without throughout Reject— for bandwidth being 80MHz or less, when transmitting single RU with full BW using an HE MU PPDU, both compressed and non-compressed HE-SIG-B format are allowed. The current descriptions look reasonable.