[openpgp] [Technical Errata Reported] RFC9580 (8847)

RFC Errata System <[email protected]> Wed, 18 Mar 2026 12:27:08 -0700 (PDT)
Newsgroups gmane.ietf.openpgp
Message-ID <[email protected]>
The following errata report has been submitted for RFC9580,
"OpenPGP".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8847

--------------------------------------
Type: Technical
Reported by: Daniel Huigens <[email protected]>

Section: 9.1

Original Text
-------------
32 octets, size octet, encoded key [Section 5.1.6]

56 octets, size octet, encoded key [Section 5.1.7]

Corrected Text
--------------
32 octets, size octet, [sym. algo ID if v3 PKESK,]
encoded key [Section 5.1.6]

56 octets, size octet, [sym. algo ID if v3 PKESK,]
encoded key [Section 5.1.7]

Notes
-----
In Table 18 (OpenPGP Public Key Algorithms Registry), the last column (PKESK Format) is missing a value for the X25519 and X448 rows in the case of v3 PKESKs. See the referenced sections 5.1.6 and 5.1.7.

This also affects the corresponding IANA registry (OpenPGP Public Key Algorithms), which will need to be updated as well.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9580 (draft-ietf-openpgp-crypto-refresh-13)
--------------------------------------
Title               : OpenPGP
Publication Date    : July 2024
Author(s)           : P. Wouters, Ed., D. Huigens, J. Winter, Y. Niibe
Category            : PROPOSED STANDARD
Source              : Open Specification for Pretty Good Privacy
Stream              : IETF
Verifying Party     : IESG

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