On 20/05/14 02:06, Tore Anderson wrote:
Now it would be eating our own dog food if there were a RIPE BCP publication that states that the best way to provide IPv4 on a modern wifi is NAT64. However, as far as I know, there is no such document, no plans for it, and I would be surprised major wifi hotspot would want to move to 464XLAT. But you never know.
We are talking about the RIPE meeting here, not a random wifi hotspot at your local coffee shop or wherever. We're the ones actually insisting that others to go do this IPv6 thing, so we should really be at the forefront of such efforts ourselves. If the BCP you're describing is to ever be written, we can't expect that a coffee shop, airport or whatever will provide the deployment experience on which such a document could be based - the RIPE meeting, on the other hand, would be a perfect fit.
Hey, I think the next step would be to leave IPv6 + IPv4 on main RIPE-MTG wifi network, but instead of DNS to start provisioning DNS64 by default. That's what I'm doing majority of the time and it works flawlessly. What would this mean - DNS64 would return A and AAAA record for *every* query (unless the queried name is IPv6-only) and lot's of today IPv4 traffic would shift to IPv6+NAT64 and give us the opportunity to observe how all this works on a larger scale... Whichever legacy app that does not support IPv6 might be used by attendees - it would still work using IPv4 transport. There were networks and events where we "secretly" started to insert DNS64 instead a normal DNS- we called that an experiment - and people did not even notice ;) Cheers, Jan