Re: [v6ops] Bar BoF on a 6to4 replacement?

Owen DeLong <owen@delong.com> Mon, 01 December 2014 20:38 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 414E01A8A81 for <v6ops@ietfa.amsl.com>; Mon, 1 Dec 2014 12:38:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.001
X-Spam-Level:
X-Spam-Status: No, score=-1.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 NdNSpwPKxpiU for <v6ops@ietfa.amsl.com>; Mon, 1 Dec 2014 12:38:49 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 6A6CA1A1A7E for <v6ops@ietf.org>; Mon, 1 Dec 2014 12:38:49 -0800 (PST)
Received: from [10.20.0.185] ([192.31.187.123]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.2) with ESMTP id sB1KZP4Q004031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Dec 2014 12:35:26 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com sB1KZP4Q004031
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1417466127; bh=9bM9PYdu5qsCUF2bGS+990ZuhYI=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=N/sNny3mgItqUm5p7kGck1YzQsFgvJHy+1nYcw4/BePvhVpDGrm5jfCdv79tpIGnP crAIiPmwW5wFKT6a7/HIKuNLsv5Oo6Pzes++SdGrs/0rLGr/DvTcmb+3ndOrFjl6NQ /bnw7egvQI65rWM0+aEzR+KB5cG9C+BJnweHjSjA=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20141113195636.GY31092@Space.Net>
Date: Mon, 01 Dec 2014 12:35:20 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8586C6F3-34C6-4E2C-996E-359393B39FC9@delong.com>
References: <2134F8430051B64F815C691A62D9831832D76378@XCH-BLV-504.nw.nos.boeing.com> <AD4F3B9C-18D2-4B6F-867C-423368D6F489@muada.com> <4C77BAB8-38FD-4830-B779-E24586EB9275@delong.com> <5458294D.9000502@massar.ch> <64F92F49-4A31-4268-99D3-8A482E95735F@delong.com> <EB80E1B1-335F-45CA-BAFA-C2DB1BA58F1A@muada.com> <54643D0B.4070208@gmail.com> <88329C76-8C09-42D1-A0F7-9A65B98E1D44@muada.com> <alpine.DEB.2.02.1411132029560.25356@uplift.swm.pp.se> <D202E444-D659-447E-919A-10C6DB48A0BE@muada.com> <20141113195636.GY31092@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1990.1)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Mon, 01 Dec 2014 12:35:27 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/UOV5SC5M0EhGNbsOwIDorp02-8s
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Bar BoF on a 6to4 replacement?
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: Mon, 01 Dec 2014 20:38:50 -0000

> On Nov 13, 2014, at 11:56 AM, Gert Doering <gert@space.net> wrote:
> 
> Hi,
> 
> On Thu, Nov 13, 2014 at 09:50:31AM -1000, Iljitsch van Beijnum wrote:
>> There's no reason tunnels have to be so-so. 
> 
> I'm wondering who would provide these tunnels in the future, and what would
> their business model be.
> 
> This is a real question.  Today, you can get tunnels from Sixxs nodes
> (enthusiasts, which might eventually consider the IPv6 deployment issue
> to be "solved" and stop running tunnel nodes), HE.NET (it's good marketing,
> but eventually the costs involved might win over the marketing gain?), 

I’m no longer with HE, but I will say that this is unlikely. While the cost of supporting
the tunnel brokers is not zero, it comes sufficiently close that I’d be very surprised
to see it reach this state at any point prior to ubiquitous native IPv6 and the deprecation
of IPv4 as a common backbone internet protocol. HE has multiple reasons for
providing the tunnelbroker service that go beyond mere marketing.

(In other words, there will probably be pockets of IPv4, but “the internet” will be an
IPv6 internet and IPv4 will exist in islands where it can’t yet be deprecated, but the
hosts that still talk to the internet will do so over IPv6 somehow.)

Owen