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 athttps://www.rfc-editor.org/info/rfc9906.¶

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 (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 GOST R 34.10-2001 and GOST R 34.11-94 algorithms are documented in[RFC5933] and their use with DNS Security Extensions (DNSSEC) is further described in[RFC9364]. These two algorithms were deprecated by the Orders of theFederal Agency for Technical Regulation and Metrology of Russia(Rosstandart) in August 2012 and were superseded by GOST 34.10-2012and GOST 34.11-2012, respectively. The use of these two neweralgorithms in DNSSEC is documented in[RFC9558], and their associatedrequirement levels are not changed by this document.¶

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

2.Deprecating ECC-GOST Algorithms in DNSSEC

The GOST R 34.11-94 algorithm[RFC5933]MUST NOT be used whencreating Delegation Signer (DS) records. Validating resolversMUST treat GOST R 34.11-94DS records as insecure. If no other DS records of acceptedcryptographic algorithms are available, the DNS records below the delegation pointMUST be treated as insecure.¶

The GOST R 34.10-2001 algorithm[RFC5933] (mnemonic "ECC-GOST")MUST NOT be used when creating DNS Public Key (DNSKEY) and Resource Record Signature (RRSIG) records. Validating resolversMUST treatRRSIG records created from DNSKEY records using these algorithms as unsupported algorithms. If no other RRSIG records of accepted cryptographicalgorithms are available, the validating resolverMUST consider theassociated resource records as insecure.¶

3.Security Considerations

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

4.Operational Considerations

This document removes support for ECC-GOST. Zone operators currently making useof ECC-GOST-based algorithms should switch to algorithms that remain supported.DNS registries should prohibit their clients from uploading and publishingECC-GOST-based DS records to ensure that they are using algorithms that aresupported by DNSSEC validators and thus can be DNSSEC validated.¶

5.IANA Considerations

IANA has updated the GOST R 34.10-2001 (12) entry in the "DNS Security Algorithm Numbers" registry[DNSKEY-IANA][RFC9904] 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:

[RFC5933],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 toMUST NOT.¶

IANA has updated the GOST R 34.11-94 (3) entry in the "Digest Algorithms" registry[DS-IANA] 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:

[RFC5933],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 toMUST NOT.¶

6.References

Acknowledgments

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

Authors' Addresses