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

Clarify that stateless_reset_token is not mandatory #2548

Closed
wants to merge 1 commit into from
Closed

Clarify that stateless_reset_token is not mandatory #2548

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2293,7 +2293,7 @@ connection error MUST use a 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 NEW_CONNECTION_ID frame sent by either peer, and servers can specify the
the NEW_CONNECTION_ID frame sent by either peer, and servers MAY specify the
stateless_reset_token transport parameter during the handshake (clients cannot
because their transport parameters don't have confidentiality protection). This
value is protected by encryption, so only client and server know this value.
Expand Down Expand Up @@ -4003,7 +4003,7 @@ stateless_reset_token (0x0002):

: A stateless reset token is used in verifying a stateless reset, see
{{stateless-reset}}. This parameter is a sequence of 16 bytes. This
transport parameter is only sent by a server.
transport parameter is only sent by a server (but it's not mandatory).

max_packet_size (0x0003):

Expand Down