[rfc-dist] RFC 9212 on Commercial National Security Algorithm (CNSA) Suite Cryptography for Secure Shell (SSH)
rfc-editor@rfc-editor.org Tue, 15 March 2022 01:50 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A603A1655 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 14 Mar 2022 18:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level:
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ZcdN1ObqRWYs for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 14 Mar 2022 18:50:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95C003A16A9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 14 Mar 2022 18:50:45 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E69D95BEB7B; Mon, 14 Mar 2022 18:50:44 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 499) id 774C51E642; Mon, 14 Mar 2022 18:50: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
Message-Id: <20220315015043.774C51E642@rfc-editor.org>
Date: Mon, 14 Mar 2022 18:50:43 -0700
Subject: [rfc-dist] RFC 9212 on Commercial National Security Algorithm (CNSA) Suite Cryptography for Secure Shell (SSH)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9212
Title: Commercial National Security Algorithm (CNSA)
Suite Cryptography for Secure Shell (SSH)
Author: N. Gajcowski,
M. Jenkins
Status: Informational
Stream: Independent
Date: March 2022
Mailbox: nhgajco@uwe.nsa.gov,
mjjenki@cyber.nsa.gov
Pages: 10
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-gajcowski-cnsa-ssh-profile-07.txt
URL: https://www.rfc-editor.org/info/rfc9212
DOI: 10.17487/RFC9212
The United States Government has published the National Security
Agency (NSA) Commercial National Security Algorithm (CNSA) Suite,
which defines cryptographic algorithm policy for national security
applications. This document specifies the conventions for using the
United States National Security Agency's CNSA Suite algorithms with
the Secure Shell Transport Layer Protocol and the Secure Shell
Authentication Protocol. It applies to the capabilities,
configuration, and operation of all components of US National
Security Systems (described in NIST Special Publication 800-59) that
employ Secure Shell (SSH). This document is also appropriate for all
other US Government systems that process high-value information. It
is made publicly available for use by developers and operators of
these and any other system deployments.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org