[Editorial Errata Reported] RFC9000 (8106)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 17 September 2024 07:00 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06BE2C151985; Tue, 17 Sep 2024 00:00:51 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 433023B874; Tue, 17 Sep 2024 00:00:50 -0700 (PDT)
To: rfc-editor@rfc-editor.org
Subject: [Editorial Errata Reported] RFC9000 (8106)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240917070050.433023B874@rfcpa.rfc-editor.org>
Date: Tue, 17 Sep 2024 00:00:50 -0700
Message-ID-Hash: HXLO2C5U5VLFJ7YBMA4XQXVBN4YSYMYC
X-Message-ID-Hash: HXLO2C5U5VLFJ7YBMA4XQXVBN4YSYMYC
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-quic.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: lars@eggert.org, jri.ietf@gmail.com, mt@lowentropy.net, quic@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aL-OJjRgFTGG3ieNrl7q56xBKuk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>

The following errata report has been submitted for RFC9000,
"QUIC: A UDP-Based Multiplexed and Secure Transport".

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

--------------------------------------
Type: Editorial
Reported by: Lars Eggert <lars@eggert.org>

Section: 13.2.1

Original Text
-------------
   Every packet SHOULD be acknowledged at least once, and ack-eliciting
   packets MUST be acknowledged at least once within the maximum delay
   an endpoint communicated using the max_ack_delay transport parameter;


Corrected Text
--------------
   Every packet SHOULD be acknowledged at least once, and ack-eliciting
   packets MUST be acknowledged at least once. All acknowledgments MUST
   occur within the maximum delay an endpoint communicated using the
   max_ack_delay transport parameter;


Notes
-----
The original text can be read as if it were OK to only ACK once within the max_ack_delay, and not always.

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.

--------------------------------------
RFC9000 (draft-ietf-quic-transport-34)
--------------------------------------
Title               : QUIC: A UDP-Based Multiplexed and Secure Transport
Publication Date    : May 2021
Author(s)           : J. Iyengar, Ed., M. Thomson, Ed.
Category            : PROPOSED STANDARD
Source              : QUIC
Stream              : IETF
Verifying Party     : IESG