RFC 8702 on Use of the SHAKE One-Way Hash Functions in the Cryptographic Message Syntax (CMS)

rfc-editor@rfc-editor.org Fri, 31 January 2020 22:07 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A9C241201E3; Fri, 31 Jan 2020 14:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id fskSojvC-0Kq; Fri, 31 Jan 2020 14:07:30 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9E16120BC1; Fri, 31 Jan 2020 14:07:29 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6461EF4071A; Fri, 31 Jan 2020 14:07:21 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3MDIgb24gVXNlIG9mIHRoZSBTSEFLRSBPbmUtV2F5IEhhc2ggRnVuY3Rpb25zIGluIHRoZSBDcnlwdG9ncmFwaGljIE1lc3NhZ2UgU3ludGF4IChDTVMp?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spasm@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200131220721.6461EF4071A@rfc-editor.org>
Date: Fri, 31 Jan 2020 14:07:21 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/auttjch8LEr0AP_e1kp-ESIg2hk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 31 Jan 2020 22:07:37 -0000

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

        RFC 8702

        Title:      Use of the SHAKE One-Way 
                    Hash Functions in the Cryptographic Message 
                    Syntax (CMS) 
        Author:     P. Kampanakis, 
                    Q. Dang
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2020
        Mailbox:    pkampana@cisco.com, 
        Pages:      16
        Updates:    RFC 3370

        I-D Tag:    draft-ietf-lamps-cms-shakes-18.txt

        URL:        https://www.rfc-editor.org/info/rfc8702

        DOI:        10.17487/RFC8702

This document updates the "Cryptographic Message Syntax (CMS)
Algorithms" (RFC 3370) and describes the conventions for using the
SHAKE family of hash functions in the Cryptographic Message Syntax as
one-way hash functions with the RSA Probabilistic Signature Scheme
(RSASSA-PSS) and Elliptic Curve Digital Signature Algorithm (ECDSA). 
The conventions for the associated signer public keys in CMS are also

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF.

This is now a Proposed Standard.

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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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 https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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