Parent-side authoritative DNS records for enhanced delegation
draft-peetterr-dnsop-parent-side-auth-types-00

Document Type Active Internet-Draft (individual)
Authors Peter van Dijk  , Petr Spacek 
Last updated 2020-09-24
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized 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)
dnsop                                                        P. van Dijk
Internet-Draft                                                  PowerDNS
Intended status: Standards Track                               P. Spacek
Expires: 28 March 2021                                             CZNIC
                                                       24 September 2020

     Parent-side authoritative DNS records for enhanced delegation
             draft-peetterr-dnsop-parent-side-auth-types-00

Abstract

   A DNS RRtype numeric range that behaves like DS is reserved.  This
   means: being authoritative on the parent side of a delegation; being
   signed by the parent; being provided along with delegations by the
   parent.  If this document had become an RFC five years ago, deploying
   new types (along the lines of NS2/NS2T, DSPKI or various other
   imagined things like DNS ('signed delegation NS')) would be easier to
   deploy and experiment with today.

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 28 March 2021.

Copyright Notice

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

van Dijk & Spacek         Expires 28 March 2021                 [Page 1]
Internet-Draft           parent-side-auth-types           September 2020

   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.  Document work . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Conventions and Definitions . . . . . . . . . . . . . . . . .   3
   4.  Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Implementation  . . . . . . . . . . . . . . . . . . . . . . .   3
     5.1.  Authoritative server changes  . . . . . . . . . . . . . .   3
     5.2.  Validating resolver changes . . . . . . . . . . . . . . .   3
     5.3.  Stub resolver changes . . . . . . . . . . . . . . . . . .   4
     5.4.  Zone validator changes  . . . . . . . . . . . . . . . . .   4
     5.5.  Domain registry changes . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Implementation Status . . . . . . . . . . . . . . . . . . . .   4
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   5
   11. Informative References  . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Document history . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [RFC4035] defines the DS Resource Record, as a type with the special
   property that it lives at the parent side of a delegation, unlike any
   other record (if we can briefly ignore NSEC living on both sides of a
   delegation as an extra special case).  In various conversations and
   posted drafts in DPRIVE and DNSOP, a need to publish other kinds of
   data parent-side has been identified.  Some drafts simply proposed a
   new type, assuming that authoritative DNS servers and registry
   operations would eventually follow along; other drafts have tried to
   shoehorn new kinds of data into the DS record.  If, when DS was
   defined, or at any time since then, a range of RRtype numbers would
   have been specified to have the same behaviour as DS, those drafts,
   and the experiments that need to go with figuring out the exact
   definition of a protocol, would have been much more feasible.  This
   document requests that IANA allocate such a range.

van Dijk & Spacek         Expires 28 March 2021                 [Page 2]
Internet-Draft           parent-side-auth-types           September 2020
Show full document text