Around three years ago, I had a conversation with a very experienced network engineer about IPv6 and how it would improve the way we network. At the time, things were busy, but I managed to find some time to look into the technology. I was intrigued: A network protocol suite that offered a solution to our dwindling address base, tighter security measures, and features for streaming media applications would be fantastic. When would we have this miracle of modern science? “In a few years,” seemed to be the general consensus.
Well, here we are, three years later, and we are still using the current version of TCP/IP, v4. Not having heard much about IPv6 recently, I set out to answer this question: “IPv6, where are we now?”
Ready, Set . . .
In 2001, the name of the game with IPv6 is integration rather than migration. Nearly all major operating systems have implementations of IPv6 available or currently in development. As you might expect, Unix and Linux platforms are particularly well catered for, although implementations for other platforms (including Windows, NetWare, and Macintosh) are also available. Networking hardware manufacturers are also approaching a state of complete readiness for IPv6; some major manufacturers already offer IPv6 support for their products, and others have beta offerings available.
So if the world is ready, the hardware is ready, and the software is ready, when can we expect to see IPv6 become part of our daily lives? It would seem that now it isn’t the technology that’s causing the delays, but rather the demand for the technology from the marketplace causing slower-than-expected progress.
|How Many Addresses Are a Lot?|
As you may know, one of the biggest features that IPv6 will provide is a wider address space. Rather than using the 32-bit addressing format of the current version of TCP/IP, IPv6 uses a 128-bit addressing system. This system yields a staggering 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses. Even though they are not all usable, they should keep us going–for a while, at least!
Many companies aren’t even asking themselves whether they need IPv6. One of the root causes is that many organizations don’t understand IPv6. Or, rather, they don’t see the need for it on their networks–and they may be right. Using Network Address Translation (NAT) to remove the requirement for large blocks of IP addresses has all but eliminated the need for many organizations to look for a solution to the lack of available IP addresses. In addition, other features of IPv6 are only useful to those organizations considering the deployment of IPv6-dependent applications, most of which are awaiting large-scale IPv6 adoptions before becoming affordable and commonplace. In the case of applications driving implementations, it is almost a case of the chicken and the egg.
Wireless May Lead the Way
Although IPv6 does offer more than just an expanded address base, this feature is seen as the biggest driver behind a wide-scale implementation of the new protocol. The largest use of the expanded address base is that of mobile wireless. Even though in certain areas of the world the adoption of wireless devices has been slower than was hoped, the growth potential for this market area is staggering–it will truly need the addressing and other features of IPv6.
An interesting tilt on these statistics was made during a presentation by Nokia at a recent IPv6 forum meeting. The company stated that at present, China has the use of only 4 million IPv4 addresses–but the country currently has over 50 million cellular handsets. If all of these handsets needed an IP address, the only practical solution would be to use IPv6. And mobile handsets are only the beginning: Consider that every home, office, factory, hotel room, and hospital room will be loaded with wireless IP devices in the future, and the need for an almost self-configuring protocol with sufficient addresses becomes even more evident.
Although wireless is one of the areas in which we will see IPv6 manifest itself, other areas are fast gearing up for IPv6 implementation. One of the less visible uses will be IPv6 networks that allow IPv4 networks to connect to each other. Already a number of network hardware vendors are offering products that can be used as IPv6 edge devices, allowing a secure IPv6 network to be used externally while retaining the investment in IPv4 networks internally. Other areas in which IPv6 will become heavily adopted include secure communications and Voice over IP implementations. These areas of adoption will be largely unseen by the masses, who nonetheless will become reliant on the functions that IPv6 provides in these situations.
For more information on IPv6, visit playground.sun.com/ipng or the IPv6 Forum Web site at www.ipv6forum.com.
CrossNodes article: “The Next Version of the Internet Protocol – IPv6”
I must say, though, that even if the IPv6 revolution does not appear on the front cover of every technical magazine or Web site, it is not for the lack of development work. Although the actual development of the IPv6 standard is being performed by the Internet Engineering Task Force (IETF), other developmental parties and groups are continually working toward the introduction and integration of IPv6 on a global scale. One of the most active of these groups is the IPv6 Forum, whose 60+ members read like a Who’s Who of the networking and telecommunications industry. Many universities and other educational establishments also have IPv6 working groups.
Taken separately, all this information points to something big brewing. Taken as a whole, it means much more: The large-scale deployment of IPv6 is more a question of “how soon” rather than “when.” Whatever happens over the next few years, we can be reasonably sure that IPv6 will be a major feature of the IT landscape in the near future. How long in the future? If you were to ask me for a vaguely educated guess, I’d have to say, “in a few years.” //
Drew Bird (MCT, MCNI) is a freelance instructor and technical writer. He has been working in the IT industry for 12 years and currently lives in Kelowna, BC., Canada. You can e-mail Drew at email@example.com.