Verified.

-d


> On Mar 14, 2026, at 8:29 AM, RFC Errata System <[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]>
> 
> 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

_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to