> If you want the network to come up in a timely fashion, the new system needs to poke the network to get information proactively sent to it as soon as possible

> If you want the network to come up in a timely fashion, the new system needs to poke the network to get information proactively sent to it as soon as possible, at which point you have about the same level of complexity as poking a DHCP server. I've had to fight with ip-helper issues and DHCP scopes enough times to not wish to have to deal with it if possible. I have to configure the router (or the VLAN on a Layer 3 switch) anyway, so a few extra lines for /64 scopes that are sent out via RAs on the same device I have to touch anyway is easier. > The reaction I have every time I interact with IPv6 is that it seems incredibly hard to make a system just use the configuration you tell it to use and never ever listen to any configuration from the network. On Debian with interfaces(5): auto eth0 iface eth0 inet6 static address 2001:db8:aaa:bbbb:cccc::dead:beef netmask 64 gateway 2001:db8:aaa:bbbb:cccc::1 accept_ra 0 For Netplan-based stuff, this looks similar: * https://github.com/canonical/netplan/blob/main/examples/direct_connect_gateway_ipv6.yaml https://github.com/canonical/netplan/blob/main/examples/dire... I recently had to switch ISPs to one that doesn't do IPv6 for FTTH (but their smart offerings are (AFAICT) IPv6-only), but my previous IPv6 did, and activating it for my home network was a couple clicks on my Asus router: all my devices (including a networked printer) picked it up without issue.