RFC Errata
Found 5 records.
Status: Verified (5)
RFC 8520, "Manufacturer Usage Description Specification", March 2019
Source of RFC: opsawg (ops)
Errata ID: 5664
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Leslie Daigle
Date Reported: 2019-03-18
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2019-03-23
Throughout the document, when it says:
Universal Resource Locator Universal Resource Name
It should say:
Uniform Resource Locator Uniform Resource Name
Notes:
Note that there are multiple instances throughout the document.
There haven't been UNIVERSAL resource locators, identifiers, or names for twenty years. I've labeled these as technical errata because they refer to something that doesn't exist.
Errata ID: 6295
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Nick Lamb
Date Reported: 2020-09-23
Verifier Name: Rob Wilton
Date Verified: 2020-09-24
Section 4.1 says:
For example, if one saw the line "manufacturer" : "flobbidy.example.com", then all Things that registered with a MUD URL that contained flobbity.example.com in its authority section would match.
It should say:
For example, if one saw the line "manufacturer" : "flobbity.example.com", then all Things that registered with a MUD URL that contained flobbity.example.com in its authority section would match.
Notes:
Taken at face value it implies somehow a MUD Manager knows about a relationship between two different names flobbidy.example.com and flobbity.example.com in an unexplained way, the correction removes this confusion.
Errata ID: 7173
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Zeno Heeb
Date Reported: 2022-10-20
Verifier Name: Rob Wilton
Date Verified: 2024-01-15
Section 9 says:
Within each access list, access is permitted to packets flowing to or from the Thing that can be mapped to the domain name of "service.bms.example.com".
It should say:
Within each access list, access is permitted to packets flowing to or from the Thing that can be mapped to the domain name of "test.example.com".
Notes:
The subdomain in the Figure does not correspond to the one in the text.
Errata ID: 7819
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Russ Housley
Date Reported: 2024-02-23
Verifier Name: Rob Wilton
Date Verified: 2024-02-26
Section 13.1 says:
Note: A MUD file may need to be re-signed if the signature expires.
It should say:
Note: A MUD file may need to be re-signed if the certificate needed to validate the signature expires.
Notes:
The signature does not expire, but the certificate does.
Errata ID: 5702
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Stuart Cheshire
Date Reported: 2019-04-22
Verifier Name: Ignas Bagdonas
Date Verified: 2019-04-24
Section 16 says:
implementors should take into account what other information they are advertising through mechanisms such as Multicast DNS (mDNS) [RFC6872]
It should say:
implementors should take into account what other information they are advertising through mechanisms such as Multicast DNS (mDNS) [RFC6762]
Notes:
Incorrect reference for Multicast DNS (mDNS).