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

Fred Baker <fredbaker.ietf@gmail.com> Tue, 19 September 2017 20:41 UTC

Return-Path: <fredbaker.ietf@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 14B5F1343A0 for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 13:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 B-ZM4PYEJ6PP for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 13:41:54 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8EFB13439C for <v6ops@ietf.org>; Tue, 19 Sep 2017 13:41:53 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id d16so2070213ioj.3 for <v6ops@ietf.org>; Tue, 19 Sep 2017 13:41:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mlrIrLDCaH6DzS/aQOiI+YVuDoXQcdCZSiZOJgJ6mkY=; b=szpStYP6ZcNLX1bWA2sCQkT/O3e65p8K3tEjgDP9ZeTFL3chGf7IvC13sfMJSjSCIB idd98yUypI6DLcTOQ8e4kAozkn6vfYphHV2lDU/6c4OdlbNeKwhjq6JYCshoMTXrue3c fmiqHOnt42IkcxAeX5KRKT3isanCGMtqX/Ca4ziiB36ttp/NHzEXuA5HKg/GBn4LgQle QUmBrr8mAB2DNjVhsclvEFSxLJfKIFuMTXNvzsatHM82YWzse2WFfNHcBG8RVYrPAb70 lJlWX07KFYUt0+RNIRGYWIF69P/odQvSb5/GOlkMGMjYYYUwLLpWwz7qq9TAr2ZpNamb WWVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mlrIrLDCaH6DzS/aQOiI+YVuDoXQcdCZSiZOJgJ6mkY=; b=CutooB/3C6RKgDORy7L6xZOnTb9oDv6le3GsRoA9foTj2ZZ6tSq2/B1UrgZ09RMBAS g1MFa6douZT/xy6ifAyw28JIjvD20lP665qVgifshpnd2paEg1OyM9317+i3qBkiOZto A+DGgsq2idAFZTs1w1Qkj6MipW5Hby3KaVYEPsa+AS3L4fDyiy/PBYOCT8SS6uemT5UM I9cfa2moGm0tfQOGUyuFFNNoExElUfvoKORUj/FpWlj9AM8BV60lI2A//k4rnHnz2HJ+ Krsouz0vbOF74eJDnPaGK30IdaQ/YwuSgyA6fdCMfIb9+AlTZOF1r7IvbgLunQd7U9j1 9kMQ==
X-Gm-Message-State: AHPjjUiV4st+zzbvbwvE4kXroZQtBZYXskWG8VBAHI0yGRf8A3wr2I45 gM0JGyFt+N4UCXN0n3TLjAQ=
X-Google-Smtp-Source: AOwi7QBj9K/e00/A2+AlMiAAOuXL1KR72MhlU5VG665hdmk63YnO8aptyu2/g94g0vXQRCMWv3cqWA==
X-Received: by 10.202.207.144 with SMTP id f138mr2775825oig.37.1505853713138; Tue, 19 Sep 2017 13:41:53 -0700 (PDT)
Received: from ?IPv6:2600:8802:5600:e::1da8? ([2600:8802:5600:e::1da8]) by smtp.gmail.com with ESMTPSA id c126sm101223oia.35.2017.09.19.13.41.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Sep 2017 13:41:52 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.6\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <b16c4ca2-da97-9a5a-0f88-6388ebbda80e@gmail.com>
Date: Tue, 19 Sep 2017 13:41:50 -0700
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9C2822F-56EE-47D8-AAB5-C041A3D22F41@gmail.com>
References: <C1017FAF-91C3-4CA3-89C2-B64FF5100E41@consulintel.es> <85d934b3-ae06-c0ea-3519-4069c8387f0a@gmail.com> <C33DB89E-C005-4A32-9066-C8EE710F3255@consulintel.es> <b16c4ca2-da97-9a5a-0f88-6388ebbda80e@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-Mailer: Apple Mail (2.3445.1.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/7PtX1dx4YYxwWzw6bRehCU4kRsE>
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 20:41:56 -0000

Chair hat off.

If it were ONLY about IPv4, I might agree with you, or suggest another working group. 464XLAT is about connecting an IPv6-only (subset of a) network to an IPv4 network, which I would think remains a current issue. If we're serious about talking about IPv6-only networks, an important part of that is helping people get there. That has been my argument for doing anything related to transition mechanisms, in v6ops or anywhere else. 

If we were to declare anything HISTORIC, it would be other transition mechanisms that have been documented but not widely found useful. We killed 6to4 and Teredo...

> On Sep 19, 2017, at 12:33 PM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> 
> 
> 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
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops