RFC 9189 on GOST Cipher Suites for Transport Layer Security (TLS) Protocol Version 1.2
rfc-editor@rfc-editor.org Mon, 14 March 2022 18:54 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 808BA3A118E
for <ietf-announce@ietfa.amsl.com>; Mon, 14 Mar 2022 11:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01,
URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id yHAxYYxgE_52 for <ietf-announce@ietfa.amsl.com>;
Mon, 14 Mar 2022 11:54:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id EF5B73A1177
for <ietf-announce@ietf.org>; Mon, 14 Mar 2022 11:54:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 499)
id 576E911C11A; Mon, 14 Mar 2022 11:54:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkxODkgb24gR09TVCBDaXBoZXIgU3VpdGVzIGZvciBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkgKFRMUykgUHJvdG9jb2wgVmVyc2lvbiAxLjI=?=
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: <20220314185446.576E911C11A@rfc-editor.org>
Date: Mon, 14 Mar 2022 11:54:46 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/W8P20zRcyTvsiJoBlfp4He2HUM8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2022 18:54:54 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9189
Title: GOST Cipher Suites for Transport
Layer Security (TLS) Protocol Version 1.2
Author: S. Smyshlyaev, Ed.,
D. Belyavsky,
E. Alekseev
Status: Informational
Stream: Independent
Date: March 2022
Mailbox: svs@cryptopro.ru,
beldmit@gmail.com,
alekseev@cryptopro.ru
Pages: 92
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-smyshlyaev-tls12-gost-suites-18.txt
URL: https://www.rfc-editor.org/info/rfc9189
DOI: 10.17487/RFC9189
This document specifies three new cipher suites, two new signature
algorithms, seven new supported groups, and two new certificate types
for the Transport Layer Security (TLS) protocol version 1.2 to
support the Russian cryptographic standard algorithms (called "GOST"
algorithms). This document specifies a profile of TLS 1.2 with GOST
algorithms so that implementers can produce interoperable
implementations.
This specification facilitates implementations that aim to support
the GOST algorithms. This document does not imply IETF endorsement of
the cipher suites, signature algorithms, supported groups, and
certificate types.
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