[DNSOP] Registration request - missing "_tls" entry in t he Underscored and Globally Scoped DNS Node Names registry (RFC 8460)
Dan Mahoney <[email protected]>
| Newsgroups | gmane.ietf.dnsop |
|---|---|
| Message-ID | <[email protected]> |
Hello, I am Requesting the following addition to the "Underscored and Globally Scoped DNS Node Names" registry, per RFC 8552 Section 3: RR Type _NODE NAME Reference TXT _tls RFC 8460 RFC 8460 (SMTP TLS Reporting) defines a TXT record at _smtp._tls.<domain>. Under RFC 8552, the name that actually needs registering is the one closest to the root - here, "_tls" - with "_smtp" as a subordinate name under it. Subordinate names aren't separately registered; they're the responsibility of whoever holds the parent entry, so this is not a request to also add "_smtp". This looks like a oversight from prior work. RFC 8553 updated every pre-8552 RFC that used underscored names - 2782, 3263, 3529, 3620, 3832, 3958, 4120, 4227, 4386, 4387, 4976, 5026, 5328, 5389, 5415, 5518, 5555, 5617, 5679, 5766, 5780, 5804, 5864, 5928, 6120, 6186, 6376, 6733, 6763, 7208, 7489, 8145 - but RFC 8460 isn't on that list, despite landing in the same window (September 2018). "_tls" currently has no entry in the registry at all. No change to RFC 8460 itself is being requested - just the missing registration. I believe this falls under the "Expert Review" process in RFC 8552 Section 3 rather than requiring a new draft or an RFC Errata - my read is that Errata are for correcting what a published RFC actually says (typos, misstatements, etc.), and there's nothing wrong with RFC 8460's text here. But if a draft, errata, or some other mechanism is actually the right path for this, please let me know and I'll follow up accordingly. Requestor: Dan Mahoney (isc.org, but writing personally although I did ask management approval). Date: August 18, 2026 _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]