A crisis in the making: Only 4% of the Internet supports IPv6
royal.pingdom.com
royal.pingdom.com
Now we'll have a clusterfuck of overlay technologies, dual-stack corner cases and last-minute crises. Yay, IETF.
How well Dan's article has stood up: http://cr.yp.to/djbdns/ipv6mess.html
According to this guy's somewhat pessimistic view, we're at least two years from the beginning of IPv4 shortages. We already have 4% uptake when there's very little incentive to do anything about ipv6. When the pressure comes on a little bit, uptake will skyrocket.
The great thing is that there's a network effect here: the more people get on ipv6, the more benefit there is to each additional punter. It's more and more attractive as more people join. I think we'll have no problem rolling this snowball.
I admittedly know very little about the shortcomings of IPv6; I do know it handles fragmentation differently, which is apparently causing problems with tunnels, and as far as I can tell, it's a much "bigger" standard, not just IPv4 with a bigger address space, with some parts that are possibly completely pointless. (a little like multicast in IPv4 which seems to get very little practical use) As a developer, is there any particular technology other than IPv4 and IPv6 that I should be targetting?
So for instance, if you want to be able to address billions of people, the scheme that you use to do that should look more like email addresses (which are effectively unbounded) and less like a globally synchronized database of integers.
A lot of problems that are basically intractable at the router/switch layer are much easier to solve with relay servers. Multicast is another great example; IP multicast was a failure, but multicast delivery semantics with (say) 80% of the performance improvements of IP multicast are achievable with relays.
This isn't a crackpot idea; Frans Kaashoek and rtm at MIT had a project investigating it, called Reliable Overlay Networks. I did a startup in the late '90s based on overlays. The technology worked great.
The pain involved in NAT and 1918 addresses would be mitigated if our applications were less tightly coupled to IP (gethostbyname -> sockaddr_in -> connect), and if we could just pick a NAT traversal / NAT rendesvouz technology and run with it.
So my answer to your question is, you shouldn't worry about the alternative. Just keep building normal socket applications.
IPv6 is the future of IP, regardless of its flaws. It is much farther along than anything else, and I don't see that changing. (And I don't see anyone using IPv6 until IPv4 addresses become Really Expensive, which probably won't be for 10 or 15 more years.)
First, the "push towards DNSSEC" is largely just a superficial trend story. There are operational problems with DNSSEC that will probably severely retard DNSSEC adoption. I'm not going to pretend DNSSEC isn't more likely to happen after the last few months, but none of the problem with DNSSEC that almost left it DOA before have changed.
Second, there's no real relationship between DNSSEC and IPv6. DNSSEC signs arbitrary records, including A.