RE: Call for action vs. lost opportunity (Was: Re: Renumbering)

[<michael.dillon at bt.com>]

> Are there any documents that give adoption instructions for 
> what are expected to be common scenarios?  These would be 
> step-by-step cookbooks, with explanations for when they apply 
> and when they don't?

There are lots and lots of documents in lots and lots of places. Many of
them were written years ago and include deprecated stuff, such as 6bone.
They are written from numerous points of view, i.e. enterprise, academic
campus, Research & Education Network, European, etc.

> Given the adoption hurdles IPv6 has been showing, then 
> efforts to both make it easy and publicize/document that it's 
> easy could be helpful.

Yes. Given that the IPv4 exhaustion date is now within the planning
horizon of ISPs, ARIN has set up a wiki at http://www.getipv6.info to
document how to use IPv6. Since ARIN's audience is ISPs, this is taking
the ISP point of view to the problem.

For instance, if you are an end user, 6to4 is something that you
configure to dip your toes in IPV6 and see how it works without touching
existing IPv4 infrastructure. But for an ISP, 6to4 is a relay service
that you configure in several routers to ensure that an end user's early
experience with IPv6 is more positive and less likely to include high
hop count, and high latency caused by trombone-shaped tunneling
architecture.

IMHO the type of document that Dave is talking about requires many
authors. A wiki is well-suited to creating such documents. But it needs
contributors who know something about IPv6 who will write up some of
this cookbook material-path: <ietf-bounces at ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXu3E-0005lc-Cg; Wed, 19 Sep 2007 03:32:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXu3A-0005jP-Kp
	for ietf at ietf.org; Wed, 19 Sep 2007 03:32:44 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXu36-0007Ed-1Y
	for ietf at ietf.org; Wed, 19 Sep 2007 03:32:40 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.113]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 19 Sep 2007 08:32:38 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 19 Sep 2007 08:34:52 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0010D7194 at E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <46F000C0.6040005 at dcrocker.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Call for action vs. lost opportunity (Was: Re: Renumbering)
Thread-Index: Acf6FPxJUWzHSBJ1SCWf2syfvoFvdgAeWalg
References: <200709130810.l8D8A4mN067629 at drugs.dv.isc.org>	<46E92188.5070504 at iglou.com>	<2990.1189685347.711941 at peirce.dave.cridland.net>	<2098B1AA-19B6-4F99-BB7C-6A7631AFC628 at virtualized.org>	<Pine.LNX.4.64.0709131942470.22434 at hermes-2.csi.cam.ac.uk>	<823FD693-9B95-4602-8F49-6A4D7E7337CF at virtualized.org>	<46E99802.9070202 at piuha.net>	<7442AD34-4EC0-49A1-89D1-85A2F3B63554 at virtualized.org>	<00f301c7f666$56836fe0$038a4fa0$ at net>	<024808CA-B9FB-484B-A892-74959A663C95 at virtualized.org><07e901c7fa04$e905c0b0$bb114210$ at net>
	<46F000C0.6040005 at dcrocker.net>
From: <michael.dillon at bt.com>
To: <ietf at ietf.org>
X-OriginalArrivalTime: 19 Sep 2007 07:32:38.0591 (UTC)
	FILETIME=[4148DCF0:01C7FA8F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: RE: Call for action vs. lost opportunity (Was: Re: Renumbering)
X-BeenThere: ietf at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf at ietf.org>
List-Help: <mailto:ietf-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>,
	<mailto:ietf-request at ietf.org?subject=subscribe>
Errors-To: ietf-bounces at ietf.org

> Are there any documents that give adoption instructions for 
> what are expected to be common scenarios?  These would be 
> step-by-step cookbooks, with explanations for when they apply 
> and when they don't?

There are lots and lots of documents in lots and lots of places. Many of
them were written years ago and include deprecated stuff, such as 6bone.
They are written from numerous points of view, i.e. enterprise, academic
campus, Research & Education Network, European, etc.

> Given the adoption hurdles IPv6 has been showing, then 
> efforts to both make it easy and publicize/document that it's 
> easy could be helpful.

Yes. Given that the IPv4 exhaustion date is now within the planning
horizon of ISPs, ARIN has set up a wiki at http://www.getipv6.info to
document how to use IPv6. Since ARIN's audience is ISPs, this is taking
the ISP point of view to the problem.

For instance, if you are an end user, 6to4 is something that you
configure to dip your toes in IPV6 and see how it works without touching
existing IPv4 infrastructure. But for an ISP, 6to4 is a relay service
that you configure in several routers to ensure that an end user's early
experience with IPv6 is more positive and less likely to include high
hop count, and high latency caused by trombone-shaped tunneling
architecture.

IMHO the type of document that Dave is talking about requires many
authors. A wiki is well-suited to creating such documents. But it needs
contributors who know something about IPv6 who will write up some of
this cookbook material, or dust off old papers and presentations and
copy the key bits, with corrections, into the wiki.

--Michael Dillon

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf





, or dust off old papers and presentations and
copy the key bits, with corrections, into the wiki.

--Michael Dillon

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf