RFC 9995 on CBOR Object Signing and Encryption (COSE) Hash Envelope

rfc-editor@rfc-editor.org Tue, 14 July 2026 03:37 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from celery-78f7859f6-lcn9z (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 1EBD011642D7C; Mon, 13 Jul 2026 20:37:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784000235; bh=gNfQ0Wecd06cDNP/DLt8w3F7zcHEc3rm7E+uctpE9Zg=; h=Subject:From:To:Cc:Date; b=qaZJJEEHY1TBG78yfsyzXcJepOceTSp/pHyXMNqUQDYYx/5c/3dpCUemlquvgPsFK 604jFaHDX8SAy1B8hWVA24rt//R+kgMkDc0ez/wVOuxO+Sw6Agz1L95ppfkQiE9834 LVRfmOE/CeqFWJoFw9gLRn3nLzqIbA6q2YPTDD5Y=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 9995 on CBOR Object Signing and Encryption (COSE) Hash Envelope
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Tue, 14 Jul 2026 03:37:15 -0000
message-id: <178400023497.14.13587933980689217049@rfc-editor.org>
Message-ID-Hash: RS3QSPMRLUGVUUYE3HOQRLFD7QYTAI4K
X-Message-ID-Hash: RS3QSPMRLUGVUUYE3HOQRLFD7QYTAI4K
X-MailFrom: rfc-editor@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: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, cose@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/mNhDaq2-6ty1SZPeF29lAMzSF6c>
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 9995

        Title:      CBOR Object Signing and Encryption (COSE) Hash Envelope
        Author:     O. Steele,
                    S. Lasker,
                    H. Birkholz
        Status:     Proposed Standard
        Stream:     IETF
        Date:       July 2026
        Mailbox:    orie@or13.io,
                    stevenlasker@hotmail.com,
                    henk.birkholz@ietf.contact
        Pages:      8

        I-D Tag:    draft-ietf-cose-hash-envelope-10

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

        DOI:        10.17487/RFC9995

This document defines new CBOR Object Signing and Encryption (COSE) header parameters for signaling a payload as an output of a hash function. This mechanism enables faster validation, as access to the original payload is not required for signature validation. Additionally, hints of the hashed payload's content format and availability are defined, providing references to optional discovery mechanisms that can help to find the original payload content.

This document is a product of the CBOR Object Signing and Encryption Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. 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/series/rfc-download/

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