Observations on Deploying New DNSSEC Cryptographic Algorithms
draft-york-dnsop-deploying-dnssec-crypto-algs-04

Document Type Active Internet-Draft (individual)
Last updated 2016-11-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)
DNSOP                                                            D. York
Internet-Draft                                          Internet Society
Intended status: Informational                                   O. Sury
Expires: May 18, 2017                                             CZ.NIC
                                                              P. Wouters
                                                                 Red Hat
                                                          O. Gudmundsson
                                                              CloudFlare
                                                       November 14, 2016

     Observations on Deploying New DNSSEC Cryptographic Algorithms
            draft-york-dnsop-deploying-dnssec-crypto-algs-04

Abstract

   As new cryptographic algorithms are developed for use in DNSSEC
   signing and validation, this document captures the steps needed for
   new algorithms to be deployed and enter general usage.  The intent is
   to ensure a common understanding of the typical deployment process
   and potentially identify opportunities for improvement of operations.

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 May 18, 2017.

Copyright Notice

   Copyright (c) 2016 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

York, et al.              Expires May 18, 2017                  [Page 1]
Internet-Draft      Deploying New DNSSEC Crypto Algs       November 2016

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Aspects of Deploying New Algorithms . . . . . . . . . . . . .   3
     2.1.  DNS Resolvers Performing Validation . . . . . . . . . . .   4
       2.1.1.  Resolvers and Unknown Algorithms  . . . . . . . . . .   4
     2.2.  Authoritative DNS Servers . . . . . . . . . . . . . . . .   5
     2.3.  Signing Software  . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Registries  . . . . . . . . . . . . . . . . . . . . . . .   6
     2.5.  Registrars  . . . . . . . . . . . . . . . . . . . . . . .   6
     2.6.  DNS Hosting Operators . . . . . . . . . . . . . . . . . .   7
     2.7.  Applications  . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   9
   Appendix B.  Changes  . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The DNS Security Extensions (DNSSEC), broadly defined in [RFC4033],
   [RFC4034] and [RFC4035], make use of cryptographic algorithms in both
   the signing of DNS records and the validation of DNSSEC signatures by
   recursive resolvers.

   The current list of cryptographic algorithms can be found in the IANA
   "Domain Name System Security (DNSSEC) Algorithm Numbers" registry
   located at <http://www.iana.org/assignments/dns-sec-alg-numbers/>
   Algorithms are added to this IANA registry through a process defined
   in [RFC6014].  Note that [RFC6944] provides some guidance as to which
Show full document text