We Need Infrastructure Before IPv6 Becomes a Real Problem

Rainer Enders
While there's no doubt that IPv6 is an eventual end point, we have a long road to get there. It's time that we, as an industry, take a step back and think about what transitioning to IPv6 entails. In fact, with so much fervor in favor of IPv6, this year's IPv6 Day missed a crucial point on this transition - infrastructure. At this point, the move to IPv6 isn't about whether Google or Facebook have enabled their sites to address IPv6 connectivity. The question, rather, is: Will anyone have the capacity to really take advantage of IPv6?

First, let's do a review of where we are: IP addresses are strings of numbers that are assigned to all devices that connect to the Internet. Until recently, the strings of numbers were a collection of 8-bit numbers (totaling 32 bits), but this configuration maxes out at 4.3 billion addresses, which we exhausted earlier this year, according to the Internet Assigned Numbers Authority. So now, the U.S. government has been spearheading initiatives urging the adoption of IPv6. Should the U.S. government mandate federal agencies to transition their websites to IPv6? Should the U.S. government require states to implement IPv6? The argument in favor of this is that so many Americans depend on federal websites. But there's a missing step here. The vast majority of Americans simply cannot access IPv6 yet. The government transitioning to IPv6 would ultimately be futile if the infrastructure isn't in place for us to access the sites.

In fact, according to Akamai's State of the Internet 2011 1st Quarter of 'the top one million Web sites as ranked by Alexa IPv6 reachability of these sites appeared to remain fairly constant at approximately 0.25 percent through the first half of the quarter but jumped suddenly to the 3 percent range in mid-February.' Sure, that looks like progress, but that's actually misleading. In fact, ZDNet's Steven J. Vaughan-Nichols took a much closer look at what's going on and found that this spike was mostly because of Google 'white-listing' Comcast for IPv6 connectivity. According to Vaughn-Nichols, this allowed Comcast 'to reach many blogspot.com [Google's domain name for blogs] hosts over IPv6.? But without this boost, IPv6 reachability at the end of the quarter would be approximately 0.3 percent. The study also found that aggregate IPv6 traffic volumes are between 0.1 and 0.2 percent of Web traffic.

While these numbers paint a dire picture, numbers don't tell the true impact of what's happening. But this will. I live in Walnut Creek, a community less than 30 miles from San Francisco - arguably, the epicenter of technology and innovation in the world. And yet, my community isn't yet equipped to handle IPv6 or high-speed Internet protocols. If we - just a stone's throw from Silicon Valley - can't transition easily to technological innovations, how can we expect anything more from the rest of the country?

The truth is, the transition to IPv6 will be a slow rollout that will happen over the next 10 years. There's still too much work that needs to be done from providers in terms of upgrading their wiring, pipes and firmware. So rather than steamrolling the industry towards adoption, let's take a step back and think about preparedness.

Add Comment      Leave a comment on this blog post
Sep 19, 2011 4:09 AM Silvia Hagen Silvia Hagen  says:
Rainer I agree with what John says, that is my experience too and I also talk for large enterprises over here in Europe, but also in the US where I also consult. One point that I would like to add: In the discussion about IPv6 integration we have to diffentiate between our internal network and our public facing services. For the outside world and the reachability of our website the integration of IPv6 is a very good step, very often not too complicated and simply allows everyone out there to reach us, even the new Internet users, who with the time may have good native IPv6 access but maybe only limited IPv4 access (due to NAT or translation). While we offer our website over IPv6, we still over it over IPv4 (dual-stack) we are reachable for ALL Internet users. Safe way to go. Internally, the world doesn't really care how we access our internal systems, but as in large enterprises it can take several years to integrate IPv6 if we want to do it safely and with a minimum of cost, it is better to start the project now, just as John explains. Silvia Reply
Jan 18, 2012 10:01 PM Consultoria RH Consultoria RH  says:
Este blog � uma representa��o exata de compet�ncias. Eu gosto da sua recomenda��o. Um grande conceito que reflete os pensamentos do escritor. Consultoria RH Reply

Post a comment





(Maximum characters: 1200). You have 1200 characters left.



Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.