There are of course the companies who are pushed to adopting IPv6 platform because of the numbers. Take Verizon. They would never be able to have sufficient addresses, nor IPv4 infrastructure to cater for, say 100.000.000 on-the-go WiFi phones. Piece of cake with IPv6 inherently mobile IPv6 addressing.

Or take a look at the OLTP (One Laptop Per Child) program pushing PCs to far corners of this earth with no IP infrastructure of any kind. The secret sauce that makes it work is made out of IPv6-based mesh networking. It’s there. It works.

But I’m looking at it from the user’s perspective. We don’t care what addressing schemes are used but today establishing network connections and VPNs between or amongst family members, or classmates who may use very different types of computers a) requires a fair amount of technical knowledge and b) bunches of often misbehaving and difficult to tame applications and c) requires that those computers don’t move around a lot.

Easy enough to set up today but we need to do it without tunnel brokers in the middle or clumsy translations. Also, the programmers are asleep, I think, and very few end-user applications support IPv6 yet. Ekiga, which had IPv6 support built in since the beginning has mysteriously pulled the feature out. Who will fill the VoIP/IM vacuum for IPv6 adopters? To me, the time to write IPv6 support in your applications is TODAY. Thinking about it until the “1st World” wakes up and everyone else has it, is not very smart.