Rebecca VanRheenen <rvanrhee...@amsl.com> wrote:
    > We are unable to verify this erratum that the submitter marked as
    > editorial.  Please note that we have changed the “Type” of the
    > following errata report 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/).

I filed this report after some discussion on the list.
It fixes a comment, rather than the underlying CDDL.

So I agree that it's not strictly editorial.

    > You may review the report at: https://www.rfc-editor.org/errata/eid7576

    > Please see https://www.rfc-editor.org/how-to-verify/ for further
    > information on how to verify errata reports.

    > Further information on errata can be found at:
    > https://www.rfc-editor.org/errata.php.

    > Thank you.

    > RFC Editor/rv


    >> On Jul 26, 2023, at 9:33 AM, RFC Errata System
    >> <rfc-edi...@rfc-editor.org> wrote:
    >>
    >> The following errata report has been submitted for RFC8995,
    >> "Bootstrapping Remote Secure Key Infrastructure (BRSKI)".
    >>
    >> --------------------------------------
    >> You may review the report below and at:
    >> https://www.rfc-editor.org/errata/eid7576
    >>
    >> --------------------------------------
    >> Type: Editorial Reported by: Michael Richardson
    >> <mcr+i...@sandelman.ca>
    >>
    >> Section: 4.3
    >>
    >> Original Text
    >> -------------
    >> objective-value = text ; name of the (list of) supported ; protocols:
    >> "EST-TLS" for RFC 7030.
    >>
    >>
    >> Corrected Text
    >> --------------
    >> objective-value = text ; name of the supported protocols.  ; e.g.,
    >> "EST-TLS" for RFC 7030.
    >>
    >>
    >> Notes
    >> -----
    >> This objective does not support a list of supported protocols.  The
    >> comment in the example might lead people to conclude they can do that.
    >>
    >> Instructions:
    >> -------------
    >> This erratum is currently posted as "Reported". If necessary, please
    >> use "Reply All" to discuss whether it should be verified or
    >> rejected. When a decision is reached, the verifying party can log in
    >> to change the status and edit the report, if necessary.
    >>
    >> --------------------------------------
    >> RFC8995 (draft-ietf-anima-bootstrapping-keyinfra-45)
    >> --------------------------------------
    >> Title : Bootstrapping Remote Secure Key Infrastructure (BRSKI)
    >> Publication Date : May 2021 Author(s) : M. Pritikin, M. Richardson,
    >> T. Eckert, M. Behringer, K. Watsen Category : PROPOSED STANDARD Source
    >> : Autonomic Networking Integrated Model and Approach Area : Operations
    >> and Management Stream : IETF Verifying Party : IESG
    >>


--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*



Attachment: signature.asc
Description: PGP signature

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima

Reply via email to