Re: [openpgp] First remarks on the last I-D

Werner Koch <wk@gnupg.org> Tue, 07 June 2022 16:06 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 9E812C159482 for <openpgp@ietfa.amsl.com>; Tue, 7 Jun 2022 09:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.109 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBe5Xy0eZOBj for <openpgp@ietfa.amsl.com>; Tue, 7 Jun 2022 09:06:09 -0700 (PDT)
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 53B6FC157B5C for <openpgp@ietf.org>; Tue, 7 Jun 2022 09:06:09 -0700 (PDT)
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=cA3yRUY+x19QtEFkZ1zc//sGBH6XbcBHDiWLUS6m9XM=; b=VEjk4CdIYwguYnUEhTaOH5BSMS 2lVQNvrCbRPv/4lsjPSFcoy5C0aLggCUw7yWxChEpySxgTv6M4ljt1r/t3S0Zzc5+k/lvwPaOlgkt TMaxM31/MEOMjDvMQt55i2s/dah0T5taEmb1oF/lpKxjTOB6eWnofwRkkDxLtb66cB8s=;
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.89 #1 (Debian)) id 1nybiZ-0003zv-4P for <openpgp@ietf.org>; Tue, 07 Jun 2022 18:06:07 +0200
Received: from wk by wheatstone.g10code.de with local (Exim 4.92 #5 (Debian)) id 1nybgt-0000wD-E8; Tue, 07 Jun 2022 18:04:23 +0200
From: Werner Koch <wk@gnupg.org>
To: Justus Winter <justus@sequoia-pgp.org>
Cc: Paul Wouters <paul@nohats.ca>, openpgp@ietf.org
References: <165453577116.17285.7902041139949315015@ietfa.amsl.com> <87tu8xkjx4.fsf@wheatstone.g10code.de> <1378eec-4255-930-736-ffd27f292d48@nohats.ca> <87fskgy5c0.fsf@europ.lan>
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Jabber-ID: wk@jabber.gnupg.org
Mail-Followup-To: Justus Winter <justus@sequoia-pgp.org>, Paul Wouters <paul@nohats.ca>, openpgp@ietf.org
Date: Tue, 07 Jun 2022 18:04:23 +0200
In-Reply-To: <87fskgy5c0.fsf@europ.lan> (Justus Winter's message of "Tue, 07 Jun 2022 15:24:15 +0200")
Message-ID: <87leu8jw8o.fsf@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=ARC_Information_Terrorism_CFC_Macintosh_Internet_LUK_E.T._AVIP_BART_"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/B_YCR4BwkVaK2YvtURj7_dggCfQ>
Subject: Re: [openpgp] First remarks on the last I-D
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: Tue, 07 Jun 2022 16:06:14 -0000

> We have customers that care about FIPS, and we need a FIPS-compatible
> subset of OpenPGP now, rather than wait and hope that some existing

Oh what a pitty for your customers ;-).  That is not chartered work.

And really - back when you worked for me you have not been that
energetic to support our customers back then or drive 4880bis forward.

> There are open questions around Brainpool that needs answering.  For
> example, why isn't brainpoolP384r1 included?  How do we encode points
> and scalars?

Obviously in the way it has already been done. Niibe-san had a proposal
long ago to modernize things with backward compatibility in mind.

Brainpoolp384r1 does not make real sense but I have no concert about
adding it back.  In fact Yubikeys and CardOS supports it.

> Not cherry-picking the commit that partially added Brainpool support to

Not sure I understand this.


Shalom-Salam,

   Werner

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein