RFC 9044 on Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)

rfc-editor@rfc-editor.org Tue, 08 June 2021 22:56 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 F1B5E3A0DE1; Tue, 8 Jun 2021 15:56:50 -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 vjztackytEZ1; Tue, 8 Jun 2021 15:56:46 -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 4A93C3A0E4A; Tue, 8 Jun 2021 15:56:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9AC06F4073A; Tue, 8 Jun 2021 15:56:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9044 on Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)
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: <20210608225615.9AC06F4073A@rfc-editor.org>
Date: Tue, 08 Jun 2021 15:56:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/4Pd90hNhOFwVDOEvpxMSVJMPYVE>
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: Tue, 08 Jun 2021 22:56:57 -0000

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

        
        RFC 9044

        Title:      Using the AES-GMAC Algorithm with 
                    the Cryptographic Message Syntax (CMS) 
        Author:     R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2021
        Mailbox:    housley@vigilsec.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lamps-cms-aes-gmac-alg-05.txt

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

        DOI:        10.17487/RFC9044

This document specifies the conventions for using the AES-GMAC
Message Authentication Code algorithm with the Cryptographic Message
Syntax (CMS) as specified in RFC 5652.

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