[openpgp] Re: Specifying OpenPGP file extensions (and MIME type)?
Daniel Huigens <d.huigens@protonmail.com> Wed, 18 December 2024 15:32 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 B6B26C1CAF5A for <openpgp@ietfa.amsl.com>; Wed, 18 Dec 2024 07:32:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 KyxOlBwkSuTF for <openpgp@ietfa.amsl.com>; Wed, 18 Dec 2024 07:32:50 -0800 (PST)
Received: from mail-4316.protonmail.ch (mail-4316.protonmail.ch [185.70.43.16]) (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 6CA08C1519B3 for <openpgp@ietf.org>; Wed, 18 Dec 2024 07:32:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1734535958; x=1734795158; bh=d4UZH/zU/LUK6ROT0GHdMIhqM8WrSKA/lR4zMrxxHo4=; 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:List-Unsubscribe:List-Unsubscribe-Post; b=xknvFdH33gBCHaL6ajVw9SPMJ+VaFU1R1yaReRTQF/HMYJExOISJvko2Xru1gPfQb jrJIpEKoxhQDiaT5DDxQe1F8ufWpygcIVuKCjktUrh0n73Xmu8DpGwuh2L1tFbj/cS 4gRcRB/tkgamTc7YWAPGIedDiwZGiGCTq46TseNV9uUqM84WnjqVpXD8jXhyI+yykf dHEdWLjqUvFH9E+jX7CZCbdmYtwfVqbF3iWIJQPhfWRcJOUGkW1rFKHZwlNSyMw2K9 Pne1iAQjr5fjkk++v1zdMeAF17rDEmerLJqvYU0h9Z1cpGPSCwiFs1HD3eBZPirovZ icbe2KiJ1pOJg==
Date: Wed, 18 Dec 2024 15:32:32 +0000
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
From: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <sYcaYzsrk48hcbpG3CtdEreiML_V637bHCcmag-3ERtwt8l_LeC9LE40D6-8o_F7x5sPyhw-YpfZfzs9jj4wwHqKsPCd9HAXBvBbTj3dSVc=@protonmail.com>
In-Reply-To: <87y10efgxp.fsf@fifthhorseman.net>
References: <WKLyA6liA56T21xXuqMWjCP4K0eTEfOMuz8oNLua_JiZwEhJJiXjl9Ed7h-HrI_jUYeST-UJ-hEdOsaDjUeGBvvZZkewDRphetWVjCkICLc=@protonmail.com> <87y10efgxp.fsf@fifthhorseman.net>
Feedback-ID: 2934448:user:proton
X-Pm-Message-ID: bd3024dfe9c8c4d1feeefe387ab779206b1b8b6a
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: FPKSHY552E372GRXY7OPNDK3TJI2E2FH
X-Message-ID-Hash: FPKSHY552E372GRXY7OPNDK3TJI2E2FH
X-MailFrom: d.huigens@protonmail.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: 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/mE2wFM1cNpaszj2Kx114eaX_Ruw>
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 Tuesday, December 17th, 2024 at 16:49, Daniel Kahn Gillmor wrote: > > Perhaps we could define application/pgp-message, to cover both > > encrypted messages and inline-signed messages, for example? > > Is there a reason to use the same media type for both kinds of messages? > If we're defining media types, why not define two distinct ones: one for > an inline-signed message and one for an encrypted message? 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? Is it useful to allow unencrypted and unsigned messages, as the current grammar does? Perhaps not.) ..then perhaps indeed the MIME types could be split too. Best, Daniel
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Huigens
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Kahn Gillmor
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Huigens
- [openpgp] Re: Specifying OpenPGP file extensions … Andrew Gallagher
- [openpgp] Re: Specifying OpenPGP file extensions … Daniel Huigens
- [openpgp] Re: Specifying OpenPGP file extensions … Steffen Nurpmeso