Remove deprecated GOST algorithms from active use within 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 6 April 2025.¶

Copyright Notice

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

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 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.¶

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 increases the security of the DNSSEC ecosystem by deprecating algorithms that make use of older algorithms with ECC-GOST derived uses.¶

4. Operational Considerations

Zone owners currently making use of ECC-GOST based algorithms should immediate switch to algorithms with stronger cryptographic strengths. DNS registries [RFC9499] should prohibit their clients to upload and publish ECC-GOST based DS records.¶

5. IANA Considerations

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] for ECC-GOST (23) 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.¶

Appendix A. Acknowledgments

The authors appreciate the comments and suggestions from the following IETF participants in helping produce this document: Mark Andrews, Brian Dickson, Paul Wouters 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¶

Authors' Addresses