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.

Sign up for GitHub

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

Jump to bottom

New transport parameters and 0-RTT #4165

Merged
merged 6 commits into from Sep 24, 2020
Merged

New transport parameters and 0-RTT #4165

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c1a8ef9
New transport parameters and 0-RTT
martinthomson Sep 24, 2020
c8f67ec
Tweaks
martinthomson Sep 24, 2020
ed2e7e7
Again!
martinthomson Sep 24, 2020
768d9c3
subsequent connections
martinthomson Sep 24, 2020
ba182a8
-definitions for
martinthomson Sep 24, 2020
b718a32
don't rely on context
martinthomson Sep 24, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 3 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1849,8 +1849,9 @@ some identifiers are reserved in order to exercise this requirement.
A client that does not understand a transport parameter can discard it and
attempt 0-RTT on subsequent connections. However, if the client adds support
for a discarded transport parameter, it risks violating the constraints that
the transport parameter establishes. New transport parameters can avoid this
problem by setting a default of the most conservative value.
the transport parameter establishes if it attempts 0-RTT. New transport
parameters can avoid this problem by setting a default of the most conservative
value.

New transport parameters can be registered according to the rules in
{{iana-transport-parameters}}.
Expand Down