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

James Woodyatt <jhw@nestlabs.com> Tue, 27 January 2015 19:42 UTC

Return-Path: <jhw@nestlabs.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 8B28D1A89A2 for <v6ops@ietfa.amsl.com>; Tue, 27 Jan 2015 11:42:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 RUU1ACKmb2CO for <v6ops@ietfa.amsl.com>; Tue, 27 Jan 2015 11:42:09 -0800 (PST)
Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D72661A89A4 for <v6ops@ietf.org>; Tue, 27 Jan 2015 11:42:07 -0800 (PST)
Received: by mail-oi0-f41.google.com with SMTP id z81so14097390oif.0 for <v6ops@ietf.org>; Tue, 27 Jan 2015 11:42:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=UUg55s1AJqvYr57anMuhrb+RfX/kqwqCmJgf3yyrCmU=; b=PARNG/jxp9wTmUv2N5JOgzR+2sJoMdUK8CuMToHtpSx+8PldkiDclC/1mPwCQBwDq9 94JJiztMZ3wFnv3PIaSVEdyCLGMkIUP1eXP9UdcwgVvB09/O8GqTvxTS7wm5YetXy5Zw ZHDnvDuq6DhXe1JMeahnQZRwoSbdz40q8aF/NdaoTyGsxrWDlQv8zmvNjJPUDOgtarpc NfWPXALa8B6g/blA/AvTtFpLxJKyyVzSa0d71thTkXXePhQVOCzBbprivalOGBxkIUkv U1gpQndZ7x+63nZRCeU0k+Yj0fYJP0+nCk17GdvCtdPqluaKzlGMUdlmc5LqKmTf5YO3 tvcw==
X-Gm-Message-State: ALoCoQlhbzfkgMwFUd9s4R0fKKRfm2Vw8ASisRS+1y+uU04zAt1qYES1acZmU9rGNkmBuJNKi/pX
MIME-Version: 1.0
X-Received: by 10.202.95.7 with SMTP id t7mr1752232oib.104.1422387727266; Tue, 27 Jan 2015 11:42:07 -0800 (PST)
Received: by 10.76.150.2 with HTTP; Tue, 27 Jan 2015 11:42:07 -0800 (PST)
In-Reply-To: <CO2PR04MB585F5568616227C5624EF52FE320@CO2PR04MB585.namprd04.prod.outlook.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>
Date: Tue, 27 Jan 2015 11:42:07 -0800
Message-ID: <CADhXe51TGUuUm1s_qnGZAFxniYWLz6KnmUuv2XuhS-RWTmqZbg@mail.gmail.com>
From: James Woodyatt <jhw@nestlabs.com>
To: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cdf7037893f050da773d0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/J2TieGKwthZNvIgRwvK-Ra1omXE>
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:42:10 -0000

On Mon, Jan 26, 2015 at 11:34 PM, Metzler, Dan J <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.

p.s. My thanks to George Michaelson for capturing that information.  Very
illuminating.


-- 
james woodyatt <jhw@nestlabs.com>
Nest Labs, Communications Engineering