Because that is the “closer” thing we are going to get in the user and corporate networks in the next few years.
IETF has not used before IPv4-NAT, so yes, is less cool, but is more *real world* and if we want to make sure that users don’t get into troubles, we should get that dogfood.
By the way, I’m starting to think that before continuing this discussion, we should understand (and the NOC folks are probably the right ones to confirm) if we still believe that the main SSID should be a stable production network or open to trying things …
I asked a few emails ago, what is our target with any change in the main SSID, for example:
1) Try real world (real world has IPv4 behind NAT), using for example CLAT, so the WAN can be IPv6-only
2) Try IPv6-only in the LAN, which we know many things will fail if they use literal IPv4 addresses
3) Something else?
4) Marketing “hey we are the IETF, we use IPv6-only, everything works” which can never be true, because if anyone has an IPv4 only device or app, will not work … It is better marketing to make sure that CPEs and OS support CLAT so nothing gets broken?
Is the reason to report to app/developers what is broken? Who is going to report that?
Can we enforce them to sort it out? If the answer is not, then it makes sense to ensure that we have mechanisms such as CLAT to avoid users get broken things, right?
If we want to try broken apps, is the IETF the right network or we should look for app/developers conferences?
Regards,
Jordi
-----Mensaje original-----
De: ietf <ietf-bounces@xxxxxxxx> en nombre de Christian Huitema <huitema@xxxxxxxxxxx>
Responder a: <huitema@xxxxxxxxxxx>
Fecha: miércoles, 2 de agosto de 2017, 15:57
Para: <ietf@xxxxxxxx>
Asunto: Re: Incremental Deployment of CLAT on the router for IETF Meetings
On 8/2/2017 1:48 AM, JORDI PALET MARTINEZ wrote:
> In the Chicago (IETF 98), I’ve been allocated a /64 so I can run my own CLAT in my laptop (I was doing it either by means of a VM with OpenWRT or a VM with Ubuntu and Jool).
>
> It was working perfectly.
>
> Of course, I’ve tried that in other scenarios, including some thousands of CPEs in customer networks.
I have no doubt that a combination of IPv6 native and network provided
CLAT will work. It effectively provides devices with a dual stack
service, native IPv6 and natted IPv4. We know that dual stack works --
it has been the default service on the main IETF network for years. We
also know that natted IPv4 kind of works -- that's what most customers
have been getting for many years, and most applications have adapted by now.
But then, why deploy that on the main IETF network? IPv6 plus natted
IPv4 is definitely less cool than IPv6 plus native IPv4, which is what
the network has traditionally provided.
-- Christian Huitema
--
Christian Huitema
**********************************************
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.