Hacker News new | past | comments | ask | show | jobs | submit login

Browsers are just one tiny piece of the fossilization issue. We got countless vendors of networking gear, we got clouds (just how many AWS, Azure and GCP services are capable of running IPv6 only, or how many of these clouds can actually run IPv6 dual-stack in production grade?), we got even more vendors of interception middlebox gear (from reverse proxies and load balancers, SSL breaker proxies over virus scanners for web and mail to captive portal boxes for public wifi networks), we got a shitload of phone telco gear of which probably a lot has long since expired maintenance and is barely chugging along.





Ok. You added OEMs to the list, but then just named the same three dominant players as clouds. Last I checked, every device on the planet supports IPv6, if not those other protocols. Everything from the cheapest home WiFi router, to every Layer 3 switch sold in the last 20-years.

I think this is a 20-year old argument, and it’s largely irrelevant in 2024.


> I think this is a 20-year old argument, and it’s largely irrelevant in 2024.

It's not irrelevant - AWS lacks support for example in EKS or in ELB target groups, where it's actually vital [1]. GCE also lacks IPv6 for some services and you gotta pay extra [2]. Azure doesn't support IPv6-only at all, a fair few services don't support IPv6 [3].

The state of IPv6 is bloody ridiculous.

[1] https://docs.aws.amazon.com/vpc/latest/userguide/aws-ipv6-su...

[2] https://cloud.google.com/vpc/docs/ipv6-support?hl=de

[3] https://learn.microsoft.com/en-us/azure/virtual-network/ip-s...


Plenty doesn’t support IPv6.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: