Yesterday's Windows update causes IPv4 to be default

[Doug Barton]

On 11/21/2012 11:18 AM, Phil Mayers wrote:
> On 11/21/2012 06:03 PM, Doug Barton wrote:
> 
>> I'm responding pseudo-randomly to Phil here but Nick and Lorenzo are 
>> making the same mistake. :)
> 
> You've read too much into my response, I fear.

Fair enough, and thank you for clarifying.

> In the context of your comment:
> 
> """
> Oh c'mon, that's just silly. The intermittent problems are almost
> certainly not the fault of the content end of the system, they are
> almost certainly on the user end, or somewhere in between.
> """
> 
> ...I was merely pointing out that, thus far, the most significant IPv6
> problems *we* have experienced have been *exactly* intermittent ones at
> the content end.
> 
> I don't assert that this is true universally, that our experience will
> remain so, or that any robustness solutions should be based on this
> anecdote. Merely that "almost certainly not at the content end" is not
> supported by *my* experience.

So I undoubtedly erred in generalizing from my own experience, which has
thrown a red herring into the mix.

My point more generally is that extrapolating from our own anecdotal
experiences at the point in time is an error, and it seems that at least
you and I are in agreement on that much.

Doug