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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 21 September 2017 08:34 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 6A8B11331FF for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 01:34:27 -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 C8KImJ3pjjQm for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 01:34:25 -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 75A7B1323B4 for <v6ops@ietf.org>; Thu, 21 Sep 2017 01:34:25 -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 v8L8YMxr139574; Thu, 21 Sep 2017 10:34:22 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B131A2038CB; Thu, 21 Sep 2017 10:34:22 +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 9861620387A; Thu, 21 Sep 2017 10:34:22 +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 v8L8YM4s025873; Thu, 21 Sep 2017 10:34:22 +0200
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Lorenzo Colitti <lorenzo@google.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>
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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <bd4c7462-2483-b617-e64c-b5dcfc768e17@gmail.com>
Date: Thu, 21 Sep 2017 10:34:22 +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: <alpine.DEB.2.20.1709211030060.29378@uplift.swm.pp.se>
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/EKK0vUhYGoTAuL7atBbyUiCqSiY>
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 08:34:27 -0000


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

>