DNSSEC automation
draft-wisser-dnssec-automation-01

Document Type Active Internet-Draft (individual)
Authors Ulrich Wisser  , Shumon Huque 
Last updated 2021-02-22
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
On Agenda dnsop at IETF-110
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Domain Name System Operations (dnsop)                          U. Wisser
Internet-Draft                           The Swedish Internet Foundation
Intended status: Standards Track                                S. Huque
Expires: 25 August 2021                                       Salesforce
                                                        21 February 2021

                           DNSSEC automation
                   draft-wisser-dnssec-automation-01

Abstract

   This document describes an algorithm and a protocol to automate
   DNSSEC multi-signer [RFC8901] "Multi-Signer DNSSEC Models" setup,
   operations and decomissioning.  It primarily deals with Model 2 of
   the Multi-Signer specification, where each operator has their own
   distinct KSK and ZSK sets (or CSK sets).  It makes use of [RFC8078]
   "Managing DS Records from the Parent via CDS/CDNSKEY" and [RFC7477]
   "Child-to-Parent Synchronization in DNS" to accomplish this.

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 25 August 2021.

Copyright Notice

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

Wisser & Huque           Expires 25 August 2021                 [Page 1]
Internet-Draft              DNSSEC automation              February 2021

   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.  Out-Of-Scope  . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Notation  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Running a multi-signer setup  . . . . . . . . . . . . . .   3
     2.2.  Secure change of name server operator . . . . . . . . . .   3
   3.  Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Setting up a new multi-signer group . . . . . . . . . . .   4
     3.2.  Configuration . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  A new signer joins the multi-signer group . . . . . . . .   4
       3.3.1.  Prerequisites . . . . . . . . . . . . . . . . . . . .   4
       3.3.2.  Steps for joining . . . . . . . . . . . . . . . . . .   4
     3.4.  A signer leaves the multi-signer group  . . . . . . . . .   5
   4.  Automation  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Centralized . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Decentralized . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   [RFC8901] describes the necessary steps and API for a multi-signer
   DNSSEC configuration.  In this document we will combine [RFC8901]
   with [RFC8078] and [RFC7477] to define a fully automatable algorithm
   for setting up, operating and decomissioning of a multi-signer DNSSEC
   configuration.

   One of the special cases of multi-signer DNSSEC is actually the
   secure change of DNS operator.

Wisser & Huque           Expires 25 August 2021                 [Page 2]
Internet-Draft              DNSSEC automation              February 2021

1.1.  Out-Of-Scope

   In order for any multi-signer group to give consistent answers across
   all nameservers, the data contents of the zone also have to be
   synchronized (in addition to infrastructure records like NS, DNSKEY,
Show full document text