nanog mailing list archives
RE: Yahoo and IPv6
From: "Tony Hain" <alh-ietf () tndh net>
Date: Mon, 9 May 2011 12:40:50 -0700
-----Original Message----- From: Doug Barton [mailto:dougb () dougbarton us] Sent: Monday, May 09, 2011 12:11 PM To: Jared Mauch Cc: nanog () nanog org; Arie Vayner Subject: Re: Yahoo and IPv6 On 05/09/2011 10:27, Jared Mauch wrote:I do feel the bar that Yahoo is setting is too high. There are a lotof network elements that are broken, either DNS servers, home 'gateway/nat' devices, or other elements in the delegation chain. Publicly held corporations are responsible to their shareholders to get eyeballs on their content. *That* is their job, not promoting cool new network tech. When you have millions of users hitting your site every day losing 1/2000 is a large chunk of revenue. The fact that the big players are doing world IPv6 day at all should be celebrated, promoted, and we should all be ready to take to heart the lessons learned from it. The content providers are not to be blamed for the giant mess that IPv6 deployment has become. If 6to4 and Teredo had never happened, in all likelihood we wouldn't be in this situation today.
Which situation ??? The one where the content can demonstrate how broken the networks really are? Or the one where the content sites are exposed for their lack of prior planning? The entire point of those technologies you are complaining about was to break the stalemate between content and network, because both sides will always wait and blame the other. The fact that the content side chose to wait until the last possible minute to start is where the approach falls down. Expecting magic to cover for lack of proactive effort 5-10 years ago is asking a bit much, even for the content mafia. In any case, the content side can mitigate all of the latency related issues they complain about in 6to4 by putting in a local 6to4 router and publishing the corresponding 2002:: prefix based address in DNS for their content. They choose to hold their breath and turn blue, blaming the network for the lack of 5-9's access to the eyeballs when they hold at least part of a solution in their own hands. We are about the witness the most expensive, complex, blame-fest of a transition that one could have imagined 10 years ago. This is simply due to the lack of up-front effort that both sides have demonstrated in getting to this point. Now that time has expired, all that is left to do is sit back and watch the fireworks. Tony
-- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Current thread:
- Re: Yahoo and IPv6, (continued)
- Re: Yahoo and IPv6 TJ (May 09)
- Re: Yahoo and IPv6 Arie Vayner (May 09)
- Re: Yahoo and IPv6 Cameron Byrne (May 09)
- Re: Yahoo and IPv6 Owen DeLong (May 09)
- Re: Yahoo and IPv6 Brandon Ross (May 09)
- RE: Yahoo and IPv6 Voll, Toivo (May 31)
- Re: Yahoo and IPv6 Valdis . Kletnieks (May 09)
- Re: Yahoo and IPv6 Kevin Oberman (May 09)
- Re: Yahoo and IPv6 Jared Mauch (May 09)
- Re: Yahoo and IPv6 Doug Barton (May 09)
- RE: Yahoo and IPv6 Tony Hain (May 09)
- Re: Yahoo and IPv6 Doug Barton (May 09)
- Re: Yahoo and IPv6 Jeff Wheeler (May 09)
- Finger pointing [was: Yahoo and IPv6] Patrick W. Gilmore (May 09)
- Re: Finger pointing [was: Yahoo and IPv6] Jeff Wheeler (May 09)
- Re: Yahoo and IPv6 Jared Mauch (May 09)
- Re: Yahoo and IPv6 Jeff Wheeler (May 09)
- Re: Yahoo and IPv6 Joel Maslak (May 09)
- Re: Yahoo and IPv6 Jeff Wheeler (May 09)
- Re: Yahoo and IPv6 Robert Drake (May 14)
- Re: Yahoo and IPv6 Cameron Byrne (May 09)
- Re: Yahoo and IPv6 Owen DeLong (May 09)