<!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.6944.0">
<TITLE>RE: [arin-discuss] ipv6 technology supplier phone bank?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>I would also add that technology supplier isn't the only place that needs work.<BR>
<BR>
Based on a brief survey of websites very few if any returned AAAA records for www.DOMAIN-NAME.com<BR>
<BR>
www.cnn.com <BR>
www.mit.edu<BR>
www.harvard.edu<BR>
www.abc.com<BR>
www.microsoft.com<BR>
www.google.com<BR>
www.yahoo.com<BR>
<BR>
the above did NOT return any IPv6 data. Unless I'm doing something wrong with<BR>
<BR>
dig www.DOMAIN-NAME.com aaaa<BR>
<BR>
Since that did return IPv6 data when I did www.arin.net or www.icann.org or www.isc.org<BR>
<BR>
Got to have places for the eye-balls to goto, ergo content needs to be available via the protocol.<BR>
That will help drive the end-users, which will drive the service providers, the equipment providers, etc.<BR>
<BR>
It is an eco-system issue we are dealing with.<BR>
<BR>
Just my $0::2/128 worth.<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: arin-discuss-bounces@arin.net on behalf of Paul Vixie<BR>
Sent: Thu 9/24/2009 7:49 AM<BR>
To: arin-discuss@arin.net<BR>
Subject: [arin-discuss] ipv6 technology supplier phone bank?<BR>
<BR>
> Date: Thu, 24 Sep 2009 08:40:54 +0100<BR>
> From: <michael.dillon@bt.com><BR>
> ...<BR>
> Maybe ARIN could organize an IPv6 awareness sprint, and provide a room<BR>
> full of phones, with coffee and snacks for the volunteers?<BR>
<BR>
this could be done, and would be among other things a great experience of<BR>
shared pain, shared fun, and shared learning for all. (and i can see a<BR>
way to extend it beyond that room on that day, using a ticket system after<BR>
we get back to our own offices.) however, one part of the challenge seems<BR>
daunting:<BR>
<BR>
> Any would-be heroes should sit down at the phone and start calling minor<BR>
> equipment vendors and software vendors to find out when they will support<BR>
> IPv6. Any bit of software used in network operational support or by home<BR>
> users needs to be IPv6 capable.<BR>
<BR>
how should we build the target list, since many of our vendors are several<BR>
layers deep behind resellers, and since pounding on the resellers may be<BR>
like pushing on ropes?<BR>
<BR>
overall i'm intrigued by this idea, it's a great use of ARIN's resources --<BR>
and i mean especially the talents and contacts of *all* of the people here,<BR>
not just ARIN staff/board/council.<BR>
<BR>
paul vixie<BR>
chairman<BR>
ARIN BoT<BR>
_______________________________________________<BR>
ARIN-Discuss<BR>
You are receiving this message because you are subscribed to<BR>
the ARIN Discussion Mailing List (ARIN-discuss@arin.net).<BR>
Unsubscribe or manage your mailing list subscription at:<BR>
<A HREF="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</A><BR>
Please contact info@arin.net if you experience any issues.<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>