RFC 9709 on Encryption Key Derivation in the Cryptographic Message Syntax (CMS) Using HKDF with SHA-256

rfc-editor@rfc-editor.org Fri, 10 January 2025 21:44 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A6CBC14F6B5; Fri, 10 Jan 2025 13:44:43 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id D86A021D1BC; Fri, 10 Jan 2025 13:44:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9709 on Encryption Key Derivation in the Cryptographic Message Syntax (CMS) Using HKDF with SHA-256
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250110214442.D86A021D1BC@rfcpa.rfc-editor.org>
Date: Fri, 10 Jan 2025 13:44:42 -0800
Message-ID-Hash: 6QXHAAP2SFBGHIYOSLJ2LHMADIRRHGVF
X-Message-ID-Hash: 6QXHAAP2SFBGHIYOSLJ2LHMADIRRHGVF
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spasm@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Ltx6RI0zVFh0m3x2MhfmRftmcgw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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

        
        RFC 9709

        Title:      Encryption Key Derivation in the 
                    Cryptographic Message Syntax (CMS) Using HKDF 
                    with SHA-256 
        Author:     R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2025
        Mailbox:    housley@vigilsec.com
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lamps-cms-cek-hkdf-sha256-05.txt

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

        DOI:        10.17487/RFC9709

This document specifies the derivation of the content-encryption key
or the content-authenticated-encryption key in the Cryptographic
Message Syntax (CMS) using the HMAC-based Extract-and-Expand Key
Derivation Function (HKDF) with SHA-256. The use of this mechanism
provides protection against an attacker that manipulates the
content-encryption algorithm identifier or the
content-authenticated-encryption algorithm identifier.

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