I think the fundamental problem with ipv6 is that it’s a bit more complex to learn than ipv4 and not universally deployed at the remote host/server level.
New cloud companies who want to be competitive have to purchase ipv4 blocks at significant cost reducing their ability to compete with the incumbent players.
So if you go 100% ipv6 at home, some percentage of the internet will be inaccessible to you unless you employ some workarounds.
We’ll drop ipv4 quite fast once everything is up on ipv6 because nearly every modern network enabled device supports it.
The only reason I think we’ve not gotten over the hump is because our alternatives are still easy enough to work with and nobody requires it.
I think the fundamental problem with ipv6 is that it’s a bit more complex to learn than ipv4 and not universally deployed at the remote host/server level.
New cloud companies who want to be competitive have to purchase ipv4 blocks at significant cost reducing their ability to compete with the incumbent players.
So if you go 100% ipv6 at home, some percentage of the internet will be inaccessible to you unless you employ some workarounds.
We’ll drop ipv4 quite fast once everything is up on ipv6 because nearly every modern network enabled device supports it.
The only reason I think we’ve not gotten over the hump is because our alternatives are still easy enough to work with and nobody requires it.
Only if Chrome announces that the IPv6 version will be the default and the IPv4 version must be manually activated in the future.
All companies announce migration to IPv6
Huh? You know Chrome right now does ipv6 and iov4.
And ipv6 is the default when doing dual stack unless explicitly configured differently.