-
Notifications
You must be signed in to change notification settings - Fork 117
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
kazuho
wants to merge
84
commits into
kazuho/path-migration
Choose a base branch
from
kazuho/multipath-05
base: kazuho/path-migration
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rded, as we have done
…ps h3 fuzzer of h2o
…ted" when multipath is used
…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
support ECN
…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)
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for multipath QUIC (draft-05).
Known limitations:
For readability, the base branch of this PR points to #554, but the plan is to merge the two at once.