Hi Mahesh, all, I also think this is correct… however, I strongly recommend that the errata is edited so that we have the exact OLD/NEW text.
Otherwise, the rendered inline version will be inconvenient for readers like in the recent https://www.rfc-editor.org/rfc/inline-errata/rfc9761.html#eid8818. Thanks. Cheers, Med De : Mahesh Jethanandani <[email protected]> Envoyé : jeudi 19 mars 2026 09:41 À : Madison Church <[email protected]> Cc : BOUCADAIR Mohamed INNOV/NET <[email protected]>; RFC Errata System <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Objet : Re: [Editorial Errata Reported] RFC9761 (8828) Thanks Madison. Authors, please confirm that the Errata can be verified. I believe the Errata is correct. Cheers. On Mar 19, 2026, at 5:20 AM, Madison Church <[email protected]<mailto:[email protected]>> wrote: Hi Mahesh and Med, 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/eid8828. 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, and safe travels for IETF! Madison Church RFC Production Center On Mar 14, 2026, at 10:29 AM, RFC Errata System <[email protected]<mailto:[email protected]>> wrote: The following errata report has been submitted for RFC9761, "Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8828 -------------------------------------- Type: Editorial Reported by: Wenxi Wang <[email protected]<mailto:[email protected]>> Section: 7 Original Text ------------- { "ietf-mud:mud": { ... "ietf-access-control-list:acls": { ... } } } Corrected Text -------------- { "ietf-mud:mud": { ... }, "ietf-access-control-list:acls": { ... } } Notes ----- Instead of being nested within "ietf-mud:mud", "ietf-access-control-list:acls" goes parallel to "ietf-mud:mud", both as root objects. This will make it consistent with RFC8520 (see JSON example in Section 9, https://datatracker.ietf.org/doc/html/rfc8520#section-9). 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. -------------------------------------- RFC9761 (draft-ietf-opsawg-mud-tls-18) -------------------------------------- Title : Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices Publication Date : April 2025 Author(s) : T. Reddy.K, D. Wing, B. Anderson Category : PROPOSED STANDARD Source : Operations and Management Area Working Group Stream : IETF Verifying Party : IESG Mahesh Jethanandani [email protected]<mailto:[email protected]> ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
