http://help.yahoo.com/l/us/yahoo/ipv6/general/ipv6-05.html
"Will IPv6 become a permanent change on June 8, 2011?
No. World IPv6 day is a 24-hour trial period in which we will publish our content on both the IPv4 and IPv6 servers. Yahoo! is participating in order to help prepare our services (as well as your hardware) to help ensure a smooth transition for when the IPv4 addresses run out. "
Huh… I thought IPv4 addresses had run out already….
At IANA level and now for anyone in the AP region at least.
World IPv6 Launch
"Will IPv6 become a permanent change on June 8, 2011?
No. World IPv6 day is a 24-hour trial period in which we will publish our content on both the IPv4 and IPv6 servers. Yahoo! is
participating in order to help prepare our services (as well as your hardware) to help ensure a smooth transition for when the
IPv4 addresses run out. "
Huh� I thought IPv4 addresses had run out already�.
At IANA level and now for anyone in the AP region at least.
Unfortunately, I suspect many organizations will be following that approach.
I hope that some will instead see this as a great opportunity for the last
step in making their public services IPv6 reachable *... and that they also
start/continue/complete taking IPv6 within their internal networks as well.*
Unfortunately, I suspect many organizations will be following that approach.
I hope that some will instead see this as a great opportunity for the last
step in making their public services IPv6 reachable *... and that they also
start/continue/complete taking IPv6 within their internal networks as well.*
my ipv6 peering with yahoo came up like 8 months ago...
I don't think there's anything particularly unfortunate about what major
content providers are doing with ipv6, give them customers and they wil
support them.
> Unfortunately, I suspect many organizations will be following that
approach.
>
> I hope that some will instead see this as a great opportunity for the
last
> step in making their public services IPv6 reachable *... and that they
also
> start/continue/complete taking IPv6 within their internal networks as
well.*
my ipv6 peering with yahoo came up like 8 months ago...
Sure, but peering is not the same as publicly/universally reachable
services. I hope that World IPv6 Day raises enough awareness, and yields
enough success stories, that we make some noticeable progress in the near
future.
I don't think there's anything particularly unfortunate about what major
content providers are doing with ipv6, give them customers and they wil
support them.
It is unfortunate (to me), because content providers being accessible is an
important step in breaking this chicken-egg scenario.
We need the service providers and content providers to make this "IPv6
thing" usable/relevant - and (just IMHO) the sooner the better.
*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.
Even more disturbing than that is that when I run a test from here it says that I have broken v6. But I don't have broken v6 and test-v6.com proves it with a 10/10. This Yahoo tool doesn't seem to even give a hint as to what it thinks is broken.
Can anyone from Yahoo shed some light on what this tool is doing and how to get it to tell us what it thinks is broken?
Looking at the Javascript that drives the test, it appears the *real* problem
is that they set a 3 second timeout on the download - which basically means
that if you have to retransmit either the DNS query or the TCP SYN, you're
dead as far as the test is concerned.
I believe the problem Yahoo is talking about in regards to "broken" IPv6 networks. It really comes down to your network would break for 0.078% of the people trying to reach their site via IPv6. Broken in this case means;
...."the user has a broken home gateway, or a broken firewall or his Web browser has a timeout that's between 21 and 186 seconds, which we consider to be broken. That's a lot of breakage, and that is a very big barrier for content providers to support IPv6."
Actually, I have just noticed a slightly more disturbing thing on the Yahoo
IPv6 help page...
Not speaking in any official capacity, but .. thanks.
The location that's affecting the results is pending removal from DNS;
and ASAP we hope to have the name moved to the geo-LB that suppors v6,
instead of the round robin it is today.
IANA is out of IPv4.
APNIC is into their austerity policy which covers their entire last /8.
RIPE-NCC is probably next and I expect they will likely run out next month.
I suspect ARIN's free pool will probably last until October-ish, give or take.
LACNIC and AfriNIC are kind of wildcards. If consumption remains within their
regions, they probably have addresses for some time.
If organizations from the other regions start pillaging their address space, it
could evaporate in weeks, depending on how they react.
It'd certainly be interesting to watch and see how many things that might be in the APNIC region are actually getting ARIN assignments over the next few weeks/months.
For production, yes. However, in terms of recommendations to prepare for
IPv6 day, uh, no... The better recommendation would be to explain the
exact issue detected and suggest ways for the user to resolve it.
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.
The *really* depressing part is that it says the same thing for me, on a *known*
working IPv6 network.
FWIW, it is happy with my connection and consistently reports positive results.
I'm running my own addresses through HE tunnels and tunnels
to Layer42.
The tunnels ride over Comcast and Raw Bandwidth DSL.
And then when I retry it a few minutes later, with a tcpdump running, it works.
And then another try says it failed, though tcpdump shows it seems to work.
For what it's worth, the attempted download file is:
% wget http://v6test.yahoo.com/eng/test/eye-test.png
--2011-05-09 11:44:39-- http://v6test.yahoo.com/eng/test/eye-test.png
Resolving v6test.yahoo.com... 2001:4998:f00d:1fe::2000, 2001:4998:f00d:1fe::2002, 2001:4998:f00d:1fe::2003, ...
Connecting to v6test.yahoo.com|2001:4998:f00d:1fe::2000|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [image/png]
Saving to: `eye-test.png.1'
Looking at the Javascript that drives the test, it appears the *real* problem
is that they set a 3 second timeout on the download - which basically means
that if you have to retransmit either the DNS query or the TCP SYN, you're
dead as far as the test is concerned.
Well, if you're having to retransmit those intermittently, then, it does seem you
have some level of brokenness with your network, no?
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 World IPv6 Launch 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.
The *really* depressing part is that it says the same thing for me, on a *known*
working IPv6 network.
FWIW, it is happy with my connection and consistently reports positive results.
I'm running my own addresses through HE tunnels and tunnels
to Layer42.
The tunnels ride over Comcast and Raw Bandwidth DSL.
Yup -- while not perfect, the Yahoo! testing has been working well for me.
Yahoo has to tread a very careful line between giving too little and too much information -- I have tried walking a few non-technical folk through troubleshooting their v6 connectivity by phone and it is really very hard to do, and that is interactively. Writing something that someone can download, print and then follow is nigh impossible. No matter how well this guide is written, a number of folk will manage to screw it up, and of *course* that will be Yahoo's fault....
Jason's page at http://test-ipv6.com/ gives way way more information (and the page at http://ipv6-test.com/ also gives some more), both of these pages are much too complex for the average user.
Well, if you're having to retransmit those intermittently, then, it does seem you
have some level of brokenness with your network, no?
So if I retransmit because *your* router is down, it's a brokenness in *my* network?
Given the following posting from earlier this morning:
The location that's affecting the results is pending removal from DNS;
and ASAP we hope to have the name moved to the geo-LB that suppors v6,
instead of the round robin it is today.
I feel pretty damned justified in saying it wasn't *my* network causing the retransmits.
(Oh - and kudos for the person quoted above for 'fessing up, and to the people
that tracked down the actual issue. That always sucks when the test rig itself
has issues. Glad to hear it will be fixed)
