[Errata Verified] RFC9114 (7780)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 29 January 2024 09:24 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 C518DC14F5FD; Mon, 29 Jan 2024 01:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.358
X-Spam-Level:
X-Spam-Status: No, score=-2.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_LOW=-0.7, 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=unavailable 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 UFVp2KOQ6DsI; Mon, 29 Jan 2024 01:24:12 -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 A50A7C14F605; Mon, 29 Jan 2024 01:18:06 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 646EF3E8CF; Mon, 29 Jan 2024 01:18:06 -0800 (PST)
To: lucas@lucaspardue.com, mbishop@evequefou.be
Subject: [Errata Verified] RFC9114 (7780)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, quic@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240129091806.646EF3E8CF@rfcpa.amsl.com>
Date: Mon, 29 Jan 2024 01:18:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XYM1Hr-2ARlvM0K1dMEItiAwPdc>
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: Mon, 29 Jan 2024 09:24:16 -0000

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

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

--------------------------------------
Status: Verified
Type: Technical

Reported by: Lucas Pardue <lucas@lucaspardue.com>
Date Reported: 2024-01-24
Verified by: Francesca Palombini (IESG)

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.

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