It's definitely more of an education issue. I still run into "IT" people that instinctively disable IPv6 no matter what. How do we fix this? The sad thing is IPv6 is actually easier in many respects: subnetting is simpler, no NAT hackery, SLAAC...

> I still run into "IT" people that instinctively disable IPv6 no matter what. How do we fix this?

- force ISPs to follow RIPE guidance on addressing (static prefix, at least /56 for every site, DHCPv6-PD)

- force the manufacturers of low-end routers (e.g. provided by ISPs) to have good IPv6 support (good firewalling, DHCPv6-PD, mDNS, PCP/UPNP, advertise static ULA prefix to have working local network even if internet connection is cut)

- force Android team to support DHCPv6

- force browsers to support full IPv6 addresses in URLs / URIs (link local addresses, scope id)

- force avahi / mDNS to support IPv6 scope id - make operating system manufacturers to have a better unified socket API which can resolve any type of address (IPv4, IPv6, DNS, mDNS, etc. maybe even URLs directly) and deprecate all other API

- make software developers to use this new API and don't try to parse IP addresses or URLs themselves

- have a good solution for multi-homing / WAN failover (without BGP and PI address space)

- have a good solution for mobile / roaming devices (phones, notebooks)

and maybe we could make IPv6 stable and universally working

(Waste a /40 for every company, get low on available prefixes and start over designing IPv8 to have 256 bit addresses with 184 bit host part...)