So how bad is it?
Well, we don't hear much about the IPV4 exhaustion really, while according to the down counter it should be very fast now. Of course there are all kinds of ways to bypass the need for additional ip addresses in IPV4 in web clients as well as web servers. So how big is the problem really I'm often asking myself. The only way we, being a web development company, need different ip addresses is when we want to use an SSL connection, although I guess that can also be easily installed on the same ip address.
I'm also still amazed that ISP's don't seem to push IPV6, as they seem to have had the problem. However, here in The Philippines normally you just get a private ip address from your ISP, so no real need.
Big disadvantage on the private site (computer users at home) could be that normally behind your NAT router you kind of automatically have a firewall. With IPV6 you would lose that protection of course.
And of course home router builders and sellers will not be happy with IPV6, as home routers would simply not be needed anymore as you don't need support for connecting different computers to one ip address given by the ISP.
So what's next? I don't really know, but may keep you updated here.