In your letter dated Sat, 17 May 2014 22:59:44 +0200 you wrote:
You need more operational practice :-) - you *really* want to get rid of dual-stack wherever you can, and instead of having to maintain and monitor IPv4 *and* IPv6 throughout your network, IPv6+NAT64 gives you a nice and clean single-stack network, with an ugly IPv4 wart near the exit.
Dual-Stack operation sucks big time, because it means you have to configure everything twice, monitor everything twice, firewall everything twice, etc.
I'm curious how people want to transition to IPv6+NAT64. Of course, getting rid of IPv4 solves a lot of problems. But just any eyeball network will have to support IPv4 for a very long time. So we can bitch on this list about Android not supporting NAT464, but in reality, are you going to tell users to dump their old devices, just because they don't support NAT464? On the RIPE meeting network, if you have to support traditional dual stack in addition to NAT64, there is no net gain for the ops team. For any eyeball provider, how do you switch to NAT64? Can you tell all your customers to dump their old CPEs? Is upgrading all CPEs worth it? Does anybody know how to debug this stuff? And because you are effectively tunnelling IPv4, any ACL you would need in NAT44, you probably also need in NAT64.