IETF Logo Mail Archive

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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 21 September 2017 10:33 UTC

Return-Path: <prvs=14370a98a6=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 95B711348BE for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 03:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham 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 IPA78nT_UcPO for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 03:33:44 -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 501A81348BC for <v6ops@ietf.org>; Thu, 21 Sep 2017 03:33:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1505990021; x=1506594821; 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=LCk/PFniq2sEt6SJUUaQM4Xbg iNM9CF/Si/xyt3bmfc=; b=Xta47q3hgjdBYiAgHHd0WLrvbQkt18qBPok1MhLld oGpbA8iADI/Q0mzyN0TXYIDHWgCdT2jZ6HlWMMRmCyBEcBEdGTQ58wZw5qWMIFNn OnNV2pbAS2XCD5Lc+jXgmzcxNCVAUG14YGEdhR1+duFHi+k3ObrjbgQays8E8FWZ fo=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=kjPapezn2A3Pp5L90ziNE0fP6+kKaKDYshQ8aJJEirw/SCr0aPLP8M2SDZfs sY2ieYj/Zx4y9E/8pv8bB/aCu0wrBSlOh3YLA3NnuUc3lllKqBE0IAt5w LrNYJka4rEpy0oguhRHOFbkXEs2uvjwulWbqjYuGUwJ1kXEBcMWYSk=;
X-MDAV-Processed: mail.consulintel.es, Thu, 21 Sep 2017 12:33:41 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 21 Sep 2017 12:33:40 +0200
Received: from [10.0.5.203] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005562101.msg for <v6ops@ietf.org>; Thu, 21 Sep 2017 12:33:40 +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:170921:md50005562101::hmehMLfGj7vSXjEU:000000lv
X-Return-Path: prvs=14370a98a6=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: Thu, 21 Sep 2017 07:33:36 -0300
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Message-ID: <78CED789-6366-4CE0-8CC9-E630B13F743C@consulintel.es>
Thread-Topic: [v6ops] reclassify 464XLAT as standard instead of info
References: <C1017FAF-91C3-4CA3-89C2-B64FF5100E41@consulintel.es> <a4385de4-ba3e-0b36-1bfd-ef3210fba08c@gmail.com> <6BD0B640-8853-4B32-9B30-936D8F58000F@consulintel.es> <8503DEC8-026D-4AA2-A887-87B29A2B2611@apple.com> <CAKD1Yr1Dh_qPVbKYXU9e9N2EqeKgS9yQYDR9aao9R-zGa3cU=g@mail.gmail.com> <376bfd13-8f22-3255-0f3b-d077cc205cc9@gmail.com> <CAKD1Yr1V5BsrrEO68ASS1hF-Qj3Q_SsyquXeRx0gNRdNURcKsw@mail.gmail.com> <55371780-be6c-49e6-fe40-bf3b4c05fcfd@gmail.com> <alpine.DEB.2.20.1709211030060.29378@uplift.swm.pp.se> <bd4c7462-2483-b617-e64c-b5dcfc768e17@gmail.com>
In-Reply-To: <bd4c7462-2483-b617-e64c-b5dcfc768e17@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7mXnL5_1DgS_YbkZjrAY2wlww2M>
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: Thu, 21 Sep 2017 10:33:46 -0000

Yes, why not?

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: jueves, 21 de septiembre de 2017, 5:35
Para: Mikael Abrahamsson <swmike@swm.pp.se>
CC: "v6ops@ietf.org WG" <v6ops@ietf.org>
Asunto: Re: [v6ops] reclassify 464XLAT as standard instead of info

    
    
    Le 21/09/2017 à 10:31, Mikael Abrahamsson a écrit :
    > On Thu, 21 Sep 2017, Alexandre Petrescu wrote:
    > 
    >> I am not sure how the tethered clients will have end-to-end IPv6 if 
    >> they dont have a prefix dedicated to them.  Or maybe do you propose 
    >> that to be 64share?
    > 
    > That's what android already does, and have done for years. Probably 
    > Apple iOS devices as well. RFC7278.
    
    So you propose moving 64share to BCP as well?
    
    Alex
    
    > 
    
    _______________________________________________
    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.

v2.23.0 | Report a Bug | By Email