Re:Tell HN: IPv6-only still pretty much unusable
by mort96 on Wednesday December 07, 2022 @12:20PM
(#33897112)
If it describes problems we're still struggling with, it's still relevant.
Re:Tell HN: IPv6-only still pretty much unusable
by howinteresting on Wednesday December 07, 2022 @12:17PM
(#33897076)
I mean, v6 is still mostly a failure, so (rightly or not) the situation is going to be blamed on the people that have been pushing v6. That's just the cost of trying to push the entire world towards a new standard.
(I know that v6 has been a success within datacenters and such.)
Re:Tell HN: IPv6-only still pretty much unusable
by ipython on Wednesday December 07, 2022 @08:42PM
(#33903013)
Actually, aws and the big cloud providers are only now starting to release ipv6 aware services.
If close to half of US traffic to google transits over ipv6 is considered a failure, I would hate to see “success”.
Re:Tell HN: IPv6-only still pretty much unusable
by noipv6 on Wednesday December 07, 2022 @12:33PM
(#33897319)
by what definition would you call ipv6 "mostly a failure"? 30-40% global eyeball network (to the end user) adoption after ~10 years of active deployment, against very vocal opposition seems commendable enough to me.
Re:Tell HN: IPv6-only still pretty much unusable
by commandersaki on Saturday December 10, 2022 @02:16AM
(#33930673)
More like 15 years of active deployment, and I'd expect levels at 90%. The world changed after IPv6 with smartphones that are controlled by a select few carriers, so it's easy to deploy IPv6 in which they're in dire need.
But the rest of the networks: enterprises, hosting providers, cloud providers, ISPs really don't give a shit. It's merely a cost centre or a burden.
Re:Tell HN: IPv6-only still pretty much unusable
by cryptonector on Wednesday December 07, 2022 @01:51PM
(#33898464)
It talks quite a bit about how to tackle migrations. It doesn't specify specific solutions for IPv6, no, but it does talk about what doesn't work and what should be looked into. It's a blog, not an Internet-Draft.
It doesn't give a fix because no fix is possible. Because the problem comes from the design of v4, not from v6.
For some reason djb wasn't able to get his head around that, and people have been pointing to that damn page as if it's some big gotcha ever since. No, it's just the situation we're stuck with, thanks to the people that designed v4.