Re: [quicwg/base-drafts] Clean up text on Maximum Table Size. (#2115)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> -requests or responses are first permitted to be sent. For clients using 0-RTT
-data in HTTP/3, the table size is the remembered value of the setting, even if
-the server later specifies a larger maximum in its SETTINGS frame.  For HTTP/3
-servers and HTTP/3 clients when 0-RTT is not attempted or is rejected, the
-initial maximum table size is the value of the setting in the peer's SETTINGS
-frame.
+The initial dynamic table capacity is the value of the maximum dynamic table
+capacity when HTTP requests or responses are first permitted to be sent.  For
+HTTP/3 servers and HTTP/3 clients when 0-RTT is not attempted or is rejected,
+the initial maximum table capacity is zero.  For clients using 0-RTT data in
+HTTP/3, the initial table capacity is the remembered value of the setting, even
+if the server later specifies a different maximum dynamic table capacity in its
+SETTINGS frame.  It is not an error for the SETTINGS frame to contain a
+SETTINGS_MAXIMUM_DYNAMIC_TABLE_CAPACITY value lower than the initial table
+capacity on a 0-RTT connection; the maximum dynamic table capacity only limits
+subsequent table capacity changes.  However, if an endpoint receives a

Yes, just forbid reductions.  It's simpler.

I don't like this because I think that it means that I have to send a capacity update instruction, which I don't currently, but that's my problem.

-- 
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/2115#discussion_r242767981