4 ms·
If every engineer took the extra 10 minutes to enable IPv6 for their AWS services we would have a much better availability. I believe it's less than 50 lines o
by xfalcox 7y ago
If every engineer took the extra 10 minutes to enable IPv6 for their AWS services we would have a much better availability.
I believe it's less than 50 lines of Terraform code to enable it for the standard Application Load Balancer use case.
- regecks 7y agoI have the opposite experience when it comes to availability. I sell some software that runs on servers, and we used to get so many tickets that came down to the server's IPv6 transit being busted in sometimes obvious, sometimes subtle ways. And then we have to fight with their NOC to convince them something is broken. IPv6 is an afterthought in many networks. There is less peering, less monitoring, less users overall to uncover issues. It got so tedious to deal with that support burn that I just changed our software to not dual-stack any of its outgoing connections. Not heard a peep since.
- xfalcox 7y agoDoes the software runs well under heavy CGNAT? Because that is where we are going if everyone follows you.
- seppel 7y agoThe whole problem with ipv6 is that earlier adaptors have not much advantages (while still having to support ipv4 anyway) whereas late adaptors will have it much easier (better ecosystems, much less bugs anywhere else, problems are documented and well understood, infrastructure is tested, etc.). The incentives from the business side are just plain wrong. They can change when CGNAT causes problems. But they don't as long as other stuff is more important.
- saurik 7y agoWhat is the concrete problem you envision from "heavy CGNAT"?
- paulddraper 7y agoLots of networks and software is broken on ipv6. The more you use ipv4, the more reliable things are. Someday that will hopefully change.