3 ms·
Honestly, can someone explain why it took so long? I mean, you can get IPv6 on a bunch of low-end budget VPSs. Why couldn't Amazon do it? And why cant GCE do i
by dispose13432 10y ago
Honestly, can someone explain why it took so long?
I mean, you can get IPv6 on a bunch of low-end budget VPSs. Why couldn't Amazon do it? And why cant GCE do it?
Is it a lot of work?
- rb2k_ 10y agoA colleague of mine gave a talk at SRECon about the fun world of IPv6 provisioning: https://www.youtube.com/watch?v=0gjuVhph520 https://www.youtube.com/watch?v=0gjuVhph520 Granted, that isn't necessarily a pre-requisite for going dual stack (aka: just attaching a v6 address to a machine), but it shows the fun problems you run into.
- vbernat 10y agoThe more layers you have, the more time you need to convert all of them to IPv6 (from network to all the applications). IPv6 implementations of various things is always less complete than their IPv4 counterpart. Notably, even low-level stuff may still be difficult to make with IPv6. For example, Linux supports IP equal-cost multipath routing for IPv6 since 2012. Quagga, a popular routing daemon, still doesn't support that. BIRD, another open-source routing daemon, just got partial support for it this year. If your network is relying on this, it's an additional burden to deploy IPv6.