3 ms·
> 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 pro
by 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.