DNS Scoped Data Through Global '_Underscore' Naming of Attribute Leaves
draft-ietf-dnsop-attrleaf-02

Document Type Expired Internet-Draft (dnsop WG)
Last updated 2017-09-30 (latest revision 2017-03-29)
Replaces draft-crocker-dns-attrleaf
Stream IETF
Intended RFC status Best Current Practice
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Tim Wicinski
IESG IESG state Expired
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to "Tim Wicinski" <tjw.ietf@gmail.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-dnsop-attrleaf-02.txt

Abstract

Formally, any DNS "RR" may occur for any domain name. However some services have defined an operational convention that applies to DNS leaf nodes that have a reserved node name, beginning with an underscore. The underscore construct is used to define a semantic scope for DNS records that are associated with the parent domain. This specification explores the nature of this DNS usage and defines the "DNS Global Underscore Scoped Entry Registry" registry with IANA.

Authors

Dave Crocker (dcrocker@bbiw.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)