[Technical Errata Reported] RFC9114 (7238)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 04 November 2022 09:49 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A51C15257E for <quic@ietfa.amsl.com>; Fri, 4 Nov 2022 02:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TA2_gsQAijl for <quic@ietfa.amsl.com>; Fri, 4 Nov 2022 02:49:14 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4907FC152709 for <quic@ietf.org>; Fri, 4 Nov 2022 02:49:14 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0E3C755F68; Fri, 4 Nov 2022 02:49:14 -0700 (PDT)
To: mbishop@evequefou.be, martin.h.duke@gmail.com, Zaheduzzaman.Sarker@ericsson.com, matt.joras@gmail.com, lucaspardue.24.7@gmail.com
Subject: [Technical Errata Reported] RFC9114 (7238)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: jai.forums2013@gmail.com, quic@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20221104094914.0E3C755F68@rfcpa.amsl.com>
Date: Fri, 04 Nov 2022 02:49:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/U_SQsmbxRzzP6mL5TYne21sbbYM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2022 09:49:18 -0000

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

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

--------------------------------------
Type: Technical
Reported by: Jaikiran Pai <jai.forums2013@gmail.com>

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".

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

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