A Milestone in a Transition
We live in an age of transitions. Right now we’re in the middle of an important one that most people probably haven’t yet noticed.
Since you’re reading this blog, you’re obviously familiar with the Internet. You may not realize that it works, in part, because Internet Protocol addresses are assigned to each device that connects to the Internet. Your desktop computer at work, your personal laptop, the routers that provide Wi-Fi, all have their own IP address. And, since even more devices connect to the Internet today, so does your gaming system, your mobile phone and other gadgets you own.
As we mentioned here back in February, the Internet Assigned Numbers Authority (IANA), the organization responsible for handing out global IP addresses, has run out of existing addresses, which is somewhat analogous to a telephone company running out of phone numbers.
The current system of addresses is known as IPv4, which stands for Internet Protocol Version 4. It offers 4.3 billion IPv4 addresses, which we’re now exhausting. Plans have been underway for some time to transition to a new IP address system, called IPv6. IPv6 has significantly more addresses than IPv4 so there should be plenty to accommodate current and future needs.
IPv6 uses 128 bit addresses, compared to IPv4′s 32 address bits, which offers a dramatically larger address space. As an example, an IPv4 might look like this: 192.168.10.1. In contrast, an IPv6 address might be expressed like this: 2001:0db8:85a3:0000:0000:8a2e:0370:7334.
All the Parts of the Internet, Working Together
This transition involves all the parts of the entire Internet “ecosystem,” including content providers and websites, ISPs, consumer electronics retailers, equipment manufacturers, and consumers. And this week brings an important milestone.
Wednesday, June 8, 2011, is World IPv6 Day. It’s a global-scale test of IPv6 sponsored by the Internet Society. On Wednesday, starting at midnight GMT (8:00 p.m. Tuesday night on the East Coast), a number of participants will enable IPv6, in addition to their current IPv4 connectivity, on their main websites for 24 hours.
NCTA, as well as some of our member companies, will be participating. NCTA’s website at www.ncta.com will be accessible through IPv6. For those of you running IPv6 you can test this at ipv6.ncta.com or at www.ncta.com. In addition, cable operators such as Bright House Networks, Charter, Comcast, Cox, GCI, and Time Warner Cable will be conducting limited tests on that day to assess how subscribers will interact with their websites (and others) that are testing IPv6.
As I mentioned, this transition has already been quietly underway for some time, and cable has been playing a role since 2004. For example, you may recall that over the past three years, this blog has featured information about deployment of wideband service based on the DOCSIS 3.0 standard. From the beginning, the D3 specification included IPv6 support.
Comcast began IPv6 trials over a year ago. CableLabs conducted interoperability testing since 2009, to help vendors improve their IPv6 implementation.
NCTA hosted a content summit in November 2010, where MSOs and programmers worked together on transition plans. The cable industry also hosted a series of webinars in May 2011 for retailers, describing why they should carry and promote IPv6-capable electronics.
Next week, we’re hosting the IPv6 Summit during The 2011 Cable Show to provide an opportunity for cable operator and programmer executives, senior managers, technologists and other experts to learn more about the transition and collaborate on solutions and strategies. The Cable Show will also feature an IPv6 Pavilion on the Show floor featuring a wide range of consumer devices that are IPv6-enabled.
We’ll have more information tomorrow on World IPv6 Day and what’s going to take place.
“Honey (or Dad) will you fix the network again?” That’s the kind of greeting I’ve been getting far too frequently when I come home from work lately. Have you heard that one yet? Clouds are often used graphically to represent the network connections and it seems my personal cloud (home network) has been suffering some growing pains lately. This growth has required far more attention from the local IT-guy (me).