PSA: You may wish to point to the most recent revision (or use a link that lists all revisions, and would point to the perhaps-eventual RFC), as opposed to an expired document from 2025:
* https://datatracker.ietf.org/doc/draft-ietf-v6ops-prefix-to-...
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.
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 of the IT folks telling the DHCP system to not remembering and give a new address each time.
The 'static' delegation, however, is the policy decision of the protocol because it deals very poorly with a different policy. And it shouldn't; protocols should give mechanisms for implementing different reasonable policies — and there is nothing unreasonable about dynamic delegation except for the fact that the creators of IPv6 decided "yeah, no, those should be static, and if someone thinks otherwise, they can see figure 1".
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.
That draft BCP doesn't put it as well as the RFC's unfortunately.
In short renumbering as little as possible is the current best practice because IPv6 renumbering is not as robust as it can be.
Flash renumbering (AKA renumbering without warning) has been documented as a problem.
The practical problem is the default lifetimes for prefixes are in days or weeks, and without something to notice and report the prefix is gone hosts continue to use it.
A number of RFCs are working their way through the system to get the handling of renumbering and especially flash renumbering as robust as possible.
Even when it is documented the best way to handle the sitation and the RFCs are published. It will take a little bit for all of the software to be updated.
All of that said renumbering somewhat regularly (monthly?) on IPv6 remains important so that bugs don't creep into the process unnecessarily.
Non-sticky, dynamic prefixes cause all sort of mayhem because suddenly your RAs, firewall rules, DNS recods, NAT64 pools etc. are all outdated and you have to somehow update them.
Residential assignments are often /56 (2^8 subnets) or even maybe /60 (2^4 subnets): this may or may not be enough for business needs, depending on the size of the organization.
ULA is absolutely routable. Are you confusing it with LLA?
> and has lower precedence (3) than ipv4 (35)
This already got changed in https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc672..., the document is fully done with the RFC editor queue and only waiting for the [SNACBIT] reference to get published.
New preference table:
Prefix Precedence Label
::1/128 50 0
$known_local/4x 45 14 (**)
::/0 40 1
fc00::/7 30 13 (*)
::ffff:0:0/96 20 4 (*)
2002::/16 5 2 (*)
2001::/32 5 5
::/96 1 3
fec0::/10 1 11
3ffe::/16 1 12Yes many keep track of that RFC. However you're aware that every client device, tv, phone, esp32, iot device, has to apply this change? That will take decades
I don't necessarily disagree with the assessment, but to a certain extent I like getting new addresses/prefixes to help with privacy: with my previous ISP I had my own Asus router (now have to use ISP-provided), and it had built-in functionality to schedule reboots.
To me it seems the main issue is that the old prefix immediately stops being valid. There's not exactly a shortage of IPv6 addresses, so the ISP shouldn't be in any hurry to reuse the old prefix. If they were to still route it to the customer for, say, 24 hours, then it would give equipment time to switch over to the new one.
This is a guess on my part, of course, I don't know any network engineers at my own ISP.