RFC 5940 on Additional Cryptographic Message Syntax (CMS) Revocation Information Choices

rfc-editor@rfc-editor.org Thu, 19 August 2010 23:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF04E3A6A46 for <ietf-announce@core3.amsl.com>; Thu, 19 Aug 2010 16:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.059
X-Spam-Level:
X-Spam-Status: No, score=-102.059 tagged_above=-999 required=5 tests=[AWL=-0.059, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 6Nzz6jiOl2kl for <ietf-announce@core3.amsl.com>; Thu, 19 Aug 2010 16:21:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 182813A67EF for <ietf-announce@ietf.org>; Thu, 19 Aug 2010 16:21:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2BDB9E06DA; Thu, 19 Aug 2010 16:22:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5940 on Additional Cryptographic Message Syntax (CMS) Revocation Information Choices
From: rfc-editor@rfc-editor.org
Message-Id: <20100819232207.2BDB9E06DA@rfc-editor.org>
Date: Thu, 19 Aug 2010 16:22:07 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 19 Aug 2010 23:21:33 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5940

        Title:      Additional Cryptographic Message Syntax (CMS) 
                    Revocation Information Choices 
        Author:     S. Turner, R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2010
        Mailbox:    turners@ieca.com, 
                    housley@vigilsec.com
        Pages:      9
        Characters: 15127
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-turner-additional-cms-ri-choices-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5940.txt

The Cryptographic Message Syntax (CMS) allows revocation information
to be conveyed as part of the SignedData, EnvelopedData,
AuthenticatedData, and AuthEnvelopedData content types.  The
preferred format for revocation information is the Certificate
Revocation List (CRL), but an extension mechanism supports other
revocation information formats.  This document defines two additional
revocation information formats for Online Certificate Status Protocol
(OCSP) responses and Server-Based Certificate Validation Protocol
(SCVP) requests and responses.  [STANDARDS TRACK]

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
Association Management Solutions, LLC