Hey guys, I deployed our servers on 10.0.0.0/14 and didnt’ bother with ipv6. Oh no! The company that we just acquired also deployed their servers on 10.0.0.0/14, so all of your assumption in your dumb-ass contrived scenario are invalidated.
ipv6 adoption only matters for public reach. Right now if you want a website accessible by 75% of the world, it has to be an ipv4 endpoint. Though that is changing. Here is a blog post by someone from akamai in 2018 talking about the rapid adoption of ipv6.
https://www.akamai.com/blog/performance/six-years-since-world-ipv6-launch
Basically if you aren’t deploying a service as native ipv6, you’ve already fucked up.
Hey guys, I deployed our servers on 10.0.0.0/14 and didnt’ bother with ipv6. Oh no! The company that we just acquired also deployed their servers on 10.0.0.0/14, so all of your assumption in your dumb-ass contrived scenario are invalidated.
ipv6 adoption only matters for public reach. Right now if you want a website accessible by 75% of the world, it has to be an ipv4 endpoint. Though that is changing. Here is a blog post by someone from akamai in 2018 talking about the rapid adoption of ipv6. https://www.akamai.com/blog/performance/six-years-since-world-ipv6-launch
Basically if you aren’t deploying a service as native ipv6, you’ve already fucked up.
Most competent IT departments would just set up bidirectional NAT.
https://www.juniper.net/documentation/us/en/software/session-smart-router/docs/config_static_nat/