Re: [v6ops] An Update to Happy Eyeballs

[Philip Homburg <[e-mail]>]

>Tommy Pauly and myself have written up what we've learned
>in the past few years maintaining and improving Apple's Happy Eyeballs stack,
>and submitted it as draft-pauly-v6ops-happy-eyeballs-update.

The draft says: Intended status: Standards Track

With that in mind I would prefer splitting the DNS and the connection
parts over two different drafts.

The reason is two fold:
1) The only API that we standardized (getaddrinfo) cannot support the required
   behavior. So an application would have to choose between using a standard
   API or implementing happy eyeballs.
2) In my experience, AAAA hardly ever times out. (I wanted to write 'fail',
   but failure, as in not returning the correct AAAA can be close to 1%. But
   as long as there is no delay, it doesn't matter for happy eyeballs).

I think setting up tcp connections in staggered fashion is highly useful. 
Writing code that gets triggered by DNS responses coming is not supported by
standard APIs and may make code needlessly complex. So we should not require
such behavior.