It boggles my mind that they would deliberately design Internet (!) Protocol that poorly handles the dynamic nature of the networks its supposed to interconnect. The prefixes are dynamic, that's the fact of life.
But then again, at least half of the IPv6 design looks as a deliberate and somewhat spiteful attempt to force the ISPs and ASs to do things in a radically different ways than they are doing already just fine.
My read is that if things followed RFCs and best practices from the protocols correctly, a lot of things wouldn't be an issue.
I remember about 10 years ago trying to get IPv6 on an ISP and they were handing me a /128. And clients like home routers had/have bad UIs for managing IPv6.
Of course the infrastructure should handle dynamic allocations properly, and IPv6 delegations should not change every time a connection/daemon bounces just because it can.
> It boggles my mind that they would deliberately design Internet (!) Protocol that poorly handles the dynamic nature of the networks its supposed to interconnect. The prefixes are dynamic, that's the fact of life.
The 'dynamic' nature of these delegations is a policy decision of the ISP and not of the protocol: nothing is stopping them from giving the same prefix to the same customer.
It's no different than a DHCP(v4) server on a corporate network remembering which MAC got which IPv4 address in the past and giving the same one over the course of time, or the IT folks telling the DHCP system to not remember and give a new address each time.