Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Jarkko, I think the issue was that these APs' mobility is tied to the STA which is also mobile. So how about: Issues:
That highlights what's so unique about this device, that since it is bound to a mobile STA any information that it transmits has to have the same sort of privacy protections as the STA.
I still maintain that the privacy protections the STA is going through are probably for naught because the connection to a DS the AP is providing will provide very granular tracking of the user. Service providers do gather PII on customers
and do track customers so the user won't really have true anonymity. But other devices will not be able to construct any similar PII (which might be fine, I mean the handset that used to only randomize pre-association did so not to provide privacy to the user
but to prevent 3rd party entities from constructing location PII which undercut the vendor's proprietary—pronounced $$$-- APIs to provide same, so this is kind of the same deal).
Dan. -- "the object of life is not to be on the side of the majority, but to escape finding oneself in the ranks of the insane." – Marcus Aurelius On 1/19/22, 12:10 PM, "Jarkko Kneckt" <00000d5619618f4f-dmarc-request@xxxxxxxxxxxxxxxxx> wrote: Hi, In today’s 802.11bi call we discussed on the technical issue 6). I heard that there were comments on the naming of the use case. - Soft AP name is not well defined and confusing. To mitigate the issue we could rename the use case and use only the name mobile AP. Cheers, Jarkko To unsubscribe from the STDS-802-11-TGBI list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBI&A=1 To unsubscribe from the STDS-802-11-TGBI list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBI&A=1 |