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 a burst instance, consecutive Fine Timing Measurement frames shall be spaced at “Within least Min Delta FTM apart.” to Fine Timing Measurement frames transmitted to a given peer STA “Consecutive shall be spaced at least Min Delta FTM apart.” Identifiers Comment Proposed change CID 7468 "The FTM Format And Bandwidth field Change to "The FTM Format And Mark RISON indicates the requested or allocated packet Bandwidth field indicates the 9.4.2.167 format and bandwidth used by all Fine Timing requested or allocated PPDU 1066.30 Measurement frames in an FTM session" -- format and bandwidth that can be this is not true, since FTM frames can use a used by Fine Timing Measurement simpler or narrower format than indicated. frames in an FTM session" Proposed resolution: ACCEPTED Identifiers Comment Proposed change CID 7504 should be a mechanism to allow the As it says in the comment. A bit in Mark RISON responding STA to ask the initiating STA to the FTM frame could be used to 11.24.6 re-initiate an FTM session (because it wants to signal this 1764.23 change the parameters) 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 10.8 says "For MSDUs or A-MSDUs Work out which is right and make Mark RISON belonging to the service class of QoSAck the other one say the same. Even when the receiver is a QoS STA, the QoS Data better, avoid the duplication frames that are used to send these MSDUs or
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
11-16-0276-06-000m-resolutions-for-some-comments-on-11mc-d5-0-sbmc1.docx