The IESG has received a request from the Domain Name System Operations WG (dnsop) to consider the following document: - 'DNS Scoped Data Through "Underscore" Naming of Attribute Leaves' <draft-ietf-dnsop-attrleaf-13.txt> as Best Current Practice PLEASE NOTE: The draft-ietf-dnsop-attrleaf-fix and draft-ietf-dnsop-attrleaf documents are very closely related. Please read **both** of them when commenting. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2018-09-25. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract Formally, any DNS resource record may occur under any domain name. However some services have defined an operational convention, which applies to DNS leaf nodes that are under a DNS branch having one or more reserved node names, each beginning with an _underscore. The underscored naming construct defines a semantic scope for DNS record types that are associated with the parent domain, above the underscored branch. This specification explores the nature of this DNS usage and defines the "DNS Global Underscore Scoped Entry Registry" with IANA. The purpose of the Underscore registry is to avoid collisions resulting from the use of the same underscore-based name, for different services. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf/ballot/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc2181: Clarifications to the DNS Specification (Proposed Standard - IETF stream) rfc2782: A DNS RR for specifying the location of services (DNS SRV) (Proposed Standard - IETF stream) rfc5518: Vouch By Reference (Proposed Standard - IETF stream) rfc6698: The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA (Proposed Standard - IETF stream) rfc8145: Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC) (Proposed Standard - IETF stream) rfc8162: Using Secure DNS to Associate Certificates with Domain Names for S/MIME (Experimental - IETF stream) rfc5026: Mobile IPv6 Bootstrapping in Split Scenario (Proposed Standard - IETF stream) rfc7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC) (Informational - Independent Submission Editor stream) rfc7929: DNS-Based Authentication of Named Entities (DANE) Bindings for OpenPGP (Experimental - IETF stream) rfc5509: Internet Assigned Numbers Authority (IANA) Registration of Instant Messaging and Presence DNS SRV RRs for the Session Initiation Protocol (SIP) (Proposed Standard - IETF stream) draft-ietf-acme-acme: Automatic Certificate Management Environment (ACME) (None - IETF stream) rfc3921: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence (Proposed Standard - IETF stream) rfc6733: Diameter Base Protocol (Proposed Standard - IETF stream) draft-ietf-uta-mta-sts: SMTP MTA Strict Transport Security (MTA-STS) (None - IETF stream) rfc7553: The Uniform Resource Identifier (URI) DNS Resource Record (Informational - IETF stream) rfc7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1 (Proposed Standard - IETF stream) rfc7671: The DNS-Based Authentication of Named Entities (DANE) Protocol: Updates and Operational Guidance (Proposed Standard - IETF stream)
