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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 19 September 2017 17:05 UTC

Return-Path: <prvs=1435462033=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 51D92134295 for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 10:05:30 -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 ofkH8l2kFJ3W for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 10:05:28 -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 0473C1331C1 for <v6ops@ietf.org>; Tue, 19 Sep 2017 10:05:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1505840723; x=1506445523; 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=AwotELWzLlcMB+QY2/tQEowYv m6M6oXSxHUokFvtkOw=; b=jd2WNrFHj7qSQCCuCroBCp7nfbInnF/XBomF6Rzmh xi+F6AP4JSEWiUoOR/j0Pklx+XTJ6SZqp6pJyOdUcHh+ntESB+gCW8+xYSv4gxQV WZ/D6pjKjqS5C0Ksu30BcvzAm5gMXD3ZgBoAsG13PwEgCmRENCC7VStsJUIFmAdj Ho=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=OK9t/KKX4IV5ErTRaa+CoHSMdLH+EZCOAjgEDJa0ttqHpp4Af8vDvmgZ5EC1 NJuSwMfl72BSkw7U8rqXBAmn2FAyQb1TyK9PeBK+dk6xI03bN32sTLSWy dRffzTTmCk+pdvlPz31ZdgHuczm0rgcQc7X+uRLQHGxRDcjm2gipE4=;
X-MDAV-Processed: mail.consulintel.es, Tue, 19 Sep 2017 19:05:23 +0200
X-Spam-Processed: mail.consulintel.es, Tue, 19 Sep 2017 19:05:23 +0200
Received: from [45.6.254.173] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005560272.msg for <v6ops@ietf.org>; Tue, 19 Sep 2017 19:05: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:170919:md50005560272::UWBPj3c9nkkn/bm/:00005Ipw
X-MDRemoteIP: 45.6.254.173
X-Return-Path: prvs=1435462033=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: Tue, 19 Sep 2017 14:05:19 -0300
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <C33DB89E-C005-4A32-9066-C8EE710F3255@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>
In-Reply-To: <85d934b3-ae06-c0ea-3519-4069c8387f0a@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/lxJPh-dzyk9S5Ps0RG-sqMJ4hMo>
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 17:05:30 -0000

Not at all, just to avoid this protocol to be discriminated compared to others.

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.