DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates
draft-arends-dnsop-dnssec-algorithm-update-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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)
DNSOP                                                          R. Arends
Internet-Draft                                                     ICANN
Intended status: Standards Track                             J. Schlyter
Expires: September 13, 2017                                     Kirei AB
                                                               M. Larson
                                                                   ICANN
                                                          March 12, 2017

      DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates
             draft-arends-dnsop-dnssec-algorithm-update-00

Abstract

   The DNS Security Extensions (DNSSEC) require the use of cryptographic
   algorithm suites for generating digital signatures and cryptographic
   hashes over DNS data.  The algorithms specified for use with DNSSEC
   are reflected in IANA registries.  This document updates some entries
   in these registries.  The main reason for these updates is to retire
   the use of SHA1.

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 September 13, 2017.

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
   (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

Arends, et al.         Expires September 13, 2017               [Page 1]
Internet-Draft          DNSSEC Algorithm Updates              March 2017

   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.  Reserved Words  . . . . . . . . . . . . . . . . . . . . .   2
   2.  The DNS Security Algorithm Implementation Status Lists  . . .   2
     2.1.  Status Definitions  . . . . . . . . . . . . . . . . . . .   2
     2.2.  Algorithm Implementation Status Assignment Rationale  . .   3
     2.3.  DNSSEC Implementation Status Table  . . . . . . . . . . .   3
     2.4.  Specifying New Algorithms and Updating the Status of
           Existing Entries  . . . . . . . . . . . . . . . . . . . .   4
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Domain Name System (DNS) Security Extensions (DNSSEC, defined by
   [RFC4033], [RFC4034], [RFC4035], [RFC4509], [RFC5155], and [RFC5702])
   use digital signatures over DNS data to provide source authentication
   and integrity protection.  DNSSEC uses IANA registries to list codes
   for digital signature algorithms and hash functions.

   This document updates a set of entries in the IANA registries titled
   "DNS Security (DNSSEC) Algorithm Numbers" and "Delegation Signer (DS)
   Resource Record (RR) Type Digest Algorithms".

1.1.  Reserved Words

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  The DNS Security Algorithm Implementation Status Lists

2.1.  Status Definitions

   Must Implement: The algorithm MUST be implemented to interoperate
   with other implementations of this specification.
Show full document text