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

[JORDI PALET MARTINEZ <[e-mail]>]

Yeah, I read the draft and provided inputs.

And I understand what you’re saying however, not all the OSs have CLAT by default, it doesn’t work for us, and even less for end-customers.

I don’t think Apple has anything similar, just they mandated for iOS (smartphones), to have all the apps with IPv6 support, but is not the same for the laptops.

The last IETF I got a /64 prefix delegated by the NOC to my computer and I was running a VM with a CLAT daemon. All worked fine, but it requires the NOC to delegate me a prefix and have the VM running, which is not practical for every participant. Doing the same having the CLAT in a VM in the NOC itself, works for all.

Regards,
Jordi
 

-----Mensaje original-----
De: Tore Anderson <[e-mail]>
Responder a: <[e-mail]>
Fecha: lunes, 17 de julio de 2017, 11:00
Para: JORDI PALET MARTINEZ <[e-mail]>
CC: IPv6 Ops WG <[e-mail]>, Jim Martin <[e-mail]>, Russ Housley <[e-mail]>, Suresh Krishnan <[e-mail]>, Alissa Cooper <[e-mail]>, Randy Bush <[e-mail]>
Asunto: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

    * 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
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.