Re: [CFRG] Proposed CFRG process for handling errata

Russ Housley <housley@vigilsec.com> Thu, 24 December 2020 17:05 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5436E3A1323 for <cfrg@ietfa.amsl.com>; Thu, 24 Dec 2020 09:05:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 JBT1yY_YayYf for <cfrg@ietfa.amsl.com>; Thu, 24 Dec 2020 09:05:39 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F8633A1321 for <cfrg@irtf.org>; Thu, 24 Dec 2020 09:05:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id C8FD3300BBC for <cfrg@irtf.org>; Thu, 24 Dec 2020 12:05:36 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id x84LUbW76Rzs for <cfrg@irtf.org>; Thu, 24 Dec 2020 12:05:34 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 25B6F30066E; Thu, 24 Dec 2020 12:05:34 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <47855176-ce02-07b2-3f78-6f373c6f118d@isode.com>
Date: Thu, 24 Dec 2020 12:05:35 -0500
Cc: IRTF CFRG <cfrg@irtf.org>, "cfrg-chairs@ietf.org" <cfrg-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <99913B60-7876-42F9-BDBA-E8E649C0F333@vigilsec.com>
References: <40067f90-ec2c-2a36-f6df-8afa97189cd1@isode.com> <47855176-ce02-07b2-3f78-6f373c6f118d@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/LpqC8EpQVBc_Zd7qG6F078f3dr4>
Subject: Re: [CFRG] Proposed CFRG process for handling errata
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Dec 2020 17:05:42 -0000

Seems fine to me.  Hopefully most errata will not require Crypto Review Panel consultation.

Russ

> On Dec 24, 2020, at 5:25 AM, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
> 
> Dear CFRG participants,
> 
> Below is the proposed process that CFRG chairs would follow when handling errata submitted on CFRG documents.
> 
> Please let chairs know by January 16th if you have comments or concerns. Statements of support for this proposal are also welcome.
> ------------
> 
> An erratum is submitted through www.rfc-editor.org website An erratum on a CFRG document results in email to irsg@irtf.org (+authors/editors of the RFC) with subject like "[Technical Errata Reported] RFCXXXX (YYYY)", where XXXX is the relevant RFC number and YYYY is the corresponding erratum number (assigned automatically by RFC Editor's website).
> 
> Note that the current errata system is not designed for reporting of extensions and things that were not known or intended at the time the document was written. It is only designed for reporting problems/bugs in documents.
> 
> 
> One of CFRG chairs becomes the response CFRG chair for the erratum. He/she verifies that the erratum designation (Technical versa Editorial) is correct. (Note that the designation can be changed later and it is Ok if initially it is unclear for some errata which one it is.) The CFRG chair can also request deletion of obviously bogus erratum, such as submitted by spammers.
> 
> The CFRG chair then can optionally request review from the Crypto Review Panel <https://trac.ietf.org/trac/irtf/wiki/Crypto%20Review%20Panel>, by emailing crypto-panel@irtf.org and asking for comments on how to resolve the erratum. A proposed resolution can be suggested, if available. The request should specify a deadline, typically 2 weeks. This deadline can be extended by request from Crypto Review Panel members. Note that feedback from Crypto Review Panel is advisory in nature.
> 
> The CFRG chair then emails the CFRG mailing list <cfrg@irtf.org> asking for comments on how to resolve the erratum. (Possible subject to use: "Proposed resolution for erratum YYYY on RFC XXXX") A proposed resolution can be suggested, if available. The proposed resolution takes into consideration feedback received from the Crypto Review Panel (if requested). The request should specify a recommended deadline for discussions.
> 
> The CFRG chair follows the CFRG mailing list discussion of the erratum resolution and posts a summary email after the deadline expires. If there is a clear resolution ("accept", "reject" or "hold for document update") the suggested resolution (and possible changes to the erratum text) are included in the summary email. The IRTF Chair should be notified about the proposed resolution for the erratum.
> 
> The IRTF Chair verifies outcome of the process and either acts on the erratum as proposed by the CFRG chair or delegates this decision to another person (who might be the CFRG chair). (The IRTF chair can provide technical feedback on the erratum in his/her personal capacity. The IRTF Chair can also restart discussion of the erratum on the CFRG mailing list.)
> 
> ------------
> 
> Best Regards,
> 
> Alexey, for the CFRG chairs
> 
> _______________________________________________
> CFRG mailing list
> CFRG@irtf.org
> https://www.irtf.org/mailman/listinfo/cfrg