Someone left the following comment on one of my blog posts a few days ago:
IPv6 to a network engineer is like Communism to a Marxist. It would come in such a distant future that it would be in a form we can barely picture accurately. […] So my money is on NAT444, at least in the US.
Meanwhile on planet Earth (in 2014):
- More than 2.5% of Internet users use IPv6 to reach Google and the growth seems to be exponential;
- 6.15% of US customers (and 11% of Swiss customers) use IPv6 to reach Google. APNIC reports a bit higher number (more than 7%)
- 60% of US transit autonomous systems run IPv6, and 40% of the US content (weighted based on Alexa index) is reachable over IPv6 (source: Cisco’s IPv6 statistics);
- Almost 20% of autonomous systems in RIPE region, and 13% of AS in ARIN region advertise IPv6 prefixes;
- 464XLAT is included in Android 4.4 and T-Mobile uses IPv6-only connectivity for mobile users with the new phones (464XLAT makes Skype work over IPv6-only networks).
We’re getting close to the point where content providers ignoring IPv6 will get penalized, and some engineers are bound to face the five stages of IPv6 grief. Do keep in mind that a proper IPv6 deployment takes anywhere from 6 months to 3 years.
How Do I Get Started?
I created numerous IPv6 webinars to help you design and deploy IPv6 in your network, and if you’re looking for free resources, you’ll find plenty of them on the Internet: