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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 21 September 2017 11:10 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 D41411348FB for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 04:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 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, URIBL_BLOCKED=0.001] 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 6YMkjQf7pgov for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 04:10:41 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 D5B02132D41 for <v6ops@ietf.org>; Thu, 21 Sep 2017 04:10:40 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v8LBAca7001196 for <v6ops@ietf.org>; Thu, 21 Sep 2017 13:10:38 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7BF60207CEC for <v6ops@ietf.org>; Thu, 21 Sep 2017 13:10:38 +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 7264E207CEB for <v6ops@ietf.org>; Thu, 21 Sep 2017 13:10:38 +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 v8LBAb5K026022 for <v6ops@ietf.org>; Thu, 21 Sep 2017 13:10:37 +0200
To: 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> <bd4c7462-2483-b617-e64c-b5dcfc768e17@gmail.com> <78CED789-6366-4CE0-8CC9-E630B13F743C@consulintel.es> <dbac4f8a-55e0-345b-667c-937b75869890@gmail.com> <F8A62D88-6FAE-48A1-A28F-F84451F781BA@consulintel.es>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f26447b3-8d9b-2216-495e-59413e3a8913@gmail.com>
Date: Thu, 21 Sep 2017 13:10:37 +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: <F8A62D88-6FAE-48A1-A28F-F84451F781BA@consulintel.es>
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/SKGTQACnDwTUdS8UfrV6o0pdsUI>
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 11:10:44 -0000


Le 21/09/2017 à 13:03, JORDI PALET MARTINEZ a écrit :
> DHCPv6-PD is a good thing to have. I’ve confronted thoughts on DHCPv6
> vs SLAAC … However, I understand it will be nice to have DHCPv6
> implemented everywhere, as for example enterprise environments prefer
> a more controlled environment.
> 
> However, having DHCPv6 doesn’t exclude having 64share as well.

It does: try to run both on a computer and you will see.

In practice: a particular operator had to make some choice some time. 
That choice led to either 64share on an APN, or DHCPv6-PD on another 
APN.  They had some reason to put each such thing on a distinct APN.

It's not simply a matter of having two distinct RFCs.  I can live with 
thousands of RFCs if you wish.  But I cant live with different APN each 
for an RFC.

I dont want a Connection Management software to switch between APNs like 
that.

I am not sure whether I explain this ok, but that's the way it is.

> Otherwise, if we follow your suggestion, we should cleanup 60-70% of
> the protocols that we have, because they are redundant.

In this discussion we talk 64share and DHCPv6-PD.  Pick one.

(for the other 60-70% protocols in MIB we can discuss separately if you 
wish).

Alex

> 
> 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, 7:57 Para: <v6ops@ietf.org> Asunto: Re: [v6ops] reclassify
> 464XLAT as standard instead of info
> 
> 
> 
> Le 21/09/2017 à 12:33, JORDI PALET MARTINEZ a écrit :
>> Yes, why not?
> 
> Because DHCPv6-PD does that.
> 
> Alex
> 
>> 
>> 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.
>> 
>> 
>> 
>> _______________________________________________ v6ops mailing list 
>> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>> 
> 
> _______________________________________________ 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.
> 
> 
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>