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

put the QUIC layer in control of selecting the path (mode 3) #5

Closed
marten-seemann opened this issue Jul 23, 2023 · 0 comments · Fixed by #11
Closed

put the QUIC layer in control of selecting the path (mode 3) #5

marten-seemann opened this issue Jul 23, 2023 · 0 comments · Fixed by #11

Comments

@marten-seemann
Copy link
Owner

Currently the draft says:

Upon the completion of path validation, the QUIC stack passes the result (successful or failed) back to the ICE stack. The ICE stack then nominates an address pair. The client SHOULD then migrate the QUIC connection to this path in a timely manner.

As pointed out by @martinthomson on the list, we should put the QUIC layer in charge of selecting a path when using mode 3. A QUIC stack (multipath or not) will necessarily have some path selection / scheduling logic. We don't need to hand off the decision to ICE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant