Yes it is. The exact scenario from the article is a well known problem with dynamic prefixes: https://www.ietf.org/archive/id/draft-palet-v6ops-prefix-ass...
> https://www.ietf.org/archive/id/draft-palet-v6ops-prefix-ass...
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):
* https://datatracker.ietf.org/doc/draft-ietf-v6ops-prefix-to-...
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.
Agreed.
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.