4 ms·

I have to support ipv4. Why would I want to also support ipv6, increasing my risk and my workload. If ipv6 had been designed form the start to allow seemless t

• Plasmoid 2y ago
  > ipv6 had been designed form the start to allow seemless transparent access to ipv4 from an ipv6 It does. It's called NAT64, and it works/breaks as well as regular NAT44.
• bigstrat2003 2y ago
  It's not twice the work. It's actually very little work to run dual stack.
• WorldMaker 2y ago
  > (what services are ipv6 only, even today) A good majority chunk of cell carriers today have gone IPv6-only for phones. They rely on NAT64 gateways (rather than CGNAT) to access IPv4-only resources. A lot of consumer internet is slowly following that lead as a better alternative to CGNAT. At least if your customers are consumers we are really close to "You might only need to serve IPv6." (It's the "Enterprise-grade internet" that is interestingly lagging and falling behind in IPv6 adoption, and maybe doesn't see enough reason to support IPv6-only well; especially if the cost of IPv4 plateaus again, as some suggest it might. Recent AWS cost increases for IPv4 have been something of a call to action to some Corporations, but in general if you are B2B you probably need IPv4 support for a while longer as the economic incentives games play out on a long, slow horizon.)