IETF Logo Mail Archive

[openpgp] Re: I-D list for Open Specification for Pretty Good Privacy notification: Changes to draft-gallagher-openpgp-code-point-exhaustion

Andrew Gallagher <andrewg@andrewg.com> Thu, 20 March 2025 14:25 UTC

Return-Path: <andrewg@andrewg.com>
X-Original-To: openpgp@mail2.ietf.org
Delivered-To: openpgp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2B381FB1FBF for <openpgp@mail2.ietf.org>; Thu, 20 Mar 2025 07:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=andrewg.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 510B4TxUAuty for <openpgp@mail2.ietf.org>; Thu, 20 Mar 2025 07:24:58 -0700 (PDT)
Received: from fum.andrewg.com (fum.andrewg.com [IPv6:2a01:4f9:c011:23ad::1]) (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 mail2.ietf.org (Postfix) with ESMTPS id 362CDFB1FA9 for <openpgp@ietf.org>; Thu, 20 Mar 2025 07:24:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=andrewg.com; s=andrewg-com; t=1742480696; bh=rZHeaM9Hk6wq+xpRT5gj/UCENZ1Gmc1XZ999zTFlTPk=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=geWR8HJe6PKT7HUb/NhP2FGV4eM5q8RGN2AiAwvMvZxa2oopdbjdxp177VsaxViov GlctZ/dG+hDTkYxnxMkh16nwzT6btqHVvsW/6SDYI+q6CbGNwC852n/X8AIY8kqiAK pwg/or45GkSTbZxCWvzil6/oIxGE7hhAuEDxZk60UfQOCmsxhO5kyBWCBGMcEIkwYH /hDxQ0KkXNXsXWHQnSACsM8UGwHseThEbWX/8BlyPfc7cmCBXQXvH6C7gNrLaG3mJj wJgwxcw0YEvv8jU1b54ehoW6mCOYw+CTQ2Nw6/vu1pq775X6NSY37i8Fn8xu2yNxTr a8hvmR4pDIEhQ==
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 6E9AE5DDA2; Thu, 20 Mar 2025 14:24:56 +0000 (UTC)
From: Andrew Gallagher <andrewg@andrewg.com>
Message-Id: <40552758-BA64-4E10-803B-EF0E6E7BE45F@andrewg.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2E926574-E372-4711-B88E-A67DB64D59C2"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.9\))
Date: Thu, 20 Mar 2025 14:24:38 +0000
In-Reply-To: <09_pBNGQp8U3bJBeEpRqAggxanUlbvZNMtEvjS6qu1LUbACtuK9ttEKH6FUksLHkLyH9jTL4gI6Ua1gs4cXL_L9Hw1jW_2lSf3Cwgpd1kr0=@protonmail.com>
To: Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org>
References: <174231559348.277.2581535826712330509@dt-celery-57d64c6895-fcmg2> <B321DC63-56E0-44C2-96AA-D60205C148B2@andrewg.com> <64a412e9-0062-486e-b70f-c7ede14cf4b2@posteo.de> <09_pBNGQp8U3bJBeEpRqAggxanUlbvZNMtEvjS6qu1LUbACtuK9ttEKH6FUksLHkLyH9jTL4gI6Ua1gs4cXL_L9Hw1jW_2lSf3Cwgpd1kr0=@protonmail.com>
X-Mailer: Apple Mail (2.3731.700.6.1.9)
Message-ID-Hash: 4EXGUG5O4EWKOA6VULDM3DS5PU7HJJHH
X-Message-ID-Hash: 4EXGUG5O4EWKOA6VULDM3DS5PU7HJJHH
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: Heiko Schäfer <heiko.schaefer@posteo.de>, IETF OpenPGP <openpgp@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: I-D list for Open Specification for Pretty Good Privacy notification: Changes to draft-gallagher-openpgp-code-point-exhaustion
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/m36z81UJWitVtnvl1TuX507nOy0>
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 20 Mar 2025, at 12:46, Daniel Huigens <d.huigens=40protonmail.com@dmarc.ietf.org> wrote:
> 
> So, if the WG is in favor of that I can make that change, of course. But, I just personally think that reserving half of every OpenPGP registry for future expansion purposes is unnecessary; reserving a single value (e.g. 255) should be enough.

To be clear, I’m not suggesting that we formally reserve code points >=128, I’m just suggesting that we don’t allocate them until we need to. I don’t see how moving the persistent symmetric range closer to the top of the current assigned range is an issue - presumably at some point the allocated code points will have to flow around the reserved range, and it might be better to get it over with as quickly as possible. If you want to reserve a clean nybble-ful of code points, then why not make it the next available nybble? :-)

A

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