Tell HN: IPv6-only still pretty much unusable
It&#x27;s been a quarter of a century since IPv6 launch.<p>There&#x27;s some really good lessons learned here. IPv6 requires everyone, everywhere, needs to change their configuration to add IPv6 addresses and network connectivity  to every node&#x2F;endpoint. The madness of course is that all the underlying infrastructure software (routers, OS, standard libraries) all support IPv6. It would seem, at a large enough scale, that software is the easy part, configuration is the hard part.<p>DJB wrote this up two decades ago[0] and it remains relevant. In particular the comparison between IPv6 and MX records. It took me a little while to wrap my brain around just extending existing software to support sometimes 32bit and sometimes 128. Ultimately it wasn&#x27;t hard to dream up a few solutions for how that would work.<p>The other thing, FWIW, which has been slowing IPv6 adoption is business owners not asking for it as a high priority item from their providers. I&#x27;ve seen this happen way more often that I would like where provider asks a customer what they want and the customer never mentions IPv6, and when prompted shrugs it off because they don&#x27;t see it as a business critical (and in fairness, it hasn&#x27;t been). Yes provider isn&#x27;t asking the &#x27;nerds&#x27; at their customer&#x27;s businesses, but those folks also aren&#x27;t the ones paying the bills so...<p>0: <a href="https:&#x2F;&#x2F;cr.yp.to&#x2F;djbdns&#x2F;ipv6mess.html" rel="nofollow">https:&#x2F;&#x2F;cr.yp.to&#x2F;djbdns&#x2F;ipv6mess.html</a>