3 ms·

To blame, maybe. But say you get a class E network. Are you fine not being able to talk to anything hosted on AWS? Blame is not correlated with pain.

MrStonedOne 4y ago
b112 4y ago
It may take a year or two, but I think AWS would clean up its act. I'd be worried about some megacorp using it inside some deep internal project, and for a decade after having bizarre deliverabilities issues for mail or something, randomly, without its staff understanding why.
- knorker 4y ago
  I think a year or two may be optimistic. One can only assume that if you start using class E then you've already used up all of 10/8. So the only option is to move to IPv6. I don't know AWS internals, but they may need to do hardware revisions they need to roll out to switch ASICs, not to mention millions of lines of code. And the addresses will be "kinda broken" everywhere, basically forever. So AWS wouldn't even get the blame. So there's no incentive for them to have a moon landing program costing them many billions, throwing away hardware before they otherwise would. Of course it is 2022, so I would hope that AWS's current production hardware is IPv6 ready at equal pps, FIB size, and features, but I wouldn't be surprised if not. But the software should not be underestimated. That IPv4 address in a database, stored as 32bit integer, is not exactly trivial to extend on disk and by every single reader and writer. Nobody will want these second class addresses, not on the client nor the server, so who are they for? (on the public Internet, that is. They could be used as 100.64.0.0/10)
icedchai 4y ago
You may have difficulty talking to other things, too. Older equipment simply won't communicate with class E addresses. It's hard coded in! It works for AWS because they control their network, end-to-end.

3 ms·

To blame, maybe. But say you get a class E network. Are you fine not being able to talk to anything hosted on AWS? Blame is not correlated with pain.

by knorker 4y ago

MrStonedOne 4y ago
b112 4y ago
It may take a year or two, but I think AWS would clean up its act. I'd be worried about some megacorp using it inside some deep internal project, and for a decade after having bizarre deliverabilities issues for mail or something, randomly, without its staff understanding why.
- knorker 4y ago
  I think a year or two may be optimistic. One can only assume that if you start using class E then you've already used up all of 10/8. So the only option is to move to IPv6. I don't know AWS internals, but they may need to do hardware revisions they need to roll out to switch ASICs, not to mention millions of lines of code. And the addresses will be "kinda broken" everywhere, basically forever. So AWS wouldn't even get the blame. So there's no incentive for them to have a moon landing program costing them many billions, throwing away hardware before they otherwise would. Of course it is 2022, so I would hope that AWS's current production hardware is IPv6 ready at equal pps, FIB size, and features, but I wouldn't be surprised if not. But the software should not be underestimated. That IPv4 address in a database, stored as 32bit integer, is not exactly trivial to extend on disk and by every single reader and writer. Nobody will want these second class addresses, not on the client nor the server, so who are they for? (on the public Internet, that is. They could be used as 100.64.0.0/10)
icedchai 4y ago
You may have difficulty talking to other things, too. Older equipment simply won't communicate with class E addresses. It's hard coded in! It works for AWS because they control their network, end-to-end.