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

Move stateless reset token to the end #842

Merged
merged 6 commits into from
Oct 12, 2017
Merged
Changes from 1 commit
Commits
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
12 changes: 6 additions & 6 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -1601,12 +1601,12 @@ CONNECTION_CLOSE or APPLICATION_CLOSE frame if it has sufficient state to do so.
#### Detecting a Stateless Reset

A client detects a potential stateless reset when a packet with a short header
either cannot be decrypted or is marked as a potential duplicate. The client
then performs a constant-time comparison of the last 16 octets of the packet
with the Stateless Reset Token provided by the server in its transport
parameters. If this comparison is successful, the client MUST discard all
connection state and not send any further packets on this connection. If the
comparison is unsuccessful, the packet can be discarded.
either cannot be decrypted or is marked as a duplicate packet. The client then
compares the last 16 octets of the packet with the Stateless Reset Token
provided by the server in its transport parameters. If these values are
identical, the client MUST discard all connection state and not send any further
packets on this connection. If the comparison fails, the packet can be
discarded.


#### Calculating a Stateless Reset Token
Expand Down