IPv6 and Python3 are case studies in how not to roll out a new version unless you're cool with multi-decade upgrade windows.
Is there an alternative, though? Both Python3 and IPv6 both solve problems that would have been at least as painful to do incrementally, IMHO.
AWS to start charging for IPv4 usage, but critical services don't support IPv6
11–20 of 245 posts
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#12IPv6 and Python3 are case studies in how not to roll out a new version unless you're cool with multi-decade upgrade windows.
I think cloud providers charging for IPv4 is a great stick, since the initial carrots (easier subnetting, huge networks, multiple IPs per host, encryption, etc) didn't work. I do wish they provided NAT64 services though.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#13Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#14Anyone that is surprised by this behavior from AWS probably has very little experience using it. The whole console is full of dark pattens to get you to setup larger than needed defaults and accidentally leave things running.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#15Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#16if you add these new charges onto the existing prices their offering becomes completely uncompetitive
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#17Do the other cloud providers give you IPv4 endpoints for free? I didn't think that was the case. (ie I thought AWS was just falling into line with the others on charging). As for the "critical services not supporting IPv6" in the post I was quite surprised that it's such a short list of things that don't work - I would have expected more. They've obviously made a ton of progress.
I get the feeling this is far from an exhaustive list. I think this person just mentioned two things that they had run into and could say didn’t support IPv6 without having to look it up.
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#18Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#19So, these intermediate steps are just cooking the final dish.
Peace. ;)
Re: AWS to start charging for IPv4 usage, but critical services don't support IPv6
#20IPv6 and Python3 are case studies in how not to roll out a new version unless you're cool with multi-decade upgrade windows.
Is there an alternative, though? Both Python3 and IPv6 both solve problems that would have been at least as painful to do incrementally, IMHO.
If IPv6 had left out the mandatory added complexity, and just focused on the larger addresses and cleanups, it would have been easier to adopt. The other changes could have happened via other standards, rather than bundling them all into "IPv6".