[Editorial Errata Reported] RFC9000 (6811)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 06 January 2022 01:52 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 C80A63A1377 for <quic@ietfa.amsl.com>; Wed, 5 Jan 2022 17:52:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCiGpwUYT84z for <quic@ietfa.amsl.com>; Wed, 5 Jan 2022 17:51:56 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 183633A1374 for <quic@ietf.org>; Wed, 5 Jan 2022 17:51:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 3016AE43A2; Wed, 5 Jan 2022 17:51:55 -0800 (PST)
To: rfc-editor@rfc-editor.org
Subject: [Editorial Errata Reported] RFC9000 (6811)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: mt@lowentropy.net, jri.ietf@gmail.com, mt@lowentropy.net, quic@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220106015155.3016AE43A2@rfc-editor.org>
Date: Wed, 05 Jan 2022 17:51:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hz5AJNURWfPHChiTtIjr99A4raE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Jan 2022 01:52:01 -0000
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/eid6811 -------------------------------------- Type: Editorial Reported by: Martin Thomson <mt@lowentropy.net> Section: 5.1.1 Original Text ------------- The sequence number of the initial connection ID is 0. If the preferred_address transport parameter is sent, the sequence number of the supplied connection ID is 1. Additional connection IDs are communicated to the peer using NEW_CONNECTION_ID frames (Section 19.15). The sequence number on each newly issued connection ID MUST increase by 1. Corrected Text -------------- The sequence number of the initial connection ID is 0. If the preferred_address transport parameter is sent, the sequence number of the supplied connection ID is 1. The sequence number for NEW_CONNECTION_ID frames starts at 2 when the preferred_address transport parameter is sent and 1 otherwise. Additional connection IDs are communicated to the peer using NEW_CONNECTION_ID frames (Section 19.15). The sequence number on each newly issued connection ID MUST increase by 1. Notes ----- It is not sufficiently clear that the (implied) sequence number for the preferred_address transport parameter is taken from the sequence only when the transport parameter is present. The original text might be read to imply that the first NEW_CONNECTION_ID frame always starts with 2, though maybe only at a server. The proposed addition is much more explicit. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can 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 Area : Transport Stream : IETF Verifying Party : IESG
- [Editorial Errata Reported] RFC9000 (6811) RFC Errata System
- Re: [Editorial Errata Reported] RFC9000 (6811) Chris Smiley