STD 70, RFC 5652 on Cryptographic Message Syntax (CMS) Wed, 11 August 2010 17:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F37BB3A679F; Wed, 11 Aug 2010 10:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -102.014
X-Spam-Status: No, score=-102.014 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MO3pKN91HoKl; Wed, 11 Aug 2010 10:45:55 -0700 (PDT)
Received: from ( [IPv6:2001:1890:1112:1::2f]) by (Postfix) with ESMTP id D6FB73A684B; Wed, 11 Aug 2010 10:45:24 -0700 (PDT)
Received: by (Postfix, from userid 30) id 11EB2E06B7; Wed, 11 Aug 2010 10:46:01 -0700 (PDT)
Subject: STD 70, RFC 5652 on Cryptographic Message Syntax (CMS)
Message-Id: <>
Date: Wed, 11 Aug 2010 10:46:01 -0700
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Aug 2010 17:45:56 -0000

RFC 5652 has been elevated to a Full Standard.

        STD 70        
        RFC 5652

        Title:      Cryptographic Message Syntax (CMS) 
        Author:     R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2009
        Pages:      56
        Characters: 126813
        Obsoletes:  RFC3852
        See Also:   STD0070

        I-D Tag:    draft-ietf-smime-rfc3852bis-00.txt


This document describes the Cryptographic Message Syntax (CMS).  This
syntax is used to digitally sign, digest, authenticate, or encrypt
arbitrary message content.  [STANDARDS TRACK]

This document is a product of the S/MIME Mail Security Working Group of the IETF.

This is now a 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
For downloading RFCs, see

Requests for special distribution should be addressed to either the
author of the RFC in question, or to  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC