[rfc-dist] RFC 9481 on Certificate Management Protocol (CMP) Algorithms
rfc-editor@rfc-editor.org Sun, 05 November 2023 15:36 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 F3855C013FF0; Sun, 5 Nov 2023 07:36:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.532
X-Spam-Level:
X-Spam-Status: No, score=0.532 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 zQuO64Tbut0O; Sun, 5 Nov 2023 07:36:30 -0800 (PST)
Received: from rfcpa.amsl.com (unknown [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 EFF08C3799CE; Sun, 5 Nov 2023 07:35:59 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id D78EF289F0; Sun, 5 Nov 2023 07:35:59 -0800 (PST)
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, spasm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231105153559.D78EF289F0@rfcpa.amsl.com>
Date: Sun, 05 Nov 2023 07:35:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/o9CWAeDjSDMW5jNOjWV_r7_XVgM>
Subject: [rfc-dist] RFC 9481 on Certificate Management Protocol (CMP) Algorithms
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: Sun, 05 Nov 2023 15:36:34 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9481 Title: Certificate Management Protocol (CMP) Algorithms Author: H. Brockhaus, H. Aschauer, M. Ounsworth, J. Gray Status: Standards Track Stream: IETF Date: November 2023 Mailbox: hendrik.brockhaus@siemens.com, hans.aschauer@siemens.com, mike.ounsworth@entrust.com, john.gray@entrust.com Pages: 28 Updates: RFC 4210 I-D Tag: draft-ietf-lamps-cmp-algorithms-15.txt URL: https://www.rfc-editor.org/info/rfc9481 DOI: 10.17487/RFC9481 This document describes the conventions for using several cryptographic algorithms with the Certificate Management Protocol (CMP). CMP is used to enroll and further manage the lifecycle of X.509 certificates. This document also updates the algorithm use profile from Appendix D.2 of RFC 4210. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. 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