We need to quit looking back at the v4 space like this, bite the bullet and deploy v6. It's already in use on some networks, and inevitable on 95+% of the rest.
The amount of time spent bike-shedding "well, v4 isn't running out as fast as they say it is" or "NAT will save us" (lol, no) that time is better spent deploying v6. For many installations, its actually not that big of a deal to do.
And we will move, but it's not going to happen until 98% of the world's networking infrastructure (both public and private) is IP6 ready, which probably won't be for another decade.
That's the thing though. If everyone is waiting on everyone else, nothing gets done.
If your network doesn't already support v6, you're the person everyone is waiting on! You don't need to wait for your upstream provider to supply you with v6, tunnels are super easy to get.
The only exception to tunneling is if you're hosting a public-facing service, don't have v6 connectivity and don't trust existing tunnel providers. In this case: First, why are you at you're current host or colo center? They're probably shit. Second, set up a box at a provider with good connectivity to run the tunnel yourself. This is basically what we already do when we want to use our public v4 space but the ISP doesn't want to let us talk BGP.
The amount of time spent bike-shedding "well, v4 isn't running out as fast as they say it is" or "NAT will save us" (lol, no) that time is better spent deploying v6. For many installations, its actually not that big of a deal to do.