Re: Simples
> How, exactly? Invent some more numbers?
Options might include:
* An IPv4 address extension header. When a client talks to a server which doesn't support the address extension option then it would fall back to stateful PAT.
That's the sort of approach which should have been taken in the first place.
If instead we want to complete the IPv6 transition:
* A comprehensive, global NAT64 infrastructure is put into place. It could be hosted by the existing CDNs (e.g. Akamai, Cloudflare, Google), and would treat the whole IPv4 Internet as a pool of content to be served to IPv6-only clients. It would be run as a public service, like public DNS resolvers.
Access providers could then start providing IPv6-only connections, releasing the chokepoint of IPv4 supply at client side.
As usage ramps up, content providers have an incentive to make their content available via IPv6: (a) to get better logs, (b) to serve content faster to this increasing pool of IPv6-only users.
Biting the hand that feeds IT
