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

Jean Mahoney <jmahoney@amsl.com> Fri, 15 December 2023 17:05 UTC

Return-Path: <jmahoney@amsl.com>
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 C101BC14CEF9 for <rfc-interest@ietfa.amsl.com>; Fri, 15 Dec 2023 09:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 BbP6grykuFgF for <rfc-interest@ietfa.amsl.com>; Fri, 15 Dec 2023 09:05:29 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (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 518BFC14F5E4 for <rfc-interest@rfc-editor.org>; Fri, 15 Dec 2023 09:05:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 36748424B455; Fri, 15 Dec 2023 09:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4PydMrUHyGuo; Fri, 15 Dec 2023 09:05:29 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id F15DA424B426; Fri, 15 Dec 2023 09:05:28 -0800 (PST)
Message-ID: <33a43b17-3b75-4045-b6f5-1e9d9e906fea@amsl.com>
Date: Fri, 15 Dec 2023 11:05:28 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Carsten Bormann <cabo@tzi.org>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
References: <1336A3E8-BB12-45F1-80CE-415BFFE2A18F@akamai.com> <2e01b2f8-b330-45fe-8d10-747a0710237d@amsl.com> <34BF4554-BD06-42F6-ABD7-403FF94A9337@tzi.org>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <34BF4554-BD06-42F6-ABD7-403FF94A9337@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/tsmDx45UB0tZNwA_9LxOHYhLnEQ>
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 17:05:29 -0000


On 12/15/23 10:06 AM, Carsten Bormann wrote:
> 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?

[JM] Yes, when an RFC is obsoleted, its associated errata pages will 
contain a note and a link to the obsoleting RFC (e.g., "Note: This RFC 
has been obsoleted by RFC 9110" [1]). Updating RFCs are not noted 
currently, but we'll take a look at adding that info.

Best regards,
Jean

[1] https://www.rfc-editor.org/errata/eid1077


> 
> (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-
>