DNS Scoped Data Through "Underscore" Naming of Attribute Leaves
draft-ietf-dnsop-attrleaf-14

Document Type Active Internet-Draft (dnsop WG)
Last updated 2018-10-11 (latest revision 2018-10-10)
Replaces draft-crocker-dns-attrleaf
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews SECDIR, GENART will not review this version
Stream WG state Submitted to IESG for Publication
Document shepherd Benno Overeinder
Shepherd write-up Show (last changed 2018-07-21)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Warren Kumari
Send notices to "Tim Wicinski" <tjw.ietf@gmail.com>, Benno Overeinder <benno@NLnetLabs.nl>
IANA IANA review state IANA OK - Actions Needed
IANA action state None
dnsop                                                         D. Crocker
Internet-Draft                               Brandenburg InternetWorking
Intended status: Standards Track                        October 10, 2018
Expires: April 13, 2019

    DNS Scoped Data Through "Underscore" Naming of Attribute Leaves
                      draft-ietf-dnsop-attrleaf-14

Abstract

   Formally, any DNS resource record may occur under any domain name.
   However some services use an operational convention for defining
   specific interpretations of an RRset, by locating the records in a
   DNS branch, under the parent domain to which the RRset actually
   applies.  The top of this subordinate branch is defined by a naming
   convention that uses a reserved node name, which begins with an
   _underscore.  The underscored naming construct defines a semantic
   scope for DNS record types that are associated with the parent
   domain, above the underscored branch.  This specification explores
   the nature of this DNS usage and defines the "DNS Global Underscore
   Scoped Entry Registry" with IANA.  The purpose of the Underscore
   registry is to avoid collisions resulting from the use of the same
   underscore-based name, for different services.

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 https://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 April 13, 2019.

Copyright Notice

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

Crocker                  Expires April 13, 2019                 [Page 1]
Internet-Draft                DNS AttrLeaf                  October 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Underscore Scoping  . . . . . . . . . . . . . . . . . . .   3
     1.2.  Scaling Benefits  . . . . . . . . . . . . . . . . . . . .   4
     1.3.  "Global" Underscored Node Names . . . . . . . . . . . . .   4
     1.4.  Interaction with DNS wildcards  . . . . . . . . . . . . .   5
   2.  DNS Underscore Scoped Entry Registries Function . . . . . . .   5
   3.  RRset Use Registration Template . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  DNS Underscore Global Scoped Entry Registry . . . . . . .   7
     4.2.  DNS Underscore Global Scoped Entry Registry Definition  .   8
     4.3.  Initial entries . . . . . . . . . . . . . . . . . . . . .   8
   5.  Guidance for Expert Review  . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  12
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The core Domain Name System (DNS) technical specifications assign no
   semantics to domain names or their parts, and no constraints upon
   which resource record (RR) types are permitted to be stored under
   particular names [RFC1035], [RFC2181].  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.  DNS data semantics have been
   limited to the specification of particular resource record types, on
   the expectation that new resource record types would be added as
   needed.  Unfortunately, the addition of new resource record types has
Show full document text