<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: [arin-ppml] Fantasyland</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Now THAT is interesting....and disappointing...<BR>
I believe it makes a fantastic scorecard and target for 'anyone' who wishes to influence practical participation in the IPv6 Internet.<BR>
I know that I will be sharing this with my colleagues at Washington University in St. Louis.<BR>
I hope we all learn to appreciate the taste of dogfood.<BR>
<BR>
Bill Darte<BR>
ARIN AC<BR>
Washington University in St. Louis<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: arin-ppml-bounces@arin.net on behalf of bmanning@vacation.karoshi.com<BR>
Sent: Thu 8/28/2008 4:45 PM<BR>
To: michael.dillon@bt.com<BR>
Cc: ppml@arin.net<BR>
Subject: Re: [arin-ppml] Fantasyland<BR>
<BR>
On Thu, Aug 28, 2008 at 12:03:29PM +0100, michael.dillon@bt.com wrote:<BR>
> > > Why shouldn't the company in question just deploy IPv6 and install<BR>
> > > NAT-PT gateways to cover the next 2-3 years before<BR>
> > > IPv6 transit is widely available?<BR>
><BR>
> > Please provide a vendor list for NAT-PT gateways that<BR>
> > provide production level service/availability - today.<BR>
><BR>
> I would hope that the company in question would plan their deployment<BR>
> exercise and not just rush out buying equipment and blasting out their<BR>
> old network. As part of the planning exercise, they might go to the ARIN<BR>
> IPv6 wiki at <<A HREF="http://www.getipv6.info/index.php/Investigate_Middleboxes">http://www.getipv6.info/index.php/Investigate_Middleboxes</A>><BR>
> where they will note vendor names. If they contact said vendors, then<BR>
> there is motivation for said vendors to provide production level service<BR>
> and availabilty within the timeframe for implementation. Note that there<BR>
> is also the possibility of consulting firms using open-source NAT-PT who<BR>
> would then provide the SLA and support component.<BR>
><BR>
> Obviously, today, there is only one vendor on that page and no mention<BR>
> of<BR>
> where open-source NAT-PT can be found. I would hope that anyone with<BR>
> more<BR>
> information would log on to the wiki and update this page and others.<BR>
<BR>
<BR>
which raises the question of "eating our own dogfood"...<BR>
<BR>
there have been a number of calls for folks to take first<BR>
steps to get their "externally" facing DNS, SMTP, HTTP services<BR>
visable on IPv6. One might find this survey of interest.<BR>
<BR>
<A HREF="http://www.mrp.net/IPv6_Survey.html">http://www.mrp.net/IPv6_Survey.html</A><BR>
<BR>
clearly we have a ways to go to meet the first hurdle. As for NAT-PT,<BR>
the IETF is still trying to settle on a standard.<BR>
<BR>
--bill<BR>
_______________________________________________<BR>
PPML<BR>
You are receiving this message because you are subscribed to<BR>
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).<BR>
Unsubscribe or manage your mailing list subscription at:<BR>
<A HREF="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</A><BR>
Please contact info@arin.net if you experience any issues.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>