DNS Scoped Data Through '_Underscore' Attribute Leaves
draft-crocker-dns-attrleaf-07

Document Type Replaced Internet-Draft (dnsop WG)
Last updated 2016-03-14 (latest revision 2015-11-14)
Replaced by draft-ietf-dnsop-attrleaf
Stream IETF
Intended RFC status Best Current Practice
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-dnsop-attrleaf
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)

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-crocker-dns-attrleaf-07.txt

Abstract

Historically, any DNS RR may occur for any domain name. Recent additions have defined DNS leaf nodes that contain 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 "underscore names" 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.)