Search RFCs
BCP 222
RFC 8552
Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves,March 2019
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8552
Discuss this RFC: Send questions or comments to the mailing listdnsop@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8552
Abstract
Formally, any DNS Resource Record (RR) may occur under any domainname. However, some services use an operational convention fordefining specific interpretations of an RRset by locating the recordsin a DNS branch under the parent domain to which the RRset actuallyapplies. The top of this subordinate branch is defined by a namingconvention that uses a reserved node name, which begins with theunderscore character (e.g., "_name"). The underscored namingconstruct defines a semantic scope for DNS record types that areassociated with the parent domain above the underscored branch. Thisspecification explores the nature of this DNS usage and defines the"Underscored and Globally Scoped DNS Node Names" registry with IANA.The purpose of this registry is to avoid collisions resulting fromthe use of the same underscored name for different services.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.