The following errata report has been rejected for RFC9114,
"HTTP/3".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7238

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Jaikiran Pai <jai.forums2...@gmail.com>
Date Reported: 2022-11-04
Rejected by: Francesca Palombini (IESG)

Section: 4.2.2

Original Text
-------------
Because this limit is applied separately by each implementation that
processes the message, messages below this limit are not guaranteed
to be accepted.


Corrected Text
--------------
Because this limit is applied separately by each implementation that
processes the message, messages above this limit are not guaranteed
to be accepted.


Notes
-----
The section 4.2.2 specifies header size constraints and notes that 
implementations can send a SETTINGS frame with a 
SETTINGS_MAX_FIELD_SECTION_SIZE identifier to set a limit on the maximum size 
of the message header. Since this a maximum size, the sentence that states that 
intermediaries aren't guaranteed to accept a message below this limit seems odd 
and I think it should instead say "above this limit".
 --VERIFIER NOTES-- 
The current RFC text is correct. The problem that is being described is where 
1) a client sends a message smaller than MAX_FIELD_SECTION_SIZE and might 
expect that to work but 2) the server is an intermediary that needs to forward 
the message onto another server that, for example,  has a smaller value for 
MAX_FIELD_SECTION_SIZE preventing this.

Any further clarification to this text, if any is needed, should be made via an 
update to this document. We encourage you to participate in suggesting 
improvement/clarifications by opening an issue on the spec issue tracker 
(https://github.com/quicwg) or in the mailing list: <quic@ietf.org>.

See https://mailarchive.ietf.org/arch/msg/quic/8E8kNJe1VGKEjotTl3IT2oZoGGo/

--------------------------------------
RFC9114 (draft-ietf-quic-http-34)
--------------------------------------
Title               : HTTP/3
Publication Date    : June 2022
Author(s)           : M. Bishop, Ed.
Category            : PROPOSED STANDARD
Source              : QUIC
Stream              : IETF
Verifying Party     : IESG

Reply via email to