Re: [quicwg/base-drafts] Binding settings into session tickets (#2790)

[Nick Harper <[e-mail]>]

There are a few more options here:

* When sending SETTINGS, send all values, not just the ones changed from the previous connection (i.e. don't send a delta). Once the client receives that SETTINGS frame, both sides agree on that state for the rest of the connection, but they might not agree on the SETTINGS for early data (it could be the default settings, or it could be the SETTINGS from any previous connection).
* Use the default settings for early data. Both peers will always agree on the settings state and there aren't any ordering concerns between SETTINGS and NST. However, this prevents using anything that depends on SETTINGS in early data, e.g. QPACK or future extensions. (Unless QPACK or a future extension defines some way to remember a value for early data on the next connection.)

-- 
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/issues/2790#issuecomment-517466065