Re: [v6ops] draft-ietf-v6ops-6to4-to-historic WGLC

Tore Anderson <tore@fud.no> Tue, 20 January 2015 13:16 UTC

Return-Path: <tore@fud.no>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 813781B2A2E for <v6ops@ietfa.amsl.com>; Tue, 20 Jan 2015 05:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level:
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 WhW6X6jRlNR6 for <v6ops@ietfa.amsl.com>; Tue, 20 Jan 2015 05:16:38 -0800 (PST)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BD511B2A2D for <v6ops@ietf.org>; Tue, 20 Jan 2015 05:16:38 -0800 (PST)
Received: from [2a02:c0:2:4:6666:17:0:1001] (port=44829 helo=echo.ms.redpill-linpro.com) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from <tore@fud.no>) id 1YDYfb-00034A-JD; Tue, 20 Jan 2015 14:16:35 +0100
Date: Tue, 20 Jan 2015 14:16:15 +0100
From: Tore Anderson <tore@fud.no>
To: v6ops@ietf.org
Message-ID: <20150120141615.472bc219@echo.ms.redpill-linpro.com>
In-Reply-To: <201501181900.t0IJ02ps011175@irp-lnx1.cisco.com>
References: <201501181900.t0IJ02ps011175@irp-lnx1.cisco.com>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/Fv6LeHrwI1LWFoJPPeK_tTFhVEY>
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 20 Jan 2015 13:16:40 -0000

* fred@cisco.com

> This is to initiate a one week working group last call of
> http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic.  

I have read this document, and I think it is ready to move forward.

Its operational need for this document is less pressing now than when
the -00 version was published back in 2011. Nevertheless, I find it
valuable and correct to put the final nail in 6to4's coffin at this
point in time. While the operational community for the most part has
already realised that 6to4 has no future, there might be some who have
not been paying attention and formal deprecation of the protocol may
help prevent them from making the mistake of attempting to base
production systems on it.

I have one minor comment though: In section 1, it says «a substantial
amount of 6to4 traffic is still observed by IPv6 content providers».
While I do see 6to4 traffic, it is quite far from being of "substantial"
levels. I would therefore recommend replacing "substantial" with
something milder like "noticeable", "measurable", or something along
those lines.

For what it's worth, today the Google public IPv6 graph shows just a
measly 0.01% of their total IPv6 traffic being Teredo/6to4, so it's not
just me.

Tore