IPv6
The Register recently published an article marking IPv6’s 30th birthday, interviewing networking luminaries about the protocol’s journey from savior to technological also-ran.
APNIC chief scientist Geoff Huston didn’t mince words, calling IPv6: “An extremely conservative protocol that changed as little as possible” and “a classic case of mis-design by committee.”
Yet despite these criticisms, industry experts maintain IPv6 isn’t entirely a failure. As ARIN’s John Curran argues, “IPv4’s continued viability is largely because IPv6 absorbed that growth pressure elsewhere – particularly in mobile, broadband, and cloud environments.”
The article made its way to Hacker News, a Reddit-like forum frequented by engineers and highly technical practitioners, where it sparked over 600 comments. The discussion revealed not a disagreement between experts and engineers, but rather a shared understanding of IPv6’s shortcomings, viewed through different lenses.
The Ground Truth: What Engineers Actually Think
One comment perfectly captured the adoption problem: “I don’t use IPv6 because it solves a problem that I don’t have and it provides functionality that I don’t want. And also because I don’t understand it very well.”
This brutally honest admission summarizes three decades of IPv6’s struggle: for most organizations, IPv4 with NAT works fine, the migration effort seems unjustified, and the complexity feels unnecessary.
The most heated debates centered on Network Address Translation. While IPv6 advocates correctly insisted “NAT is not a firewall,” practitioners pushed back with pragmatic concerns. They prefer having both NAT and firewalls as defense-in-depth, arguing that even if NAT isn’t technically security, non-routable private addresses provide psychological comfort and an extra layer of protection against misconfiguration.
Dynamic ISP prefix delegation emerged as a critical pain point. Unlike the stable private IPv4 ranges users control, many ISPs change IPv6 prefixes unpredictably, breaking internal addressing schemes and forcing constant updates to DNS records and firewall rules. Android’s refusal to support DHCPv6 compounds these problems, making enterprise device management nearly impossible without workarounds.
Where IPv6 Actually Wins
The discussion wasn’t entirely negative. Engineers running homelabs and self-hosted services praised IPv6 for eliminating port forwarding nightmares since multiple services can use standard ports simultaneously without proxy servers. VPN users highlighted how IPv6’s unique addressing eliminates the private IP range collisions that plague complex multi-site networks.
France’s success story drew attention: achieving over 97% IPv6 deployment by tying it to 5G licensing requirements. As one commenter noted: “Over here IPv6 JustWorks to the point of absolute boredom.”
This regulatory approach proves IPv6 can succeed, but apparently requires government mandates rather than organic adoption.
The most damning evidence against IPv6’s relevance? Major platforms including Amazon Retail, eBay, GitHub, TikTok, and Slack still lack IPv6 support.
One wry observer summarized the situation with dark humor: “Here’s a prediction. Linux on the desktop will have >50% penetration well before IPv6 does.”
IPv6 is Making Strides
After 30 years, IPv6 remains the networking protocol that’s perpetually five years away from widespread adoption, solving problems most people don’t have, while creating new ones they’d rather avoid. Yet the story isn’t quite over. Organizations like Huawei have acquired 2.56 decillion IPv6 addresses, while Starlink appears to have obtained 150 sextillion, helping push more countries past 50% IPv6 adoption. Whether this represents a genuine turning point or simply the continuation of a three-decade stalemate remains to be seen.
