Re: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-02.txt (fwd)

Derek Atkins <derek@ihtfp.com> Tue, 23 February 2021 17:24 UTC

Return-Path: <derek@ihtfp.com>
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 3A6183A0C1C for <openpgp@ietfa.amsl.com>; Tue, 23 Feb 2021 09:24:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ihtfp.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 RDDpXhpbO0nV for <openpgp@ietfa.amsl.com>; Tue, 23 Feb 2021 09:24:35 -0800 (PST)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB48B3A0C18 for <openpgp@ietf.org>; Tue, 23 Feb 2021 09:24:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 8C137E2040; Tue, 23 Feb 2021 12:24:33 -0500 (EST)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 17959-01; Tue, 23 Feb 2021 12:24:32 -0500 (EST)
Received: by mail2.ihtfp.org (Postfix, from userid 48) id 583E4E2044; Tue, 23 Feb 2021 12:24:32 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1614101072; bh=IO/P9HZfAEyHeQELHJK8Dz7v/I7qM0yfvOAp2fwlkME=; h=In-Reply-To:References:Date:Subject:From:To; b=lKyxsZBzHjCmdRNkVoUAzrS7amQoeyDy50cZi49qcvQG7kdcuyWXmTJUFDOrehUPP KDFiQhoCn34+lodvRsBermyRq7bu97hTysBCb7Vykb8K5A4tIQysiMqIaO35NDmzos SUKaYY0MwaN+h0zgrp07JxyxUlGlxQ5T7j/gg5N4=
Received: from 192.168.248.239 (SquirrelMail authenticated user warlord) by mail2.ihtfp.org with HTTP; Tue, 23 Feb 2021 12:24:32 -0500
Message-ID: <8473b015f635c0f88f9bceed8acda0f8.squirrel@mail2.ihtfp.org>
In-Reply-To: <87a6rug0x5.fsf@wheatstone.g10code.de>
References: <7d8bdda1-4e5c-6c10-f3cd-1d191fad595c@nohats.ca> <4f3d66b74b46b5b8bf27b5e1589bf80e.squirrel@mail2.ihtfp.org> <87a6rug0x5.fsf@wheatstone.g10code.de>
Date: Tue, 23 Feb 2021 12:24:32 -0500
From: "Derek Atkins" <derek@ihtfp.com>
To: "Derek Atkins" <derek@ihtfp.com>, "Paul Wouters" <paul@nohats.ca>, openpgp@ietf.org
User-Agent: SquirrelMail/1.4.22-14.fc20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/BZW0A4W-KD5NDj43fQkzWosAM5s>
Subject: Re: [openpgp] I-D Action: draft-ietf-openpgp-crypto-refresh-02.txt (fwd)
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, 23 Feb 2021 17:24:36 -0000

HI,

On Tue, February 23, 2021 12:16 pm, Werner Koch wrote:
> On Tue, 23 Feb 2021 08:15, Derek Atkins said:
>>    Implementations SHOULD generate V4 signatures.  Implementations MUST
>>    NOT create version 3 signatures; they MAY accept version 3
>>    signatures.
>>
>> There is no MUST create version.  Is this intended to change?
>
> This is is an editorial problem due to our step by step re-iteration
> process.  The dropped draft-ietf-openpgp-rfc4880bis-10.txt had this text:
>
>    Implementations MUST generate version 5 signatures when using a
>    version 5 key.  Implementations SHOULD generate V4 signatures with
>    version 4 keys.  Implementations MUST NOT create version 3
>    signatures; they MAY accept version 3 signatures.
>
> which should explain above.  But right in the course of re-iteration
> Paul and me should have noticed that and adjusted it accordingly.

Okay, so this is "intended to change" are more edits are done.
Gotcha.

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant