Re: [v6ops] Fwd: New Version Notification for draft-collink-v6ops-ent64pd-01.txt

[Lorenzo Colitti <[e-mail]>]

On Wed, Dec 21, 2022 at 4:19 PM Ole Troan <otroan=
[e-mail]> wrote:

> > IMO that is actually one of the best things about this draft: it
> provides a way to do the same in IPv6, while giving those unlimited devices
> true end-to-end-connectivity, and without costing any more network
> resources than if there was just one device. The lack of permissionless
> network extension is a major feature gap between IPv6 and IPv4. This draft
> doesn't just bridge that gap, it's actually a major improvement, because
> unlike IPv4, the permissionless extension provides end-to-end connectivity.
>
> There’s nothing permission-less about DHCP-PD. It has to be explicitly
> configured and each individual request granted by policy. By the network.
> HNCP is further along the permission-less scale.
>

Yes, of course PD needs to be explicitly configured, just like DHCPv4. But
I'm not referring to how the device gets connectivity - that is never
permissionless, even with SLAAC - rather to how it shares that connectivity
to downstream devices. If you have an IPv4 or IPv6 address, you can extend
the network, but you can't provide end-to-end connectivity to the devices
you share the address with. If you have an IPv6 address via SLAAC or DHCPv6
it's the same. But with DHCPv6 PD, you can extend the network *and* provide
end-to-end connectivity.