Re: [v6ops] 464xlat case study (was reclassify 464XLAT as standard instead of info)

Hi James,

Basically, we could say that CLAT or the bump-in-the-stack, have the same result.

May be the difference is that CLAT can be also in CPEs, which I’m not sure in the case of the bump-in-the-stack.

However, I recall having asked some of the Apple folks working on the HE update (not sure if it was David or Tomy), and unless I misunderstood it, bump-in-the-stack doesn’t solve the tethering problem or something else (not working for literals or apps that use sock api). Again, I’m not sure what was the issue, so I maybe expressing it incorrectly here, but it will be interesting to clarify.

Regards,
Jordi

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de james woodyatt <jhw@google.com>
Responder a: <jhw@google.com>
Fecha: martes, 26 de septiembre de 2017, 23:59
Para: "Heatley,N,Nick,TQB R" <nick.heatley@bt.com>
CC: IPv6 Ops WG <v6ops@ietf.org>
Asunto: Re: [v6ops] 464xlat case study (was reclassify 464XLAT as standard instead of info)

    On Sep 25, 2017, at 04:56, Heatley,N,Nick,TQB R <nick.heatley@bt.com> wrote:

    So this is my opinion: 464xlat is the currently the adopted approach when:
    - IPv4 addresses are (near) exhausted for the mass-market, 
    - AND the provider network demands a translation technology (i.e. incompatible with encaps.)
    - AND at the client end,  apps are not purged of IPv4 literals OR tethering to an unknown OS is required

    For the first two bullet items and the second half of the third bullet item, you only need NAT64+DNS64, not the whole of 464XLAT.

    You only put the CLAT on the handset for one thing, and one thing only: dealing with applications that still use IPv4 literals, and it’s not the only way to skin that cat, c.f. the approach used by Apple, which uses a bump-in-the-stack at a higher layer of the operating system instead of using the CLAT according to 464XLAT. It works fine in all the cases anyone really cares about, and when the apps that still use IPv4 literals are all retired from service, it won’ t be necessary ever again.

    --james woodyatt <jhw@google.com>

    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops

**********************************************
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 exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.