An Extension Language for the DNS
draft-levine-dnsextlang-09

Document Type Active Internet-Draft (individual)
Last updated 2016-09-30
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          J. Levine
Internet-Draft                                      Taughannock Networks
Intended status: Standards Track                                P. Vixie
Expires: April 3, 2017                                September 30, 2016

                   An Extension Language for the DNS
                       draft-levine-dnsextlang-09

Abstract

   Adding new RRTYPEs to the DNS has required that DNS servers and
   provisioning software be upgraded to support each new RRTYPE in
   Master files.  This document defines a DNS extension language
   intended to allow most new RRTYPEs to be supported by adding entries
   to configuration data read by the DNS software, with no software
   changes needed for each RRTYPE.

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 April 3, 2017.

Copyright Notice

   Copyright (c) 2016 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

Levine & Vixie            Expires April 3, 2017                 [Page 1]
Internet-Draft           DNS Extension Language           September 2016

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Typical usage . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Extension language syntax . . . . . . . . . . . . . . . . . .   3
     3.1.  Lexical structure . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Storage in the DNS  . . . . . . . . . . . . . . . . . . .   4
     3.3.  Storage in a file . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Stanza structure  . . . . . . . . . . . . . . . . . . . .   5
     3.5.  Field types . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  References - Normative  . . . . . . . . . . . . . . . . .  11
     7.2.  References - Informative  . . . . . . . . . . . . . . . .  11
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  12
     A.1.  Changes from -08 to -09 . . . . . . . . . . . . . . . . .  12
     A.2.  Changes from -07 to -08 . . . . . . . . . . . . . . . . .  12
     A.3.  Changes from -06 to -07 . . . . . . . . . . . . . . . . .  12
     A.4.  Changes from -05 to -06 . . . . . . . . . . . . . . . . .  12
     A.5.  Changes from -04 to -05 . . . . . . . . . . . . . . . . .  13
     A.6.  Changes from -03 to -04 . . . . . . . . . . . . . . . . .  13
     A.7.  Changes from -02 to -03 . . . . . . . . . . . . . . . . .  13
     A.8.  Changes from -01 to -02 . . . . . . . . . . . . . . . . .  13
     A.9.  Changes from -00 to -01 . . . . . . . . . . . . . . . . .  13
   Appendix B.  Descriptions of currently defined RRTYPEs  . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   The Domain Name System[RFC1034] [RFC1035] is designed to be
   extensible, with new record types, known as RRTYPEs, added as needed.
   While it is straightforward in principle to add a new RRTYPE, in
   practice it can be difficult due to the software changes needed to
   add the new RRTYPE to the master file format read by many
   authoritative DNS servers, and to the provisioning software used to
   create and update the master files or the local equivalent.

   While some new RRTYPEs, notably those for DNSSEC [RFC4033], require
Show full document text