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

Tickets and tokens are not for communication #3820

Merged
merged 3 commits into from
Jul 14, 2020
Merged

Tickets and tokens are not for communication #3820

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2278a54
Tickets and tokens are not for communication
martinthomson Jul 3, 2020
bd96059
tokens and tickets are opaque
martinthomson Jul 6, 2020
8302a5f
Reword first part
martinthomson Jul 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1765,9 +1765,9 @@ Note:
: TLS session tickets and address validation tokens are used to carry QUIC
configuration information between connections. Specifically, to enable a
server to efficiently recover state that is used in connection establishment
and address validation. These MUST NOT be used to communicate application
semantics between endpoints. The potential for reuse of these tokens means
that they require stronger protections against replay.
and address validation. These have no application-level semantics; clients
MUST treat them as opaque values. The potential for reuse of these tokens
means that they require stronger protections against replay.

A server that accepts 0-RTT on a connection incurs a higher cost than accepting
a connection without 0-RTT. This includes higher processing and computation
Expand Down