-
Notifications
You must be signed in to change notification settings - Fork 204
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
Talk more about multiple tokens #2962
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some suggestions, but looks good.
draft-ietf-quic-transport.md
Outdated
{{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 it migrates prior to completing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be preferable to avoid the word 'migrate' here, and reuse the preceding text: "if there is a change in its local IP address or network interface."?
draft-ietf-quic-transport.md
Outdated
the handshake. | ||
|
||
Clients might receive multiple tokens on a single connection. Aside from | ||
preventing linkability, any token can be used in connection attempt. Servers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
preventing linkability, any token can be used in connection attempt. Servers | |
preventing linkability, any token can be used in any connection attempt. Servers |
I think this is what you meant?
This addresses some questions about use of multiple tokens, as well as cleaning up the text adjacent in minor ways. Closes #2801.
53b8707
to
992fa67
Compare
This addresses some questions about use of multiple tokens, as well as
cleaning up the text adjacent in minor ways.
Closes #2801.