Hi Paul, We are unable to verify this erratum that the submitter marked as editorial, so we changed the Type to “Technical”. As Stream Approver, please review and set the Status and Type accordingly (see the definitions at https://www.rfc-editor.org/errata-definitions/).
You may review the report at: https://www.rfc-editor.org/errata/eid8523. Information on how to verify errata reports can be found at: https://www.rfc-editor.org/how-to-verify/. Further information on errata can be found at: https://www.rfc-editor.org/errata.php. Thank you, RFC Editor/mc > On Aug 1, 2025, at 6:15 AM, RFC Errata System <[email protected]> > wrote: > > The following errata report has been submitted for RFC9482, > "Constrained Application Protocol (CoAP) Transfer for the Certificate > Management Protocol". > > -------------------------------------- > You may review the report below and at: > https://www.rfc-editor.org/errata/eid8523 > > -------------------------------------- > Type: Editorial > Reported by: David von Oheimb <[email protected]> > > Section: 2 > > Original Text > ------------- > PKIMessages > > Corrected Text > -------------- > PKIMessage structures > > Notes > ----- > This pertains to all three occurrences of the word "PKIMessages" in sections > 2, 2.3, and 2.5. > > "PKIMessages" can be misinterpreted as the ASN.1 type "PKIMessages", defined > as: > > PKIMessages ::= SEQUENCE SIZE (1..MAX) OF PKIMessage > > Yet what is meant in all three occurrences in this RFC is simply: PKIMessage > structures > (i.e., one ore more structures of type PKIMessage), not a list/sequence of > PKIMessage. > > Note: The same disambiguation has already been done in RFC 9811 > (as mentioned in > https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc6712bis/10/). > > 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. > > -------------------------------------- > RFC9482 (draft-ietf-ace-cmpv2-coap-transport-10) > -------------------------------------- > Title : Constrained Application Protocol (CoAP) Transfer for > the Certificate Management Protocol > Publication Date : November 2023 > Author(s) : M. Sahni, Ed., S. Tripathi, Ed. > Category : PROPOSED STANDARD > Source : Authentication and Authorization for Constrained > Environments > Stream : IETF > Verifying Party : IESG _______________________________________________ Ace mailing list -- [email protected] To unsubscribe send an email to [email protected]
