[ppml] IPv6 getting real: was Policy Proposal: IPv4 Transfer Policy Proposal

[Kevin Kargel]

I completely understand that the list of things I touched on was
primarily the "trivial" applications, I did that on purpose to stress a
point.  Whether realistic or not these "trivial" applications are the
things that will generate noise from my residential ISP customers.  I am
sure that commercial and enterprise implementations face a completely
different set of priorities, with the exception of smooth running VPN's
being critical.

I am also sure that there are many critical apps that I did not mention
which are not IPv6 functional today, but I do not want to write a
treatise.  I do find it quite interesting that end user applications
seem to be riding the leading edge, for example Operating Systems and
Email Clients are ready, while email servers and RBL's are lagging
behind.

IPv6 is technically possible today (Great news IMHO, and kudos to all
that brought it to being), but I would certainly not call it useful for
the average consumer --  yet.  

As I stated earlier, the biggest drawback up here in the boonies is that
none of my upstream providers are offering IPv6.  The day after I have
IPv6 upstream available I will be routing, in some shape or fashion.

Kevin





> -----Original Message-----
> From: Bill Darte [mailto:BillD at cait.wustl.edu] 
> Sent: Wednesday, February 13, 2008 12:09 PM
> To: Kevin Kargel; ppml at arin.net
> Subject: IPv6 getting real: was Policy Proposal: IPv4 
> Transfer Policy Proposal
> 
> 
> > 
> > There is no way we will be able to go IPv6 only until ALL 
> of the major 
> > content providers are IPv6 functional, and ALL of the email 
> providers 
> > are compliant.  Think of how you would complain if your ISP 
> went IPv6 
> > and told you that you could now email to "some" places..  or even 
> > "most"
> > places.  
> > 
> > There are a lot of things that need to be functional before
> > IPv6 is a reality for ISP's..  little stuff like IPv6 
> RBL's, bug free 
> > IPv6 VPN compatibility with ALL of the major VPN hardware 
> and software 
> > vendors,
> > IPv6 connectivity for entertainment networks like Xbox Live 
> and PS3, 
> > gaming sites, IM protocols, and a host of other applications that 
> > consumers rightfully demand.  Any one of these "trivial" 
> services not 
> > working is a deal killer for an ISP converting to IPv6 only.
> > 
> (Snip)
> > 
> > What tends to be forgotten, is that for the little guys 
> IPv6 will not 
> > be a complete solution until EVERYTHING that is available 
> on IPv4 is 
> > also available on IPv6 and the use is just as transparant 
> to the end 
> > user.
> > 
> > Kevin
> > 
> 
> 
> Thanks for this list of things that you feel must become 
> 'real' before there can be a significant adoption of IPv6 by 
> the industry.
> 
> I would like to call for others to consider what among this 
> listing of things may NOT be a problem in your experience, 
> and ALSO other serious items that Kevin may have missed 
> including applications.
> 
> I believe it is important to identify all the stumbling 
> blocks (perhaps as a checklist) that may exist so potential 
> adopters can get a heads up and importantly begin to apply 
> leverage to their vendors for support...in order to reduce 
> the number of hurdles.
> 
> Or perhaps a comprehensive checklist already exists that I'm 
> unaware of... 
> 
> Finally, I'm interested in initiatives that you know exist or 
> could/should exist (open source projects, research needed, 
> etc.) that would help reduce these stumbling blocks.
> 
> It would be nice to consider what ARIN (beyond policy and 
> within its charter and mission) could support to promote adoption.
> 
> Bill Darte
> ARIN AC
>