RFC 5272 on Certificate Management over CMS (CMC)
rfc-editor@rfc-editor.org Thu, 12 June 2008 00:22 UTC
Return-Path: <owner-ietf-pkix@mail.imc.org>
X-Original-To: ietfarch-pkix-archive@core3.amsl.com
Delivered-To: ietfarch-pkix-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2BC43A67A6 for <ietfarch-pkix-archive@core3.amsl.com>; Wed, 11 Jun 2008 17:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.9
X-Spam-Level:
X-Spam-Status: No, score=-16.9 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UPnzszKFpsTf for <ietfarch-pkix-archive@core3.amsl.com>; Wed, 11 Jun 2008 17:22:45 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 2F3053A67A4 for <pkix-archive@ietf.org>; Wed, 11 Jun 2008 17:22:44 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m5BNhQGB086143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2008 16:43:26 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id m5BNhQX0086142; Wed, 11 Jun 2008 16:43:26 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m5BNhO7t086130 for <ietf-pkix@imc.org>; Wed, 11 Jun 2008 16:43:25 -0700 (MST) (envelope-from rfc-editor@rfc-editor.org)
Received: by bosco.isi.edu (Postfix, from userid 70) id 55936136501; Wed, 11 Jun 2008 16:43:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5272 on Certificate Management over CMS (CMC)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ietf-pkix@imc.org
Message-Id: <20080611234324.55936136501@bosco.isi.edu>
Date: Wed, 11 Jun 2008 16:43:24 -0700
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
A new Request for Comments is now available in online RFC libraries.
RFC 5272
Title: Certificate Management over CMS (CMC)
Author: J. Schaad, M. Myers
Status: Standards Track
Date: June 2008
Mailbox: jimsch@nwlink.com, mmyers@fastq.com
Pages: 83
Characters: 167138
Obsoletes: RFC2797
I-D Tag: draft-ietf-pkix-2797-bis-07.txt
URL: http://www.rfc-editor.org/rfc/rfc5272.txt
This document defines the base syntax for CMC, a Certificate
Management protocol using the Cryptographic Message Syntax (CMS).
This protocol addresses two immediate needs within the Internet
Public Key Infrastructure (PKI) community:
1. The need for an interface to public key certification products
and services based on CMS and PKCS #10 (Public Key Cryptography
Standard), and
2. The need for a PKI enrollment protocol for encryption only keys
due to algorithm or hardware design.
CMC also requires the use of the transport document and the
requirements usage document along with this document for a full
definition. [STANDARDS TRACK]
This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 Internet
Official Protocol Standards (STD 1) 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
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
USC/Information Sciences Institute