Re: [v6ops] reclassify 464XLAT as standard instead of info

Le 25/09/2017 à 11:27, JORDI PALET MARTINEZ a écrit :
> If you have IPv6-only access network, which is what 464XLAT is 
> offering, you have 100% IPv6-only in the access network.

Is that IPv6-only access network using GTP-IPv6? (a 3GPP spec that may 
exist that I dont have number)

Or is it using ATM? (IPv6 over ATM RFC2492, ATM is widely used to 
connect in-house networks to an operator)

> What you have at the customer sites/LANs and core/transit, is a 
> different history.
> 
> This is the reason we need to have a clear definition … I will try
> to update the document this week:
> 
> draft-palet-ietf-v6ops-ipv6-only

> 3.  IPv6-only
> 
>    IPv6-only MUST be used only if, a complete network, end-to-end, is
>    actually not forwarding IPv4 at layer-2, which will mean that no-IPv4
>    addresses are configured, neither used for management, neither the
>    network is providing transition/translation support, neither there is
>    IPv4 transit/peering.

Is this "IPv6-only" something wrong?  What do you mean by "forwarding 
IPv4 at layer2".   IP is at layer 3, be it v4 or v6.  IP encapsulation 
is also layer 3.

Alex

> 
> Regards, Jordi
> 
> 
> -----Mensaje original----- De: v6ops <v6ops-bounces@ietf.org> en 
> nombre de Alexandre Petrescu <alexandre.petrescu@gmail.com>
> Responder a: <alexandre.petrescu@gmail.com> Fecha: lunes, 25 de
> septiembre de 2017, 11:21 Para: <v6ops@ietf.org> Asunto: Re: [v6ops]
> reclassify 464XLAT as standard instead of info
> 
> 
> 
> Le 25/09/2017 à 11:05, Kossut Tomasz - Hurt a écrit :
>> Hi,
>> 
>> True ! 464xlat enabled IPv6 transition for mobile networks. Thank 
>> you ! In IPv6-only network you can expect up to 60% native IPv6
> 
> ? I thought in an IPv6-only network there is 100% native IPv6?
> 
> Alex
> 
>> 
>> Cheers,
>> 
>> TK
>> 
>> *From:*Lorenzo Colitti [mailto:lorenzo@google.com] *Sent:* Monday, 
>> September 25, 2017 3:55 AM *To:* Mark Andrews *Cc:* Gert Doering; 
>> v6ops@ietf.org WG *Subject:* Re: [v6ops] reclassify 464XLAT as 
>> standard instead of info
>> 
>> On Sat, Sep 23, 2017 at 6:25 AM, Mark Andrews <marka@isc.org 
>> <mailto:marka@isc.org>> wrote:
>> 
>> Stop exaggerating.  Google went and added CLAT to the Android. They
>> can just as easily add DS-Lite to Android and we would have 
>> billions of machines that support DS-Lite.  Just because NAT64 and 
>> 464XLAT are sexy doesn't mean that it is good technology.
>> 
>> We added 464xlat to Android because there were credible deployment 
>> plans in place for 464xlat on real networks that Android devices 
>> connect to. In hindsight, we were right, as 464xlat went from 
>> credible plan to successful deployment with an installed base in 
>> the tens of millions.
>> 
>> I personally think that if we had not done this, we wouldn't have 
>> IPv6-only mobile networks today and we'd all still be lamenting the
>> chicken and egg problem for IPv6-only networks. Getting rid of IPv4
>> in the network is a great step forward, and as Apple has shown,
>> once that's happened, host OSes can start removing IPv4 access from
>> applications, too. (And make no mistake: without 464xlat, those
>> networks would *not* have gone IPv6-only, and it would have been
>> much harder, or even impossible, for Apple to say that apps must
>> operate in IPv6-only environments, because there would have been no
>> such environments.)
>> 
>> DS-Lite has no such credible deployment plans in place. Wifi 
>> networks are going to provide IPv4 for many years. Mobile networks 
>> were never going to deploy DS-Lite because the encapsulation would 
>> have broken their billing platforms. And so, here we are.
>> 
>> We'll all get to IPv6-only eventually, and some time after that, 
>> we'll get rid of IPv4. At that time, you can salt the earth over 
>> 464xlat if you want. But until then, I wouldn't be too eager to 
>> bash 464xlat as a technology. It was the right thing to do at the 
>> time.
>> 
>> 
>> 
>> _______________________________________________ v6ops mailing list
>>  v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>> 
> 
> _______________________________________________ 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.
> 
> 
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> 