Re: [quicwg/base-drafts] Clarify the state a client stores with a token (#3150)

[Nick Harper <[e-mail]>]

nharper commented on this pull request.



> @@ -1746,7 +1747,8 @@ validate a client address.  Tokens are not integrated into the cryptographic
 handshake and so they are not authenticated.  For instance, a client might be
 able to reuse a token.  To avoid attacks that exploit this property, a server
 can limit its use of tokens to only the information needed to validate client
-addresses.
+addresses.  A server MUST NOT require the client to correlate any additional
+information with a token (e.g. a NewSessionTicket).

You're right that this isn't a testable "MUST NOT". I think the proposed language here is better suited with the language above describing a client's behavior.

Here I'm trying to provide some advice to server implementers that clients aren't going to keep track of which token came from where (or goes with which ticket), so if they expect that a token and ticket used on a new connection came from the same old connection, they're going to have a bad time.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3150#discussion_r338871141