[Technical Errata Reported] RFC9114 (7780)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 24 January 2024 22:10 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 8D611C14F680 for <quic@ietfa.amsl.com>; Wed, 24 Jan 2024 14:10:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, 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=ham 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 33gNmDVpJ1Z1 for <quic@ietfa.amsl.com>; Wed, 24 Jan 2024 14:10:27 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 B4D45C14F61F for <quic@ietf.org>; Wed, 24 Jan 2024 14:10:27 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 90335E7C65; Wed, 24 Jan 2024 14:10:27 -0800 (PST)
To: mbishop@evequefou.be, martin.h.duke@gmail.com, zahed.sarker.ietf@gmail.com, matt.joras@gmail.com, lucas@lucaspardue.com
Subject: [Technical Errata Reported] RFC9114 (7780)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: lucas@lucaspardue.com, quic@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240124221027.90335E7C65@rfcpa.amsl.com>
Date: Wed, 24 Jan 2024 14:10:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Iq7SnUDFp4jJK5v7kqwVpwN06k4>
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: Wed, 24 Jan 2024 22:10:31 -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/eid7780 -------------------------------------- Type: Technical Reported by: Lucas Pardue <lucas@lucaspardue.com> Section: 7.2.6 Original Text ------------- The GOAWAY frame applies to the entire connection, not a specific stream. A client MUST treat a GOAWAY frame on a stream other than the control stream as a connection error of type H3_FRAME_UNEXPECTED. Corrected Text -------------- The GOAWAY frame applies to the entire connection, not a specific stream. An endpoint MUST treat a GOAWAY frame on a stream other than the control stream as a connection error of type H3_FRAME_UNEXPECTED. Notes ----- HTTP/3 originally only supported GOAWAY from server to client. In this PR we added the ability to also send GOAWAY from client to server https://github.com/quicwg/base-drafts/pull/3129/files. Unfortunately we didn't update the highlighted text to cover the situation where a server receives a GOAWAY on a different stream. FWIW the implementation I am responsible for already applies the rule to request streams. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will 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
- [Technical Errata Reported] RFC9114 (7780) RFC Errata System