Re:IPv6 Support for AWS Extended to 15 Regions
by Animats on Wednesday January 25, 2017 @11:58PM
(#13488880)
It's embarrassing that the cloud providers weren't IPv6-capable from day one. They're new, not legacy systems.
[ Parent
| on HN ]
Re:IPv6 Support for AWS Extended to 15 Regions
by hossbeast on Thursday January 26, 2017 @01:09AM
(#13489119)
EC2 is 10 years old
Re:IPv6 Support for AWS Extended to 15 Regions
by robin_reala on Thursday January 26, 2017 @01:38AM
(#13489223)
IPv6 is 18 years old.
Re:IPv6 Support for AWS Extended to 15 Regions
by StreamBright on Thursday January 26, 2017 @07:39AM
(#13490821)
However, most of the users of internet were not ipv6 ready until very recently. It is a simply supply and demand question, where nobody wanted to invest in ipv6 infra first. Replacing networking gear for supporting ipv6 is very pricey operation too. I remember having pretty bad issues of having a dual stack in software. One example is when the python resolver library defaulted to ipv6 resolution first for a domain name, and the nxdomain to the AAAA request invalidated the name cache on the servers. When we changed this behaviour to default to ipv4 we saved an insane amount of CPU time. There are lots of issues like this one in a cloud environment, most people are never going to face this though.