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

Define stateless reset token #4317

Merged
merged 3 commits into from Oct 30, 2020
Merged

Define stateless reset token #4317

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fea5481
Define stateless reset token
martinthomson Oct 29, 2020
818b6c4
Mike's suggestions
martinthomson Oct 29, 2020
5d6285f
polish
martinthomson Oct 30, 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
12 changes: 6 additions & 6 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2961,18 +2961,18 @@ A stateless reset is not appropriate for indicating errors in active
connections. An endpoint that wishes to communicate a fatal connection error
MUST use a CONNECTION_CLOSE frame if it is able.

To support this process, an endpoint can issue a stateless reset token, which
is a 16 byte value that is hard to guess. If that endpoint sends a stateless
reset, a UDP datagram that ends in the stateless reset token, the recipient
will immediately end the connection.
To support this process, an endpoint issues a stateless reset token, which is a
16 byte value that is hard to guess. If that endpoint sends a stateless reset,
a UDP datagram that ends in the stateless reset token, the recipient will
immediately end the connection.
martinthomson marked this conversation as resolved.
Show resolved Hide resolved

A stateless reset token is issued by including the value in the Stateless Reset
Token field of a NEW_CONNECTION_ID frame. Servers can also issue a
stateless_reset_token transport parameter during the handshake that applies to
the connection ID that it selected during the handshake; clients cannot use
this transport parameter because their transport parameters do not have
confidentiality protection. These tokens are protected by encryption, so only
client and server know their value. Tokens are invalidated when their
confidentiality protection. These exchanges are protected by encryption, so
only client and server know their value. Tokens are invalidated when their
associated connection ID is retired via a RETIRE_CONNECTION_ID frame
({{frame-retire-connection-id}}).

Expand Down