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

Daniel Huigens <d.huigens@protonmail.com> Fri, 21 March 2025 05:48 UTC

Return-Path: <d.huigens@protonmail.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 3F9BC103F06B for <openpgp@mail2.ietf.org>; Thu, 20 Mar 2025 22:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.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 xgYXqLxrfqtk for <openpgp@mail2.ietf.org>; Thu, 20 Mar 2025 22:48:04 -0700 (PDT)
Received: from mail-10629.protonmail.ch (mail-10629.protonmail.ch [79.135.106.29]) (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 7A529103F05F for <openpgp@ietf.org>; Thu, 20 Mar 2025 22:48:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1742536082; x=1742795282; bh=16W1KELeU4evlsZ0Ajwk1pt0rbYzhn1K5qa4Kpa732s=; 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=LCUArC0k6iKPWH0ZH45PDPy5P4e68E2vC5+9N9hXAmnVfjbdIy465nJYq11aYohet VOhBVh11y6lI889CkUv2J2Xn24MKf3V5/1halTip8U6MrUl/1zlafcalM9M0AhFMwY c+/Tv2K/IAN6TS5zF8/MzH0XVC7oB6pov6v4RWM2BqdgR51NU9VFjY2fIeYWX11Knk 8ihXg8s63wdd9YERoMV6undpb5my83SGclOmZQJHptaECgGvBsH3YdZ+fp/7Mgft15 SDGn3HDhzrQagN1qcAx376a2u0dCl7upk6VQCj+9HJ2mMf+ooFvfLBsxHIhTS0fqQy j6tO3oY/+QmFQ==
Date: Fri, 21 Mar 2025 05:47:57 +0000
To: Andrew Gallagher <andrewg=40andrewg.com@dmarc.ietf.org>
From: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <7SgZS64TuZy7t2MIyL3OzvLo8wOp0Sd4gFcSVkSSAbVCE3nME7EzZ53kao0uCJcd8DkbZN9qE6E9eFY4DhJCw3XpyYVSGX8u4wPOivTZRx0=@protonmail.com>
In-Reply-To: <40552758-BA64-4E10-803B-EF0E6E7BE45F@andrewg.com>
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> <40552758-BA64-4E10-803B-EF0E6E7BE45F@andrewg.com>
Feedback-ID: 2934448:user:proton
X-Pm-Message-ID: 403d05860645cfe939b655a577a565fd6a17aa60
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1=_ji6bzstm376Zf80520w0noe1giApd6AzMH6gMHettE"
Message-ID-Hash: 77SRM2C75XR3ZTRZKMXEIDDBO4I3N4UN
X-Message-ID-Hash: 77SRM2C75XR3ZTRZKMXEIDDBO4I3N4UN
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: 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/YlLzXkDaCOopyjtuLtvg42I0IYA>
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 Thursday, March 20th, 2025 at 21:24, Andrew Gallagher wrote:

> 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.

Well, not necessarily, if 128 asymmetric algorithms turns out to be sufficient forever (and in that case, checking whether a given algorithm is symmetric collapses back to just checking whether the first bit is set).

> If you want to reserve a clean nybble-ful of code points, then why not make it the next available nybble? :-)

But sure, fair enough. Obviously it's not very difficult to check either way so if the WG prefers that I can change it ofc.

Best,
Daniel