IPv6 brokenness experiment, November results

[Dan Wing]

> -----Original Message-----
> From: ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de 
> [mailto:ipv6-ops-bounces+dwing=cisco.com at lists.cluenet.de] On 
> Behalf Of Erik Kline
> Sent: Tuesday, December 01, 2009 6:09 AM
> To: Chris Hills
> Cc: ipv6-ops at lists.cluenet.de
> Subject: Re: IPv6 brokenness experiment, November results
> 
> 2009/12/1 Chris Hills <chaz at chaz6.com>:
> > On 01/12/09 09:22, Tore Anderson wrote:
> >> Opera is still by far the biggest cause of breakage - 
> about nine out of
> >> ten clients that are unable to access the dualstack site 
> appears to be
> >> Opera users with (presumably) broken 6to4 or Teredo 
> connectivity.  Three
> >> weeks ago they told me that the issue was beeing looked 
> into, but no
> >> word yet on whether a fix is forthcoming or not.
> >
> > I recently updated Opera to 10.10-4742 on Linux x86 (qt4 
> shared) and it
> > now seems to prefer ipv4 when both ipv4 and ipv6 are 
> available for the
> > website, from a host with global unicast addresses.
> 
> Hmmm...somehow that doesn't quite seem like the right fix.  In a
> dualstacked but heavily v4-NAT'd world it would still prefer v4?

I agree the new Opera behavior is not desirable.

We wrote Happy Eyeballs to encourage quicker response to IPv6
breakage (such as dead tunnels) or to IPv4 breakage (such as
exhausted TCP ports), so that users are effectively unaware
of the browser preferring IPv4 over IPv6 (during the morning) 
or preferring IPv6 over IPv4 (during the afternoon),
http://tools.ietf.org/html/draft-wing-http-new-tech-00

-d