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

Owen DeLong <owen@delong.com> Tue, 27 January 2015 19:57 UTC

Return-Path: <owen@delong.com>
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 6910E1A8A28 for <v6ops@ietfa.amsl.com>; Tue, 27 Jan 2015 11:57:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, 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 BjIMZw9R1UCV for <v6ops@ietfa.amsl.com>; Tue, 27 Jan 2015 11:57:28 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 9DAEF1A6FF0 for <v6ops@ietf.org>; Tue, 27 Jan 2015 11:57:28 -0800 (PST)
Received: from delong-dhcp227.delong.com (delong-dhcp27 [192.159.10.227]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id t0RJriW2010802 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Jan 2015 11:53:44 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com t0RJriW2010802
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1422388424; bh=8NVkTn5rSG3yLtf+zLjrpXPl6ok=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=wDxSeG/qKEbnlHc3qfctyRAkUTB5jCIT3XYJj3MWS0GXbMb/7z8zQ6/vzyrY0P2l+ PXqRLGyqq7qL0p/nvdP0YCpMTaFlDq83GoDt0JEjrKj9+VUUVyq0jyDHxn91ucpqIL 5oe9Rzw7QA8JD8JPhBXGsdUgCmcwmojVJdjAu2Zk=
Content-Type: multipart/alternative; boundary="Apple-Mail=_9BE68BAB-7818-4F58-9224-0E782451D960"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CADhXe51TGUuUm1s_qnGZAFxniYWLz6KnmUuv2XuhS-RWTmqZbg@mail.gmail.com>
Date: Tue, 27 Jan 2015 11:53:41 -0800
Message-Id: <0CFB7162-4F60-411F-901A-8500F2690E4E@delong.com>
References: <CAKD1Yr1Ec7=g5VNZtbBw6Tutr2oi-1_SmcEJu_JCDKUvSGsAUA@mail.gmail.com> <799288670.862323.1422315117216.JavaMail.yahoo@mail.yahoo.com> <CAKr6gn1-w3RuOOWjxXhA8_tLk1GQDN4LFqY=+8e1-y_8b=DGGw@mail.gmail.com> <54C70777.8080704@gmail.com> <CAKD1Yr3aOWBu7aU7WA2rgs4_AjgBUrg3V12q9Nfx--b9+wR0zg@mail.gmail.com> <CO2PR04MB585F5568616227C5624EF52FE320@CO2PR04MB585.namprd04.prod.outlook.com> <CADhXe51TGUuUm1s_qnGZAFxniYWLz6KnmUuv2XuhS-RWTmqZbg@mail.gmail.com>
To: James Woodyatt <jhw@nestlabs.com>
X-Mailer: Apple Mail (2.1993)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Tue, 27 Jan 2015 11:53:44 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/XL6wgnlg_mgCCRWPZkcisbrPBMs>
Cc: IPv6 Ops WG <v6ops@ietf.org>
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, 27 Jan 2015 19:57:30 -0000

> On Jan 27, 2015, at 11:42 , James Woodyatt <jhw@nestlabs.com> wrote:
> 
> On Mon, Jan 26, 2015 at 11:34 PM, Metzler, Dan J <dan-metzler@uiowa.edu <mailto:dan-metzler@uiowa.edu>> wrote:
>  
> 
> Unless an alternative auto-configured solution is provided out-of-the-box by vendors, (not likely if WGs are claiming it isn’t needed), then 6to4 is likely to hang around; even if it isn’t the optimal solution.  I heard claims that it would be a good 5-6 years before vendors would be able to push an alternative solution out the door, and by that time IPv6 will have reached critical mass.  Well if that is the future we’re putting forward and we aren’t pursuing an alternative solution, then we are waiting for IPv6 to reach critical mass before 6to4 really becomes “dead”; or at least waiting for all ISPs to provide some kind of IPv6 connectivity.  (Or, we’re waiting for the relay operators to cut off their access.)  Until then it is likely that 6to4 will hang around in at various levels because there will always be a group of internet users that are using the existing 6to4 relays to be able to reach IPv6 only hosts, and over time we can expect the number of v6 only hosts to go up; not down. 
> 
> 
> I hate to be That Guy, but I can't keep myself from wondering aloud if we might see measurable *intentional* usage of 6to4 [RFC 3056] in the wild for as long as we still see IPv4 in the wild.  When I'm feeling especially depressed about this topic, I wonder if we might see 6to4 as the *last* major application of IPv4 before we turn off its lights in the default free zone.

I think that’s pretty unlikely.

6to4 really doesn’t do you much good if you’ve got IPv6 connectivity available, and I can’t imagine that a network would be the last vestigial holdout of transition rather than some arcane application or end device.

Owen