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

add support for multipath (draft-05) #559

Open
wants to merge 84 commits into
base: kazuho/path-migration
Choose a base branch
from

Conversation

kazuho
Copy link
Member

@kazuho kazuho commented Sep 19, 2023

This pull request adds support for multipath QUIC (draft-05).

Known limitations:

  • PATH_STATUS and PATH_ABANDON are ignored.

For readability, the base branch of this PR points to #554, but the plan is to merge the two at once.

kazuho added 30 commits June 14, 2023 21:21
@jhatala
Copy link

jhatala commented Oct 11, 2023

(the draft in question)

kazuho added 23 commits October 12, 2023 16:35
…m_paths` is used in the anticipation of merging multipath #559
[examples-echo] immediate means now, not 1 second later
…er-for-control-frames

make certain MAX_DATA and MAX_STREAMS frames are sent
…omplete.

H2O opens the HTTP/3 control stream when the connection is created. As that
happens before the peer grants any stream credit, QUICLY_PENDING_FLOW_OTHERS_BITgets set, and that leads to `quicly_get_first_timeout` return zero whenever
there is space in CWND.

But because write keys for the application packet number space is unavailable,
`quicly_send` cannot make progress.

Hence the hot loop.

This PR fixes `quicly_get_first_timeout`. The function no longer returns `0`
(indicating now) when the write keys for the application packet number space is
available.
fix entering hot loop if app opens a stream before the handshake is complete (amends #551)
@funglee2k22
Copy link

Do we have a timeline to adopt multipath QUIC in quicly ?

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

Successfully merging this pull request may close these issues.

3 participants