referring to this row of the table, in VHT case MFB (as shown in the picture below) includes the SNR, hence HT MFB and VHT MFB are different. Also, MAI is not defined for the VHT case control field in 'VHT format'; HT control field is defined as [B0=HT/VHT, on HT/VHT format]; HT format description for B1-B31 reflects 11n-2009 and simply add text specifying that this is the meaning when B0 is set to 0. VHT format has an independent description for B1-B31 which uses the current one in table and is valid only when B0 is set to 1; The denomination +HTC is intended to mean that an HT control field is included (either in HT or VHT format); When relevant, the HT or VHT format is explicitly indicated with additional text; 1344 7.1.3.5a 5 TR Don't need to re-interpret MFB/ASELC field in Table 7-6a, because when HT/VHT Remove the mentioned text and table 7-6a. Agree. As in comment MAC
field is 1, subsequent text, figures and tables already explain the re-define HTC field in details, therefore this table is redundant. 1473 7.1.3.5a 5 42 TR the definition of MFB/ASELC subfield is not accurate when it is as a subfield of VHT control field. if the HT/VHT subfield is set to the value 0, this subfield contains recommended MFB expressed as an HT MCS, and if the HT/VHT subfield is set to the value 1, the 4 highest numbered bits of this subfield contains a recommended VHT MCS ,and the lowest numbered 3 bits of this subfield contain a recommended VHT NSTS is interpreted as defined in Figure7-4f . Modified. Description for HT and VHT format have been placed in separate sections MAC 1120 7.1.3.5a 5 11 TR This section does not make a lot of sense as amended. Essentially two formats for this field are described: HT Control Rename the field "HT/VHT Control". Define meaning to "HT Control" and "VHT Control" (i.e. format dependent on B0 setting). Modified. proposed new description account for this comment MAC
233 7.1.3.5a 5 27 TR Why have a VHT bit when a transmission is either VHT or HT as indicated by the SIGNAL field in the PHY preamble? Suggest removing this redundant bit. After auto-detection the information about whether the frame is HT or VHT may be passed through RXVECTOR from PHY to MAC. Also Change "Figure frame format" accordingly. Suggest removing this redundant HT/VHT bit. Change "Figure frame format" showing HT/VHT control field. Insert text indicating "HT/VHT control field is a HT control field or a VHT control field depending on whether the MPDU is a HT MPDU or VHT MPDU respectively." Reject the removal of B0; The bit B0 is needed in case of control wrapper. Control wrapper can be sent with non-HT in which case B0 defines the type of the field. Discussion on whether the VHTC can be in HT PPDU and vice versa; MAC Comments referred to capability indications
VHT format Capability in VHT capabilities info can be indicated with 1 bit in position B22; Section 9.7a HT Control field operation need be updated accordingly; Comments referred to format 1234 7.1.3.5a 6 5 TR Fields such as AC Contstraint are not defined. Add them to table perhaps with "see table 7-6a" as a definition Added in the table; description points to the HT case MAC 1345 7.1.3.5a 7 58~64 TR Need to describe how to set Nsts, MCS and SNR fields in table7-6i. Insert in table 7-6i: Nsts field is set to true Nsts-1, MCS field is set to MCS, SNR field refer to (9-1) in 9.18.3. Agree. Added reference to section 9.18.3 (Link Adaptation using the VHT control field), where MAC
more details are provided 885 7.1.3.5a 7 38 TR The unsolicited feedback should refer to SU or MU VHT PPDU If the Unsolicited MFB subfield is set to 1 and the FB Tx Type subfield is set to 1, the unsolicited MFB refers to a beamformed or VHT PPDU. Reject. According to description in 9.18.3, FB Tx Type subfield is set according to the Beamformed indication in SIG-A2, only refers to SU case. The receiver of unsolicited feedback can use the GID(L and H) to determine if feedback is referred to an SU or MU PPDU MAC 24 7.1.3.5a 7 58 TR "Nsts" should be defined in section 3.2 as well as "MCS". Insert the following definitions in section 3.2: Nsts: The number of space-time streams. Agree MAC 966 12.3.5.10.2 65 1 TR in figure 7-4e, the only reserved bit is in position 29; For helping the receiver parsing in case of future extensions, the posistion Move the 'Solicited/unsolicited' bit in position 29 and have B1 to be reserved; modify table 7-6h accordingly; As suggested. Note: Section of comment was wrong. Comment refers to 7.1.3.5a. COEX
of the reserved bit should be within the first byte; Some Editorial comments 1004 7.1.3.5a 7 38 ER Grammer: "If the Unsolicited MFB subfield is set to 1 and FB Tx Type subfield is set to 0, the unsolicited MFB refers to either unbeamformed VHT PPDU, transmit diversity utilizing Alamouti coding VHT PPDU." Change the sentence to "If the Unsolicited MFB subfield is set to 1 and FB Tx Type subfield is set to 0, the unsolicited MFB refers to either unbeamformed VHT PPDU or VHT PPDU with STBC." Agree. As suggested. Ed 1005 7.1.3.5a 7 40 ER The terminology 'Alamouti coding' is not used in 4.01. Change 'Alamouti coding' to 'STBC' Agree. Modified to "using an STBC VHT PPDU". Ed 1353 7.1.3.5a 7 40 ER "….. refers to either unbeamformed VHT PPDU, transmit diversity utilizing ….." What's the grammar there? Shouldn't be "either….or……"? change to ""….. Refers to either unbeamformed VHT PPDU or transmit diversity utilizing ….." Agree. See #1004 Ed
Bits: 2 2 1 2 1 1 1 1 B11-B12 B13-B15 B16-B18 B19 B20 Grouping Set Compressed Steering Number of Beamformer Antennas Supported Number Of Sounding Dimensions MU Tx Capable MU Rx Capable 2 3 3 1 1 B21 B22 B22B23-B31 VHT TXOP PS +HTC-VHT Capable Reserved 1 1 13 12 Figure --VHT Capabilities Info field The subfields of the VHT Capabilities Info field are defined in . Table --Subfields of the VHT Capabilities Info field Add the following row after the last row of Table 7-16 Subfield Definition Encoding +HTC-VHT Capable of receiving a HT Control field in the VHT format Set to 0 if not supported Set to 1 if supported Note—A STA that sets MU Rx Capable to 0 is not able to demodulate an MU VHT PPDU with only one non-zero Nsts subfield. Note—The Compressed Steering Number of Beamformer Antennas Supported also indicates the maximum number of space time streams in the NDP packet that the STA can support as a beamformee. Include in the the following sections, with the specified changes: 9.17 Sounding PPDUs