4 ms·

AWS is holding onto those routers running something earlier than, what, IOS 12.4 from 2005? And all those servers with iDRAC6s from, what, 2012? Some day peop

by kjs3 3y ago

AWS is holding onto those routers running something earlier than, what, IOS 12.4 from 2005? And all those servers with iDRAC6s from, what, 2012? Some day people will stop pretending IPv6 support is something that hasn't been ubiquitous in network gear for a decade or more.

jedberg 3y ago
The gear might support it in theory, but may not actually have sufficiently powerful CPUs or enough RAM to actually handle all the traffic. Also there is a bunch of software in between that needs upgrades. If it were easy and straightforward they would have done it years ago. The fact that even today most things AWS don’t support ipv6 tells me that it’s hard.
- kjs3 3y 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.
  - jedberg 3y ago
    > You have absolutely no idea what their constraints are or what their IPv6 decision making process is. 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.
    - kjs3 3y ago
      Yes I do. I've talked to them about it in depth. Thanks for that. I needed a good chuckle after today.
      - jedberg 3y ago
        I mean you can choose to believe me or not, but I just worked at Amazon for the last two years and worked with AWS networking products while I was there, including this: https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-global-accelerator-ipv6/ https://aws.amazon.com/blogs/networking-and-content-delivery...
      - inemesitaffia 3y ago
        You know he's like a Staff Engineer at Amazon right now right?
      - theshackleford 3y ago
        And thank you as well. Everyone’s a comedian today apparently.
      - overstay8930 3y ago
        You know there are actual network engineers who've like, written IPv6 RFCs here right?

by kjs3 3y ago

jedberg 3y ago

The gear might support it in theory, but may not actually have sufficiently powerful CPUs or enough RAM to actually handle all the traffic. Also there is a bunch of software in between that needs upgrades. If it were easy and straightforward they would have done it years ago. The fact that even today most things AWS don’t support ipv6 tells me that it’s hard.

kjs3 3y 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.
- jedberg 3y ago
  > You have absolutely no idea what their constraints are or what their IPv6 decision making process is. 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.
  - kjs3 3y ago
    Yes I do. I've talked to them about it in depth. Thanks for that. I needed a good chuckle after today.
    - jedberg 3y ago
      I mean you can choose to believe me or not, but I just worked at Amazon for the last two years and worked with AWS networking products while I was there, including this: https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-global-accelerator-ipv6/ https://aws.amazon.com/blogs/networking-and-content-delivery...
    - inemesitaffia 3y ago
      You know he's like a Staff Engineer at Amazon right now right?
    - theshackleford 3y ago
      And thank you as well. Everyone’s a comedian today apparently.
    - overstay8930 3y ago
      You know there are actual network engineers who've like, written IPv6 RFCs here right?