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

Document Type Active Internet-Draft (dnsop WG)
Last updated 2017-03-05
Replaces draft-crocker-dns-attrleaf
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd Tim Wicinski
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to "Tim Wicinski" <tjw.ietf@gmail.com>
Network Working Group                                         D. Crocker
Internet-Draft                               Brandenburg InternetWorking
Intended status: Best Current Practice                     March 5, 2017
Expires: September 6, 2017

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

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 6, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Crocker                 Expires September 6, 2017               [Page 1]
Internet-Draft                DNS AttrLeaf                    March 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Scaling Benefits and TXT and SRV Resource Records . . . . . .   3
   3.  Underscore DNS Registry Function  . . . . . . . . . . . . . .   4
   4.  DNS Underscore Registry Definition  . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Related and Updated Registries  . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  References -- Informative . . . . . . . . . . . . . . . .   9
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   ** This is merely a re-submission of the -00 version, to re-initiate
   discussion.  /Dave

   The core DNS technical specifications assign no semantics to domain
   names or their parts, and no constraints upon which resource records
   (RRs) are permitted to be associated with particular names.  Over
   time, some leaf node names, such as "www" and "ftp" have come to
   imply support for particular services, but this is a matter of
   operational convention, rather than defined protocol semantics .
   This freedom in the basic technology has permitted a wide range of
   administrative and semantic policies to be used -- in parallel.  Data
   semantics have been limited to the specification of particular
   resource records, on the expectation that new ones would be added as
   needed.

   As an alternative to defining new RRs, some DNS service enhancements
   have specified a restricted scope for the occurrence of particular
   resource records.  That scope is a leaf node, within which the uses
   of specific resource records can be formally defined and constrained.
   The leaf has a distinguished naming convention: It uses a reserved
   DNS node name that begins with an underscore ("_").  Because a "host"
   domain name is not allowed to use the underscore character, this
   distinguishes the name from all legal host names.[RFC1035]
   Effectively, this convention creates a space for attributes that are
Show full document text