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

describe how 0-RTT is accepted and rejected #2841

Merged
merged 16 commits into from Aug 16, 2019
Merged
Changes from 1 commit
Commits
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
2 changes: 1 addition & 1 deletion draft-ietf-quic-tls.md
Expand Up @@ -632,7 +632,7 @@ A server rejects 0-RTT by sending a ServerHello without the early_data
extension. A server will always reject 0-RTT if it sends a TLS
HelloRetryRequest. When rejecting 0-RTT, a server MUST NOT process any 0-RTT
packets, even if it is in possesion of the keys to do so. When 0-RTT was
rejected, a client MUST treat receipt of an acknowledgement for a 0-RTT packet
rejected, a client SHOULD treat receipt of an acknowledgement for a 0-RTT packet
as a connection error of type PROTOCOL_VIOLATION.

When 0-RTT is rejected, all connection characteristics that the client assumed
Expand Down