On Mon, 15 Jan 2024, Warren Kumari wrote:
Subject: [DNSOP] Dealing with some open Errata:
[ + Dave Crocker (author), Paul Wouters, Frederico Neves (registry experts)]
Hi there all,
As part of the Great Errata Cleanup of 2024, I'm going through reported Errata
and trying to close them.
I'm just dealing with the ones that I can do myself, but there are some which I
need WG input on.
These include two Errata filed by Bernie Hoeneisen (author of RFC6118) against
RFC8552 - "Scoped Interpretation of DNS Resource Records through
"Underscored" Naming of Attribute Leaves"
I'd like to get feedback by Monday Jan 29th, otherwise I'll just go with my
proposed resolutions below.
Errata1: https://www.rfc-editor.org/errata/eid7066
---
Section 4.1.2. says:
| URI | _dccp | [RFC7566] |
It should say:
?
Notes:
Wrong reference. RFC7566 does not even mention "dccp". Unaware of a useful
reference. Not sure this line needs to be removed.
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
—-
I **think** that the correct reference for this is actually RFC7553 - "The Uniform
Resource Identifier (URI) DNS Resource Record". Note that
this initially confused me, because I was looking for DCCP (and TCP and UDP) in
the URI *registry*, not in the DNS RR definition.
I think this might have been 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 think dccp got added to this list because it is
references as a "transport protocol" in RFC4340 and the author wanted
to make sure transport protocol names were not accidentally squatted
by newly invented things with a clashing name/acronym.
My proposed resolution: Mark Errata verified, update reference to be RFC7553.
I would update the reference to 4340.
Errata 2: https://www.rfc-editor.org/errata/eid7068:
—-
Section 4.1.2. says:
| URI | _tcp | [RFC6118] |
| URI | _udp | [RFC6118] |
It should say:
?
Notes:
Wrong reference. RFC6118 does not even mention "tcp" nor "udp". Unaware of
useful reference(s). Not sure this line needs to be removed.
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
---
My proposed resolution: Same as above.
I believe these should be fixed to RFC7553:
See: https://datatracker.ietf.org/doc/html/rfc7553#section-4.1
As another example, suppose we are looking for the URI for a service
with Service Name "A" and Transport Protocol "B" for host
example.com. Then we would query for
(QNAME,QTYPE)=("_A._B.example.com","URI").
eg: _smtp._tcp.example.com IN URI <rrdata>
As a Delegated Expert, if someone wants a new entry in this IANA
registry, I look for clashes with existing transport protocols
and would probably reject it if I find such a clash.
Paul
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
