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

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

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