[Errata Held for Document Update] RFC9000 (7374)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 29 May 2023 13:52 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 C7898C1516E0; Mon, 29 May 2023 06:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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 OCThlBRByrvT; Mon, 29 May 2023 06:52:03 -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 3AB1DC15154C; Mon, 29 May 2023 06:52:03 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id F0BF785293; Mon, 29 May 2023 06:52:02 -0700 (PDT)
To: ietf@bobbriscoe.net, jri.ietf@gmail.com, mt@lowentropy.net
Subject: [Errata Held for Document Update] RFC9000 (7374)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: zaheduzzaman.sarker@ericsson.com, iesg@ietf.org, quic@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230529135202.F0BF785293@rfcpa.amsl.com>
Date: Mon, 29 May 2023 06:52:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ysl-1OhvYmjD0fxiWT_mxRIJ-mA>
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 May 2023 13:52:06 -0000

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

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

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Bob Briscoe <ietf@bobbriscoe.net>
Date Reported: 2023-02-27
Held by: Zaheduzzaman Sarker (IESG)

Section: 13.4.1

Original Text
-------------
                                                               If an
   endpoint does not implement ECN support or does not have access to
   received ECN fields, it does not report ECN counts for packets it
   receives.

   Even if an endpoint does not set an ECT field in packets it sends,
   the endpoint MUST provide feedback about ECN markings it receives, if
   these are accessible.  

Corrected Text
--------------
                                                               If an
   endpoint does not have access to
   received ECN fields, it does not report ECN counts for packets it
   receives.

   Even if an endpoint does not set an ECT field in packets it sends,
   the endpoint MUST provide feedback about ECN markings it receives, if
   these are accessible.  

Notes
-----
In the second sentence, the only allowed exception to "MUST provide feedback about received ECN markings" is inaccessibility. The first sentence contradicts this by allowing two exceptions: inaccessibility and just "not implementing ECN support". 

If "not implementing ECN support" was really intended to be an allowed exception, the capitalized "MUST" would have been pointless.

Therefore it is proposed that the words "does not implement ECN support or " are deleted from the first paragraph.

NOTE : Based on discussion in https://mailarchive.ietf.org/arch/msg/quic/lsz4X-cZql71Ba56uQhNQz4NzGc/ , the error type is changed from technical to editorial.

--------------------------------------
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
Area                : Transport
Stream              : IETF
Verifying Party     : IESG