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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 25 September 2017 09:21 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A6C71330B0 for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 02:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gF24uqFKUcyo for <v6ops@ietfa.amsl.com>; Mon, 25 Sep 2017 02:21:00 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB55F1320C9 for <v6ops@ietf.org>; Mon, 25 Sep 2017 02:20:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v8P9Kw7G010897 for <v6ops@ietf.org>; Mon, 25 Sep 2017 11:20:58 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id EAD662091D5 for <v6ops@ietf.org>; Mon, 25 Sep 2017 11:20:57 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E18042090F0 for <v6ops@ietf.org>; Mon, 25 Sep 2017 11:20:57 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v8P9KvA4026531 for <v6ops@ietf.org>; Mon, 25 Sep 2017 11:20:57 +0200
To: v6ops@ietf.org
References: <E48DDA04-C058-4992-906E-8C8BC0E102AB@consulintel.es> <1BFA3605-4B16-4331-A7BA-3BDECBCA64EC@gmail.com> <85868796-18C7-48F4-BE69-8D50A1F47EF3@jisc.ac.uk> <472CC0F7-73C2-4A21-8F96-BBC966B01B77@employees.org> <de6b9aac-a3cc-0915-77c7-9fb880c3a16a@gmail.com> <20170921223305.B72A8878E716@rock.dv.isc.org> <CAKD1Yr13ijKCB_71_2vMyGurc3-kSraLJycGxZwf121tjp8u1Q@mail.gmail.com> <20170922070719.74AA687A424E@rock.dv.isc.org> <20170922114847.GV45648@Space.Net> <369B3917-D9F3-41D4-A7BD-DAE134310004@employees.org> <20170922122146.GY45648@Space.Net> <20170922212502.E0CFF87B00BA@rock.dv.isc.org> <CAKD1Yr0VdmS0APz-G5VmxMNY1y9Kj+g0VP4Jx0_MXLkqkVyE8Q@mail.gmail.com> <4bf16a40ffd44e9498babf7094b1e526@orange.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f8b54014-c5af-d63f-5eed-35f19728b4f7@gmail.com>
Date: Mon, 25 Sep 2017 11:20:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <4bf16a40ffd44e9498babf7094b1e526@orange.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/eDRlZkEKczFcoRTyrNmBRLhvFzM>
Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2017 09:21:02 -0000


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
>