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

Werner Koch <wk@gnupg.org> Wed, 08 June 2022 13:50 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 9D51EC15948C for <openpgp@ietfa.amsl.com>; Wed, 8 Jun 2022 06:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.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, 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 c4Mo-4nF7r49 for <openpgp@ietfa.amsl.com>; Wed, 8 Jun 2022 06:50:11 -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 38220C14F6E7 for <openpgp@ietf.org>; Wed, 8 Jun 2022 06:50:10 -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=spTHKV1higegE/tkFtZVa8QQrAKcv4WB7tEm+GkCtEQ=; b=HSC8r5CPCmNG5ybyb0/ZMwYpXO z7QmF8zrjGvgNBTxzWBMzWjaekW/QLtjzDfRGVAbwCIZZSyirOQG0PnoGSGC+RKMggEjNwMABc4Cp wRKEEoPDS3dGIZ8pcxNFrYCQ+5OCjYF0ayJ+XQ4WMBZwVbVEwZ1pyyYCCz42UoPa4tFM=;
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.89 #1 (Debian)) id 1nyw4V-0007P7-8Z for <openpgp@ietf.org>; Wed, 08 Jun 2022 15:50:07 +0200
Received: from wk by wheatstone.g10code.de with local (Exim 4.92 #5 (Debian)) id 1nyw2R-0006Mv-1i; Wed, 08 Jun 2022 15:47:59 +0200
From: Werner Koch <wk@gnupg.org>
To: Paul Wouters <paul@nohats.ca>
Cc: Ronald Tse <tse=40ribose.com@dmarc.ietf.org>, openpgp@ietf.org
References: <BB9D0AB9-CC8C-420E-8082-E9F64B09BF46@ribose.com> <790E2D75-3B92-4322-A72A-DC8ABED899BF@nohats.ca>
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Jabber-ID: wk@jabber.gnupg.org
Mail-Followup-To: Paul Wouters <paul@nohats.ca>, Ronald Tse <tse=40ribose.com@dmarc.ietf.org>, openpgp@ietf.org
Date: Wed, 08 Jun 2022 15:47:58 +0200
In-Reply-To: <790E2D75-3B92-4322-A72A-DC8ABED899BF@nohats.ca> (Paul Wouters's message of "Tue, 7 Jun 2022 20:13:32 -0400")
Message-ID: <87czfji7w1.fsf@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=CDC_Storm_Worm_Ceridian_brigand_H5N1_Somolia_Denial_of_service_PLA_L"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/JidFd-7hdq4winuPfwdI98ot93w>
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: Wed, 08 Jun 2022 13:50:15 -0000

On Tue,  7 Jun 2022 20:13, Paul Wouters said:
> can and is). The question was whether it would be NIST approved soon
> or not, so GCM could be avoided while still retaining NIST
> compatibility.

Where is NIST compatibility in the WG charter?

For NIST compatibility CFB/MDC can still be used.


Shalom-Salam,

   Werner

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