Re: [openpgp] Possible to define a common key format for LibrePGP and OpenPGP-IETF?

Justus Winter <justus@sequoia-pgp.org> Fri, 15 December 2023 13:27 UTC

Return-Path: <justus@sequoia-pgp.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 1834AC14CF1A for <openpgp@ietfa.amsl.com>; Fri, 15 Dec 2023 05:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=sequoia-pgp.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7sd5MxH2WoC for <openpgp@ietfa.amsl.com>; Fri, 15 Dec 2023 05:27:47 -0800 (PST)
Received: from harrington.uberspace.de (harrington.uberspace.de [185.26.156.85]) (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 CDD9BC14F61D for <openpgp@ietf.org>; Fri, 15 Dec 2023 05:27:46 -0800 (PST)
Received: (qmail 22056 invoked by uid 500); 15 Dec 2023 13:27:45 -0000
Authentication-Results: harrington.uberspace.de; auth=pass (plain)
Received: from unknown (HELO unkown) (::1) by harrington.uberspace.de (Haraka/3.0.1) with ESMTPSA; Fri, 15 Dec 2023 14:27:44 +0100
From: Justus Winter <justus@sequoia-pgp.org>
To: Werner Koch <wk@gnupg.org>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>, Kai Engert <kaie@kuix.de>
In-Reply-To: <87o7er7idi.fsf@jacob.g10code.de>
References: <fda84dd5-4279-46cd-9b6a-90f211222df3@kuix.de> <87v88zbtub.fsf@europ.lan> <87o7er7idi.fsf@jacob.g10code.de>
Date: Fri, 15 Dec 2023 14:27:43 +0100
Message-ID: <87sf43bnow.fsf@europ.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Rspamd-Bar: -
X-Rspamd-Report: BAYES_HAM(-0.212312) SIGNED_PGP(-2) SUBJECT_ENDS_QUESTION(1) MIME_GOOD(-0.2)
X-Rspamd-Score: -1.412312
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sequoia-pgp.org; s=uberspace; h=from; bh=Zdun/4hRa3w3NV/9y2kgyXEhywD/eGEqcx4NC1k5eAA=; b=UYNTi8vOLMIBwaHaCxCET57nffjNjUDR/4LkPPKjVinRqKaYpAg2LlRbNbJt4r8qxoUt3HdRzD G8nEPKGwG/MTI7sCVsq5pAjC1iLfdtln9epazTRyJdLx+BhUFd/AM8D83NVQlOUYz96u6cQ8W1Nj NN1/H1Ln9m/+hdauCm3/2RbvrvrGI56NijjFIPzOdO2zpvu2fDlS1WnrGLyTKljfcqfiiFa8+weH CQSlRN0NcwnhBxStqa+h5JgsG+cC9LIh49/Cxg8H1W0uxuGSFjDe4TkjOABnOLq/jX5hNd1c+dGC I72353TAgUhsqs73OynXgDtzyFK1pMGe7OpV3XnoezkFFAj3ZCsQX+L9524lGRxGJVKWR+Pt7Key d+qzO2GL7jHfNXA+UJxBcJS+6g+WhRfaDW7pCSsWhtaQCDQolrQ5nSDCOXtE1CBHeg6CcUBFarI8 B67h+iaP0+EO9skRhnPlC+E5v1vj0gkKv33ev0c6GZ5pBMfKoJ7SdO4Oj8307aQCGvp4Vf9LLKBN 1bcqtS20AB5OgD7ixNbXjAQBDGVLVR0EFKCXuVxmYNelHojwNBeTesAlMNLOAiHM6K4hs23zgAPM Mp9SCAn9Bvtn6VVWONCOvD/0mBAHpIrSQ6K+28g/4Oge2dXO80vzUTHu0NSaqcuTK4UvLv5J46R4 M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/yKdBgkcqYgo64ceh00J4sFbCakI>
Subject: Re: [openpgp] Possible to define a common key format for LibrePGP and OpenPGP-IETF?
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 15 Dec 2023 13:27:51 -0000

Hi Werner :)

Werner Koch <wk@gnupg.org> writes:

> On Fri, 15 Dec 2023 12:14, Justus Winter said:
>
>> That compromise is affectionately called
>> draft-ietf-openpgp-crypto-refresh-12.
>
> Sorry, that was not the compromise.  The compromise was found in 2021.
> After that the remaining design team changed large parts again without
> the consent of people from GnuPG or Ribose.

It is a good thing that we were keeping notes all the time.  In fact,
someone went over all the notes and created a handy table that we can
consult now:

https://mailarchive.ietf.org/arch/msg/openpgp/9-WktrFNuZVYZVwlAKl0J56k5Vc/

We can see that GnuPG was present at 32 of the 46 design team meetings,
or 70%.  Ribose was present at 17/46 meetings, roughly 37%.  We can also
see that GnuPG was more consistently represented in the latter phase of
the design team work when NIIBE took over from you.

> In fact our later remarks were never taken into account and thus GnuPG
> and Ribose basically stopped participating in discussion.

It seems to me that you are conceding that you were participating in the
process, but chose not to raise concerns back then when you had the
chance to influence the compromise.  That seems like a poor strategy in
retrospect, but attacking the process and the people who put a lot of
thought and energy into it is a lot worse.

Best,
Justus