[v6ops] [*SPAM* Score/Req: 3.9/3.3] Re: reclassify 464XLAT as standard instead of info

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 20 September 2017 13:19 UTC

Return-Path: <prvs=143688d48d=jordi.palet@consulintel.es>
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 B31851331E7 for <v6ops@ietfa.amsl.com>; Wed, 20 Sep 2017 06:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.505
X-Spam-Level:
X-Spam-Status: No, score=0.505 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FUZZY_MILLION=2.505] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 tqIsAvmD3fvd for <v6ops@ietfa.amsl.com>; Wed, 20 Sep 2017 06:19:27 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B73C0133205 for <v6ops@ietf.org>; Wed, 20 Sep 2017 06:19:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1505913563; x=1506518363; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=aicoEcOxQfjsUWK84W2FJc0sS hAvAlvYSzZhNp/gaUc=; b=nbayvvKXJzM5W+q8jf4yxmWAcI6w5LmhMO8TcNSEM GMT85uj3z8MkKAoEvnkEY8xmzuh/RPulinjWRsjq1XE5wyh3CE2tOdT99aE3ElVZ CnrWKmUR495WK8r32GBb1x4CbWavkWwTu8+77yRavu9DRYoL3GprGPLGobA1uqV3 Fk=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=lWbnBFyMT6hw1JwdhxqWDsbgGmu83UIk8tDsCgIw6qO1kzLvyJET23EBbXTE 8lgNtVGI1uH+XqoNQ/nNyh2xyZQcfqT1r0eSad9eAQ/0AL1JAoqHb3pKO jGdTG9DizeKaleM3ZyZ/LI1jOuMaGAQFBKl7k5YHcdSphV08Z33tHE=;
X-MDAV-Processed: mail.consulintel.es, Wed, 20 Sep 2017 15:19:23 +0200
X-Spam-Processed: mail.consulintel.es, Wed, 20 Sep 2017 15:19:22 +0200
Received: from [45.6.249.104] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005561232.msg for <v6ops@ietf.org>; Wed, 20 Sep 2017 15:19:22 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170920:md50005561232::PCitZ0uOJVSUw6Lu:00006CEh
X-Return-Path: prvs=143688d48d=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.26.0.170902
Date: Wed, 20 Sep 2017 10:19:15 -0300
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <39456568-1DF0-4D51-8E94-0FDF3595EB31@consulintel.es>
Thread-Topic: [v6ops] reclassify 464XLAT as standard instead of info
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> <d441f1cd-7b22-f94f-1fe2-4b12ab47ae21@gmail.com>
In-Reply-To: <d441f1cd-7b22-f94f-1fe2-4b12ab47ae21@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
X-Spam-Prev-Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/nU-CRNpp2Y6yG6fNVHUJm5vCtuI>
Subject: [v6ops] [*SPAM* Score/Req: 3.9/3.3] Re: 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 13:19:28 -0000

Google is your friend:

https://android.googlesource.com/platform/external/android-clat/

Same for other questions that you asked before … you can find it also for OpenWRT.

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: miércoles, 20 de septiembre de 2017, 9:55
Para: Erik Kline <ek@google.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Asunto: Re: [v6ops] reclassify 464XLAT as standard instead of info

    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).
    > 
    
    _______________________________________________
    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.