Re: Address privacy

[[e-mail]]

Tom,

> The problem isn't in identification for apps, it's that the fact that
> the logs created by the app correlate user identity with an IP
> address. Given that correlation, the log could conceivably be used to
> identify participants in completely unrelated communications. Using IP
> addresses to identify individuals involved in communications does
> happen, there are a number of instances noted on the web particularly
> in law enforcement.

is your concern about correlation done by a man in the middle?
or is it the end-points? The operators of those end-points have built an enormous marketplace to trade this information behind your back. temporary addresses will not help against surveillance capitalism.

Temporary addresses doesn't in it's default setting solve the problem of correlation either.
Or should users ensure that they used services that shouldn't be correlated on different days? ;-)
And ensure that they never tainted an address by using it for authentication somewhere.

7217 iids and temporary addresses have the same privacy properties, if you look in table 1 in 7721.
separated by the address lifetime.

A natural consequence of this is that to protect against correlation at layer 3 (all the other tracking would still happen) you need a new address per connection. with a lifetime equal to the connection lifetime.
The network's response to that is likely to assign a static /64 to each host. So now, you can correlate on the prefix instead.

“Addressing can follow topology or topology can follow addressing; choose one” – Y. Rekhter

Ole