[openpgp] Stop dragging around old material, please!

Rick van Rein <rick@openfortress.nl> Mon, 14 November 2022 11:42 UTC

Return-Path: <vanrein@vanrein.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 3E3A8C1524BF for <openpgp@ietfa.amsl.com>; Mon, 14 Nov 2022 03:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.634
X-Spam-Level:
X-Spam-Status: No, score=-1.634 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kpnmail.nl
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 omDFlzuSjIb6 for <openpgp@ietfa.amsl.com>; Mon, 14 Nov 2022 03:42:32 -0800 (PST)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.168]) (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 233A8C14F747 for <openpgp@ietf.org>; Mon, 14 Nov 2022 03:42:28 -0800 (PST)
X-KPN-MessageId: 67d867dd-6411-11ed-be70-005056aba152
Received: from smtp.kpnmail.nl (unknown [10.31.155.40]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id 67d867dd-6411-11ed-be70-005056aba152; Mon, 14 Nov 2022 12:42:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kpnmail.nl; s=kpnmail01; h=content-type:mime-version:message-id:subject:to:from:date; bh=fpojlOQ2R3TAamQ1IkxicucOjt3+2DSA64PoCd1ArXw=; b=gXaZn2wbmReprKbplArEUD/R067xAqKpvLM35Qjd0O5Dry4OzYYGh/XgtbDdmoHRswXDf9paQdaho LMO7Nv/sTjDwKv6Dju4AiVBvV5UVOOuhhRWln+0F8sf+j8CUtnQjgObfW7sPPHRlWIWZMZJnYuGqZt iDzw2fnK5fn3zlqo=
X-KPN-MID: 33|Ex1KLw4ND/NcOE8QXnek8pcPklaNUTOeR3OxZXG9Df3v0ZGDhtgxxpJ4tqq/yDL H6t3ttIk4ZVKU7x35fAu8ixKluEMxppqXqjFtlN87P0c=
X-KPN-VerifiedSender: No
X-CMASSUN: 33|ej7sSSzfqUccEv9Iq8Kx+hW0rorKjuSDOm0IKq/ij/t8n7UklmU3ESvU92gJZ9W 8R9MIsidLU0SfMAtXOzpJ+g==
X-Originating-IP: 77.173.183.203
Received: from fame.vanrein.org (77-173-183-203.fixed.kpn.net [77.173.183.203]) by smtp.xs4all.nl (Halon) with ESMTPSA id 692f26dd-6411-11ed-9ebc-005056ab7584; Mon, 14 Nov 2022 12:42:26 +0100 (CET)
Received: by fame.vanrein.org (Postfix, from userid 1000) id EA6BD2B4AF; Mon, 14 Nov 2022 11:42:25 +0000 (UTC)
Date: Mon, 14 Nov 2022 11:42:25 +0000
From: Rick van Rein <rick@openfortress.nl>
To: openpgp@ietf.org
Message-ID: <20221114114225.GA1789@openfortress.nl>
Mail-Followup-To: openpgp@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/9HV5nT6EgohoP8EA3RVUJ5uFsP4>
Subject: [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: Mon, 14 Nov 2022 11:42:39 -0000

Hello,

At IETF 115 I offered to proof-read the draft for this WG.
Back then, I thought the old formats were finally being
ditched, something I already fought for during RFC 4880.

Now I find that it's being renamed to Legacy.  I think this
is a mistake, but I understand the scare of making choices.

Question:
Is there any use of old packet formats that uses crypto
that we would still consider healthy today?  None of the
signatures would now be reliable, but the encryption may
have protected us during transit back then, but not when
our email boxes get broken.

Suggestion:
There is an option to simply STOP MENTIONING old formats,
and relying on registries that continue to allocate their
tags.  The old format was specified in older RFCs and can
still be added to software that wants to be compliant with
old forms, even when they are deprecated or obsoleted.


Thanks,
 -Rick