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

Finesse relationship of resumption and 0-RTT #4723

Merged
merged 1 commit into from Jan 11, 2021
Merged

Finesse relationship of resumption and 0-RTT #4723

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Expand Up @@ -684,8 +684,8 @@ of type PROTOCOL_VIOLATION.

QUIC can use the session resumption feature of TLS 1.3. It does this by
carrying NewSessionTicket messages in CRYPTO frames after the handshake is
complete. Session resumption is the basis of 0-RTT, but can be used without
also enabling 0-RTT.
complete. Session resumption can be used to provide 0-RTT, and can also be
used when 0-RTT is disabled.

Endpoints that use session resumption might need to remember some information
about the current connection when creating a resumed connection. TLS requires
Expand Down