Re: A common problem with SLAAC in "renumbering" scenarios

[Richard Patterson <[e-mail]>]

On Thu, 14 Feb 2019 at 10:51, JORDI PALET MARTINEZ
<[e-mail]> wrote:
>
> There are many other ways to track people. I don't really think that having a different prefix, even if it changes every few minutes, will avoid anyone to be tracked.

I agree that there are better ways, but IP addresses are still
considered personal data from a GDPR perspective, and courts also
generally agree that they are sufficient from a copyright infringement
enforcement perspective.
There's a bare minimum period of time a provider would have to
relinquish subscriber information when a copyright holder/enforcer
comes knocking, but not over and above that period.   If the rights
holder can infer that a subscriber had that IP/prefix indefinitely,
that may open up that subscriber to legal action for the entire
lifetime of them being a customer.


> In addition to that, I think it is easy for operators to implement a policy such as a configuration web page for your connectivity where you can choose a non-persistent prefix to be changed in your network every "n" hours. Up to the ISP to decide if the default policy is "persistent" or "non-persistent".

That's an additional platform and development work, on top of the
already non-trivial work required to extend the RADIUS platform to be
topology aware and integration with an IPAM or another method to
assign address/prefixes.