On Mon, May 9, 2011 at 8:16 AM, Arie Vayner <ariev@vayner.net> wrote:
Actually, I have just noticed a slightly more disturbing thing on the Yahoo IPv6 help page...
I have IPv6 connectivity through a HE tunnel, and I can reach IPv6 services (the only issue is that my ISP's DNS is not IPv6 enabled), but I tried to run the "Start IPv6 Test" tool at http://help.yahoo.com/l/us/yahoo/ipv6/ and it says: "We detected an issue with your IPv6 configuration. On World IPv6 Day, you will have issues reaching Yahoo!, as well as your other favorite web sites. We recommend disabling IPv6<http://us.lrd.yahoo.com/_ylt=ArHGqIAYvt_4fpp3N3vLzmNRJ3tG/SIG=11vv8jc1f/**http%3A//help.yahoo.com/l/us/yahoo/ipv6/general/ipv6-09.html>, or seeking assistance in order to fix your system's IPv6 configuration through your ISP or computer manufacturer."
What disturbs me is the piece saying "We recommend disabling IPv6<http://us.lrd.yahoo.com/_ylt=ArHGqIAYvt_4fpp3N3vLzmNRJ3tG/SIG=11vv8jc1f/**http%3A//help.yahoo.com/l/us/yahoo/ipv6/general/ipv6-09.html> ", with a very easy link...
No IPv6 is better than broken* IPv6. *broken being defined as: you go to www.yahoo.com with your broken IPv6 connection (6to4?) and www.yahoo.com fails to load within your margin of acceptable latency, then you go to a competitor's web site. The point of IPv6 day is that we "shake out" the issues together as one community. If it works great, that is great and we can make solid decisions based on real world data on how to fix and move forward. As an operator of a soon to be production launched IPv6-only + NAT64 service, nobody is more eager for native IPv6 content than me. That said, this is the right path for the content guys to dip their toes in. ================================= T-Mobile USA IPv6 Beta http://bit.ly/9s0Ed3 =================================