NOTE—When a STA is in normal (non-APSD) PS mode, the rules described in 11.2.2.6 for PS-Poll operation apply to any downlink block ack agreement without an associated schedule. An (A-)MSDU delivered for this block ack agreement in response to the PS-Poll frame might be delivered in an Identifiers Comment Proposed change CID 7595 Mark RISON 11.1.4.3.5 1568.45 This para is duplicated in the next 2 Delete this para CID 7596 Mark RISON 11.1.4.3.5 1568.50 What about other things that need to be tied specifically to the probe request? Add " If dot11RadioMeasurementActivated is true and the RSNI element was requested, an RSNI element containing the of the Probe Request frame shall be included (see 9.4.x.x (RSNI element) and Table 9-x (RSNI values)). NOTE--If no RSNI measurement result is available, the RSNI value is set to indicate "Measurement not available" (see Table 9-x (RCPI values))." and similarly for any other elements CID 7597 Mark RISON 11.30.1 1842.42 What about other things that need to be tied specifically to the probe request? Add " If dot11RadioMeasurementActivated is true and the RSNI element was requested, an RSNI element containing the RSNII of the Probe Request frame shall be included (see 9.4.x.x (RSNI element) and Table 9-x (RSNI values)). NOTE--If no RSNI measurement result is available, the RSNI value is set to indicate "Measurement not available" (see 9-x (RCPI values))." and similarly for any other elements Discussion: For all things that can be Requested that are specific to a frame, it is necessary to state which frame they are specific to and what value is used of the request cannot be satisfied. It is true that there appears to be some duplication. Proposed changes: Change 11.1.4.3.5 Contents of a probe response from 1568.45 as follows:
there are no such parameters anymore (we deleted them in favour of dot11(Re)AssociationResponseTimeOut) Discussion: Nah, probably just easier to go with the dot11 flow! Proposed changes: Change 1017.26 as follows: A non-PCP and non-AP STA that receives a DMG Operation element can use the of this field to configure the AssociateFailureTimeout parameter in the MLME-ASSOCIATE.request primitive and the ReassociateFailureTimeout parameter in the MLME-REASSOCIATE.request primitive set dot11AssociationResponseTimeOut. Change 1719.47 as follows: the STA has sent a (Re)Association Request frame within dot11AssociationResponseTimeOut but has not received a corresponding (Re)Association Response frame and the (Re)AssociateFailureTimeout has not expired At 2885.19 change “Association” to “(Re)Association”. Proposed resolution: REVISED Make the changes shown under “Proposed changes” for CID 7240 in <this document>, which instead kill (Re)AssociateFailureTimeout again. Identifiers Comment Proposed change CID 7317 Mark RISON 11.1.2.1 1554.34 "A STA contained in the AP or PCP shall initialize its TSF timer independently of any simultaneously started APs or PCPs" -- this cannot in general be acheved, unless the APs/PCPs are coordinated. Needs to be restricted to managed ("enterprise/corporate") contexts, but this is arguably out of scope of the standard anyway Change to "A STA contained in the AP or PCP shall initialize its TSF timer independently of any simultaneously started APs or PCPs it is aware of", or delete Discussion: A STA doesn’t necessarily know about simultaneously-started APs or PCPs. Proposed changes: Option 1: Delete the offending sentence.