[openpgp] Re: Fwd: I-D list for Open Specification for Pretty Good Privacy notification: Changes to draft-gallagher-openpgp-code-point-exhaustion
Heiko Schäfer <heiko.schaefer@posteo.de> Thu, 20 March 2025 08:44 UTC
Return-Path: <heiko.schaefer@posteo.de>
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 E308CF79208 for <openpgp@mail2.ietf.org>; Thu, 20 Mar 2025 01:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.395
X-Spam-Level:
X-Spam-Status: No, score=-4.395 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, RCVD_IN_DNSWL_MED=-2.3, 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_HELO_NONE=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=posteo.de
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 tNsZnQbUOi3B for <openpgp@mail2.ietf.org>; Thu, 20 Mar 2025 01:44:20 -0700 (PDT)
Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (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 650C5F78FB8 for <openpgp@ietf.org>; Thu, 20 Mar 2025 01:44:11 -0700 (PDT)
Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 273DC240028 for <openpgp@ietf.org>; Thu, 20 Mar 2025 09:44:10 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1742460250; bh=R67Hj1oJaTHZ7f1JTGxyQ0k7mQC7gbZS0f/IKbHiYrg=; h=Content-Type:Message-ID:Date:MIME-Version:Subject:To:From:From; b=br/eIEzL+fje/pP/8++8vj1TJnAKGe3IqIvaGnnif0Ip0n37KXgATgSB+QCmlpYnY AZhZwiO+wLQGDbpXt8XtVJhvprzPC1f4hKunfgI4eRw3CfnpTz+/gGZ3NnxA7dNAHw qltyVLAHDaSSY2i29zD8CfNt98xJ3TgxyIF4NtNSfHL8Zqkg2BFNJel4EMWeduEEc/ zbBK2klx5FAsv/pqjVjeHFB/i7qNLGp7lSlzsHig1QgOPX0ayXe+eGMUbB7y4pRmV8 ick3ZN44JizkrtxgtIMvN/x+JFdA5ZrE0IGOOJZMJWs7xJ51Y/afxkOETPpNlB3ALB YFFL+tS4CGtpA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4ZJJyx5MLjz9rxG for <openpgp@ietf.org>; Thu, 20 Mar 2025 09:44:09 +0100 (CET)
Received: from services.foundation.hs (services.foundation.hs [192.168.21.4]) by mail.foundation.hs (Postfix) with ESMTP id 78ECD705C5 for <openpgp@ietf.org>; Thu, 20 Mar 2025 09:44:09 +0100 (CET)
Content-Type: multipart/alternative; boundary="------------Ezz5bmFzpTRu6S77CUHBkm6S"
Message-ID: <64a412e9-0062-486e-b70f-c7ede14cf4b2@posteo.de>
Date: Thu, 20 Mar 2025 08:44:08 +0000
MIME-Version: 1.0
To: openpgp@ietf.org
References: <174231559348.277.2581535826712330509@dt-celery-57d64c6895-fcmg2> <B321DC63-56E0-44C2-96AA-D60205C148B2@andrewg.com>
Content-Language: en-US
From: Heiko Schäfer <heiko.schaefer@posteo.de>
In-Reply-To: <B321DC63-56E0-44C2-96AA-D60205C148B2@andrewg.com>
Message-ID-Hash: 2WL3CTR327HYOI52KQ54AOKRSNZ6Y573
X-Message-ID-Hash: 2WL3CTR327HYOI52KQ54AOKRSNZ6Y573
X-MailFrom: heiko.schaefer@posteo.de
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: [openpgp] Re: Fwd: 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/1x6JOyR2-XZw1gsuqbHcdOkvmjQ>
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>
Hello, I'm sure much discussion would be needed to positively decide in favor of the scheme proposed in draft-gallagher-openpgp-code-point-exhaustion. However, as I understand it, the only immediate question that this draft is effectively asking is: "do we want to reserve bit 8, for now?" I have not seen any compelling argument against this proposition, so far. So as a defensive stance, I'm in favor of "reserving bit 8" for all code points where this bit is still unused. At least until there is a compelling argument why the currently vacant second half of a particular code point space is required for some proposed new feature. Thanks, Heiko On 3/18/25 5:44 PM, Andrew Gallagher wrote: > Hi, all. > > Apologies for uploading this so close to the meeting date, but it’s > been sitting in my draft documents for some time now and I want to > bring it to the list before we make a final decision about code point > allocation for PQC and persistent symmetric algorithms. > > tl;dr: please keep code points >=128 free, because if at some point in > the future we needed to extend the algorithm registry to more than a > single octet, having these code points available would let us define a > UTF8-like self-synchronising encoding that would be fully backwards > compatible with all existing wire formats. > > Yes, I said “all”. Please read the document, and feel free to ask > questions! ;-) > > Thanks, > A > >> Begin forwarded message: >> >> *From: *IETF Secretariat <ietf-secretariat-reply@ietf.org> >> *Subject: **I-D list for Open Specification for Pretty Good Privacy >> notification: Changes to draft-gallagher-openpgp-code-point-exhaustion* >> *Date: *18 March 2025 at 16:33:13 GMT >> *To: *<andrewg@andrewg.com> >> >> >> Hello, >> >> This is a notification from the I-D list for Open Specification for >> Pretty Good Privacy. >> >> Document: draft-gallagher-openpgp-code-point-exhaustion, >> https://datatracker.ietf.org/doc/draft-gallagher-openpgp-code-point-exhaustion/ >> >> Change by Andrew Gallagher on 2025-03-18 09:33 PDT: >> >> Changed document external resources from: None to: >> >> gitlab_repo >> https://gitlab.com/andrewgdotcom/openpgp-code-point-exhaustion >> mailing_list https://www.ietf.org/mailman/listinfo/openpgp >> >> Best regards, >> >> The Datatracker Internet-Draft tracking service >> (for the IETF Secretariat) >> >> > > > _______________________________________________ > openpgp mailing list --openpgp@ietf.org > To unsubscribe send an email toopenpgp-leave@ietf.org
- [openpgp] Fwd: I-D list for Open Specification fo… Andrew Gallagher
- [openpgp] Re: Fwd: I-D list for Open Specificatio… Daniel Huigens
- [openpgp] Re: I-D list for Open Specification for… Andrew Gallagher
- [openpgp] Re: Fwd: I-D list for Open Specificatio… Justus Winter
- [openpgp] Re: I-D list for Open Specification for… Andrew Gallagher
- [openpgp] Re: I-D list for Open Specification for… Justus Winter
- [openpgp] Re: I-D list for Open Specification for… Andrew Gallagher
- [openpgp] Re: Fwd: I-D list for Open Specificatio… Heiko Schäfer
- [openpgp] Re: Fwd: I-D list for Open Specificatio… Justus Winter
- [openpgp] Re: Fwd: I-D list for Open Specificatio… Heiko Schäfer
- [openpgp] Re: Fwd: I-D list for Open Specificatio… Justus Winter
- [openpgp] Re: Fwd: I-D list for Open Specificatio… Daniel Huigens
- [openpgp] Re: I-D list for Open Specification for… Andrew Gallagher
- [openpgp] Re: I-D list for Open Specification for… Daniel Huigens