IETF Logo Mail Archive

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

Werner Koch <wk@gnupg.org> Tue, 23 February 2021 17:20 UTC

Return-Path: <wk@gnupg.org>
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 A5FFB3A0BDE for <openpgp@ietfa.amsl.com>; Tue, 23 Feb 2021 09:20:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, 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=gnupg.org
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 eD5ErQGKf2xD for <openpgp@ietfa.amsl.com>; Tue, 23 Feb 2021 09:20:11 -0800 (PST)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7CCE3A0BDC for <openpgp@ietf.org>; Tue, 23 Feb 2021 09:20:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnupg.org; s=20181017; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=asInD0YABL55oLMdqD80WdsWCg1RmhAUZGvGDzNEIH0=; b=g/NP//cCsadTwITCzAFYdltAMo qUN/193fb0Y38SL+68jplZLa+kOZfQcOByHZoi3aG6Zo5StQZft9izpNyYx69ExQXUYkIwVN+/3zI En81rOalAnYhBR4zNmqmCuR+WUIEyJdTRl+j3vKA0hA6QDS3Uns+poD4PJRsh2fhY8Pg=;
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.89 #1 (Debian)) id 1lEbM0-0005GI-Pm for <openpgp@ietf.org>; Tue, 23 Feb 2021 18:20:08 +0100
Received: from wk by wheatstone.g10code.de with local (Exim 4.92 #5 (Debian)) id 1lEbI7-0008JS-Ny; Tue, 23 Feb 2021 18:16:07 +0100
From: Werner Koch <wk@gnupg.org>
To: Derek Atkins <derek@ihtfp.com>
Cc: Paul Wouters <paul@nohats.ca>, openpgp@ietf.org
References: <7d8bdda1-4e5c-6c10-f3cd-1d191fad595c@nohats.ca> <4f3d66b74b46b5b8bf27b5e1589bf80e.squirrel@mail2.ihtfp.org>
Organisation: GnuPG e.V.
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Mail-Followup-To: "Derek Atkins" <derek@ihtfp.com>, "Paul Wouters" <paul@nohats.ca>, openpgp@ietf.org
Date: Tue, 23 Feb 2021 18:16:06 +0100
In-Reply-To: <4f3d66b74b46b5b8bf27b5e1589bf80e.squirrel@mail2.ihtfp.org> (Derek Atkins's message of "Tue, 23 Feb 2021 08:15:06 -0500")
Message-ID: <87a6rug0x5.fsf@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=GOE_eavesdropping_NATO_doctrine_Internet_defense_information_warfare"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/Gj0wgHNgWzamlvaPvV47i21E4Gc>
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:20:14 -0000

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.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

v2.23.0 | Report a Bug | By Email