IETF Logo Mail Archive

Re: [openpgp] WG process for getting to a revised RFC 4880

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 26 January 2021 16:11 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C163A0CD9 for <openpgp@ietfa.amsl.com>; Tue, 26 Jan 2021 08:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 tos1e07I1Bb4 for <openpgp@ietfa.amsl.com>; Tue, 26 Jan 2021 08:11:21 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF36D3A0CD3 for <openpgp@ietf.org>; Tue, 26 Jan 2021 08:11:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 14E5E38A15; Tue, 26 Jan 2021 11:13:42 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nJE-NLWlunw4; Tue, 26 Jan 2021 11:13:41 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A583338A04; Tue, 26 Jan 2021 11:13:41 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CADFD618; Tue, 26 Jan 2021 11:11:19 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
cc: openpgp@ietf.org
In-Reply-To: <87lfcgfl7t.fsf@fifthhorseman.net>
References: <87lfcgfl7t.fsf@fifthhorseman.net>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 26 Jan 2021 11:11:19 -0500
Message-ID: <8056.1611677479@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/5hNXplGxjbBj6mmUyBsNqpsU1oI>
Subject: Re: [openpgp] WG process for getting to a revised RFC 4880
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 16:11:24 -0000

Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
    >  - To signal that we're in a "reset", we'll make a new draft,
    > draft-ietf-openpgp-crypto-refresh, with Paul and Werner as editors.
    > This new draft will be marked as a replacement for
    > draft-ietf-openpgp-rfc4880bis-10.

    >  - crypto-refresh-00 (that is, the first revision of the new draft)
    > will incorporate just the text of 4880 {PERIOD}, inconsequential editorial
    > updates, the verified errata of 4880, and incorporation of the relevant
    > text from RFCs 5581 (Camellia) and 6637 (ECC), so all substantive
    > changes from 4880 are things that have already been through the IETF
    > document publication process already.

I suggest that -00 be just rfc4880 be just redo in modern XML.
We did that for RFC8514 (DHCPv6bis).
So, where I marked {PERIOD} above.  Then let -01 be all the rest.

If you are using markdown, I also suggest that you start every new sentence
on a newline, as that makes the git diff process much easier.

    >  - If we can accept that crypto-refresh document as a starting point,
    > we'll have a series of diffs proposed (every week or two) to the WG.

Perfect.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email