in 9.4.1.22. This subfield is a channel number name is “Channel” and indicates a channel number. 28 35.64 9.4.2.274 Channel number missing from WUR Discovery Channel field Rejected. No change has been proposed. This is same as in 9.4.1.22 the field name is “Channel” and indicates a channel number. Similar language is also used for “WUR Channel” field in the WUR Operation element. 61 23.57 9.3.3.3 needs to be true also for the WUR discovery case. Please apply throughout these tables for each WUR Discovery entry As in comment. Revised. Agree in principle with the commenter. TGax editor to make the changes shown in under all headings that include CID 61. 78 35.50 9.4.2.276 What is the difference between the WUR Discovery operating class, channel and the WUR operating class, channel indicated in the WUR Operation element? Also why is the element providing a list of other APs? Couldn't we use the Neighbor Report element for this purpose? As in comment. Rejected. WUR Discovery operating class, channel identify the channel used to transmit WUR Discovery frame, while WUR operating class, channel indicated in the WUR Operation element identify the channel used to transmit WUR Beacon frames. List of other APs are provided to help narrow down the number of WUR Discovery channels to be scanned during WUR scanning. During the design phase, it was agreed not to reuse Neighbor Report element but to design a new element optimized for WUR Discovery use. 80 36.31 9.4.2.276 Terminology is already defined. This is a AP. So instead of saying Transmitting WUR AP simply say Co-Located WUR AP. As in comment. Accepted. TGax editor to make the changes shown in under all headings that include CID 80.
286 36.04 9.4.2.276 Why is the definition of the count field convoluted? A count of 0 indicates that one AP information field is present? Modify the definition of the count field to reflect the number of WUR AP subfields included in the list. Rejected. The WUR AP Count field specifies the number of WUR AP subfields that are included in the WUR AP List field, minus one. Therefor count of 0 indicates one AP information is present. Similar encoding is used in various fields in the baseline (FSS, TBTT Information Count etc.). 287 36.64 9.4.2.276 "WUR AP subfield" should be "Transmitting WUR AP subfield". as in the comment. Also in lines 55 and 58. Rejected. "Transmitting WUR AP subfield" does not exist. "WUR AP subfield" is correct since the subfield identifies one AP. 357 26.23 9.3.3.11 There is no need for WUR Discovery element in the Probe Response frame body. Remove it. Remove third row in the table Rejected. A WUR AP may include the WUR Discovery element in Probe Response frames that is transmitted in response to a Probe Request frame that contains a WUR Capability element to advertise the WUR discovery channel(s) used by neighboring WUR APs. 372 35.25 9.4.2.276 "The WUR Discovery element is used to advertise the WUR discovery channels on which WUR APs transmit WUR Discovery frames." Is there any point in advertising this on PCR to STAs that have already found and are decoding packets on this PCR? Maybe I just don't understand all cases for when WUR Discovery is used, but based on the "WUR scanning" concept in 31.10 I don't see the need for ever advertising this information on the PCR. Specify this as a neighbor information or remove it. Rejected. The WUR Discovery element carries information about the WUR Discovery channels of the transmitting AP itself as well as neighbour APs. Knowledge of the WUR Discovery channels helps WUR STAs to track APs (Associated as well as even when its PCR is turned off by periodically scanning for WUR Discovery frames on the advertised WUR Discovery channels.