DNS Attrleaf Changes: Fixing Specifications with Underscored Node Name Use
draft-ietf-dnsop-attrleaf-fix-05

Document Type Active Internet-Draft (dnsop WG)
Last updated 2018-10-11 (latest revision 2018-10-10)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text xml pdf html bibtex
Reviews 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 IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Warren Kumari
Send notices to Benno Overeinder <benno@NLnetLabs.nl>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
dnsop                                                         D. Crocker
Internet-Draft                               Brandenburg InternetWorking
Updates: 2782, 3263, 3404, 3529, 3620,                  October 10, 2018
         3832, 3861, 3887, 6121, 3958,
         4120, 4227, 4386, 4387, 4976,
         5026, 5328, 5389, 5415, 5518,
         5555, 5617, 5679, 5766, 5780,
         5804, 5864, 5928, 6011, 6120,
         6186, 6376, 6733, 6763, 7208,
         7489, 8145 (if approved)
Intended status: Standards Track
Expires: April 13, 2019

 DNS Attrleaf Changes: Fixing Specifications with Underscored Node Name
                                  Use
                    draft-ietf-dnsop-attrleaf-fix-05

Abstract

   Original uses of an underscore character as a domain node name
   prefix, which creates a space for constrained interpretation of
   resource records, were specified without the benefit of an IANA
   registry.  This produced an entirely uncoordinated set of name-
   creation activities, all drawing from the same namespace.  A registry
   now has been defined.  However the existing specifications that use
   underscore naming need to be modified, to be in line with the new
   registry.  This document specifies those changes.  The changes
   preserve existing software and operational practice, while adapting
   the specifications for those practices to the newer underscore
   registry model.

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.

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

Copyright Notice

   Copyright (c) 2018 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
   (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
   2.  Underscored RRset Use in Specifications . . . . . . . . . . .   3
     2.1.  TXT RRset Use . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  SRV RRset Use . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  URI RRset Use . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Underscored Template Specifications . . . . . . . . . . . . .   6
     3.1.  SRV Specification Changes . . . . . . . . . . . . . . . .   6
     3.2.  URI Specification Changes . . . . . . . . . . . . . . . .   7
     3.3.  DNSSEC Signaling Specification Changes  . . . . . . . . .   9
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     6.2.  References -- Informative . . . . . . . . . . . . . . . .  10
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  14
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Original uses of an underscore character as a domain node name
   [RFC1035] prefix, which creates a space for constrained
   interpretation of resource records, were specified without the
   benefit of an [IANA-reg] registry.  This produced an entirely
   uncoordinated set of name-creation activities, all drawing from the
   same namespace.  A registry has been now defined, and that document
   discusses the background for underscored domain name use [Attrleaf].

   The basic model for underscored name registration, as specified in
   [Attrleaf], is to have each registry entry be unique in terms of the
   combination of a resource record type and a 'global' (highest-level)

Crocker                  Expires April 13, 2019                 [Page 2]
Internet-Draft              DNS AttrLeaf Fix                October 2018
Show full document text