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

fix description which token to use for Initial packets #2800

Merged
merged 1 commit into from Jun 19, 2019
Merged

fix description which token to use for Initial packets #2800

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
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1592,10 +1592,10 @@ The server uses the NEW_TOKEN frame {{frame-new-token}} to provide the client
with an address validation token that can be used to validate future
connections. The client includes this token in Initial packets to provide
address validation in a future connection. The client MUST include the token in
all Initial packets it sends, unless a Retry or NEW_TOKEN frame replaces the
token with a newer one. The client MUST NOT use the token provided in a Retry
for future connections. Servers MAY discard any Initial packet that does not
carry the expected token.
all Initial packets it sends, unless a Retry replaces the token with a newer
one. The client MUST NOT use the token provided in a Retry for future
connections. Servers MAY discard any Initial packet that does not carry the
expected token.

A token SHOULD be constructed for the server to easily distinguish it from
tokens that are sent in Retry packets as they are carried in the same field.
Expand Down