Mike Palladino, director of IP infrastructure and operations at Internap, asks why the adoption of IPv6 is still in its infancy.
Routing IPv6 packets is well-supported within most modern hardware, but many organisations are struggling with all of the ancillary things that have to happen to facilitate IPv6 — retraining their NOC, rebuilding their management, monitoring, and troubleshooting tools to speak both IPv4 and IPv6, developing IPv6 operational experience and so forth. According to Google, on December 9, 2014, 4.29% of all of its traffic was IPv6. With IPv4 addresses near depletion, why is the adoption of IPv6 still in its infancy? There are three key reasons:
- Squeezing blood from the IPv4 stone is easier than making large design changes. The initial implementation of IPv6, or converting to dual-stack IPv4/IPv6 will always take a backseat to fighting today’s fires.
- A burgeoning IPv4 broker market has sprung up, allowing private resellers to satisfy IPv4 needs for IT organisations in the likely case that the Regional Internet Registries (such as ARIN, RIPE, APNIC, and others) cannot assist.
- Hardware limitations that potentially discourage the use of IPv6, as well as expensive and time-consuming hardware upgrades that are necessary to support IPv6.