Return-Path: <vedaal@nym.hush.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 C1942C14F69C
	for <openpgp@ietfa.amsl.com>; Wed,  4 Dec 2024 07:44:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5
	tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
	DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001,
	RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001,
	RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001,
	RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=nym.hush.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 NJbF4lTXCuwQ for <openpgp@ietfa.amsl.com>;
	Wed,  4 Dec 2024 07:44:45 -0800 (PST)
Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.200])
	(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 6A080C14F5F7
	for <openpgp@ietf.org>; Wed,  4 Dec 2024 07:44:41 -0800 (PST)
Received: from smtp3.hushmail.com (localhost [127.0.0.1])
	by smtp3.hushmail.com (Postfix) with SMTP id BA750800439
	for <openpgp@ietf.org>; Wed,  4 Dec 2024 15:44:40 +0000 (UTC)
X-hush-tls-connected: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=nym.hush.com;
 h=date:to:subject:from; s=hush;
 bh=+UFtrgAibU2lFFP60e9SJrjE66bqte57cLjJnoJfYSc=;
 b=LwM8XLiQVCctyv0XMBTyNgF6L87UadGyrIPI4i0lhhjgewNJlwQoUAd5YSbmAiOuoGzxAufDit+k0CdHT3zNhWLnJM3S8ap0zluPXlGWgmfwdRi+xx1BPHZcN219NBtKgsyUVcnhZfl3Ble2ZDOztr8GKT7clD4hiYiXHrL15GiO9hy8K9ZBWUwbDzZwnBgjKVZqN2UaDNp5yiYMzlnAqd9cfBjAlUD9iq3yN2dMXrBVy59Nz+oYo7GaNMA0IVSZ1Nmd1Eg6/4CP5KM+k/DIdgQZ9XIPKteDm/XATcqjUbAEASGohA4tcR7LQPx1aWdwhCjbA8v40Z26hd7mHv1ckA==
Received: from smtp.hushmail.com (w6.hc.hushmailinc.com [10.4.30.110])
	(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 smtp3.hushmail.com (Postfix) with ESMTPS
	for <openpgp@ietf.org>; Wed,  4 Dec 2024 15:44:40 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 48)
	id 87EE069C8; Wed,  4 Dec 2024 15:44:40 +0000 (UTC)
MIME-Version: 1.0
Date: Wed, 04 Dec 2024 10:44:40 -0500
To: "openpgp" <openpgp@ietf.org>
From: vedaal@nym.hush.com
In-Reply-To: <Z1BMJPE6BGCJPjFU@thunder.hadrons.org>
Message-ID: 
 <6fa513e4dec7d7f53938cca81f085b422e083aadd2e8e13e@smtp.hushmail.com>
Content-Type: multipart/alternative;
	boundary="=_43a347817889a36c57d2dd84a723622d"
Message-ID-Hash: VLLDLQL2Z4WZW5PWHRUCIBVFHL6GWZR4
X-Message-ID-Hash: VLLDLQL2Z4WZW5PWHRUCIBVFHL6GWZR4
X-MailFrom: vedaal@nym.hush.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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: =?utf-8?q?=5Bopenpgp=5D_Re=3A_Specifying_OpenPGP_file_extensions=3F?=
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/openpgp/kgePoHXwgNWJhF7pUA7xY3ZgaKs>
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>

--=_43a347817889a36c57d2dd84a723622d
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"



On 12/4/2024 at 7:36 AM, "Guillem Jover" 
--=_43a347817889a36c57d2dd84a723622d
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="UTF-8"

<span style=3D"font-family: Arial; font-size: 14px; line-height: 150%;"><sp=
an style=3D"font-family:Arial;font-size:14px;line-height:150%;"><br><br><di=
v class=3D"hush-quoting-section">On 12/4/2024 at 7:36 AM, "Guillem Jover" &=
lt;guillem=3D40hadrons.org@dmarc.ietf.org<blockquote class=3D"hush-quote" s=
tyle=3D"border-left:solid 1px #ccc;margin-left:10px;padding-left:10px;"><br=
>I think common extensions are =C2=AB.asc=C2=BB, =C2=AB.sig=C2=BB, =C2=AB.p=
gp=C2=BB and then the<br>unfortunately very prevalent =C2=AB.gpg=C2=BB (whi=
ch seems rather wrong, as it<br>encodes a vendor-specific name into what sh=
ould be an implementation<br>neutral data file).<br><br>=3D=3D=3D=3D=3D<br>=
. pgp is also a vendor-specific name, but is historical well entrenched in =
common usage.&nbsp; So is . gpg<br><br>It would be a backward compatibility=
 nightmare to abolish this for a new extension.&nbsp;<br><br>There is a sim=
ilar issue in medicine, where the term 'anemia' is used for low red blood c=
ell count, when it technically means 'no blood at all'. There are other exa=
mples.&nbsp;<br><br>The conclusion was, that if there is no confusion as to=
 what the term is used for, then it should be left as is.&nbsp;<br><br>The =
same may apply to Open Pgp.&nbsp;<br>If it is clear to everyone what the ex=
tension is, and how to use it, then just leave it alone.&nbsp;<br><br>Vedaa=
l&nbsp;<br><br><br></blockquote></div></span></span>
--=_43a347817889a36c57d2dd84a723622d--

