Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

[Mikael Abrahamsson <[e-mail]>]

On Mon, 17 Jul 2017, JORDI PALET MARTINEZ wrote:

> So the dogfood that we need to try (now) is the one that can sever the 
> “real” market, not the one that could serve the marked when they are 
> ready to replace (in a big %) all the apps and devices that are IPv4 
> only. We could try this in a follow up phase (actually there is an SSID 
> for that already).

My android and iOS devices work great on IPv6 only using the proposed 
suggestion. My MacOS and Windows do not (because they don't have the 
464XLAT or bump-in-the-API that is available on the mobile platforms). I 
already know this. I don't need to prove it to anyone.

It's premature to go IPv6 only on the main wifi before main operating 
systems support the same mechanisms available on the mobile devices.

1. My "mosh" session only tries the same AF that it initially connected 
to. If I initially connected on an IPv4 network, it will never connect to 
anything on an IPv6 network.

2. My Windows VM which needs to reach IPv4 only resources have no way to 
do this through the Parallels NAT44. I would need a CLAT for this.

There are lots of desktop OS applications that do not work on IPv6 only 
DNS64+DNS64 without CLAT. I have tried this, it doesn't work, there is no 
need to do wider test. OS vendors need to implement CLAT (or equivalent) 
for it to be viable.

If the main wifi is going IPv6 only, I will run my mobile devices on it, 
but I will immediately swap to the dual stack SSID for my computer.

-- 
Mikael Abrahamsson    email: [e-mail]