Re: [openpgp] Stop dragging around old material, please!

Daniel Huigens <d.huigens@protonmail.com> Thu, 17 November 2022 15:30 UTC

Return-Path: <d.huigens@protonmail.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 87DC6C14CE57 for <openpgp@ietfa.amsl.com>; Thu, 17 Nov 2022 07:30:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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 (2048-bit key) header.d=protonmail.com
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 2IYMw1nUR6IK for <openpgp@ietfa.amsl.com>; Thu, 17 Nov 2022 07:30:50 -0800 (PST)
Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D2B0C14F718 for <openpgp@ietf.org>; Thu, 17 Nov 2022 07:30:50 -0800 (PST)
Date: Thu, 17 Nov 2022 15:30:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1668699047; x=1668958247; bh=Woi5oOJpOeV6JM7hgL2ctpOL6RZgnz1uT70IhU/Me2I=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=v+cU+qmfCffcYePLrGdikf3pF0G0xBXKcKz6Ja1c4RX/09D0W8TwJjtfOWoIeFd3L YBoJXGiJ+MVVsxXSDAiMUm48envKErYrjNfXURTQbCpg2GkIu9DMn2Zs/r5XK3eRB+ 0P3oeIW0kjyWRTv106T7ZKzRPa161e/4ZqokI/AX1mLJyE9fIccYdqdzl1SUzJgEZF Uxdc+/k6RTGKLXSxjDeuW4ADaUNeAtrmsIFxwQWNbqgCJugIxxDrB2PcD/ihOKPmor xJzM8QYYKWmTIKomSiYepASC1sX8MHQ0NeGqHaAqDqu1+zZAHd/YfRhWLRHcDFzeMd ZUQJ+HTg+bITw==
To: Rick van Rein <rick@openfortress.nl>
From: Daniel Huigens <d.huigens@protonmail.com>
Cc: openpgp@ietf.org
Message-ID: <fvPH4We_ezrhe8JowNy5giZ2RlJe9T2KO9N18iI2NarMEIOHikcsW8bU695b8ws2Rv7qFG6Su0v7_H8F-lin5zh5I9ahF-tCKAujbREM3uw=@protonmail.com>
In-Reply-To: <20221117020904.GA11610@openfortress.nl>
References: <20221117020904.GA11610@openfortress.nl>
Feedback-ID: 2934448:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------bd448bb9aec560e6963926d7f69671159ca1a6b8b83fb7ee35cf08ec8838cf91"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/iy0E0EhZ3Lt6gcJpgN6Z7xxMiio>
Subject: Re: [openpgp] Stop dragging around old material, please!
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: Thu, 17 Nov 2022 15:30:54 -0000

Hey Rick,

I just wanted to say that I didn't mean to dismiss your point of view,
and actually I agree with trying to get rid of legacy stuff. I'm not
sure if it's possible in this particular case but that doesn't mean
that it's not worth discussing, IMO.

There are in fact some things in the spec that I think implementations
*can* get away with not implementing; V3 keys and signatures being one
of them (we haven't supported it for quite a while).

It might still be worth having some place to clearly state that they're
deprecated, and what the issues with them are (i.e. [1]), but maybe
describing how to create or parse them is unnecessary. Of course,
others might again disagree with me there.

Best,
Daniel

[1]: https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-crypto-refresh-07#page-62


------- Original Message -------
On Thursday, November 17th, 2022 at 03:09, Rick van Rein <rick@openfortress.nl> wrote:

> Hello OpenPGP,
> 

> The responses I got represent a clear view on how specifications
> should be written. It happens to not be mine and if I reviewed as
> offered during #115 this would trigger a strong debate. Such a
> debate might interfere with progress.
> 

> Rather than doing this review, it is more constructive if I quietly
> let this work continue without my input. I will remove myself from
> the group and its related voting rights.
> 

> Good luck,
> -Rick
> 

> _______________________________________________
> openpgp mailing list
> openpgp@ietf.org
> https://www.ietf.org/mailman/listinfo/openpgp