Expand your universe with IPv6

The internet is running out of addresses. That is what they keep telling us. The IPv4 block is simply inadequate - and given the expansive nature of internet adoption this might be true, but are we really running close to the end of the internet?

Most Regional Internet Registries have said that 2010 or 2011 would mean the end to IPv4 with the vast majority saying that their allocation of IANA ip addresses would be exhausted in early 2012. But is this really true? Honestly - the answer to that question is really moot because IPv6 is coming whether you want it or not.

So - let's talk about what plagues IPv6 implementation. Having done several of these conversions I would like to share my insights into how to make your IPv6 transition a headache free event.

The Dual Stack
Until IPv6 becomes a reality there is really no getting around the fact that IPv4 is still the standard. So, you have to allow for that. The only way you can manifest IPv6 and IPv4 is to "Dual Stack" your configuration. But understand that you have no options here - IPv6 is coming and you cannot wait until it is a reality or you risk being shut out of the internet altogether.

So, what does "Dual Stack" mean to you? Simply put it is the operation of IPv4 and IPv6 in a single environment using both IPv4 and IPv6 hosts. By adopting such a hybrid implementation programmers can write code that operates on both IPv4 or IPv6. Such software would use hybrid sockets which would accept both IPv4 and IPv6 packets. Used in conjunction with IPv4 communications, a hybrid stack would use IPv6 internally and the present IPv4 addresses as IPv6 addresses in a specially masked format.

This specially masked format is essentially an IPv4-mapped address with the first 80 bits set to zero, the following 16 bits set to one, and the final 32 bits are filled with the standard IPv4 address.

There are pitfalls to the IPv4-mapped address. One is that some O/S's don't support the hybrid format due to security issues or protocol issues. So - look at your O/S on a case by case basis. Microsoft O/S uses IPv4 and IPv6 in separate implementations so a separate socket has to be opened to support each protocol. Linux O/S use the IPV6_V6ONLY socket thus making a hybrid dual stack somewhat problematic.

Tunnelling
Without going into all of the various methods and techniques, tunnelling is a viable option for those who look at dual stacking as an overly ambitious project. Tunnelling is basically using a device or software to translate IPv4 addresses into or from IPv6 addresses before any packets are transferred to the internet.

There are various tunnelling options - Automatic Tunnelling (i.e. Teredo), Configured Tunnelling (formerly known as Configured and Automated Tunnelling), and Proxying. All work in similar ways, but differ in the approach taken (translation of IPv4 into or from IPv6, but the procedure for doing so changes).

The Box
Your equipment is going to be the first place you must look to making a change. Basically put, you have to contact the vendor who supplies your routing and switching equipment and see if your current version will support IPv6 and, more specifically, if it can perform any IPv4 / IPv6 translation. If the answer is no then you need to be prepared to upgrade either the device operating system or replace the device altogether.

Best practices for IPv6, for most early adopters, is going to be the use of devices as a translation mechanism.  Think of it as IPv4 to IPv6 NAT.  That might sound a bit simplistic, but it is essentially just that simple (don't get bogged down in the complexity behind the scenes).

The Provider
Contacting your Internet Service Provider is also critical - find out from them (in very tedious and specific detail) what their plans are for IPv6 adoption and discuss with them what you must do to ensure ZERO interruptions in your service. Don't take "I don't know" or "nothing" as an answer - somebody there knows something so escalate until you get a satisfactory answer.

If you don't feel as though your ISP is being forthright with you, or if you feel that they are unprepared, you should consider making a switch (if that is an option).

VOIP can kill you
With the introduction of vast VOIP networks IPv6 is being adopted as the standard by many carriers (especially 3G and 4G networks) as the standard. Internally VOIP works well across IPv4, but, as VOIP networks expand universally (especially in the mobile telephony space), IPv6 adoption is becoming an absolute necessity.

The End Game
Making the decision to adopt IPv6 isn't really going to be yours. At some point it will happen and your organization needs to be prepared. The hype of IP addresses running out on the internet should not sway you (CIDR and NAT have delayed the run-off of IP addresses), but preparedness is part of business.

Preparedness aside, there are benefits to IPv6 implementation that can be a boost to your business: Security (it will be easier to detect the sources of malevolent activities); Scalability (device to device communication can be greatly expanded); Cost (IPv6 has significant cost advantages for current networks, and for developing larger scale networks required by industry).

Overall the move to IPv6 is a growing reality. Being an early adopter doesn't need to be your goal, but having a plan should be.