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

Andrew Gallagher <[email protected]> Thu, 20 Mar 2025 14:24:38 +0000

Newsgroups	gmane.ietf.openpgp
Message-ID	<[email protected]>

On 20 Mar 2025, at 12:46, Daniel Huigens <[email protected]> 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

_______________________________________________
openpgp mailing list -- [email protected]
To unsubscribe send an email to [email protected]

signature.asc (application/pgp-signature, 833 B)