Easy DNSSEC Key Publish
draft-kumari-ogud-dnsop-cds-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-02-18
Replaced by rfc7344, draft-ietf-dnsop-delegation-trust-maintainance
Stream (None)
Intended RFC status (None)
Formats plain text 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)
template                                                       W. Kumari
Internet-Draft                                                    Google
Intended status: Informational                            O. Gudmundsson
Expires: August 22, 2013                                   Shinkuro Inc.
                                                              G. Barwood
                                                       February 18, 2013

                        Easy DNSSEC Key Publish
                     draft-kumari-ogud-dnsop-cds-00

Abstract

   This document describes a method to allow DNS operators to more
   easily publish updated DNSSEC Key Signing Keys.  This document does
   not address the initial configuration of trust anchors for a domain.

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 August 22, 2013.

Copyright Notice

   Copyright (c) 2013 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Kumari, et al.           Expires August 22, 2013                [Page 1]
Internet-Draft                  ezkeyroll                  February 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . . . 3
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  CDS Resource Record Format  . . . . . . . . . . . . . . . . . . 4
   4.  CDS Behavior  . . . . . . . . . . . . . . . . . . . . . . . . . 4
     4.1.  Periodic check by parental agent  . . . . . . . . . . . . . 5
   5.  Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     5.1.  Going unsigned  . . . . . . . . . . . . . . . . . . . . . . 6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . . . 7
     9.2.  Informative References  . . . . . . . . . . . . . . . . . . 7
   Appendix A.  Changes / Author Notes.  . . . . . . . . . . . . . . . 8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 8

Kumari, et al.           Expires August 22, 2013                [Page 2]
Internet-Draft                  ezkeyroll                  February 2013

1.  Introduction

   When a DNS operator first signs their zone they need to communicate
   their DS record(s) (or DNSKEY(s)) to their parent through some out of
   band method.  In many cases this is a fairly annoying and manual
   process.  Unfortunately, every time the child rolls their KSK (Key
   Signing Key) key they have to repeat the process, possibly multiple
   times.  As this is a manual process DNS operators often avoid rolling
   their keys, as they don't want to have to do go through the annoyance
   of publishing the new keys.

   This document describes a method to automate publication of
   subsequent DS records, after the initial one has been published.

   Readers are expected to be familiar with DNSSEC, including [RFC4033],
   [RFC4034], [RFC4035] and [RFC6781].

   This document is a compilation of two earlier drafts,
   draft-barwood-dnsop-ds-publish and draft-wkumari-dnsop-ezkeyroll

   This document outlines a technique in which the parent (often
   registrar / registry) periodically polls its signed children and
   automatically publish new DS records.  To a large extent the
   procedures this document follows are in [RFC6781] section 4.1.2

   This technique is in some ways similar to RFC 5011 style rollovers,
   but for subdomains instead of trust anchors
Show full document text