Hmm. let's say the results of the happy eyeballs was TCP over IPv4 (just like the figure 4) and the client cache the info.
After certain period of time, the client will do happy eyeball again because other better connections might be available . But, in this case, how the cached info will be used?
[TR] The cache expires after a specific time period. If the cache has not expired, the client uses the information from the cache. If cache has expired, the client performs happy eyeball again.
It seems that an implementation that doesn't cache the info at all and does happy eyeballs at every 10 hours won't be allowed in this draft.
[TR] No, but if the subsequent attempt is within few seconds after the first attempt of happy eyeball, it would trash the network. The endpoint may have to re-establish the (D)TLS session within few seconds for several reasons (e.g. TLS session got terminated, DOTS server rebooted NAT rebooted etc.).
Hi Tiru,
On Thu, Apr 4, 2019 at 10:46 PM Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@xxxxxxxxxx> wrote:
Thanks for the explanation. The logic makes sense to me.
I think it would be good to articulate this a bit more in the draft.
For example, the figure 4 example explains the probing period, but doesn't mention about the cache period..
Thanks,
--
Yoshi
