IETF Logo Mail Archive

Re: [rfc-i] Attaching comments to errata?

Carsten Bormann <cabo@tzi.org> Fri, 15 December 2023 16:06 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36BFBC14CEFF for <rfc-interest@ietfa.amsl.com>; Fri, 15 Dec 2023 08:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 0Eron30DmBzn for <rfc-interest@ietfa.amsl.com>; Fri, 15 Dec 2023 08:06:31 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (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 AC620C14F61F for <rfc-interest@rfc-editor.org>; Fri, 15 Dec 2023 08:06:30 -0800 (PST)
Received: from eduroam-0160.wlan.uni-bremen.de (eduroam-0160.wlan.uni-bremen.de [134.102.16.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4SsDc21DHSzDClf; Fri, 15 Dec 2023 17:06:26 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2e01b2f8-b330-45fe-8d10-747a0710237d@amsl.com>
Date: Fri, 15 Dec 2023 17:06:25 +0100
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
X-Mao-Original-Outgoing-Id: 724349185.739445-818482c4c61e45405c97bd5ee776457e
Content-Transfer-Encoding: quoted-printable
Message-Id: <34BF4554-BD06-42F6-ABD7-403FF94A9337@tzi.org>
References: <1336A3E8-BB12-45F1-80CE-415BFFE2A18F@akamai.com> <2e01b2f8-b330-45fe-8d10-747a0710237d@amsl.com>
To: Jean Mahoney <jmahoney@amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/jlxWzILR3KpN6QE-7qMfNA8n2_4>
Subject: Re: [rfc-i] Attaching comments to errata?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Dec 2023 16:06:35 -0000

Related question:

What is the normal procedure when errata reports that were classified “hold for document update” are addressed by a separate document that updates the document with the errata?  Will the updating document be findable from the (errata view of) the updated document?

(This is about to happen with RFC 8610 and draft-ietf-cbor-update-8610-grammar [1].)

Grüße, Carsten

[1]: https://www.ietf.org/archive/id/draft-ietf-cbor-update-8610-grammar-00.html#name-clarifications-and-changes-

v2.23.0 | Report a Bug | By Email