[rsab] Heads-up: errata processing for RFC related documents
"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Wed, 13 March 2024 15:41 UTC
Return-Path: <ietf@kuehlewind.net>
X-Original-To: rsab@ietfa.amsl.com
Delivered-To: rsab@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E8D8C14F617; Wed, 13 Mar 2024 08:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kuehlewind.net
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 pJ2eRZqYgIVL; Wed, 13 Mar 2024 08:41:17 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [80.237.130.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50297C14EB17; Wed, 13 Mar 2024 08:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kuehlewind.net; s=he234030; h=To:Cc:Date:Message-Id:Subject:Mime-Version: Content-Type:From:From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc: MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=IJq/E0qSp+m6jNUGNf2CFVXHUKMma6hqUMZh1wQ22Is=; t=1710344450; x=1710776450; b=W6F0TfrkmIN3iMT9+yW7sgzjEwHaNs8qilKPn5aGgmzVgQ/KDLrh4jufF+/nF3AUTX5TF+E/GQ Oh6HZXzin8YRmD092u+0n0O7G+61asqCBTgz5HmWaJCPGkD+20z0Jqn3Jr09DovfXhdex+mF3LQPZ 2VejD5TWRlbzBUiFl4eTgER+dIiQrj3uN1IpsxIGV8dHwIhb/gEUb670mKixdgxd4QLCFm/wI2+Lf NaY/2ZWYMb8shdVhDxAhqAMZlmVFCXKpQ/K0po2GLdfRjq+qqQkU4Usxd0bzp7awSU9nCidj0SgLY yuQ+GsROJbGZ6KboFlirL7IXqMIUNG0woDUZg==;
Received: from dslb-002-207-003-144.002.207.pools.vodafone-ip.de ([2.207.3.144] helo=smtpclient.apple); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1rkQim-0006G6-CU; Wed, 13 Mar 2024 16:40:48 +0100
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EC696EBC-1729-4D70-9765-00CDE1311B9B"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Message-Id: <0CDA6033-7475-4DEF-9DA4-7AA3F13FE538@kuehlewind.net>
Date: Wed, 13 Mar 2024 16:40:37 +0100
Cc: Sandy Ginoza <sginoza@amsl.com>
To: IAB IAB <iab@iab.org>, RSAB@rfc-editor.org
X-Mailer: Apple Mail (2.3731.700.6)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1710344450;53498df7;
X-HE-SMSGID: 1rkQim-0006G6-CU
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/uI1hwzp9HO8fN8AhzWpXH47Kheg>
Subject: [rsab] Heads-up: errata processing for RFC related documents
X-BeenThere: rsab@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Approval Board \(RSAB\)" <rsab.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rsab>, <mailto:rsab-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rsab/>
List-Post: <mailto:rsab@rfc-editor.org>
List-Help: <mailto:rsab-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rsab>, <mailto:rsab-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2024 15:41:21 -0000
Hi all, I’m discussing with the RPC the best process to handle future errata for RFC Editor related documents. These documents have been published on the IAB stream, and therefore the IAB (chair) is currently responsible for the errata processing. However, future versions of these RFCs would/will be published in the editorial stream and the RSAB (chair) will then be responsible for errata process for these. I suggest and still discussing some details with the RPC (Sandy in cc) that the IAB makes an official decision to hand the errata processing for these current IAB documents to the RSAB and note that officially down in the minutes of the next formal business meeting (on Sunday). In preparation for this, here is the current list of RFCs that are under consideration: RFC 5620 <https://www.rfc-editor.org/info/rfc5620> RFC Editor Model (Version 1) RFC 7669 <https://www.rfc-editor.org/info/rfc7669> Assigning Digital Object Identifiers to RFCs RFC 8728 <https://www.rfc-editor.org/info/rfc8728> RFC Editor Model (Version 2) RFC 9280 <https://www.rfc-editor.org/info/rfc9280> RFC Editor Model (Version 3) RFC 8729 <https://www.rfc-editor.org/info/rfc8729> The RFC Series and RFC Editor RFC 6949 <https://www.rfc-editor.org/info/rfc6949> RFC Series Format Requirements and Future Development RFC 7749 <https://www.rfc-editor.org/info/rfc7749> The "xml2rfc" Version 2 Vocabulary RFC 7990 <https://www.rfc-editor.org/info/rfc7990> RFC Format Framework RFC 7991 <https://www.rfc-editor.org/info/rfc7991> The "xml2rfc" Version 3 Vocabulary RFC 7992 <https://www.rfc-editor.org/info/rfc7992> HTML Format for RFCs RFC 7993 <https://www.rfc-editor.org/info/rfc7993> Cascading Style Sheets (CSS) Requirements for RFCs RFC 7994 <https://www.rfc-editor.org/info/rfc7994> Requirements for Plain-Text RFCs RFC 7995 <https://www.rfc-editor.org/info/rfc7995> PDF Format for RFCs RFC 7996 <https://www.rfc-editor.org/info/rfc7996> SVG Drawings for RFCs: SVG 1.2 RFC RFC 7997 <https://www.rfc-editor.org/info/rfc7997> The Use of Non-ASCII Characters in RFCs RFC 7998 <https://www.rfc-editor.org/info/rfc7998> "xml2rfc" Version 3 Preparation Tool Description RFC 8153 <https://www.rfc-editor.org/info/rfc8153> Digital Preservation Considerations for the RFC Series RFC 7322 <https://www.rfc-editor.org/info/rfc7322> RFC Style Guide RFC 5741 <https://www.rfc-editor.org/info/rfc5741> RFC 7841 <https://www.rfc-editor.org/info/rfc7841> RFC Streams, Headers, and Boilerplates RFC 8700 <https://www.rfc-editor.org/info/rfc8700> Fifty Years of RFCs Mirja
- [rsab] Heads-up: errata processing for RFC relate… Mirja Kuehlewind (IETF)
- Re: [rsab] [IAB] Heads-up: errata processing for … Mirja Kuehlewind (IETF)
- Re: [rsab] [IAB] Heads-up: errata processing for … Alvaro Retana
- Re: [rsab] [IAB] Heads-up: errata processing for … Wes Hardaker
- Re: [rsab] [IAB] Heads-up: errata processing for … Alvaro Retana
- Re: [rsab] [IAB] Heads-up: errata processing for … Mirja Kuehlewind (IETF)
- Re: [rsab] [IAB] Heads-up: errata processing for … Mirja Kuehlewind (IETF)