3 ms·
I doubt it. Realistically the AWS charge mostly causes companies to stop giving IPv4 addresses to servers that never directly talk to customers. As a knock-on e
by wongarsu 3y ago
I doubt it. Realistically the AWS charge mostly causes companies to stop giving IPv4 addresses to servers that never directly talk to customers. As a knock-on effect this will cause tooling to become more IPv6 aware, and put pressure on SaaS in infrastructure monitoring and dev tooling to be reachable via IPv6 (for example this might cause github to finally fix their IPv6 game because of higher customer demand).
Maybe companies use the same opportunity to make sure their services also work via IPv6. But they won't stop offering their services on IPv4, and AWS changes don't put meaningful pressure on ISPs to roll out IPv6. If anything it will reduce the pressure on the price of IPv4 addresses, making it more viable for ISPs to hold out.
- zinekeller 3y ago> will cause tooling to become more IPv6 aware I doubt it, especially that there is an option of using private/CGNAT ranges instead of adopting a whole new protocol. Everyone who cares about IPv6 have already done their part, and people who don't care about it will likely use the lower-friction option, and between private IPv4 networks and IPv6 I bet that a lot of people will see private IPv4 as a lower-friction option.
- wongarsu 3y agoHowever the lowest friction option is to use private IPv4 between your servers, but give every server a public IPv6 it can use for outgoing calls: updating the OS, fetching github repositories, collecting logs on your favorite SaaS, etc. Of course you can do all this via IPv4 by setting up proxies or gateways, but that's more work and more moving pieces than checking the checkbox that you want a public IPv6 and having it just work ... provided everyone you want to talk to talks IPv6.