Automating DNSSEC delegation trust maintenance
draft-kumari-ogud-dnsop-cds-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-02-25
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 27, 2013                                   Shinkuro Inc.
                                                              G. Barwood
                                                       February 25, 2013

             Automating DNSSEC delegation trust maintenance
                     draft-kumari-ogud-dnsop-cds-01

Abstract

   This document describes a method to allow DNS operators to more
   easily update DNSSEC Key Signing Keys using DNS as communication
   channel.  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 27, 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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1.  Requirements notation  . . . . . . . . . . . . . . . . . .  2

Kumari, Gudmundsson & BaExpires August 27, 2013                 [Page 1]
Internet-Draft        automating delegation maint          February 2013

   2.  Background . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  DNS delegations  . . . . . . . . . . . . . . . . . . . . .  3
     2.2.  DNSSEC key change process  . . . . . . . . . . . . . . . .  4
   3.  CDS Record . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  CDS Resource Record Format . . . . . . . . . . . . . . . .  5
     3.2.  CDS Behavior . . . . . . . . . . . . . . . . . . . . . . .  5
       3.2.1.  Periodic check by Parental Agent . . . . . . . . . . .  5
     3.3.  Usage  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
       3.3.1.  Going unsigned . . . . . . . . . . . . . . . . . . . .  6
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  7
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  7
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  7
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  8
   Appendix A. Changes / Author Notes.  . . . . . . . . . . . . . . .  8
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

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 to complete the chain of trust.  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 DS records at
   the parent.

   DNSSEC provides data integrity to information published in DNS, thus
   DNS publication can be used to automate maintenance of delegation
   information.  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], [RFC5011] and [RFC6781].

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