3796 Reuss, Edward 33.20 For the phrase ", the field is set to all ones", shouldn't the field be set to "Reserved"? Do we have a standard assignment for Reserved fields? Why does this clause explicitly specify this reserved field is set set to all ones? Change this field to follow the standard behaviour for a reserved field. Agree in principle: See 11/1216r0 MU Discussion: The language is changed in D1.1 CID 3285, and no longer contains the offending text 3797 Reuss, Edward 33.34 For the phrase "Sounding Sequence are reserved and set to 0", shouldn't the be set to "Reserved"? Do we have a standard assignment for Reserved fields? Why does this clause explicitly specify this reserved field is set to all zeros? Change this field to follow the standard behaviour for a reserved field. Agree in principle. See 11/1216r0 MU Discussion: The language is changed in D1.1 under CID 3285, and no longer contains the offending text 3396 Seok, Yongho 8.4.11.38 42.30 The phases "feedback with BW=20MHz", "feedback with BW=40MHz", and "feedback with BW=80MHz" are not clear. Rewrite the sentences with the defined term "Channel in VHT MIMO Control field. in principle. See changes implemented under CIDs 2160 and 3171 in 11/1206r1 MU For reference, thse changes are: When the BSS operates operating with a 40 MHz, 80 MHz, and or 160 MHz channel width, the subcarriers for which Compressed Feedback Beamforming Matrix subfield is sent in the Beamforming feedback with when the Channel Width subfield of the VHT MIMO Control field is equal to BW=20MHz corresponds to the tonessubcarriers in the primary 20 MHz channel. When the BSS operates operating with an 80 MHz, and or 160 MHz channel width, the subcarriers for which Compressed Feedback Beamforming Matrix subfield is sent in the Beamforming feedback with when the
MU Beamformer Capable Indicates support for(#3298) operation as an MU beamformer (see 9.30.5 (VHT sounding protocol)) Set to if not supported Set to 1 if supported MU Beamformee Capable Indicates support for(#3298) operation as an MU beamformee(see 9.30.5 (VHT sounding protocol)) Set to 0 if not supported Set to 1 if supported 3557 Stephens, Adrian 8.4.2.100.1 53.38 "NOTE 1—A STA that sets MU Beamformee Capable to 0 is not able to demodulate an MU VHT PPDU with only one non-zero NSTS subfield." This may or may not be true. Replace with: "...is not required to be able to demodulate..." Agree. See 11/1216r0 MU Change: 8.4.2.140.2 VHT Capabilities Info field NOTE 1—A STA that sets MU Beamformee Capable to 0 is not able to demodulate an MU VHT PPDU with only one non-zero NSTS subfield. 3299 Rosdahl, Jon 8.4.2.100.2 85.39 what are Compressed Steering Number of Beamformer Antennas Supported and Number of Sounding Dimensions set to if a device does not support BF? Say something like "Set to 0 if operation as a beamformee/beamformer [respectively] is not supported" Agree in principle. See 11/1216r0 MU Change: Table 8-ac13—Subfields of the VHT Capabilities Info field (continued) Compressed Steering Number of Beamformer Antennas Supported Indicates the maximum number of beamformer antennas the beamformee can support when sending compressed beamforming feedback et to maximum value minus 1 3398 Seok, Yongho 8.4.2.100.2 86.40 [should be 52.40] The number of antennas is not necessarily the same with the number of streams depending on the implementation. Focusing the number of streams seems more reasonable. Use the number of space-time streams instead of the number of antennas. MU time