[rfc-dist] RFC 9558 on Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC

rfc-editor@rfc-editor.org Thu, 11 April 2024 16:23 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59013C14F5F5; Thu, 11 Apr 2024 09:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.95
X-Spam-Level:
X-Spam-Status: No, score=-3.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fo0ykckcfwqu; Thu, 11 Apr 2024 09:23:43 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F98AC14F697; Thu, 11 Apr 2024 09:23:43 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 05F9D51B905; Thu, 11 Apr 2024 09:23:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240411162343.05F9D51B905@rfcpa.amsl.com>
Date: Thu, 11 Apr 2024 09:23:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/L937nXmzOLgT_DCgcV-B04-zB10>
Subject: [rfc-dist] RFC 9558 on Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2024 16:23:47 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9558

        Title:      Use of GOST 2012 Signature Algorithms
                    in DNSKEY and RRSIG Resource 
                    Records for DNSSEC 
        Author:     B. Makarenko,
                    V. Dolmatov, Ed.
        Status:     Informational
        Stream:     Independent
        Date:       April 2024
        Mailbox:    bmakarenko@tcinet.ru,
                    vdolmatov@gmail.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-makarenko-gost2012-dnssec-05.txt

        URL:        https://www.rfc-editor.org/info/rfc9558

        DOI:        10.17487/RFC9558

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC