IEEE P802.11 Wireless LANs MAC Comments for Discussion Date: 2018-07-31 Author(s): Name Affiliation Address Phone email Mark Hamilton Ruckus/ARRIS 350 W Java Dr Sunnyvale, CA 94089 +1.303.818.8472 For review by TG: 1281 839.64 64 9.4.1.7 In Table 9-51, Reason codes 40-44 are not defined. Please change the Reason code "45" to "40-45". Discussion: Context: Robert Stacey (ANA coordinator) confirms that these entries were assigned to 802.11e, and were apparently not used. They should be marked as “Reserved” in Table 9-51, and marked appropriately for future use in the ANA database (which Robert will do). By changing the Reason code column from “45” to “40-45” (as proposed), 40 through 44 will become Reserved. Proposed Resolution: Accepted. 1400 2272.22 22 11.38.1 "the STA shall indicate support for MCSs 8(n-1) to 8(n-1)+7" should be clearer as to what kind of MCS On lines 22 and 23 at the referenced page change "MCS" to "HT-MCS" Discussion: Context: Arguably, it should be apparent that setting bits in the Rx MCS Bitmask contained in the HT Capabilites element, would be indicating HT MCS rates. However, this paragraph is already rather confusing with the number of
1415 743.03 3 9.2.4.5.4 The way the ack policy is referred to is confusing/inconsistent. Do you refer to the options indicated by the bit pattern (e.g. "Normal Ack or Implicit Block Ack Request") or do you refer to only the type of ack being requested in the context being requested (e.g. just "Implicit Block Ack Request" in the case of an Change "The Ack Policy subfield is 2 bits in length and identifies the acknowledgment policy that is followed upon the delivery of the MPDU." to "The Ack Policy subfield is 2 bits in length and identifies, together with other information such as whether it is in the context of an S-MPDU and the value of bit 6 of the Frame Control field, the acknowledgment policy that is followed upon the delivery of the MPDU." at the referenced location 1536 1267.56 56 " Values of Operating Class are shown in Table E-4 (Global operating classes), of which operating classes that, together with the channel number, indicate the primary channel is valid (see 11.42.8 (Reduced neighbor report))." this sentence doesn't make sense Delete the referenced sentence in the referenced location 1485 2084.47 47 11.10.6 " A STA refusing a measurement request within an individually addressed Radio Measurement Request frame shall respond with a measurement report indicating that it is refusing the measurement request. A STA shall not respond to measurement requests received in Radio Measurement Request frames in this manner." is self-contradictory Add "group addressed" after "shall not respond to" in the cited text at the referenced location
1431 2249.15 15 11.31.1 "the Capabilities element, the Operation element" -- there are no such elements. Discussions with 11ad experts suggests the intent is that you use all the elements relevant to the target band/PHY In the referenced subclause change "A multi-band capable device shall include, in any transmitted FST Setup Request frame and in any transmitted FST Setup Response frame, the Capabilities element, the Operation element, the EDCA Parameter Set element, Supported Rates and BSS Membership Selectors element, Extended Supported Rates and BSS Membership Selectors element, and Supported Channels element that are applicable to the band and channel number indicated within its most recently transmitted element that was transmitted on the same band and channel number on which it is transmitting the FST Setup Request or FST Setup Response frames." to "A multi-band capable device shall include, in any transmitted FST Setup Request frame and in any transmitted FST Setup Response frame, all the elements that are applicable to the band, PHY and channel number indicated within its most recently transmitted Multi-band element that was transmitted on the same band and channel number on which it is transmitting the FST Setup Request or FST