Skip to main content

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

Document Type Replaced Internet-Draft (dnsop WG)
Author Dave Crocker
Last updated 2016-03-14 (Latest revision 2015-11-14)
Replaced by draft-ietf-dnsop-attrleaf, draft-ietf-dnsop-attrleaf, draft-ietf-dnsop-attrleaf, draft-ietf-dnsop-attrleaf, draft-ietf-dnsop-attrleaf, RFC 8552
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-dnsop-attrleaf, draft-ietf-dnsop-attrleaf
Consensus boilerplate Yes
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

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

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