[openpgp] Re: [Technical Errata Reported] RFC9580 (881 4)

Stephen Farrell <[email protected]> Wed, 18 Mar 2026 21:52:37 +0000
Newsgroups gmane.ietf.openpgp
Message-ID <[email protected]>
Hiya,

Anyone disagree? Let's say if nobody has in a week, we can ask our
AD to process this.

Cheers,
S.

PS: Given the change-over in ADs, and the ongoing IETF meeting,
there may be a little latency before the buttons are pushed.


On 18/03/2026 19:04, Daniel Huigens wrote:
> Hi all,
> 
> This erratum looks correct to me.
> Between the two given options for corrected text, I'd vote for the first one.
> 
> Best,
> Daniel
> 
> 
> On Sunday, March 8th, 2026 at 23:42, RFC Errata System <[email protected]> wrote:
> 
>> The following errata report has been submitted for RFC9580,
>> "OpenPGP".
>>
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid8814
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Daphne Shaw <[email protected]>
>>
>> Section: 5.6
>>
>> Original Text
>> -------------
>> A ZLIB-compressed series of packets is compressed with raw ZLIB-style
>> blocks [RFC1950].
>>
>> Corrected Text
>> --------------
>> A ZLIB-compressed series of packets is compressed using the ZLIB
>> compressed data format [RFC1950].
>>
>> or
>>
>> A ZLIB-compressed series of packets is compressed with ZLIB-style
>> blocks [RFC1950].
>>
>> (Or other words to that effect — the intent is to remove the
>> word "raw").
>>
>> Notes
>> -----
>> In OpenPGP, only ZIP compression uses raw blocks. The ZLIB and BZip2 algorithms both have headers present. A ZLIB stream without headers would be noncompliant to RFC-1950, section 2.3 ("A compliant compressor must produce streams with correct CMF, FLG and ADLER32...").
>>
>> The "raw" was not present in RFC-4880. I believe it came in via https://gitlab.com/openpgp-wg/rfc4880bis/-/commit/c326b8d4b946b2d51eb9885677e0521fb0ecf1a9
>>
>> 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]
OpenPGP_signature.asc (application/pgp-signature, 236 B)
-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQQwbnhHy1kPJkWsM6fk2On5l6gz3QUCabsepQUDAAAAAAAKCRDk2On5l6gz3dfV
AQDDI/TJBVEm5RWDeNt0F/gw5wAWDDBqeRZn/fHk4+oT9AD+K7kq0RejpdqLikTmzJEyx+DmKd+x
rn/tYXxjgDHqXgY=
=6/UO
-----END PGP SIGNATURE-----