DNS Scoped Data Through '_Underscore' Attribute Leaves
draft-ietf-dnsop-attrleaf-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (dnsop WG)
Author Dave Crocker 
Last updated 2016-09-16 (latest revision 2016-03-15)
Replaces draft-crocker-dns-attrleaf
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Additional Resources
- Mailing list discussion
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-00.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.)