[rfc-i] Fwd: Re: RFC 5274 on Certificate Managmement Messages over CMS (CMC): Complience Requirements
paul.hoffman at vpnc.org
Thu Jun 12 09:24:04 PDT 2008
Forwarded from the PKIX WG mailing list.
>X-Authentication-Warning: balder-227.proper.com: majordom set sender
>to owner-ietf-pkix at mail.imc.org using -f
>From: Yoav Nir <ynir at checkpoint.com>
>To: ietf-pkix at imc.org
>Subject: Re: RFC 5274 on Certificate Managmement Messages over CMS
>(CMC): Complience Requirements
>Date: Thu, 12 Jun 2008 08:17:14 +0300
>X-Mailer: Apple Mail (2.924)
>Sender: owner-ietf-pkix at mail.imc.org
>List-Unsubscribe: <mailto:ietf-pkix-request at imc.org?body=unsubscribe>
>Well, at least the real RFC doesn't have the spelling mistakes.
>On Jun 12, 2008, at 2:43 AM, rfc-editor at rfc-editor.org wrote:
>>A new Request for Comments is now available in online RFC libraries.
>> RFC 5274
>> Title: Certificate Managmement Messages over CMS
>> (CMC): Complience Requirements
>> Author: J. Schaad, M. Myers
>> Status: Standards Track
>> Date: June 2008
>> Mailbox: jimsch at nwlink.com, mmyers at fastq.com
>> Pages: 13
>> Characters: 27380
>> Updates/Obsoletes/SeeAlso: None
>> I-D Tag: draft-ietf-pkix-cmc-compl-05.txt
>> URL: http://www.rfc-editor.org/rfc/rfc5274.txt
>>This document provides a set of compliance statements about the CMC
>>(Certificate Management over CMS) enrollment protocol. The ASN.1
>>structures and the transport mechanisms for the CMC enrollment
>>protocol are covered in other documents. This document provides the
>>information needed to make a compliant version of CMC. [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
>>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 at rfc-editor.org.
>>specifically noted otherwise on the RFC itself, all RFCs are for
>>The RFC Editor Team
>>USC/Information Sciences Institute
>>Scanned by Check Point Total Security Gateway.
More information about the rfc-interest