Deprecate usage of ECC-GOST within DNSSEC
draft-ietf-dnsop-must-not-ecc-gost-06

Network Working Group                                        W. Hardaker
Internet-Draft                                                   USC/ISI
Intended status: Standards Track                               W. Kumari
Expires: 22 November 2025                                         Google
                                                             21 May 2025

               Deprecate usage of ECC-GOST within DNSSEC
                 draft-ietf-dnsop-must-not-ecc-gost-06

Abstract

   This document retires the use of GOST R 34.10-2001 (mnemonic "ECC-
   GOST") within DNSSEC.

   RFC5933 (now historic) defined the use of GOST R 34.10-2001 and GOST
   R 34.11-94 algorithms with DNS Security Extensions (DNSSEC).  This
   document updates RFC5933 by deprecating the use of ECC-GOST.

   [RFC Editor: please remove this before publication: It is unclear if
   updating RFC5933 (a Historic document) is the correct thing to do or
   not.  We did it so that it shows up in Datatracker and similar, but
   this may be a mistake.  We are happy to change this if the RFC Editor
   / IESG / whoever thinks this is a bad idea.]

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 22 November 2025.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Hardaker & Kumari       Expires 22 November 2025                [Page 1]
Internet-Draft        MUST NOT DNSSEC with ECC-GOST             May 2025

   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 Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . .   3
   2.  Deprecating ECC-GOST algorithms in DNSSEC . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  Operational Considerations  . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .   5
   Appendix B.  Current algorithm usage levels . . . . . . . . . . .   5
   Appendix C.  Github Version of this document  . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The use of the GOST R 34.10-2001 and GOST R 34.11-94 algorithms with
   the DNS Security Extensions (DNSSEC) [RFC9364] was documented in
   [RFC5933].  These two algorithms were deprecated by the Orders of the
   Federal Agency for Technical Regulation and Metrology of Russia
   (Rosstandart) in August 2012, and were superseded by GOST 34.10-2012
   and GOST 34.11-2012 respectively.  The use of GOST 34.10-2012 and
   GOST 34.11-2012 in DNSSEC is documented in [RFC9558], and so
   [RFC5933] has been made Historic.

   Thus, the use of GOST R 34.10-2001 (mnemonic GOST-ECC) and GOST R
   34.11-94 is no longer recommended for use in DNSSEC [RFC9364].

   Note that this document does not change or discuss the use of GOST
   34.10-2012 and GOST 34.11-2012.

Hardaker & Kumari       Expires 22 November 2025                [Page 2]
Internet-Draft        MUST NOT DNSSEC with ECC-GOST             May 2025

1.1.  Requirements notation

   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.  Deprecating ECC-GOST algorithms in DNSSEC

   The GOST R 34.11-94 [RFC5933] algorithm MUST NOT be used when
   creating DS records.  Validating resolvers MUST treat GOST R 34.11-94
   DS records as insecure.  If no other DS records of accepted
   cryptographic algorithms are available, the DNS records below the
   delegation point MUST be treated as insecure.

   The ECC-GOST [RFC5933] algorithm MUST NOT be used when creating
   DNSKEY and RRSIG records.  Validating resolvers MUST treat RRSIG
   records created from DNSKEY records using these algorithms as an
   unsupported algorithm.  If no other RRSIG records of accepted
   cryptographic algorithms are available, the validating resolver MUST
   consider the associated resource records as insecure.

3.  Security Considerations

   This document potentially increases the security of the DNSSEC
   ecosystem by deprecating algorithms that are no longer recommended
   for use.

4.  Operational Considerations

   This document removes support for ECC-GOST.  Zone operators currently
   making use of ECC-GOST based algorithms should switch to algorithms
   that remain supported.  DNS registries should prohibit their clients
   from uploading and publishing ECC-GOST based DS records to ensure
   that they are using algorithms which are supported by DNSSEC
   validators, and so can be DNSSEC validated.

5.  IANA Considerations

   [Note to IANA, to be removed by the RFC Editor: the registry fields
   listed above will be created by draft-ietf-dnsop-rfc8624-bis.]

Hardaker & Kumari       Expires 22 November 2025                [Page 3]
Internet-Draft        MUST NOT DNSSEC with ECC-GOST             May 2025

   IANA is requested to set the "Use for DNSSEC Signing", "Use for
   DNSSEC Validation", "Implement for DNSSEC Signing", and "Implement
   for DNSSEC Validation" columns of the DNS Security Algorithm Numbers
   registry [DNSKEY-IANA] [draft-ietf-dnsop-rfc8624-bis] for ECC-GOST
   (12) to MUST NOT.  Note that previously the "Use for DNSSEC Signing"
   and "Implement for DNSSEC Delegation" columns were already MUST NOT.

   IANA is requested to set the "Use for DNSSEC Delegation", "Use for
   DNSSEC Validation", "Implement for DNSSEC Delegation", and "Implement
   for DNSSEC Validation" columns of the "Digest Algorithms" registry
   [DS-IANA] for GOST R 34.11-94 (3) to MUST NOT.  Note that previously
   the "Use for DNSSEC Signing" and "Implement for DNSSEC Delegation"
   columns were already MUST NOT.

6.  References

6.1.  Normative References

   [DNSKEY-IANA]
              IANA, "Domain Name System Security (DNSSEC) Algorithm
              Numbers", n.d., <https://www.iana.org/assignments/dns-sec-
              alg-numbers/dns-sec-alg-numbers.xhtml>.

   [draft-ietf-dnsop-rfc8624-bis]
              W., K., "DNS Security Algorithm Numbers", n.d.,
              <https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-
              rfc8624-bis>.

   [DS-IANA]  IANA, "Delegation Signer (DS) Resource Record (RR) Type
              Digest Algorithms", n.d.,
              <http://www.iana.org/assignments/ds-rr-types>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/rfc/rfc2119>.

   [RFC5933]  Dolmatov, V., Ed., Chuprina, A., and I. Ustinov, "Use of
              GOST Signature Algorithms in DNSKEY and RRSIG Resource
              Records for DNSSEC", RFC 5933, DOI 10.17487/RFC5933, July
              2010, <https://www.rfc-editor.org/rfc/rfc5933>.

   [RFC9364]  Hoffman, P., "DNS Security Extensions (DNSSEC)", BCP 237,
              RFC 9364, DOI 10.17487/RFC9364, February 2023,
              <https://www.rfc-editor.org/rfc/rfc9364>.

6.2.  Informative References

Hardaker & Kumari       Expires 22 November 2025                [Page 4]
Internet-Draft        MUST NOT DNSSEC with ECC-GOST             May 2025

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.

   [RFC9558]  Makarenko, B. and V. Dolmatov, Ed., "Use of GOST 2012
              Signature Algorithms in DNSKEY and RRSIG Resource Records
              for DNSSEC", RFC 9558, DOI 10.17487/RFC9558, April 2024,
              <https://www.rfc-editor.org/rfc/rfc9558>.

Appendix A.  Acknowledgments

   The authors appreciate the comments and suggestions from the
   following IETF participants in helping produce this document: Mark
   Andrews, Steve Crocker, Brian Dickson, Thomas Graf, Russ Housely,
   Shumon Huque, Paul Hoffman, S Moonesamy, Peter Dickson, Peter
   Thomassen, Stefan Ubbink, Paul Wouters, Tim Wicinski, and the many
   members of the DNSOP working group that discussed this draft.

Appendix B.  Current algorithm usage levels

   The DNSSEC scanning project by Viktor Dukhovni and Wes Hardaker
   highlights the current deployment of various algorithms on the
   https://stats.dnssec-tools.org/ website.

   <RFC Editor: please delete this section upon publication>

Appendix C.  Github Version of this document

   While this document is under development, it can be viewed, tracked,
   fill here:

   https://github.com/hardaker/draft-hardaker-dnsop-must-not-gost

   <RFC Editor: please delete this section upon publication>

Authors' Addresses

   Wes Hardaker
   USC/ISI
   Email: ietf@hardakers.net

   Warren Kumari
   Google
   Email: warren@kumari.net

Hardaker & Kumari       Expires 22 November 2025                [Page 5]