Yahoo IPv6 Upgrade Could Shut Out 1M Users
alphadogg writes "Yahoo is forging ahead with a move to IPv6 on its main Web site by year-end despite worries that up to 1 million Internet users may be unable to access it initially. Yahoo's massive engineering effort to support IPv6 — the long-anticipated upgrade to the Internet's main communications protocol — could at first shut out potential www.yahoo.com users due to what the company and others call 'IPv6 brokenness.'"
Will Yahoo still have 1M users by year-end to shut out?
Once Yahoo! is only available over IPv6, the internet will have no choice but to upgrade!
From
IPv6 experts say some Internet users will experience slowdowns or have trouble connecting to IPv6-enabled Web sites because they have misconfigured or misbehaving network equipment
to
"IPv6 brokenness."
So I should blame the water company if I install my plumbing wrong?
Your hair look like poop, Bob! - Wanker.
That isn't what they're doing (yet). Although the headline/summary made it sound like they were shutting out IPv4 users, this is not the case. They will be supporting both simultaneously.
What that means is that if a website advertises itself as simultaneously IPv4/IPv6 compliant, and someone's computer/browser thinks they are IPv6 compliant but their attempts to connect via IPv6 don't make it through (ISP? router? modem? who knows), their connection times out and the site is unreachable.
The solution in this case would be to identify the node that doesn't support IPv6 (might be difficult) or force the system on the user-end to use IPv4 (shouldn't be that hard). It certainly shouldn't be the end of the world, and it shouldn't really even affect too many people. And it will be a push to at least support IPv6 (not necessarily require it) at every step of the path so that users whose computers are capable of IPv6 connections can actually connect successfully over it.
Yahoo mail has a nice tab-based interface so you can open multiple emails while writing a few more, which Gmail is missing. It's also hard to migrate 10 years' of emails to a new service (they make it hard, at least) - not to mention getting everyone to use your new email address.
It's not even a shutout from what I understand. The IPv6 request will timeout after a while and revert to IPv4, so while people will certainly experience slowdowns, I doubt anyone will be actually unable to access the site. Detect this and point people to resources to resolve the problem and things will take care of themselves. And by things taking care of themselves I mean that you will be asked to go fix the internet by your parents, grandparents, siblings, aunts, uncles, friends, friends-who-are-only-friends-when-there's-a-computer-problem, and your grandma's bridge partner who you once installed a printer for.
Honestly, if it weren't for the army of computer geeks fixing most of the IT problems for friends and family I think the whole thing would collapse overnight.
Is there some operating systems out there which still aren't compatible with IPv6, or is it a problem at the ISPs level?
yet another article that's skeptical of how ready IPv6 is. The amount of brokenness that is there is not very big. Of all the people that have the full Internet (that is IPv4 *and* IPv6) most will simply connect to any IPv6 website without issues.
And apart from the fact that yahoo seems to be a US only thing, and even there is not so relevant anymore, I applaud them doing IPv6, when they get to it. (and after Google, Comcast, Akamai and many others)
I wish we'd get over this "brokenness" story and simply deploy and then fix it for the 1% that has issues. Would be nice if it gets rolled out to the point of 20% traffic in 2011, the year we'll run out of available IPv4 addresses.
Maybe this can help?
Aside: Woah, I pasted something and it worked!
Yahoo still has a lot of good stuff. Mail and calendar work well, there is useful news and finance pages as well. I was playing around with their YUI stuff yesterday, and it is pretty cool and open source.
Sites should probably serve ipv6 from a separate colo to a separate domain name to work the kinks out first, e.g. yahoov6.com. After a testing period they could start moving the support over, assuming the results were good.
#6495ED - cornflower blue
Many people still use their instant messaging, but what I see use a LOT is the Yahoo Groups. It is a simple way for average joes to create private mailing lists. I know that at least 4 of the moms groups for creating kids playdates my wife has joined had their mail list/forum hosted on Yahoo Groups. There email seems fine too.
IIRC the problem isn't with computers that don't support IPv6. It's with networks where the computers and DNS software does support IPv6 but there's no IPv6 connectivity. In those cases a name query gets back AAAA records, the computer tries to connect via IPv6, and the connection doesn't go through because IPv6 traffic doesn't have a route off the local network. If your computers don't support IPv6 at all, the problem doesn't happen (the AAAA records never get used). If the DNS software (probably in your router) doesn't support IPv6, it won't do queries for AAAA records in the first place. Note also that at the other end (the DNS servers for the web site's domain) there should also be filtering in place: AAAA records shouldn't be being returned in queries that came in via IPv4. But not all sites do that filtering, so clients have to be prepared to get IPv6-only data back in IPv4 responses and filter it out.
They had their servers respond to both IPv4 and IPv6 on the same domain name for a day. Among one million visitors they only had 5 with a problem. 2 could be solved by rebooting the router and or the computer, 2 had unreleated problems with their internet, and one actually had triggered a bug in the OS.
http://www.heise.de/netze/meldung/IPv6-Tag-bei-heise-de-Erste-Ergebnisse-1081201.html
First, it's not really IPv6 brokenness so much as it is an issue with hosts that think they have IPv6 connectivity, but, really don't.
Second, in most cases, affected users will see long page load times, not complete inability to access the site.
The 0.05% number is probably pretty accurate. Several sites have used embedded tests to measure this and come to the same number. However, the good news is that a year ago, this was 0.1% and it is continuing to trend downward.
With IANA running out of IPv4 this month, it's not surprising that Yahoo is moving forward. It's disturbing that so many others appear not to be.
Yahoo Finance is much better than the competition. Yahoo Mail is still the market leader, just slightly ahead of Hotmail, possibly because they were one of the first. Flickr is quite popular as well.
Yahoo Sports highest trafficked sports site on the net
Yahoo Finance worlds better than Google or MSN
Yahoo Stores is a popular interface for web stores
Flickr, Delicious, etc
Yahoo! has been talking about this at conferences for a while, but I'm not sure they are using good data. Here's a lighting talk from NANOG about it:
http://www.nanog.org/meetings/nanog46/presentations/Tuesday/Igor_ipv6_recursive_light_N46.pdf
Page 2 has the crux of the issue, Yahoo! claims if you add AAAA records that 0.078% of the user base "breaks", that is they understand a AAAA enough to try IPv6, but they lack IPv6 connectivity to the destination.
There was a time this made sense. A lot of early IPv6 deployments were islands without complete connectivity. Additionally, up until about 18 months ago there was a serious lack of IPv6 interconnectivity between ISPs, they were still figuring out how to turn up peering, filter, and so on.
However, times change. ISP's are now fairly well interconnected, and getting a lot better every day. Almost no one turns up IPv6 as an island anymore. Interestingly, some of the original islands still exist, on purpose, as they are test labs or other non-production deployments. The people use them expect them to be broken in some ways, in some cases to test what the user experience is when various things break. Indeed, I suspect the number of islands is small, and constant, and thus an ever decreasing percentage of the IPv6 user base.
Another large issue with the numbers is that they are only measuring the difference between the status quo and one of the four outcomes. A user could have:
A) Broken IPv4, Broken IPv6.
B) Broken IPv4, Working IPv6.
C) Working IPv4, Broken IPv6.
D) Working IPv4, Working IPv6.
What Yahoo has done is measure the status quo (IPv4 only) to bullet point C.
However, there will be some folks in bullet B. These are folks who can't get to Yahoo! today at all, but would be able to if Yahoo! had AAAA's. Granted, it's probably smaller, but still is an offset. Basically they are trying to scare folks that 470k folks might not be able to access Yahoo with IPv6. However, 470k folks may already be unable to access it via IPv4, they just can't measure that right now because they never see the requests!
There is also the looming issue. As a we run out of IPv4 addresses (likely in late 2011) ISP's will basically be forced to turn up IPv6 only users. Even if you take Yahoo!'s numbers as correct, that 0.078% are broken, then all you would need is a larger percentage than that of the user base to be IPv6 ONLY and it makes more sense to have AAAA's and exclude them. Basically 1% deployment of IPv6 completely flips their argument if the goal is serving the largest number of folks.
My take, some folks inside Yahoo! collected some rather raw data early on in IPv6's life cycle. Folks from Marketing and such read too much into it, and went into a panic that some large number of users wouldn't be abel to get to Yahoo! This created a huge issue for the engineers trying to deploy IPv6, which they have been fighting ever since.
This is bullshit. Every single ISP I know that offers IPv6 service today delegates a prefix. All the ones I know that are preparing commercial IPv6 services will be delegating prefixes. Even the tethering you're going to get from your IPv6-capable mobile phone will delegate a /64 prefix. Most residential providers will delegate at least a /56 and the ones run by SMART PEOPLE will delegate a /48 to each subscriber.
There is no need for residential. mobile and small-office subscribers to use NAT for IPv6.
jhw
This has nothing to do with Yahoo. Those users won't be able to access any other IPv6 capable website either. Hopefully most of them will be fixed around the 8th of June, where large parts of the Internet will be unreachable for them that day.
I welcome a commitment to move ahead even if it means a few people will have to fix their Internet connection. Hopefully they have an ISP that can help them, and if not, they should probably find a different ISP.
After all the mess we will have if websites remain IPv4 only will be much worse than 0.05% of users losing access temporarily until they get a working Internet connection again.
Do you care about the security of your wireless mouse?