Revised IANA Considerations for DNSSEC

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 10 April 2022.¶

Copyright Notice

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

DNSSEC is primarily described in [RFC4033], [RFC4034], and [RFC4035]. DNSSEC commonly uses another resource record beyond those defined in RFC 4034: NSEC3 [RFC5155]. DS resrouce records were originally defined in [RFC3658], and that definition was obsoleted by RFC 4034.¶

[RFC6014] updated the requirements for how DNSSEC cryptographic algorithm identifiers in the IANA registries are assigned, reducing the requirements from being "Standards Action" to "RFC Required". However, the IANA registry requirements for hash algorithms for DS records [RFC3658] and for the hash algorithms used in NSEC3 records [RFC5155] are still "Standards Action". This document updates those IANA registry requirements. (For reference on how IANA registries can be updated in general, see [RFC8126].)¶

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶

2. Update to RFC 6014

Section 4 updates RFC 6014 to bring the requirements for DS records and NSEC3 hash algorithms in line with the rest of the DNSSEC cryptographic algorithms by allowing any DS hash algorithms, NSEC3 hash algorithms, NSEC3 parameters, and NSEC3 flags that are fully described in an RFC to have identifiers assigned in the IANA registries. This is an addition to the IANA considerations in RFC 6014.¶

3. Update to RFC 8624

This document updates [RFC8624] for all DNSKEY and DS algorithms that are not on standards track.¶

The second paragraph of Section 1.2 of RFC 8624 currently says:¶

   This document only provides recommendations with respect to
   mandatory-to-implement algorithms or algorithms so weak that they
   cannot be recommended.  Any algorithm listed in the [DNSKEY-IANA]
   and [DS-IANA] registries that are not mentioned in this document
   MAY be implemented.  For clarification and consistency, an
   algorithm will be specified as MAY in this document only when it
   has been downgraded from a MUST or a RECOMMENDED to a MAY.

That paragraph is now replaced with the following:¶

   This document provides recommendations with respect to
   mandatory-to-implement algorithms, algorithms so weak that they
   cannot be recommended, and algorithms that are defined in RFCs
   that are not on standards track. Any algorithm listed in the
   [DNSKEY-IANA] and [DS-IANA] registries that are not mentioned in
   this document MAY be implemented. For clarification and
   consistency, an algorithm will be specified as MAY in this
   document only when it has been downgraded from a MUST or a
   RECOMMENDED to a MAY.

This update is also reflected in the IANA considerations in Section 4.¶

4. IANA Considerations

In the "Domain Name System Security (DNSSEC) NextSECure3 (NSEC3) Parameters" registry, the registration procedure for "DNSSEC NSEC3 Flags", "DNSSEC NSEC3 Hash Algorithms", and "DNSSEC NSEC3PARAM Flags" are changed from "Standards Action" to "RFC Required".¶

In the "Delegation Signer (DS) Resource Record (RR) Type Digest Algorithms" registry, the registration procedure for "Digest Algorithms" is changed from "Standards Action" to "RFC Required".¶

5. Security Considerations

Changing the requirements for getting security algorithms added to IANA registries as described in this document will make it easier to get good algorithms added to the registries, and will make it easier to get bad algorithms added to the registries. It is impossible to weigh the security impact of those two changes.¶

Administrators of DNSSEC-signed zones, and of validating resolvers, may have been making security decisions based on the contents of the IANA registries. This was a bad idea in the past, and now is an even worse idea because there will be more algorithms in those registries that may not have gone through IETF review. Security decisions about which algorithms are safe and not safe should be made by reading the security literature, not by looking in IANA registries.¶

Appendix A. Acknowledgements

Donald Eastlake, Murray Kucherawy, Dan Harkins, Martin Duke, and Benjamin Kaduk contributed to this document.¶

Author's Address