News for hackers. Stuff that matters.
Re:IPv6 delegation, an unusually subtle failure mode by BadBadJellyBean on Wednesday November 18, 2026 @08:37AM (#50546169)
No. Not necessarily.
Re:IPv6 delegation, an unusually subtle failure mode by RVuRnvbM2e on Wednesday November 18, 2026 @08:54AM (#50546340)
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...
Re:IPv6 delegation, an unusually subtle failure mode by throw0101c on Wednesday November 18, 2026 @09:37AM (#50546826)
> 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), as opposed to an expired document from 2025:

* https://datatracker.ietf.org/doc/draft-ietf-v6ops-prefix-to-...

Re:IPv6 delegation, an unusually subtle failure mode by RVuRnvbM2e on Wednesday November 18, 2026 @09:39AM (#50546855)
Right, thanks. It was difficult finding a vaguely recalled RFC on my phone :D
Re:IPv6 delegation, an unusually subtle failure mode by Joker_vD on Wednesday November 18, 2026 @09:46AM (#50546952)
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.

Re:IPv6 delegation, an unusually subtle failure mode by throw0101c on Wednesday November 18, 2026 @09:51AM (#50547000)
> 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 of the IT folks telling the DHCP system to not remembering and give a new address each time.

Re:IPv6 delegation, an unusually subtle failure mode by Joker_vD on Wednesday November 18, 2026 @12:09PM (#50548886)
> 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.

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".

Re:IPv6 delegation, an unusually subtle failure mode by unethical_ban on Wednesday November 18, 2026 @11:34AM (#50548387)
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.

Re:IPv6 delegation, an unusually subtle failure mode by ebiederm on Wednesday November 18, 2026 @11:01AM (#50547937)
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.