RFC 5752 on Multiple Signatures in Cryptographic Message Syntax (CMS)

rfc-editor@rfc-editor.org Mon, 25 January 2010 18:19 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 []) by core3.amsl.com (Postfix) with ESMTP id C2CB628C0FE; Mon, 25 Jan 2010 10:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id dF7ffdJx17-d; Mon, 25 Jan 2010 10:19:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CEC6A28C108; Mon, 25 Jan 2010 10:19:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 11800E06BD; Mon, 25 Jan 2010 10:19:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5752 on Multiple Signatures in Cryptographic Message Syntax (CMS)
From: rfc-editor@rfc-editor.org
Message-Id: <20100125181929.11800E06BD@rfc-editor.org>
Date: Mon, 25 Jan 2010 10:19:29 -0800
Cc: smime@ietf.org, 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: Mon, 25 Jan 2010 18:19:24 -0000

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

        RFC 5752

        Title:      Multiple Signatures in Cryptographic Message 
                    Syntax (CMS) 
        Author:     S. Turner, J. Schaad
        Status:     Standards Track
        Date:       January 2010
        Mailbox:    turners@ieca.com, 
        Pages:      17
        Characters: 34502
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-smime-multisig-05.txt

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

Cryptographic Message Syntax (CMS) SignedData includes the SignerInfo
structure to convey per-signer information.  SignedData supports
multiple signers and multiple signature algorithms per signer with
multiple SignerInfo structures.  If a signer attaches more than one
SignerInfo, there are concerns that an attacker could perform a
downgrade attack by removing the SignerInfo(s) with the 'strong'
algorithm(s).  This document defines the multiple-signatures
attribute, its generation rules, and its processing rules to allow
signers to convey multiple SignerInfo objects while protecting against
downgrade attacks.  Additionally, this attribute may assist during
periods of algorithm migration.  [STANDARDS TRACK]

This document is a product of the S/MIME Mail Security 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@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