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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 19 September 2017 19:33 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 8AA94134384 for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 12:33:07 -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 978wO9IQG0Iq for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 12:33:05 -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 B2F5A134386 for <v6ops@ietf.org>; Tue, 19 Sep 2017 12:33:04 -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 v8JJX2QB003940 for <v6ops@ietf.org>; Tue, 19 Sep 2017 21:33:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6186620E6D6 for <v6ops@ietf.org>; Tue, 19 Sep 2017 21:33:02 +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 57B1220E3DF for <v6ops@ietf.org>; Tue, 19 Sep 2017 21:33:02 +0200 (CEST)
Received: from [132.166.84.160] ([132.166.84.160]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v8JJX1W0019867 for <v6ops@ietf.org>; Tue, 19 Sep 2017 21:33:01 +0200
To: 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>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b16c4ca2-da97-9a5a-0f88-6388ebbda80e@gmail.com>
Date: Tue, 19 Sep 2017 21:33:01 +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: <C33DB89E-C005-4A32-9066-C8EE710F3255@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/2k5Ewj4UKZaZ2l6hmAVQFCv_Vks>
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: Tue, 19 Sep 2017 19:33:07 -0000


Le 19/09/2017 à 19:05, JORDI PALET MARTINEZ a écrit :
> Not at all, just to avoid this protocol to be discriminated compared to others.

464xlat has more success than other transition mechanisms.  I saw it for 
myself.

Yet it's about IPv4.

How about Historical.

Alex

> 
> No reason to have some of the standard and others informational, even less if this is the one with has a bigger deployment. Just my opinion, but based in facts.
> 
> 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: martes, 19 de septiembre de 2017, 13:23
> Para: <v6ops@ietf.org>
> Asunto: Re: [v6ops] reclassify 464XLAT as standard instead of info
> 
>      Sounds as trying to impose 464xlat to everyone else?
>      
>      My little IoT IPv6 cellular device does not run 464xlat and neither
>      IPv4.  If 464xlat becomes Stds Track does it mean that it MUST run
>      464xlat?  I would disagree with that.
>      
>      Alex
>      
>      Le 19/09/2017 à 14:23, JORDI PALET MARTINEZ a écrit :
>      > Hi all,
>      >
>      > RFC6877 (464XLAT) is an informational document.
>      >
>      > However, this transition mechanism is the one that has a bigger deployment in terms of number of subscribers using it (hundreds of millions), which I think is even more than ALL the other transition mechanism together.
>      >
>      > Doesn’t make any sense, in my opinion to keep it as an informational document, while we have many others that are standards track and don’t have such level of deployment.
>      >
>      > I was commenting this last week with a couple of the co-authors of this document, and they have the same opinion.
>      >
>      > So, should we aim to do this?
>      >
>      > Can we even consider moving it to STD?
>      >
>      > Regards,
>      > Jordi
>      >
>      >
>      >
>      >
>      > **********************************************
>      > 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
>