Deprecate Usage of ECC-GOST within DNSSEC USC/ISI
ietf@hardakers.net
Google
warren@kumari.net
OPS dnsop This document retires the use of GOST R 34.10-2001 (mnemonic "ECC-GOST") and GOST R 34.11-94 within DNSSEC. RFC 5933 (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 RFC 5933 by deprecating the use of ECC-GOST.
Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .
Copyright Notice Copyright (c) 2025 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 () 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
  • .  Introduction
    • .  Requirements Notation
  • .  Deprecating ECC-GOST Algorithms in DNSSEC
  • .  Security Considerations
  • .  Operational Considerations
  • .  IANA Considerations
  • .  References
    • .  Normative References
    • .  Informative References
  • Acknowledgments
  • Authors' Addresses
Introduction The GOST R 34.10-2001 and GOST R 34.11-94 algorithms are documented in and their use with DNS Security Extensions (DNSSEC) is further described in . 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 these two newer algorithms in DNSSEC is documented in , and their associated requirement levels are not changed by this document. Thus, the use of GOST R 34.10-2001 (mnemonic "ECC-GOST") and GOST R 34.11-94 is no longer recommended for use in DNSSEC .
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 when, and only when, they appear in all capitals, as shown here.
Deprecating ECC-GOST Algorithms in DNSSEC The GOST R 34.11-94 algorithm MUST NOT be used when creating Delegation Signer (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 GOST R 34.10-2001 algorithm (mnemonic "ECC-GOST") MUST NOT be used when creating DNS Public Key (DNSKEY) and Resource Record Signature (RRSIG) records. Validating resolvers MUST treat RRSIG records created from DNSKEY records using these algorithms as unsupported algorithms. If no other RRSIG records of accepted cryptographic algorithms are available, the validating resolver MUST consider the associated resource records as insecure.
Security Considerations This document potentially increases the security of the DNSSEC ecosystem by deprecating algorithms that are no longer recommended for use.
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 that are supported by DNSSEC validators and thus can be DNSSEC validated.
IANA Considerations IANA has updated the GOST R 34.10-2001 (12) entry in the "DNS Security Algorithm Numbers" registry as follows:
Number:
12
Description:
GOST R 34.10-2001 (DEPRECATED)
Mnemonic:
ECC-GOST
Zone Signing:
Y
Trans. Sec.:
*
Use for DNSSEC Signing:
MUST NOT
Use for DNSSEC Validation:
MUST NOT
Implement for DNSSEC Signing:
MUST NOT
Implement for DNSSEC Validation:
MUST NOT
Reference:
, Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic, and RFC 9906
Note: The "Use for DNSSEC Signing" and "Implement for DNSSEC Delegation" columns were already set to MUST NOT. IANA has updated the GOST R 34.11-94 (3) entry in the "Digest Algorithms" registry as follows:
Value:
3
Description:
GOST R 34.11-94 (DEPRECATED)
Use for DNSSEC Delegation:
MUST NOT
Use for DNSSEC Validation:
MUST NOT
Implement for DNSSEC Delegation:
MUST NOT
Implement for DNSSEC Validation:
MUST NOT
Reference:
, Change the status of GOST Signature Algorithms in DNSSEC in the IETF stream to Historic, and RFC 9906
Note: The "Use for DNSSEC Signing" and "Implement for DNSSEC Delegation" columns were already set to MUST NOT.
References Normative References DNS Security Algorithm Numbers IANA Digest Algorithms IANA Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Use of GOST Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC This document describes how to produce digital signatures and hash functions using the GOST R 34.10-2001 and GOST R 34.11-94 algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain Name System Security Extensions (DNSSEC). Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. DNS Security Extensions (DNSSEC) This document describes the DNS Security Extensions (commonly called "DNSSEC") that are specified in RFCs 4033, 4034, and 4035, as well as a handful of others. One purpose is to introduce all of the RFCs in one place so that the reader can understand the many aspects of DNSSEC. This document does not update any of those RFCs. A second purpose is to state that using DNSSEC for origin authentication of DNS data is the best current practice. A third purpose is to provide a single reference for other documents that want to refer to DNSSEC. DNSSEC Cryptographic Algorithm Recommendation Update Process USC/ISI Google Informative References Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC This document describes how to produce digital signatures and hash functions using the GOST R 34.10-2012 and GOST R 34.11-2012 algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain Name System Security Extensions (DNSSEC).
Acknowledgments The authors appreciate the comments and suggestions from the following IETF participants in helping produce this document: , , , , , , , , , , , , , and the many members of the DNSOP Working Group that discussed this specification.
Authors' Addresses USC/ISI
ietf@hardakers.net
Google
warren@kumari.net