Make the changes shown under “Proposed changes” for CID 7478 in <this document>, which state instead that only one MSDU is sent in response to a PS-Poll. 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 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 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 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 Table 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:
consecutive Fine Timing Measurement frames in a burst instance." Discussion: It is preferable to make Min Delta FTM apply to all FTM frames, including the first FTM frame in a non-ASAP FTM session (which is not in a burst instance) and the frames at the end of one burst instance and the start of the next, as this ensures the initiating STA will not be overloaded. Proposed resolution: REVISED At 1768.30 change “Within a burst instance, consecutive Fine Timing Measurement frames shall be spaced at least Min Delta FTM apart.” to “Consecutive Fine Timing Measurement frames transmitted to a given peer STA shall be spaced at least Min Delta FTM apart.” Identifiers Comment Proposed change CID 7468 Mark RISON 9.4.2.167 1066.30 "The FTM Format And Bandwidth field indicates the requested or allocated packet format and bandwidth used by all Fine Timing Measurement frames in an FTM session" -- this is not true, since FTM frames can use a simpler or narrower format than indicated. Change to "The FTM Format And Bandwidth field indicates the requested or allocated PPDU format and bandwidth that can be used by Fine Timing Measurement frames in an FTM session" Proposed resolution: ACCEPTED Identifiers Comment Proposed change CID 7504 Mark RISON 11.24.6 1764.23 should be a mechanism to allow the responding STA to ask the initiating STA to re-initiate an FTM session (because it wants to change the parameters) As it says in the comment. A bit in the FTM frame could be used to signal this Proposed resolution: REJECTED Such a mechanism is not necessary. If the responding STA wishes to change the parameters, it can terminate the FTM session using an FTM frame with the Dialog Token set to 0, and if the initiating STA wishes to continue doing FTM it will send an FTM Request frame to start a new FTM session, allowing the responding STA to specify new parameters. Identifiers Comment Proposed change CID 7419 Mark RISON 10.8 says "For MSDUs or A-MSDUs belonging to the service class of QoSAck when the receiver is a QoS STA, the QoS Data frames that are used to send these MSDUs or Work out which is right and make the other one say the same. Even better, avoid the duplication
At 1966.22 change “A STA performing secure password-based, or PSK, authentication uses SAE authentication.” to “A STA performing password-based authentication uses PSK or SAE authentication.” At 1966.33 add an extra “NOTE 4—PSK authentication using a weak passphrase is vulnerable to offline cracking. SAE authentication is not vulnerable to this.” and renumber the subsequent NOTEs in this subclause. CID 7277 Mark RISON 11.24.6.4 1771.20 What does "or clock estimate" mean? Delete NOTE 2 Discussion: The wording is actually offset estimate”, and this term is defined in Equation (11-6) at 1772.45. Proposed changes: In Figure 11-37 change NOTE 2 as follows: NOTE 2—Initiating STA can compute either an RTT orand a clock offset estimate Add a paragraph break after the sentence (second sentence of the para, ending “802.1AS”) at 1772.41. Add a NOTE at 1772.47, italicising t1 and t4 and using a consistent prime symbol after them throughout this subclause: NOTE—The initiating STA might also track this clock offset over time to derive an estimate of the difference between the initiating STA’s time base and the responding STA’s time base, and thereby improve the accuracy of its derivation of t1’ and t4’ from the TOD and TOA fields. Number all the NOTEs in this subclause, and also in Subclause 9.6.8.33. Add a after “time base,” at 1159.22. Proposed resolution: REVISED Make the changes shown under “Proposed changes” for CID 7277 in <this document>, which clarify the intent of clock offset estimation. Identifiers Comment Proposed change CID 7208 Mark RISON 6.3.58 339.1 For MLME-FINETIMINGMSMT.request, "Set to the value of t1 (see Figure 6-17)" is misleading because it is not set to the t1 in the figure but to the time for the previous request. Ditto t4. And for the .indication it's the time in the FTM frame, which is again not the t1 and t4 in the figure Change the text as indicated in the comment