[Errata Verified] RFC9312 (7996)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 21 June 2024 16:19 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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A5FAC14F680; Fri, 21 Jun 2024 09:19:42 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 624EC7FA79; Fri, 21 Jun 2024 09:19:41 -0700 (PDT)
To: no@no.no, mirja.kuehlewind@ericsson.com, ietf@trammell.ch
Subject: [Errata Verified] RFC9312 (7996)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240621161941.624EC7FA79@rfcpa.rfc-editor.org>
Date: Fri, 21 Jun 2024 09:19:41 -0700
Message-ID-Hash: ZEL7NJTX5BTAEHAC3AVCCUDBXU5IOICS
X-Message-ID-Hash: ZEL7NJTX5BTAEHAC3AVCCUDBXU5IOICS
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: rfc-ed@rfc-editor.org, iesg@ietf.org, quic@ietf.org, iana@iana.org, rfc-editor@rfc-editor.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/bAlKKMySEwT2uoR4P5TZFSCtujU>
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 verified for RFC9312,
"Manageability of the QUIC Transport Protocol". 

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

--------------------------------------
Status: Verified
Type: Editorial

Reported by: No No <no@no.no>
Date Reported: 2024-06-20
Verified by: RFC Editor  

Section: 2.1 and 8

Original Text
-------------
Operators should expect to observe packets with other version numbers 
as a result of various Internet experiments, future standards, and 
greasing [RFC7801].

...

[RFC7801]
Dolmatov, V., Ed., "GOST R 34.12-2015: Block Cipher "Kuznyechik"", 
RFC 7801, DOI 10.17487/RFC7801, March 2016, 
<https://www.rfc-editor.org/info/rfc7801>

Corrected Text
--------------
Operators should expect to observe packets with other version numbers 
as a result of various Internet experiments, future standards, and 
greasing [RFC8701].

...

[RFC 8701]
Benjamin, D.,"Applying Generate Random Extensions And Sustain 
Extensibility (GREASE) to TLS Extensibility", RFC 8701, 
DOI 10.17487/RFC8701, January 2020, 
<https://www.rfc-editor.org/info/rfc8701>.

Notes
-----
Typo, should be RFC8701 instead of RFC7801

--------------------------------------
RFC9312 (draft-ietf-quic-manageability-18)
--------------------------------------
Title               : Manageability of the QUIC Transport Protocol
Publication Date    : September 2022
Author(s)           : M. Kühlewind, B. Trammell
Category            : INFORMATIONAL
Source              : QUIC
Stream              : IETF