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
MikeBishop
commented
2 years ago
This is a change in the RFC Editor diff that I don't think works; pulling out for separate discussion.
Original:
Proposed but incorrect:
The intended reading is: For...
...the maximum table capacity is 0.