To be clear: transitioning to IPv6 is a two step process:
1) you need to enable IPv6 everywhere
2) when that is working, you can sunset IPv4
So, every transition strategy involves both the life support for IPv4 and the delivery of IPv6.
Sometimes the ISP has no choice but to use it. And iff the ISP also rolls out IPv6 in parallel, this is fine, the users can access the dualstack websites over IPv6, while still using IPv4 for the rest of the content. And this is the key.
A lot of folks here are building products that have their front door on the Web.
And this is where all of you, as a "content provider", can make a difference for those users who already have IPv6 by providing the service both on IPv4 and IPv6.
In my conversations, the vast majority of the folks who are going to have to deploy CGN, also have already running programs to deploy IPv6. It's just that they don't necessarily advertise them, and also that these things take years - the access is by far the hardest part of the internet to transition.
At my $employer, a couple of bright interns this summer made this: http://6lab.cisco.com/stats/ - which aggregates the stats from various places and allows to get a more rounded view. Besides for the access part (EDIT: which, as I said, just takes some time), the situation is not bad at all!
1) you need to enable IPv6 everywhere 2) when that is working, you can sunset IPv4
So, every transition strategy involves both the life support for IPv4 and the delivery of IPv6.
Sometimes the ISP has no choice but to use it. And iff the ISP also rolls out IPv6 in parallel, this is fine, the users can access the dualstack websites over IPv6, while still using IPv4 for the rest of the content. And this is the key.
A lot of folks here are building products that have their front door on the Web.
And this is where all of you, as a "content provider", can make a difference for those users who already have IPv6 by providing the service both on IPv4 and IPv6.