RFC Errata
Found 9 records.
Status: Verified (8)
RFC 8552, "Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves", March 2019
Source of RFC: dnsop (ops)
Errata ID: 6551
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jason Mills
Date Reported: 2021-04-19
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2021-04-19
Section 4 says:
RFC 8552 DNS AttrLeaf March 2019 4. IANA Considerations IANA has established the "Underscored and Globally Scoped DNS Node Names" registry. This section describes the registry, the definitions, the initial entries, the use of_ta and _example, and the use of [RFC8126] as guidance for expert review. IANA has also updated the "Enumservices Registrations" registry with a pointer to this document.
It should say:
RFC 8552 DNS AttrLeaf March 2019 4. IANA Considerations IANA has established the "Underscored and Globally Scoped DNS Node Names" registry. This section describes the registry, the definitions, the initial entries, the use of _ta and _example, and the use of [RFC8126] as guidance for expert review. IANA has also updated the "Enumservices Registrations" registry with a pointer to this document.
Notes:
"the use of_ta and _example" is missing a single whitespace before `_ta`, corrected it should read:
"the use of _ta and _example"
Errata ID: 6772
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Robert Royals
Date Reported: 2021-12-03
Verifier Name: RFC Editor
Date Verified: 2021-12-06
Section 2 says:
Only global underscored node names are registered in the "Underscored and Globally Scoped DNS Node Names" registry. From the example above, that would mean _service1, _service2, _service3, _service 4, and _authority would be listed in the IANA registry.
It should say:
Only global underscored node names are registered in the "Underscored and Globally Scoped DNS Node Names" registry. From the example above, that would mean _service1, _service2, _service3, _service4, and _authority would be listed in the IANA registry.
Notes:
Typographical error with an unwanted space character between "_service" and "4"
Errata ID: 6777
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Robert Royals
Date Reported: 2021-12-06
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2021-12-06
Section 4 says:
IANA has established the "Underscored and Globally Scoped DNS Node Names" registry. This section describes the registry, the definitions, the initial entries, the use of_ta and _example, and the
It should say:
IANA has established the "Underscored and Globally Scoped DNS Node Names" registry. This section describes the registry, the definitions, the initial entries, the use of _ta and _example, and the
Notes:
There should be a space character between "of" and "_ta" in "of_ta".
Errata ID: 7064
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Bernie Hoeneisen
Date Reported: 2022-08-02
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2022-08-19
Section 4.1.2. says:
| URI | _acct | [RFC6118] |
It should say:
| URI | _acct | [RFC7566] |
Notes:
Wrong reference. Note that is also has an impact to the IANA registry: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#underscored-globally-scoped-dns-node-names
---
Readers are encouraged to read the below email thread (and may also want to read RFC6118 for additional information):
https://mailarchive.ietf.org/arch/msg/dnsop/TuoV8FmCf1l_pKr500Fo0AI8tVM/
Errata ID: 7065
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Bernie Hoeneisen
Date Reported: 2022-08-02
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2024-01-15
Section 4.2.1 says:
| URI | _iax | [RFC6118] |
It should say:
| URI | _iax | [RFC6315] |
Notes:
Wrong reference. Note that is also has an impact to the IANA registry: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#underscored-globally-scoped-dns-node-names
Errata ID: 7066
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Bernie Hoeneisen
Date Reported: 2022-08-02
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2024-01-29
Section 4.1.2. says:
| URI | _dccp | [RFC7566] |
It should say:
| URI | _dccp | [RFC4340] |
Notes:
Wrong reference. RFC7566 does not even mention "dccp".
Note that this also has an impact to the IANA registry: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#underscored-globally-scoped-dns-node-names
[ Warren Kumari (Ops AD): Please see the thread for resolution: https://mailarchive.ietf.org/arch/msg/dnsop/WFMXL5dY8sniHwVtkPfcqvWk3nI/
This was added as "part of a list used to "reserve" the names of (transport) protocols, so that constructs like _25._quic.example.com could be constructed where the _name denotes the protocol and not the name of something." . I am requesting that the IANA update the reference to match. ]
Errata ID: 7067
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Bernie Hoeneisen
Date Reported: 2022-08-02
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2024-01-29
Section 4.1.2. says:
| URI | _sctp | [RFC6118] |
It should say:
| URI | _sctp | [RFC4340] |
Notes:
Wrong reference. RFC6118 does not even mention "sctp".
Note that this also has an impact to the IANA registry: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#underscored-globally-scoped-dns-node-names
[ Warren Kumari (Ops AD): Please also see Errata 7066, and the thread https://mailarchive.ietf.org/arch/msg/dnsop/WFMXL5dY8sniHwVtkPfcqvWk3nI/
This was added as "part of a list used to "reserve" the names of (transport) protocols, so that constructs like _25._quic.example.com could be constructed where the _name denotes the protocol and not the name of something." . I am requesting that the IANA update the reference to match. ]
Errata ID: 7068
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Bernie Hoeneisen
Date Reported: 2022-08-02
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2024-01-31
Section 4.1.2 says:
| URI | _tcp | [RFC6118] |
| URI | _udp | [RFC6118] |
It should say:
| URI | _tcp | [RFC4340] | | URI | _udp | [RFC4340] |
Notes:
Wrong reference. RFC6118 does not even mention "tcp" nor "udp".
Note that this also has an impact to the IANA registry: https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#underscored-globally-scoped-dns-node-names
[ Warren Kumari (Ops AD): Please also see Errata 7066, and the thread https://mailarchive.ietf.org/arch/msg/dnsop/WFMXL5dY8sniHwVtkPfcqvWk3nI/
This was added as "part of a list used to "reserve" the names of (transport) protocols, so that constructs like _25._quic.example.com could be constructed where the _name denotes the protocol and not the name of something." . IANA will update the reference. ]
Status: Held for Document Update (1)
RFC 8552, "Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves", March 2019
Source of RFC: dnsop (ops)
Errata ID: 5665
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Ronan Flood
Date Reported: 2019-03-21
Held for Document Update by: Warren Kumari (Ops AD)
Date Held: 2019-04-11
Section 4.1.3 says:
4.1.3. _ta Under the NULL RR Type, the entry "_ta-*" denotes all node names beginning with the string "_ta-*". It does NOT refer to a DNS wildcard specification.
It should say:
4.1.3. _ta Under the NULL RR Type, the entry "_ta-*" denotes all node names beginning with the string "_ta-". It does NOT refer to a DNS wildcard specification.
Notes:
The second '*' should not be present, as a literal asterisk does not appear in all node names beginning with "_ta-".