RFC 8933 on Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier Protection

rfc-editor@rfc-editor.org Fri, 09 October 2020 22:28 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03AE63A1569; Fri, 9 Oct 2020 15:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yS0WRN316Km6; Fri, 9 Oct 2020 15:28:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 896853A0EDB; Fri, 9 Oct 2020 15:28:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 659F8F406D5; Fri, 9 Oct 2020 15:28:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8933 on Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier Protection
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: <20201009222809.659F8F406D5@rfc-editor.org>
Date: Fri, 09 Oct 2020 15:28:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/1CCeDY4ZmJkVYzDpwmtpM8l96mM>
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, 09 Oct 2020 22:28:25 -0000

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

        
        RFC 8933

        Title:      Update to the Cryptographic Message 
                    Syntax (CMS) for Algorithm Identifier Protection 
        Author:     R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    housley@vigilsec.com
        Pages:      8
        Updates:    RFC 5652

        I-D Tag:    draft-ietf-lamps-cms-update-alg-id-protect-05.txt

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

        DOI:        10.17487/RFC8933

This document updates the Cryptographic Message Syntax (CMS)
specified in RFC 5652 to ensure that algorithm identifiers in
signed-data and authenticated-data content types are adequately
protected.

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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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