Subject: [quicwg/base-drafts] Auth48: Servers and non-0-RTT clients (Issue #4980)

From: Mike Bishop <[email-masked]>
Date: Mon, 04 Apr 2022 11:42:53 -0700

This is a change in the RFC Editor diff that I don't think works; pulling out for separate discussion.

Original:
> For HTTP/3 servers and HTTP/3 clients when 0-RTT is not attempted or is rejected, the maximum table capacity is 0 until the encoder processes a SETTINGS frame with a non-zero value of SETTINGS_QPACK_MAX_TABLE_CAPACITY.

Proposed but incorrect:
> When 0-RTT is not attempted or is rejected, for HTTP/3 servers and clients, the maximum table capacity is 0 until the encoder processes a SETTINGS frame with a non-zero value of SETTINGS_QPACK_MAX_TABLE_CAPACITY.

The intended reading is:  For...

- HTTP/3 servers (always, regardless of 0-RTT) and
- HTTP/3 clients when 0-RTT is not attempted or is rejected

...the maximum table capacity is 0.

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

Message ID: <quicwg/base-drafts/issues/[email-masked]>