Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Multiple DNS Resolution Connection Attempts #1181

Open
nibanks opened this issue Jan 22, 2021 · 0 comments
Open

Support Multiple DNS Resolution Connection Attempts #1181

nibanks opened this issue Jan 22, 2021 · 0 comments
Labels
Area: Core Related to the shared, core protocol logic feature request A request for new functionality help wanted Extra attention is needed
Milestone

Comments

@nibanks
Copy link
Member

nibanks commented Jan 22, 2021

Describe the feature you'd like supported

Currently, when MsQuic is given just a ServerName to connect to, is resolves that with DNS and takes the first address returned. Instead, MsQuic should support (not sure if it should be default behavior though) the ability to do "happy eyeballs" to try connecting to multiple/all IP addresses that were available.

Proposed solution

Generally, happy eyeballs would require multiple independent connections, but with QUIC, we might be able to cheat a little and use the same connection, but just different "path" objects. We could send the same client initial packet on to each server address, save the state in the path object, and just continue the rest of the connection with whichever path gets a response first.

This likely needs some design and/or prototyping work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Core Related to the shared, core protocol logic feature request A request for new functionality help wanted Extra attention is needed
Projects
Status: No status
Status: Should be written
Development

No branches or pull requests

1 participant