RFC 9921 on CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161

rfc-editor@rfc-editor.org Fri, 27 February 2026 01:55 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
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 mail2.ietf.org (Postfix) with ESMTPS id A03E0BF2CAD2; Thu, 26 Feb 2026 17:55:25 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 91152C000CC4; Thu, 26 Feb 2026 17:55:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9921 on CBOR Object Signing and Encryption (COSE) Header Parameter for Timestamp Tokens as Defined in RFC 3161
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260227015525.91152C000CC4@rfcpa.rfc-editor.org>
Date: Thu, 26 Feb 2026 17:55:25 -0800
Message-ID-Hash: UE72DFDY2KG5IQROIMZOWYSOY3UCQUJH
X-Message-ID-Hash: UE72DFDY2KG5IQROIMZOWYSOY3UCQUJH
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, 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/C_n20vZK0LlYMPDe-WtT1STRvSU>
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 9921

        Title:      CBOR Object Signing and Encryption (COSE)
                    Header Parameter for Timestamp Tokens 
                    as Defined in RFC 3161 
        Author:     H. Birkholz,
                    T. Fossati,
                    M. Riechert
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2026
        Mailbox:    henk.birkholz@ietf.contact,
                    thomas.fossati@linaro.org,
                    maik.riechert@microsoft.com
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cose-tsa-tst-header-parameter-08.txt

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

        DOI:        10.17487/RFC9921

This document defines two CBOR Object Signing and Encryption (COSE)
header parameters for incorporating timestamping based on RFC 3161
into COSE message structures (COSE_Sign and COSE_Sign1). This enables 
the use of established timestamping infrastructure per RFC 3161 in 
COSE-based protocols.

This document is a product of the CBOR Object Signing and Encryption 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