Clues are on sale this month. Buy now.
There's a lot of rubbish argument going on in the comments regarding IPv6. Lets discuss some of them:
1) IP addresses are too long.
So was the digit count in the year before 2000. We used '99' instead. We all remember the joy of Y2K (even though in the end nothing happened). The reason the IP address is so mind-numbingly long is so that in another 10 years time you don't all complain about the lack of IP addresses and we have to start down another road to IPv47 or something.
There is more than just IP count thats responsible for the 128 bits length too. If you actually bothered investigating IPv6 (oh wait.. that requires you have sense doesn't it...) you'd see that the bits are logically divided to provide adequate addressing in logical units.
For example, it is accepted that no network segment should be smaller than a /64. This gives you 2^64 IP addresses for your company network, and allows stateless autoconfiguration by munging your MAC address into an IP address. This is good design. It means IPv6 autoconfiguration is easy.
2) Route profileration contaminates the internet.
Again, you haven't been reading. When PROPERLY CONFIGURED these kind of packets should only exist on local internal networks. Backbones, etc. should be statically configured, as you'd expect from a professional level.
3) "We had problems and had to disable IPv6".
No, you had misconfigured software. PHP (even on Windows) handles IPv6 just fine, its more likely your system just wasn't configured correctly. True, I can't speak for ASP. If you have problems because of IPv6, its because of software configuration.
4) Nobody's using it.
Actually, Akamai (one of the internet's biggest content distribution networks) recently registered an IPv6 BGP table entry. Clearly they're taking IPv6 seriously.
5) Why bother? There's plenty of IPv4 space.
No, there isn't. It runs out next year by most estimates.
6) Why don't we just reclaim unused space?
Firstly, how do you plan to do this? Legal enforcement? You'll be in courts for years and not see a single IP come back. And why should organisations give them back? They paid good money for them, they have a right to keep them in "storage" until needed. You have no right to say to them "Look, you're not using and we've run out. We can't be bothered to install the next generation IP, so we're nicking you address."
7) IPv6 sucks. <insert reasons here>
I can't refute any claim of any particular feature or the protocol on a whole "sucking". However, I would ask a question. Where's your paper on an alternative protocol? Oh wait, you haven't got one. So shut up. Until you can suggest a better idea that the world will go for, you can't talk about anything.
8) There is no chicken and egg situation; IPv6 is just not wanted.
Wrong again. IPv6 hardware requires investment. Investment requires being able to see a return. Where's the return if no ISP customers use IPv6 ?
Where's the return if router manufacturers sell to customers who's ISP doesn't use IPv6 ?
One chicken and egg scenario. Fortunately, this has been mitigated a little lately by tunnel brokers that provide IPv6 connectivity over an IPv4 link. This helps get it into use, but not everyone can have an IPv4 address as an endpoint.
By the way, I use both IPv4 and v6 at home and have NO TROUBLE WHATSOEVER. Maybe thats because I know what I'm doing, but for me it just works. Firefox looks up host details for a website. Sees an IPv6 address. Sees I have a public IPv6 address. It makes the connection. No AAAA record? It uses IPv4 instead. Most IPv6-enabled applications work in the same way. Again, if you're having trouble ITS NOT IPV6S FAULT!
Oh, and something else that other people might want to know, if you get weird DNS issues or timeouts when you enable IPv6, thats because your router is programmed by monkeys. This is a well known issue where some routers mishandle the AAAA records for DNS and return "nonexistent domain" instead of passing the records on properly. The solution? Get a proper router or run your own DNS server. Its not hard. You can get simple free caching DNS servers for Windows that will sort this one out.
So, can we stop spreading FUD, myths and Unbelievable Bullshit(tm) about IPv6 ? You'll only slow down the take up of an otherwise perfectly acceptable protocol. And when we do run out of addresses, it'll be all of you going "oh shit! we should have done something about this!" as find bits of the internet are accessible to your IPv4 only connection.