Acks for 0rtt only after Handshake Complete as in Quic-TLS 4.1.1 #3914
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
Align 2020-02-04
Remove HTTP_ prefix
Align july 15 2020
|
Close #3855 |
martinthomson
approved these changes
Jul 16, 2020
Co-authored-by: Martin Thomson <mt@lowentropy.net>
martinthomson
added
-transport
editorial
ianswett
added a commit
that referenced
this pull request
Jul 16, 2020
I noticed the 0-RTT specific text in #3914 and thought a general clarification would be better.
ianswett
approved these changes
Jul 16, 2020
janaiyengar
approved these changes
Sep 8, 2020
ianswett
approved these changes
Sep 8, 2020
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.
Specify that when the spec says that a "client only receives acknowledgments for its 0-RTT packets once the handshake
is complete", it means "as defined in the Handshake Complete section of {{QUIC-TLS}}.".