Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
From: Madison Church <mchurch@staff.rfc-editor.org>
In-Reply-To: <20250801111543.68A8228775B@rfcpa.rfc-editor.org>
Date: Wed, 13 Aug 2025 11:07:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <915C9EF9-054A-4652-86DD-B911D71D75A7@staff.rfc-editor.org>
References: <20250801111543.68A8228775B@rfcpa.rfc-editor.org>
To: Paul Wouters <paul.wouters@aiven.io>
Message-ID-Hash: MO5AYTIK43KWTORXLHPCAJFSZJC7FHZY
CC: David.von.Oheimb@siemens.com, msahni@paloaltonetworks.com,
 stripathi@paloaltonetworks.com, ace@ietf.org,
 RFC Editor <rfc-editor@rfc-editor.org>
Precedence: list
Subject: =?utf-8?q?=5BAce=5D_Re=3A_=5BEditorial_Errata_Reported=5D_RFC9482_=288523=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/ace/qv2nOI_ORN7memcRexahBH__9EQ>

Hi Paul,

We are unable to verify this erratum that the submitter marked as =
editorial, so we changed the Type to =E2=80=9CTechnical=E2=80=9D. As =
Stream Approver, please review and set the Status and Type accordingly =
(see the definitions at https://www.rfc-editor.org/errata-definitions/).=20=


You may review the report at: https://www.rfc-editor.org/errata/eid8523. =
=20

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.
=20
Thank you,=20
RFC Editor/mc

> On Aug 1, 2025, at 6:15=E2=80=AFAM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC9482,
> "Constrained Application Protocol (CoAP) Transfer for the Certificate =
Management Protocol".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8523
>=20
> --------------------------------------
> Type: Editorial
> Reported by: David von Oheimb <David.von.Oheimb@siemens.com>
>=20
> Section: 2
>=20
> Original Text
> -------------
> PKIMessages
>=20
> Corrected Text
> --------------
> PKIMessage structures
>=20
> Notes
> -----
> This pertains to all three occurrences of the word "PKIMessages" in =
sections 2, 2.3, and 2.5.
>=20
> "PKIMessages" can be misinterpreted as the ASN.1 type "PKIMessages", =
defined as:
>=20
>    PKIMessages ::=3D SEQUENCE SIZE (1..MAX) OF PKIMessage
>=20
> Yet what is meant in all three occurrences in this RFC is simply: =
PKIMessage structures=20
> (i.e., one ore more structures of type PKIMessage), not a =
list/sequence of PKIMessage.
>=20
> Note: The same disambiguation has already been done in RFC 9811=20
> (as mentioned in =
https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc6712bis/10/).
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it=20
> 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 =20
> will log in to change the status and edit the report, if necessary.
>=20
> --------------------------------------
> 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