World IPv6 Day On June 8 133
dkd903 writes "On June 8, 2011, around 300 websites will test the IPv6 readiness of the internet. The participating websites includes Google, Facebook, Yahoo and Bing. In preparation for the day, Google is notifying users to test if they are ready."
Re:Where is the Google test? (Score:5, Informative)
Try here. [test-ipv6.com]
Or, for more info on test day, Try here. [test-ipv6.com]
Re:Where is the Google test? (Score:5, Informative)
Safari, for example, had a bug until recently that caused page loads to fail if the site has an IPv6 address but the client doesn't have connectivity. In addition, there are a bunch of autoconfigured tunnel technologies that can cause problems. See, for example, APNIC's chief scientist's report on Teredo: http://www.potaroo.net/ispcol/2011-04/teredo.html [potaroo.net]
Re:What services will be online? (Score:4, Informative)
Re:Where is the Google test? (Score:5, Informative)
Re:My ISP doesn't offer IPv6 (Score:4, Informative)
The test is aimed squarely at you.
What stops the large content providers from serving over IPv6 right now today is a level of brokenness that affects a fraction of a percent of users. These are computers or networks which are nominally IPv4 only, but have some misconfigured IPv6 setup that is actively causing problems connecting to sites. The proportion of users is tiny, but if you're facebook, that's still a lot of users. Wednesday next will expose these problems on a temporary, scheduled basis.
If you run IT support for an organisation, it would be wise to see the results of, say, the RIPE IPv6 eye chart [ripe.net] on your client machines.
Re:Where is the Google test? (Score:4, Informative)
Most clients will fall back to v4 if v6 fails. The problem comes when the v6 connection attempt gets no reply at all (e.g. due to routing problems, firewalls, links that are down but the system doesn't know they are down or some combination), the client will then wait for it to time out before falling back which if the client uses standard OS timeouts can take an excruciatingly long time.
The cause of the packets not getting any reply at all may be local to the client but it could also quite possiblly be in an ISP nework somewhere. Remember the internet (whether v4 or v6) is just a (very large) set of network providers cooperating (through ICANN and the organisations it delegates to) to use non-conflicting addressing and to foward traffic to each other. Even on the better maintained v4 side it's not that unusual for two ISPs to be unable to exchange traffic for a while due to some screwup.