Last week in DLTJ Thursday Threads I posted an entry about running out of IP addresses. Since I posted that, I’ve run across a couple of other stories and websites that bring a little more context to the consequences of last week’s distribution of the last blocks of IP addresses from the world-wide pool of available addresses. The short version: channel any panic you might be feeling into making sure your systems are ready to communicate using both the existing network standard (IPv4) and the new network standard (IPv6).
The Imagined Frequently Asked Questions
I haven’t actually been asked questions about this, so these are the Questions that I Imagine are Frequently Asked.
Will the internet stop working?
It is highly unlikely that the internet will stop working. There are various tricks that can be used to maximize the usage of the IPv4 addresses. (Massive deployment of Network Address Translation, or NAT, for one.) And the deployment of IPv6 is going to happen gradually over time and space. 1
There will not be a so-called “flag day” when everyone’s computers switch from IPv4 to IPv6. (There wasn’t the last time the internet went through a similar upheaval in the 1980s — see the “History” section below.) IPv6 will coexist with IPv4 for probably most of this decade, based on what I’m reading, as computers at the edges will communicate over both IPv4 and IPv6. Some magic in the Domain Name Service (DNS) will enable this to happen. There will come a day, though, when IPv4 addresses are truly exhausted and new services will only be reachable via IPv6. Whether we get there before IPv6 is widely deployed is a topic of much debate.
Am I ready now?
Maybe, but probably not. There is a website that tests IPv6 connectivity. This website gives to general responses — can your computer access resources that are offered on both IPv4 and IPv6, and can your computer access resources that are only offered on IPv6.
The Internet Society is calling for a World IPv6 Day on June 8, 2011. “Google, Facebook, Yahoo!, Akamai and Limelight Networks will be amongst some of the major organisations that will offer their content over IPv6 for a 24-hour ‘test flight’. The goal of the Test Flight Day is to motivate organizations across the industry – Internet service providers, hardware makers, operating system vendors and web companies – to prepare their services for IPv6 to ensure a successful transition as IPv4 addresses run out.”
I manage networks. Should I care?
Dude! This is all about you. It is your chance to get new network gear that will support IPv6!
Okay, that probably won’t happen. Your gear either supports IPv6 addressing and routing (perhaps with a software upgrade), or as you phase in new gear it will support IPv6. You do have a lot of work ahead of you, though, to get your network ready. The IPv6 Act Now has suggestions and links.
I manage hardware. Should I care?
Modern operating systems have support for IPv6 as part of the operating system, and you won’t need new hardware (unless you also manage the network, see above). You’ll also need to work with the folks that make you software (see below) to coordinate the transition. DSLreports.com has information about enabling IPv6 for various operating systems.
I write software. Should I care?
Remember the year-2000 problem? Did you scoff at the short-sightedness of those older developers for only using two digits to represent the year? You are about to get your due. The move to IPv6 means a change to the size of IP addresses from 48-bits to 128-bits. Code that is storing, comparing, or outputting addresses is going to have to be reviewed and probably changed to handle both IPv4 and IPv6 addresses. Hurricane Electric has some information on porting code to IPv6.
How can I help?
Reddit notes that “There has been no strong business case for the cost of moving to IPv6, as up until now there have been enough IP addresses available”, and it also answers the question How can I help the adoption of IPv6?.
Bits of History
The last time the internet faced a major restructuring like this was when IPv4 replace the ARPANET Network Control Protocol (NCP). In November 1981, Jon Postel published RFC 801 on the transition plan from NCP to TCP. In the introduction to that document, Dr. Postel wrote:
ARPA sponsored research on computer networks led to the development of the ARPANET. The installation of the ARPANET began in September 1969, and regular operational use was underway by 1971. The ARPANET has been an operational service for at least 10 years. Even while it has provided a reliable service in support of a variety of computer research activities, it has itself been a subject of continuing research, and has evolved significantly during that time.
In the past several years ARPA has sponsored additional research on computer networks, principally networks based on different underlying communication techniques, in particular, digital packet broadcast radio and satellite networks. Also, in the ARPA community there has been significant work on local networks.
It was clear from the start of this research on other networks that the base host-to-host protocol used in the ARPANET was inadequate for use in these networks. In 1973 work was initiated on a host-to-host protocol for use across all these networks. The result of this long effort is the Internet Protocol (IP) and the Transmission Control Protocol (TCP).
These protocols allow all hosts in the interconnected set of these networks to share a common interprocess communication environment. The collection of interconnected networks is called the ARPA Internet (sometimes called the “Catenet”).
The Department of Defense has recently adopted the internet concept and the IP and TCP protocols in particular as DoD wide standards for all DoD packet networks, and will be transitioning to this architecture over the next several years. All new DoD packet networks will be using these protocols exclusively.
The time has come to put these protocols into use in the operational ARPANET, and extend the logical connectivity of the ARPANET hosts to include hosts in other networks participating in the ARPA Internet.
As with all new systems, there will be some aspects which are not as robust and efficient as we would like (just as with the initial ARPANET). But with your help, these problems can be solved and we can move into an environment with significantly broader communication services.
The transition plan for NCP to TCP called for roughly a year-long process in 1982 to transition hosts from one network stack to the other. There were gateways between the two networks during that time. In January 1983 all the gateways between the NCP-based hosts and the IP-based hosts were turned off.