Skip to main content

DNS Scoped Data Through Attribute Leaves
draft-crocker-dns-attrleaf-06

The information below is for an old version of the document.
Document Type This is an older version of an Internet-Draft whose latest revision is Replaced
Author Dave Crocker
Last updated 2012-04-15 (Latest revision 2011-10-13)
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 (None)
Formats
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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 associated with the parent domain. This note 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.)