Re: [quicwg/base-drafts] QPACK: Clarify how maximum dynamic table capacity can be set (#2330)

[afrind <[e-mail]>]

afrind commented on this pull request.



> @@ -427,16 +427,20 @@ The encoder MUST not set a dynamic table capacity that exceeds this maximum, but
 it can choose to use a lower dynamic table capacity (see
 {{set-dynamic-capacity}}).
 
+For clients using 0-RTT data in HTTP/3, the maximum table capacity is the
+remembered value of the setting. If the remembered value is not present or is 0,
+the server MAY set it to a non-zero value in its SETTINGS frame. If the

I was thinking of a case where the client was attempting 0-RTT from a session which never set SETTINGS_QPACK_MAX_TABLE_CAPACITY (leveraging the default, which is 0), rather than a case where the server had sent one but can't remember.

The 'MAY' refers to when 0-RTT is resumed using 0 or None (implying 0, the default), where the 'MUST treat as error' refers to when 0-RTT is resumed with non-zero.  

But if I confused both of you, then the text needs work. 

> For clients using 0-RTT data in HTTP/3, the server's maximum table capacity is the
remembered value of the setting, or 0 if the setting was not previously sent.  When the client's 0-RTT value of the setting is 0, the server MAY...

?

-- 
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/2330#discussion_r251666497