Re: [quicwg/base-drafts] Send complete SETTINGS (#2972)

[David Benjamin <[e-mail]>]

davidben commented on this pull request.



>  
 A server can remember the settings that it advertised, or store an
 integrity-protected copy of the values in the ticket and recover the information
 when accepting 0-RTT data. A server uses the HTTP/3 settings values in
-determining whether to accept 0-RTT data.
+determining whether to accept 0-RTT data.  If the server cannot determine that
+the settings remembered by a client are compatible with its current settings, it
+MUST NOT accept 0-RTT data.  (Remembered settings are compatible if a client
+complying with those settings would not violate the server's current settings.)

Sure, that's a plausible optimization. Although that's orthogonal to whether you believe in equality or a weaker comparison.

(Whether the optimization is worth it, I'm not sure. The benefit is slightly smaller tickets. The cost is you need to make sure the meaning of your version number is consistent, which is a hidden sharp edge to deployment.)

-- 
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/2972#discussion_r316477208