search

tfpauly / draft-happy-eyeballs-v3

Other
9 stars 7 forks source link

Inventory of HE-like Uses #51

Open boucadair opened 3 months ago

boucadair commented 3 months ago

Some HE variants were specified out there as well. It would be great to inventory those and see if they can be naturally addressed by HEv3.

See an example of such uses at https://datatracker.ietf.org/doc/html/rfc9132#name-happy-eyeballs-for-dots-sig. That variant was specified with the following in mind:

Such a procedure is needed to avoid experiencing long connection delays. For example, if an IPv4 path to a DOTS server is functional, but the DOTS server's IPv6 path is nonfunctional, a dual-stack DOTS client may experience a significant connection delay compared to an IPv4-only DOTS client in the same network conditions. The other problem is that if a middlebox between the DOTS client and DOTS server is configured to block UDP traffic, the DOTS client will fail to establish a DTLS association with the DOTS server; consequently, it will have to fall back to TLS over TCP, thereby incurring significant connection delays.

Please refer to the RFC for more details, including deviations vs RFC8305.

I suggest to a add a charter item to inventory such uses.

nicorusti commented 3 months ago

I agree that making an inventory would be a good exercise.

An HE-like approach could be useful as a transition mechanism to multipath / path aware networking architectures. I believe someone of us (SCION enthusiasts) might have done some experimental work on this, let me try to find out