<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I don't think Karl is running an ISP to the best of my knowledge. <br>
<br>
I am, but in a different way to the majority of ISP's on here, which
means I'm still awaiting my upstreams to make their IPv6 services
production* before I can do so with mine.<br>
<br>
Any adoption is good adoption at this point in time, tunnels or no
tunnels. <br>
If vendors are going to take this long to upgrade their devices to
properly support IPv6 then a tunnelled client is still a great way to
get to the IPv6 internet.<br>
<br>
- Andrew<br>
<br>
*IMHO production would be: Supported on helpdesk with guaranteed
uptimes and no longer referred to as a "beta service subject to change".<br>
<br>
On 21/06/2010 2:38 PM, Mark Newton wrote:
<blockquote
cite="mid:2D6BE33C-6E52-4F5C-AAFB-D32E790367CC@internode.com.au"
type="cite"><br>
<div>
<div>On 21/06/2010, at 1:55 PM, Andrew Cox wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">I'd recommend if you want to
get some good hands-on time with IPv6 and
don't have native connectivity currently: head to <a
moz-do-not-send="true" href="http://he.net">he.net</a> and sign up
for an allocation there.<br>
</div>
</blockquote>
<div><br>
</div>
Yes, people with a lot of time on their hands are perfectly welcome to
do that.</div>
<div><br>
</div>
<div>People running ISPs should be doing the legwork to get native
IPv6 peering and</div>
<div>transit.</div>
<div><br>
</div>
<div>The time for piss-farting about with tunnels was 2003. In 2010
you need</div>
<div>to be ready for production.</div>
<div><br>
</div>
<div> - mark</div>
<div><br>
</div>
</blockquote>
</body>
</html>