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

Allow use of token after client address change #3308

Merged
merged 1 commit into from
Feb 12, 2020
Merged

Allow use of token after client address change #3308

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1752,11 +1752,7 @@ connection attempts.

A client SHOULD NOT reuse a NEW_TOKEN token for different connection attempts.
Reusing a token allows connections to be linked by entities on the network path;
see {{migration-linkability}}. A client MUST NOT reuse a token if it believes
that its point of network attachment has changed since the token was last used;
that is, if there is a change in its local IP address or network interface. A
client needs to start the connection process over if there is any change in its
local address prior to completing the handshake.
see {{migration-linkability}}.

Clients might receive multiple tokens on a single connection. Aside from
preventing linkability, any token can be used in any connection attempt.
Expand Down