Change of Operator Procedures for Automatically Published DNSSEC Zones
draft-pounsett-transferring-automated-dnssec-zones-03

Document Type Active Internet-Draft (individual)
Last updated 2017-09-13
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                                        M. Pounsett
Internet-Draft                                     Rightside Group, Ltd.
Updates: 6781 (if approved)                           September 13, 2017
Intended status: Informational
Expires: March 17, 2018

 Change of Operator Procedures for Automatically Published DNSSEC Zones
         draft-pounsett-transferring-automated-dnssec-zones-03

Abstract

   Section 4.3.5.1 of [RFC6781] "DNSSEC Operational Practices, version
   2" describes a procedure for transitioning a DNSSEC signed zone from
   one (cooperative) operator to another.  The procedure works well in
   many situations, but makes the assumption that it is feasible for the
   two operators to simultaneously publish slightly different versions
   of the zone being transferred.  In some cases, such as with TLD
   registries, operational considerations require both operators to
   publish identical versions of the zone for the duration of the
   transition.  This document describes a modified transition procedure
   which can be used in these cases.

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 March 17, 2018.

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
   (https://trustee.ietf.org/license-info) in effect on the date of

Pounsett                 Expires March 17, 2018                 [Page 1]
Internet-Draft   Change of Operator for Automated Zones   September 2017

   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.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Changing Between Cooperating DNS Operators  . . . . . . . . .   3
     3.1.  Assumptions . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Procedure Overview  . . . . . . . . . . . . . . . . . . .   3
     3.3.  Procedure Notation  . . . . . . . . . . . . . . . . . . .   3
     3.4.  The Procedure . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Document Source  . . . . . . . . . . . . . . . . . .   7
   Appendix B.  Changelist . . . . . . . . . . . . . . . . . . . . .   7
     B.1.  Version pounsett-03 . . . . . . . . . . . . . . . . . . .   7
     B.2.  Version pounsett-02 . . . . . . . . . . . . . . . . . . .   7
     B.3.  Version pounsett-01 . . . . . . . . . . . . . . . . . . .   7
     B.4.  Version pounsett-00 . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The process described in "DNSSEC Operational Practices, version 2"
   ([RFC6781]), section 4.3.5.1 for cooperating DNS operators to move a
   DNSSEC signed zone cannot be followed in all cases.  When operators
   are moving a zone that is automatically published and/or changes
   rapidly, such as with a TLD or any other zone published from a
   registration database, it may not be feasible for the operators to
   publish different versions of the same zone.

   In these cases, it would be necessary for one or both operators to
   have the capability to add, remove, or alter arbitrary records inline
   along the zone transfer path (such as modifying the NSSet, and
   stripping RRSIGs).  It cannot be assumed that this capability exists,
   since few (if any) common DNS implementations include these
   functions, and many custom implementations exist whose feature sets
   cannot be predicted.

   As a result, it must be assumed that operators moving an
   automatically generated or frequently updated zone must be able to

Pounsett                 Expires March 17, 2018                 [Page 2]
Show full document text