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

[Tore Anderson <[e-mail]>]

* JORDI PALET MARTINEZ <[e-mail]>

> However, we have different ways for doing the same, and we should go
> for the one that has less impact and it is more realistic.
> 
> In the real world, you will not disable IPv4 in the LANs of end-users
> or enterprise customers (at least not now, may be in 3-5 years from
> now). 

Jordi,

Did you even read the draft? It is quite clear in its recommendation to
provide IPv4 Internet connectivity to be provided through a NAT64/DNS64
service. Quoting from the abstract:

   The purpose of this document is to provide a blueprint and guidance
   for deploying IPv6-only Wi-Fi at IETF meetings.  This document
   outlines infrastructure and operational guidance that operators
   should consider when deploying IPv6-only networks **using NAT64 and
   DNS64 to support communication to legacy IPv4-only services**.

(Emphasis mine.)

> This is what IETF need to test now. IPv6 only with IPv4 as a service
> (which is 464XLAT).

Precisely. The existence of NAT64/DNS64 should in turn automatically
facilitate usage of 464XLAT.

Host operating systems that implements the CLAT component of 464XLAT
(e.g., Android or recently updated Windows 10) should be able to simply
activate it. While Apple doesn't implement 464XLAT per se they have
something similar, so they should be covered too.

There is more discussion about IPv4 backwards compatibility, including
a mention of 464XLAT, in section 4.2 of the draft.

Tore