| Barking up the wrong tree? |
| Written by Paul Tiilanus | |||||||||||||||||
| Tuesday, 18 August 2009 13:51 | |||||||||||||||||
|
Today most information regarding IPv6 has either the IT- or ICT-managers of organisations or the IPv6 implementors as target audience. They know about IPv4 addresses running out and the advantages of IPv6 in addition to the extended address space. They know the urgency of migration to IPv6 and have seen the graphs of Geoff Huston. They know that migration to IPv6 is not for free and struggle for budget to implement IPv6. When pleading for budget to make content accessible via IPv6 the usual and reasonable answer is “show me the IPv6-(only-)enabled users”. When asking users why they didn’t migrate to IPv6 their answer is “show me the IPV6-(only)-content”. So there is a chicken and egg problem, and we need to break a vicious circle.
It is slightly more complex than the 2x2 matrices they are used to, but with a little explanation everyone should be able to understand. Let’s first look at the row with the IPv4 user. Both a website on IPv4 or on dual stack can be reached. An IPv6-only website requires initially many, many users that need a 4to6 translation and that is costly. Later, when the IPv4 users are a minority, that is the way to go. Look next at the row with the IPv6 user. Again a matching or dual stack website is no problem. Some new standards are on their way for interconnection of an IPv6 user to an IPv4 website, but that is risky and not an option if you want to move now. Obviously, the dual stack is attractive: all users can access your m&s website. There is an IPv4 address for it now and that need not be changed. We just add an IPv6 address and adapt the back office software to handle the longer addresses. Furthermore, some additional work to fend of hackers is needed.
|
|||||||||||||||||
| Last Updated on Thursday, 20 August 2009 07:52 | |||||||||||||||||
