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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 20 September 2017 12:55 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 7FB78132939 for <v6ops@ietfa.amsl.com>; Wed, 20 Sep 2017 05:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.128
X-Spam-Level:
X-Spam-Status: No, score=-0.128 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FUZZY_MILLION=2.505, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=no 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 RzdIykLkuKZk for <v6ops@ietfa.amsl.com>; Wed, 20 Sep 2017 05:55:02 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 1069C1321C7 for <v6ops@ietf.org>; Wed, 20 Sep 2017 05:55:01 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v8KCsxKZ029291; Wed, 20 Sep 2017 14:54:59 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7030220793D; Wed, 20 Sep 2017 14:54:59 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 60C9E2018A3; Wed, 20 Sep 2017 14:54:59 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v8KCsxgH003716; Wed, 20 Sep 2017 14:54:59 +0200
To: Erik Kline <ek@google.com>
Cc: Fred Baker <fredbaker.ietf@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <C1017FAF-91C3-4CA3-89C2-B64FF5100E41@consulintel.es> <85d934b3-ae06-c0ea-3519-4069c8387f0a@gmail.com> <C33DB89E-C005-4A32-9066-C8EE710F3255@consulintel.es> <b16c4ca2-da97-9a5a-0f88-6388ebbda80e@gmail.com> <B9C2822F-56EE-47D8-AAB5-C041A3D22F41@gmail.com> <f23854dd-0952-eedb-802b-8506dc111da7@gmail.com> <355FA9BA-CBE9-41AC-8FA6-B44C15C7420B@gmail.com> <58bb7a08-4595-f9b8-0be4-25bb471ca2db@gmail.com> <CAAedzxrMk10P8g0p5=1m8rANFy6+GvkA7+SrnWLKp3Do7sY5aw@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d441f1cd-7b22-f94f-1fe2-4b12ab47ae21@gmail.com>
Date: Wed, 20 Sep 2017 14:54:59 +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: <CAAedzxrMk10P8g0p5=1m8rANFy6+GvkA7+SrnWLKp3Do7sY5aw@mail.gmail.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/IQFbncwfAPVXtm6Uc51_803vE94>
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: Wed, 20 Sep 2017 12:55:03 -0000

No need to stress terms like billions; that's what modem manufacturers 
put on the market too routinely.  Maybe we can talk trillions of IoT 
devices.  Maybe we can use the SI prefixes, like exa, or peta.

That aside, I would like to ask you whether the CLAT src on Android is 
something I could look at?

Alex

Le 20/09/2017 à 08:03, Erik Kline a écrit :
> There seem to be some misconceptions flying around here.
> 
>> Well, I dont think 464XLAT is deployed anywhere else than on cellular. These
>> are the big numbers that the Original Poster talked about: miliions of users
>> - they are on cellular.
> 
> 464xlat is a client-side bit of code (the NAT64+DNS64 in the network
> is the "other half").  It is primarily implemented in mobile devices,
> and primarily in Android, to be more specific.
> 
> As such, the number of 464xlat capable nodes is numbered in the /billions/.
> 
> There are also some wifi (and wired) networks that are IPv6-only with
> NAT64+DNS64; mobile networks aren't the only ones.
> 
> NAT64+DNS64 is easily the single most successful IPv6 transition
> technology on the planet ([a] if one excludes "dualstack", [b] queue
> the Sean Spicer jokes).  464xlat can help ease things on the client
> side, but it's not the only way to do it (cf. iOS).
>