Finger pointing [was: Yahoo and IPv6]

2011-05-09 Thread Patrick W. Gilmore
On May 9, 2011, at 4:26 PM, Jeff Wheeler wrote:
> On Mon, May 9, 2011 at 3:58 PM, Doug Barton  wrote:
>> I do agree with you that pointing fingers at this stage is really not
>> helpful. I continue to maintain that being supportive of those content
>> networks that are willing to wade in is the right answer.

[...]

> This problem is, and always has been, on the access side.  Point your
> fingers that way.

While I agree with Jeff, I agree with Doug more.  Unfortunately, 
finger-pointing will not fix the problem.  We have identified many of the 
problems, and hopefully June 8 will shine a very bright light on any that are 
left.  Let's work on fixing the problems, and let the historians figure out 
whose "fault" it was.

-- 
TTFN,
patrick

P.S. As an aside, and since the finger was pointed in my general direction, I'd 
just like to say chicken and egg problems always suck.  However, when the 
largest sites on the 'Net have enabled v6, yet are forced to whitelist or lose 
millions of dollars because the other end is broken, I don't see how any 
rational person can seriously call this the "content mafia's" fault.



On May 9, 2011, at 4:26 PM, Jeff Wheeler wrote:

> On Mon, May 9, 2011 at 3:58 PM, Doug Barton  wrote:
>> I do agree with you that pointing fingers at this stage is really not
>> helpful. I continue to maintain that being supportive of those content
>> networks that are willing to wade in is the right answer.
> 
> Frankly, I think the finger is simply pointing in the wrong direction.
> I have zero choices for native IPv6 at home, and I'm sure that is
> true for the majority of us.  SOHO CPE support barely exists because
> access networks haven't been asking for it.  Call centers are
> certainly not equipped to evaluate "traceroute tickets" or assist
> users in any practical way, which is why we see "disable IPv6 and try
> again" as the cookie-cutter answer to any problem when the end-user
> has IPv6.
> 
> The expectation that content providers should rush to publish 
> records by default (instead of white-listing, etc.) at a time when
> even motivated end-users can't get IPv6 without resorting to tunnels
> is ridiculous.  Let's be glad that these content providers have done
> all the necessary prep work, such as deploying appropriate network
> infrastructure and updating their software, so that they can choose to
> send  responses when they want to.
> 
> This problem is, and always has been, on the access side.  Point your
> fingers that way.
> 
> -- 
> Jeff S Wheeler 
> Sr Network Operator  /  Innovative Network Concepts
> 




Re: Finger pointing [was: Yahoo and IPv6]

2011-05-09 Thread Jeff Wheeler
On Mon, May 9, 2011 at 4:40 PM, Patrick W. Gilmore  wrote:
> Unfortunately, finger-pointing will not fix the problem.

Actually, finger-pointing is very helpful at this stage.  I was able
to change my local ISP's tune from "we have enough IPv4 addresses for
our customers, so we aren't going to support IPv6" (ever) to "we will
start employee beta testing soon."  It ultimately took the threat of
running an Op-Ed in the business section of the local paper to get
them to realize they can't continue with their plan to offer no IPv6
support at all.

With 800,000 SOHO CPE units deployed that have no IPv6 support and no
remote firmware upgrade option on the horizon, I can understand why
they hoped they could avoid ever supporting v6 -- it will cost them,
literally, a hundred million dollars to fix their CPE situation and
deploy native IPv6 if their CPE vendor can't provide a remote update.
This is also why tunneled solutions are receiving so much effort and
attention -- truck rolls and CPE replacement are huge expenses.

If we don't start pointing fingers at these access networks, they
won't "get it" until the pain of IPv4 depletion lands squarely on
content networks who may eventually be unable to get any IPv4
addresses for their services, or who may be forced to buy transit from
networks who have large, legacy IPv4 pools sitting around just to get
a provider allocation.

-- 
Jeff S Wheeler 
Sr Network Operator  /  Innovative Network Concepts