| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
+ Nehru As far as I am aware the introduction of PASN in FTM exchange was to provide an ability to ensure that the measurement results are protected between unassociated non-AP STA & AP since FTM measurements are often done (for location) with
other APs besides the AP that the STA is associated with. Expanding PASN to share ‘device ID’ can potentially bring in new use cases where APs might need to be part of ESS, but like Mark is highlighting ‘what is the scope of that correlation” and do we need
to restrict it in the spec now and/or leave it for the applications to constrain? Ali From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
WARNING:
This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros. Try again with the reflector emails corrected. Mark From:
mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Joe, all, I’d like to clarify the “two main views”. At least in my opinion from the discussion, I think the views in question are:
That is, I can well imagine PASN (as a generic concept) could be used independent of the APs’ ESS(s), but when some sort of identification of the non-AP STA is used/needed/desired (to correlate
FTM requests, or for other reasons – I’m not sure what all the uses cases might be) what is the scope of that correlation? This is an important distinction, as it is the scope of the TGbh relevant aspect to all this to consider only the scope of the non-AP STA _identification_ and therefore the ability to
correlate the PASN interactions (per Joe’s “Background”) . Mark From: Joseph Levy <Joseph.Levy@xxxxxxxxxxxxxxxx>
Dear PASN/FTM experts: During today’s TGbh call a discussion was had regarding PASN and FTM use/use cases. There were two main views provided by the attendees:
I believe how this is “viewed” has implications for the use of PASN for FTM and location accuracy in general. This also has privacy impacts, as sharing an ID outside of an ESS may cause the ID to be shared to unknow entities which may
allow these entities to track the non-AP STA. Hence, the group requested this email discussion and a better understanding of the PASN use cases.
Thank you, in advance, for your assistance to provide TGbh a better understanding of the use of and use cases for PASN and FTM.
Background: TGbh is creating a PASN ID that can be used to identify a non-AP STA that is using random MAC addresses to improve its “privacy”, this PASN ID would allow the non-AP STA to be identified by the AP/network. The PASN ID is not fixed and
allows for some degree of privacy for the non-AP STA, while providing the AP/network with an “ID” for the non-AP STA (the AP/network is informed, in a non-specified manner, of the PASN ID and can use that information to identify the non-AP STA). Note: the use of the term network in this email basically includes all APs that can support PASN, this could mean; 1) all APs that are connected by some means, that may or may not be in the same ESS, 2) all APs that are connected by being
in the same ESS. Regards, Joseph To unsubscribe from the STDS-802-11-TGBK list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBK&A=1 |