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

[Andrew Gallagher <[e-mail]>]

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 <[e-mail]>
> 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: <[e-mail]>
> 
> 
> 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)
> 
>