RFC Errata
RFC 9114, "HTTP/3", June 2022
Source of RFC: quic (wit)
Errata ID: 7238
Status: Rejected
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Jaikiran Pai
Date Reported: 2022-11-04
Rejected by: Francesca Palombini
Date Rejected: 2024-10-30
Section 4.2.2 says:
Because this limit is applied separately by each implementation that processes the message, messages below this limit are not guaranteed to be accepted.
It should say:
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/