RFC 9942 on CBOR Object Signing and Encryption (COSE) Receipts
rfc-editor@rfc-editor.org Tue, 30 June 2026 22:44 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-fbb6f4d95-pnwrp (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 2B23710B300C2; Tue, 30 Jun 2026 15:44:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782859484; bh=op2K1dFdT6k77MdwAnKO+2n9i6k50pSxfMWnHjMBG4M=; h=Subject:From:To:Cc:Date; b=rkfuKG6P781bQRYA+qTleBMiI/Jzcr2T1i1uIPH/+Hkb40HJIS3rFOMh8eeZRENY/ vcZWPxc+abLufq/UzBMybmeTxlULBlPckvlKgq/FNWOsT7v5IJhJ8ojWW4qS2SYBko rgkJJyHPvGnBIPa4PRT9nY+OlLNlglG7ESHW1Pyc=
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: RFC 9942 on CBOR Object Signing and Encryption (COSE) Receipts
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Date: Tue, 30 Jun 2026 22:44:44 -0000
message-id: <178285948391.11.14604467919400066829@rfc-editor.org>
Message-ID-Hash: ADCIE2YX6UVWPIE5OGC4YFOCQIBZYDOY
X-Message-ID-Hash: ADCIE2YX6UVWPIE5OGC4YFOCQIBZYDOY
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/Ey5wy3nI4Kk9aDHZzLL48_83q4w>
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 9942
Title: CBOR Object Signing and Encryption (COSE) Receipts
Author: O. Steele,
H. Birkholz,
A. Delignat-Lavaud,
C. Fournet
Status: Proposed Standard
Stream: IETF
Date: June 2026
Mailbox: orie@or13.io,
henk.birkholz@ietf.contact,
antdl@microsoft.com,
fournet@microsoft.com
Pages: 20
I-D Tag: draft-ietf-cose-merkle-tree-proofs-18
URL: https://www.rfc-editor.org/info/rfc9942
DOI: 10.17487/RFC9942
CBOR Object Signing and Encryption (COSE) Receipts prove properties of a Verifiable Data Structure (VDS) to a verifier. VDSs and associated Proof Types enable security properties, such as minimal disclosure, transparency, and non-equivocation. Transparency helps maintain trust over time and has been applied to certificates, end-to-end encrypted messaging systems, and supply chain security. This specification enables concise transparency-oriented systems by building on Concise Binary Object Representation (CBOR) and COSE. The extensibility of the approach is demonstrated by providing CBOR encodings for Merkle inclusion and consistency proofs.
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