IETF Logo Mail Archive

Re: [CFRG] Proposed CFRG process for handling errata

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 31 December 2020 13:31 UTC

Return-Path: <alexey.melnikov@isode.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 6F0A73A0BF7 for <cfrg@ietfa.amsl.com>; Thu, 31 Dec 2020 05:31:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 gV4HvsRtcy29 for <cfrg@ietfa.amsl.com>; Thu, 31 Dec 2020 05:31:52 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 67C023A0BF6 for <cfrg@irtf.org>; Thu, 31 Dec 2020 05:31:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1609420870; d=isode.com; s=june2016; i=@isode.com; bh=e7H4TV2HIJX8Ny1YiocZ/AHXWpN2b1s4xhrP/ZKqVIg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=nBvlxx1osXNp99Xwatc1txxjATRvOt12ebvKP/Eiibnw96AP39vYfilvooYNXD8e76IQKn PVPeywCKG6m68gJZdWeemEYMJJ/XXWsT6R7+ffqPXMdVw56K5EqnJ//FXS8bqoG2noDheX lzpWpmRoYCugiholfbBGrv9xK28LDuk=;
Received: from [172.27.255.8] (connect.isode.net [172.20.0.72]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <X-3QBgBqmkiP@statler.isode.com>; Thu, 31 Dec 2020 13:21:10 +0000
To: James Muir <muir.james.a@gmail.com>, "cfrg@irtf.org" <cfrg@irtf.org>
Cc: "cfrg-chairs@ietf.org" <cfrg-chairs@ietf.org>
References: <40067f90-ec2c-2a36-f6df-8afa97189cd1@isode.com> <47855176-ce02-07b2-3f78-6f373c6f118d@isode.com> <d2273291-1bb6-1b8e-3195-5d3ab754f95d@gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <c104d7cd-58e9-2483-c0d1-ec675b6b3697@isode.com>
Date: Thu, 31 Dec 2020 13:19:19 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
In-Reply-To: <d2273291-1bb6-1b8e-3195-5d3ab754f95d@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/LDLJgz-oc1bzBCwpTQhG3tYfx58>
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, 31 Dec 2020 13:31:53 -0000

Hi James,

On 25/12/2020 19:08, James Muir wrote:
> On 2020-12-24 5:25 a.m., Alexey Melnikov 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.
>
> This sounds reasonable.  I especially like the inclusion of deadlines.
>
> You can clarify what role the authors of the RFC have in this process?

I think it is generally very sensible to get authors involved in the 
process and they are typically the first to be asked for opinion. I will 
clarify this in the proposal.

Best Regards,

Alexey

v2.23.0 | Report a Bug | By Email