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

Stateless reset too #2968

Merged
merged 5 commits into from Oct 15, 2019
Merged

Stateless reset too #2968

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
cf6dc59
Better narrow stateless reset token validity
martinthomson Aug 15, 2019
dcd76b4
Only active connection IDs are relevant
martinthomson Aug 15, 2019
57bb6b8
Forbid use of duplicate stateless reset tokens
martinthomson Aug 15, 2019
5c3d403
Grammar
martinthomson Aug 15, 2019
2357b2c
wrap
martinthomson Aug 15, 2019
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
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2355,10 +2355,10 @@ CONNECTION_CLOSE frame if it has sufficient state to do so.
To support this process, a token is sent by endpoints. The token is carried in
the Stateless Reset Token field of a NEW_CONNECTION_ID frame. Servers can also
specify 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 don't have
confidentiality protection. These tokens are protected by encryption, so only
client and server know their value. Tokens are invalidated when their
applies to the connection ID that it selected during the handshake; clients
cannot use this transport parameter because their transport parameters don't
have confidentiality protection. These tokens 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