If all the excitement about IPv6 has finally convinced you to take a serious look at what's involved in the transition, you'll want to start with this framework. After all, transitioning to IPv6 can be daunting given it will affect every networked device on the planet and it is more than just a transition of technology, it's also a transition of people and culture and the way we think.
When you do a Google search trying to find guidance on transitioning to IPv6, you come across all sorts of down-in-the-weeds technical information on IPv6 transition techniques -- think tunnel broker, ISATAP, NAT64, CGN, dual-stack, DS-Lite, ALG, NAT-PT, IPv4-mapped addressing, SLAAC, etc. These are all important topics, and there is a time and place to consider the technologies, but when you are just beginning to plan your transition, you need a bigger-picture perspective.
[ Also on InfoWorld: 8 security considerations for IPv6 deployment. | Also: Your handy IPv6 checklist. | Get your websites up to speed with HTML5 today using the techniques in InfoWorld's HTML5 Deep Dive PDF how-to report. | Learn how to secure your Web browsers in InfoWorld's "Web Browser Security Deep Dive" PDF guide. ]
Whether you are a small nonprofit with a couple employees and a basic website, or a multinational corporation with a globally distributed data center architecture, the framework presented here will help you bring your organization into the 21st century.
Before going any further, let me lay out three basic assumptions I'm making about the reader:
1) You are already convinced (or at least your boss is!) that your organization needs to move toward IPv6. It is not my intent to make the case for IPv6 transition or even for IPv6 in general.
2) Your organization's ultimate goal is an end-to-end IPv6 computing infrastructure. In other words, though you may rely on temporary transition techniques in the short term (some of which you may already have deployed), you don't want to rely on them forever. After all, eventually the whole world will transition to IPv6 and there will be no more need for IPv4. Now that may not happen for another century or two, but the point is you want a comprehensive plan that covers the entire organization.