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

[Ca By <[e-mail]>]

On Mon, Jul 17, 2017 at 9:26 AM Erik Nygren <[e-mail]> wrote:

> I'll add to the list of problems I run into on the NAT64 network:  VPN
> with split tunnelling and DNS sent through the VPN means the DNS64 gets
> bypassed. I assume the same would hold true of clients overriding the
> advertised DNS servers (eg, using Google DNS).
>
> A local CLAT helps.  Ideally VPNs doing split tunnelling could be made
> DNS64/NAT64 aware.  And apps being clever enough to do their own DNS should
> ideally also resolve ipv4only.arpa via the system resolver to do their own
> DNS64 synthesis.
>


Fyi, if you are running windows 10, just like Android, you may find you
have a local CLAT now that windows 10 has native support for 464xlat

https://blogs.technet.microsoft.com/networking/2017/07/13/core-network-stack-features-in-the-creators-update-for-windows-10/

The larger point is that common production Operating Systems are
increasingly functional without ipv4 or multiple types of ipv6-only
networks that present nat64 / dns64





> - Erik.  (Torn on which ietf we start this with...)
>
>      [Sent from my IPv6 connected T-Mobile 4G LTE mobile device]
>
> On Jul 17, 2017 9:42 AM, "Mikael Abrahamsson" <[e-mail]> wrote:
>
>> 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]
>> _______________________________________________
>> v6ops mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>> _______________________________________________
> v6ops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/v6ops
>