<p><br>
On Jun 12, 2012 4:38 PM, "Andrew Dickinson" <<a href="mailto:whydna@whydna.net">whydna@whydna.net</a>> wrote:<br>
><br>
> Is there any reason to have a delay at all (at least for TCP)?<br>
><br>
> Would it be unreasonable for a client implementation to simultaneously<br>
> send a SYN on both v4 and v6? It would then issue a RST for the<br>
> SYN-ACK that arrives last. I recognize that this may need to be done<br>
> at the application layer which probably makes it a no-go of a<br>
> generalized solution, but I suspect it could be incorporated into an<br>
> OS's TCP stack.<br>
><br>
> -A<br>
></p>
<p>As noted at the top of the thread, network access providers and content providers do not want a straight race, they want end to end v6 and they want to avoid cgn.</p>
<p>Apple's happy eyeballs implementation leads to too much ipv4 via nat444 and not enough ipv6 e2e.</p>
<p>Cgn does not introduce delay in most networks.</p>
<p>Thus, we need to explore options for meeting the content and network providers real business needs, not some theoretical users experience benefits afforded from a straight race where ipv4 is 5ms faster (cannot be perceived)</p>
<p>Fyi, this is really only a problem for apple products. The rest of the world prefers ipv6.</p>
<p>CB</p>
<p>> On Tue, Jun 12, 2012 at 3:50 PM, Daniel Roesen <<a href="mailto:dr@cluenet.de">dr@cluenet.de</a>> wrote:<br>
> > On Tue, Jun 12, 2012 at 05:21:05PM -0400, Erik Nygren wrote:<br>
> >> A "good" Happy Eyeballs implementation should compare IPv4 vs IPv6<br>
> >> TCP (HTTP) performance and availability with some preference towards<br>
> >> IPv6 (whether it is 30ms or 300ms).<br>
> ><br>
> > Unfortunately, Apple thinks different:<br>
> ><br>
> > <a href="http://www.ietf.org/mail-archive/web/v6ops/current/msg10080.html">http://www.ietf.org/mail-archive/web/v6ops/current/msg10080.html</a><br>
> ><br>
> > Best regards,<br>
> > Daniel<br>
> ><br>
> > --<br>
> > CLUE-RIPE -- Jabber: <a href="mailto:dr@cluenet.de">dr@cluenet.de</a> -- dr@IRCnet -- PGP: 0xA85C8AA0<br>
</p>