Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Chaoming and all, I also had similar questions a Mike, what is the motivation in replacing a two way frame exchange with a single Measurement Query? Are we trying to save the overhead of the session setup response? I don’t see why it has to be done, also
seems you are also proposing the Measurement Setup Request frame (from the AP) in response to a Measurement Query frame to be an implicit acknowledgement from the AP to setup the sensing session. In my opinion, a separate pair of frames for session setup (per
the original intention) is much cleaner, even if the frames don’t negotiate any sensing attributes, it can be explicit acknowledgement from both parties to proceed with sensing operations. This seems to be getting unnecessarily complicated in my humble opinion.
Btw, in your slides the Measurement Query seems to be always sent in the uplink while the Measurement Setup Request in the DL? Surely it can be bi-directional right? Regards, Rojan From: Ali Raissinia <alirezar@xxxxxxxxxxxxxxxx> Essentially, we have defined session setup as primarily a capability exchange phase thus not need to be ‘protected’. Sensing measurement setup is when parameters of sensing are assigned and there’s binding between peers to begin measurement
exchange hence it would need to be protected. For unassociated case, since MS query happens after PASN (as client knows PMF is required) it is able to benefit from PMF and protect client’s sensing capabilities as well as the fact that client has initiated a request for measurement
setup exchange. Ali From: M Montemurro <montemurro.michael@xxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Correct. MS Request/Response after the SA is complete allows the setup between the Sensing Responder and Sensing Initiator to be protected. Anything exchanged prior to SA establishment cannot be trusted in a secure environment.
Cheers, Mike On Tue, Apr 19, 2022 at 11:42 AM Ali Raissinia <alirezar@xxxxxxxxxxxxxxxx> wrote:
To unsubscribe from the STDS-802-11-TGBF list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 To unsubscribe from the STDS-802-11-TGBF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBF&A=1 |