|
|
|
|
|
|
by kjs3
876 days ago
|
|
|
If it were easy and straightforward they would have done it years ago. You have absolutely no idea what their constraints are or what their IPv6 decision making process is. Neither do I. It might be operational issues. It might be legacy code. It might just be because they've figured not doing it makes them more money or because they think not enough customers are asking for it. Hell, it could be as simple as the right executive thinking "IPv6 is a fad" and roadblocking. But it's not "because the hardware doesn't support it"; that's a long ago solved problem. And AWS designs/builds their own networking gear, so they aren't waiting on Cisco or whomever to give them what they need...they would have done it years ago. |
|
|
Yes I do. I've talked to them about it in depth.
> But it's not "because the hardware doesn't support it";
I never said the hardware doesn't support it. I said the hardware needs upgrades to support it at their scale, which includes software updates to the hardware, as well as the operations around said hardware.
It's been a priority for them for years and customers have been asking for years. It's not done because it requires a lot of work and capital. Hopefully the revenue they bring in from charging for IPv4 will help offset the cost of upgrades.