Editor's Note: Every device attached to the Internet has a unique Internet Protocol (IP) address.
They look like this: "123.123.123.123". We're using them up. When we do, the universe will end. When the universe ends, we won't be able to run Skype. As editor of Skype Journal, that bothered me.
So I asked Matti Salminen to put IPv6 in perspective, to help me sleep better at night. To give me hope. Matti is the Grand Guru of Heavy Iron, Distributed, Dispersed and Desktop Computing. He is a User Advocate and an incurably curious, life-long Student of Future Computing. Here's Matti's IPv6 for the Incurably Curious...
Let's face it, IPv6 discussions tend to be emotional rather than rational. The calm, constructive and exploratory conversations about "What if" and "Why not" seem to be rather rare. It is much more likely that you overhear in your local tech-crowded establishments a variant of:
...and from there onwards the quality of the conversation rapidly deteriorates to levels lower than is suitable for printing.
Both the media and a number of consultants tend to repurpose the same statistics about impending exhaustion of IPv4 addresses as "The Reason" for eventual migration. This practice has two immediate effects: The conversation focuses solely on debating if, and guessing when the IPv4 addresses run out, and it implicitly removes any reasons to explore potential opportunities in IPv6 technology beyond the size of the address pool.
The initial "Wow" definitely is in the numbers. How many of us know what "340 undecillion" is without googling for "undecillion"? But even the most severely mathematically-challenged can visualize without any difficulties the humongous difference between the 4,294,967,296 addresses provided by IPv4 and the 340,282,366,920,938,463,463,374,607,431,768,211,456 addresses provided by IPv6.
So it is natural that it became the eye-catching "dominant feature" in TV news and elevator pitches, where you need to cram every topic into a 15 second sound bite. But in most IPv6 presentations and papers, stuck towards the end, almost as an afterthought, you will find several "Other IPv6 improvements", including perhaps the ones we, from developers to business managers, should be most interested in:
-
IPv6 also supports natively secure end-to-end communications.
-
IPv6 also improves on Quality of Service support, allowing prioritization of timing-sensitive real-time applications, such as video or voice over IP, over less timing-critical applications.
-
IPv6 also improves support for mobile devices, such as laptops, PDAs, cell phones, wristwatch computers, GPS tracking devices, etc.
-
IPv6 also supports automatic transparent address reconfiguration while the device is on the move or in use.
Each one of those present opportunities for application development, specifically for any video and audio carrying P2P applications, such as Skype and provide added reasons to dedicate some time to seriously study what IPv6 could do to your application or device, if taken advantage of.
It is no longer just theory. In the USA, at least, Sprint and Verizon have quietly built IPv6 accessibility into their networks. Today, if you subscribe to either service and use a PDA, cell phone, or a Smartphone running Windows Mobile, here is a test for you: Point it's browser to ocnipv6.jp. Your device will already have auto configured itself with an IPv6 address and you will see it tagged next to "You are using IPv6 - " on their otherwise all Japanese home page. The chances are, that this was new to you, and that the sales clerk you bought the phone/service from, still don't know what IPv6 is. If you are not with Sprint or Verizon, maybe you should generate competitive pressure on your current phone service provider.
But Sprint and Verizon did not implement IPv6 tunneling so that you can visit Japanese IPv6 sites to verify that you are using IPv6 or to watch golfing cartoons or dancing turtles. No, the reason they did, is that, inherently, it is simpler and therefore cheaper to manage large networks and the millions of end-user devices in IPv6 than it is in IPv4. Another IPv6 feature that gets lost in the small print behind the "340 undecillion addresses" headliner/sound bite.
Most of the nay-sayers will reluctantly admit that IPv6 will eventually replace IPv4. During the transition, IPv6 and IPv4 will co-exist while the content is being migrated across. The latter, of course, will ignite another emotional argument about how long the transition period will be, if it's going to happen at all, again stealing the focus away from calm, constructive and exploratory conversations about how to get your content over to IPv6.
The Catch-22 of IPv6 is of course the content. If nobody moves or generates IPv6 content, there is little to no reason to migrate. And vice versa.
Flame wars have little appeal to me and that is not what I am trying to ignite here. What I am trying to wake up is your curiosity and a desire to dig past the headlines to search and explore the potential impact of Ipv6 to your application or device development, networking, operations and it’s potential benefits to your users. Whether Ipv6 arrives here next year or a couple of years from now, is almost irrelevant. In either case, the time to explore it is here, right now. Who knows, maybe you will come up with the “Next Killer Application” that will catapult Ipv6 to everybody’s desk in record time. But you need curiosity, some tenacity and you need an Ipv6 playground.
Most operating systems already have IPv6 support built right in. I'm using both Windows XP and Ubuntu. If you do an "ipconfig" from the Command Prompt you should see that all your network interfaces have both IPv4 and IPv6 addresses assigned to them. The ones starting with fe80: are non-routable IPv6 addresses and never visible outside your own network. If your router were to support IPv6, you could use it in-house already.
You can turn your $60.00 Linksys/Buffalo/many other routers to equal or to surpass the $600.00 IPv6 capable routers by replacing its proprietary operating system with an open and free operating system from either DD-WRT or OpenWRT.
You can get public IPv6 addresses for free from any one of the many Tunnel Brokers (See the partial list below or google for one in your country.) and be on IPv6 inside 5 minutes.
Most major manufacturers are building IPv6 support into all of their network-attached products. There are for example dozens of network attached webcams readily available, which you could access directly from anywhere with your Sprint/Verizon phones.
Quoting Wayne Homren from his IPv6 blog,
"If the first Internet revolution was about connecting people to information, and Web 2.0 is about connecting people to people in social networks, then “The Next Net” will be about connecting people to things and things to each other."
That will require both lots of addresses and the drive from bottom up for capabilities that allows us to connect to "things" and connect "things to other things." So it's time to get curious, get with the program and start exploring IPv6 potential.
-
When you meet with IPv6-aware colleagues, just say to them that "IPv6 is coming" and see what happens for its entertainment value.
-
Don't get stuck in arguments about when or if IPv4 addresses will run out or not. It’s not about “when” it’s about “how you can best benefit from Ipv6?”
-
When you talk to software authors/companies, ask what their plans are to not only tolerate IPv6 but to exploit IPv6 features. Vote with your wallets: buy products only from vendors with intelligent Ipv6 plans.
-
When you talk to you ISP or the host of your website, ask when you will get/have native IPv6 connection. Again, vote with your wallets and support the ones that have a crisp plan in place.
-
When it's cold and dark outside, take time to think how you could add value to your favorite application or product by building IPv6 support in it.
-
When you come up with an idea, start pushing it, in calm, constructive and exploratory conversations.
References:
Matti Salminen
Technology Planning and IT Management Consultant to Fortune 100 companies and startup’s alike across five continents, over a period of three decades, on behalf of two of the world’s largest Information Technology companies.