Re: [v6ops] discussion of transition technologies

Ole Troan <> Mon, 22 January 2018 21:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BF0BE12D777 for <>; Mon, 22 Jan 2018 13:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ohXlHdssmj_g for <>; Mon, 22 Jan 2018 13:25:39 -0800 (PST)
Received: from ( [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 34D0312D7E3 for <>; Mon, 22 Jan 2018 13:25:07 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 2CEEA2D5080; Mon, 22 Jan 2018 21:25:05 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by (Postfix) with ESMTP id 2052C2017F371A; Mon, 22 Jan 2018 22:25:03 +0100 (CET)
From: Ole Troan <>
Message-Id: <>
Content-Type: multipart/signed; boundary="Apple-Mail=_81EC051F-7323-4D86-B613-691B85DB482C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 22 Jan 2018 22:25:02 +0100
In-Reply-To: <>
To: " WG" <>
References: <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <>
Subject: Re: [v6ops] discussion of transition technologies
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Jan 2018 21:25:49 -0000

> After watching this debate, I'm asking myself why we want to anything
> other than
> a) watch the market deciding for itself, and
> b) formally deprecate anything we decide is broken.

Indeed, there was consensus in the IETF to let the market decide.
(Said differently, there was no consensus on standardising fewer mechanisms).

Why would anyone think that has changed significantly enough that it would matter?
If anyone wants to reopen these discussions, may I recommend they entertain themselves by reading through the few thousand messages over the last 20 years on mailing lists like ngtrans, softwire, v6ops...

It's not for the lack of trying, ngtrans shut down, coin-tosses, deprecation etc.

It isn't a choice among 26 of course. The market is deciding. And we are not the market.
The likelihood of us, as in the IETF, producing any better advice than we've already done is quite unlikely.


>   Brian
> On 23/01/2018 09:23, Fred Baker wrote:
>> On Jan 22, 2018, at 11:17 AM, Ole Troan <> wrote:
>>> What's the purpose of what you are trying to do?
>> This started out as a question among the chairs, triggered in part by an academic article that I can't share because it's not public yet. It lists 26 different transition mechanisms and tries to make recommendations, based in large part of recommendations we have made. The question started out as "can we narrow that to one such mechanism? Which ones are actually in use?" Now see the spreadsheet Lee shared, which comes from different data.
>> It sounds like Ole's data on 6rd needs to get reflected in Lee's spreadsheet.
>> After quite a bit of discussion, we think we had pretty much re-invented RFC 6180. The discussion isn't over, but I suspect we're close. So Lee asked for opinions from you guys.
>> And BTW, I suspect that dslite is a little long in the tooth for the same reason. The theory with both 6rd and dslite was/is that once there is a native path from here to there, even if the dslite configuration is still in the network it's unlikely to be used. That might be naive :-)
>> The big question among the chairs is "what is the real case for translation?" We see it in a variety of places, basically creating a way for IPv6-only devices or networks to talk with IPv4-only devices or networks, but wondering if there is a better way to proceed. My personal take is "it is what it is, no worse than IPv4/IPv4 translation" - not arguing for it, but considering it a fact of life until people become motivated to replace it with native systems and connectivity. YMMV.
>> _______________________________________________
>> v6ops mailing list