IETF Logo Mail Archive

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

Daniel Huigens <d.huigens@protonmail.com> Wed, 04 December 2024 16:51 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 AA991C151522 for <openpgp@ietfa.amsl.com>; Wed, 4 Dec 2024 08:51:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, HTML_MESSAGE=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 WmL5kK_D6bU2 for <openpgp@ietfa.amsl.com>; Wed, 4 Dec 2024 08:51:06 -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 ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7BFC1840E1 for <openpgp@ietf.org>; Wed, 4 Dec 2024 08:50:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1733331047; x=1733590247; bh=cInh1qK5cpDEml/RE4sbBWPi5ibdL1KqnmRpwO52YfQ=; h=Date:To:From:Cc:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector: List-Unsubscribe:List-Unsubscribe-Post; b=VFZTtxHVma2QnWB5/sclpCf8KZoCk/SXgIXlVnTHNAoc1YiBSXBswNGjsTX8q49ne hE00hVERXUgfLXCiY6yxb9/Y2B08BbiXpvWjK6XTWXhWCKF1uOKxwT/hXbEYtQjvgA cU+kCZggZ2afO44gJAoCfbLydAxLt/Imao8/dLwLiby5CakKx9P7lp7bzwdXoZS++i Vcsk/1WlF4OMjQ7/Sh7hxnKe0VUme0wJBHGIgoghLSs+n1Tuo3JiPTiOxygu1xG/4a FcKQGPuc77OLIeMrRHsgYfErm61s4Z70pTAtKx/6cMJx2GVhU2gdQRu0tdCsH1G1wm EkU/Dd5GMGobw==
Date: Wed, 04 Dec 2024 16:50:43 +0000
To: vedaal@nym.hush.com
From: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <WKLyA6liA56T21xXuqMWjCP4K0eTEfOMuz8oNLua_JiZwEhJJiXjl9Ed7h-HrI_jUYeST-UJ-hEdOsaDjUeGBvvZZkewDRphetWVjCkICLc=@protonmail.com>
Feedback-ID: 2934448:user:proton
X-Pm-Message-ID: 1ea2d365b0d3fbdbea6ab500007315c2bd86d685
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1=_5Y9QDJOYAc2z85W2LhEnfHexubfGFluQRoRT1FIck"
Message-ID-Hash: M3OPEAEDERJV2I37PBOLL6ITWMAY2I4S
X-Message-ID-Hash: M3OPEAEDERJV2I37PBOLL6ITWMAY2I4S
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/sAInJDtRIshpwpZk4-nSXbQ6Kvg>
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 Wednesday, December 4th, 2024 at 16:44, vedaal@nym.hush.com wrote:

> . pgp is also a vendor-specific name, but is historical well entrenched in common usage
>
>>

Since the name of the standard is OpenPGP, I think .pgp is fine as a filename, since it can also just be considered an abbreviation of that.

Beyond a filename, it would also be nice to have a MIME type for PGP messages. RFC3156 does define application/pgp-encrypted, but uses it only for the "Version: 1" control text, while using application/octet-stream for the actual encrypted data.

Perhaps we could define application/pgp-message, to cover both encrypted messages and inline-signed messages, for example?

Best,
Daniel

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