RFC 8756 on Commercial National Security Algorithm (CNSA) Suite Profile of Certificate Management over CMS
rfc-editor@rfc-editor.org Fri, 27 March 2020 18:29 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 6A1923A0829 for <ietf-announce@ietfa.amsl.com>; Fri, 27 Mar 2020 11:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, 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 1jYJ9W_xyfgV for <ietf-announce@ietfa.amsl.com>; Fri, 27 Mar 2020 11:28:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C40CC3A07B3 for <ietf-announce@ietf.org>; Fri, 27 Mar 2020 11:28:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2D5E1F40725; Fri, 27 Mar 2020 11:28:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8756 on Commercial National Security Algorithm (CNSA) Suite Profile of Certificate Management over CMS
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20200327182847.2D5E1F40725@rfc-editor.org>
Date: Fri, 27 Mar 2020 11:28:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/CQtCMypUx8ji_V1ak_wJakPZF_s>
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: Fri, 27 Mar 2020 18:29:02 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8756
Title: Commercial National Security Algorithm (CNSA)
Suite Profile of Certificate Management over
CMS
Author: M. Jenkins,
L. Zieglar
Status: Informational
Stream: Independent
Date: March 2020
Mailbox: mjjenki@nsa.gov,
llziegl@tycho.ncsc.mil
Pages: 17
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-jenkins-cnsa-cmc-profile-05.txt
URL: https://www.rfc-editor.org/info/rfc8756
DOI: 10.17487/RFC8756
This document specifies a profile of the Certificate Management over
CMS (CMC) protocol for managing X.509 public key certificates in
applications that use the Commercial National Security Algorithm
(CNSA) Suite published by the United States Government.
The profile applies to the capabilities, configuration, and operation
of all components of US National Security Systems that manage X.509
public key certificates over CMS. It is also appropriate for all
other US Government systems that process high-value information.
The profile is made publicly available here 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