IETF Logo Mail Archive

[openpgp] Re: Specifying OpenPGP file extensions (and MIME type)?

Andrew Gallagher <andrewg@andrewg.com> Wed, 18 December 2024 15:42 UTC

Return-Path: <andrewg@andrewg.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 97C59C14F6A8 for <openpgp@ietfa.amsl.com>; Wed, 18 Dec 2024 07:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=andrewg.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 8plFhPa9OqpH for <openpgp@ietfa.amsl.com>; Wed, 18 Dec 2024 07:42:51 -0800 (PST)
Received: from fum.andrewg.com (fum.andrewg.com [135.181.198.78]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2537FC14F6A5 for <openpgp@ietf.org>; Wed, 18 Dec 2024 07:42:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=andrewg.com; s=andrewg-com; t=1734536568; bh=xNDhTR1XHnrk+5nLGxgG7VOUKTH8JuGmSHkcp6TbfF8=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=BEzKZZGuT/xqE5Bx2RJgbZQcP1SFbpZ3qHCntfHhyyyRcUPm0V5/M6+M2nI/XCjsL eNYNtez0YA5IpJD3oyEC//Xa8XV8SBa6FxyaNOQ+WBYl0/RszYu0WccueUu6z5kKIP FXJt9qP5XTiCBvtxagDIlO+pyxwiRxFNcpt+dnjaHYC95Xvfy38iLnma5yvrQIAbxi f7hn9048oVnhG4iCONLyTW0l5zupg1t9PdDaF9OugAauoO+cD1Ubp5VESmFpFD9Y9v tcQCbluN/UitViOSaWfa7kGUnYrbG+Vhvr+gMFRpNUD1pCnNQOOlHLybuABFSttiEd z/Gop51+HH7Hw==
Received: from smtpclient.apple (serenity [IPv6:fc93:5820:7349:eda2:99a7::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by fum.andrewg.com (Postfix) with ESMTPSA id E2E915ED46; Wed, 18 Dec 2024 15:42:47 +0000 (UTC)
Content-Type: multipart/signed; boundary="Apple-Mail=_B924D046-BB13-41BD-AF4E-737F2F9D6BC6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.9\))
From: Andrew Gallagher <andrewg@andrewg.com>
In-Reply-To: <sYcaYzsrk48hcbpG3CtdEreiML_V637bHCcmag-3ERtwt8l_LeC9LE40D6-8o_F7x5sPyhw-YpfZfzs9jj4wwHqKsPCd9HAXBvBbTj3dSVc=@protonmail.com>
Date: Wed, 18 Dec 2024 15:42:27 +0000
Message-Id: <C2AE8233-3509-4717-AEC1-B9102669EE65@andrewg.com>
References: <WKLyA6liA56T21xXuqMWjCP4K0eTEfOMuz8oNLua_JiZwEhJJiXjl9Ed7h-HrI_jUYeST-UJ-hEdOsaDjUeGBvvZZkewDRphetWVjCkICLc=@protonmail.com> <87y10efgxp.fsf@fifthhorseman.net> <sYcaYzsrk48hcbpG3CtdEreiML_V637bHCcmag-3ERtwt8l_LeC9LE40D6-8o_F7x5sPyhw-YpfZfzs9jj4wwHqKsPCd9HAXBvBbTj3dSVc=@protonmail.com>
To: Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3731.700.6.1.9)
Message-ID-Hash: E4LY2QQKDJ72JK2PFCDQ7D2JE3QD46WG
X-Message-ID-Hash: E4LY2QQKDJ72JK2PFCDQ7D2JE3QD46WG
X-MailFrom: andrewg@andrewg.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-openpgp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, openpgp <openpgp@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: Specifying OpenPGP file extensions (and MIME type)?
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/xPVUgt6gkJo1tx8BOIw4iPsdtgk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Owner: <mailto:openpgp-owner@ietf.org>
List-Post: <mailto:openpgp@ietf.org>
List-Subscribe: <mailto:openpgp-join@ietf.org>
List-Unsubscribe: <mailto:openpgp-leave@ietf.org>

On 18 Dec 2024, at 15:32, Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org> wrote:
> 
> Well, we currently have a single grammar for all OpenPGP messages:
> https://www.rfc-editor.org/rfc/rfc9580.html#name-openpgp-messages.
> 
> But yeah, if we want to change that / split them into two (or more?

I’d prefer to go in the other direction. Why do we have different grammars for messages and certificates? It prevents us from doing really simple stuff like appending a certificate to a message. If a message is a sequence of packets and a certificate is a sequence of packets - let’s just define an “OpenPGP packet sequence” and let the OpenPGP layer deal with the nuances of “message” vs “keyring” (certificate-ring?).

A

v2.37.1 | Report a Bug | By Email | System Status