RFC 9597 on CBOR Web Token (CWT) Claims in COSE Headers

rfc-editor@rfc-editor.org Tue, 25 June 2024 00:21 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 RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6CCBC1CAE98; Mon, 24 Jun 2024 17:21:04 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 282CA7FA79; Mon, 24 Jun 2024 17:21:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9597 on CBOR Web Token (CWT) Claims in COSE Headers
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240625002104.282CA7FA79@rfcpa.rfc-editor.org>
Date: Mon, 24 Jun 2024 17:21:04 -0700
Message-ID-Hash: 6IFWEML7EHNC2UAW252RGCMJLCONKIG4
X-Message-ID-Hash: 6IFWEML7EHNC2UAW252RGCMJLCONKIG4
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.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ANSpwh8U-A4jSGxhogkYlOOuiwg>
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 9597

        Title:      CBOR Web Token (CWT) Claims in COSE Headers 
        Author:     T. Looker,
                    M.B. Jones
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2024
        Mailbox:    tobias.looker@mattr.global,
                    michael_b_jones@hotmail.com
        Pages:      6
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cose-cwt-claims-in-headers-10.txt

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

        DOI:        10.17487/RFC9597

This document describes how to include CBOR Web Token (CWT) claims in
the header parameters of any CBOR Object Signing and Encryption
(COSE) structure. This functionality helps to facilitate applications
that wish to make use of CWT claims in encrypted COSE structures
and/or COSE structures featuring detached signatures, while having
some of those claims be available before decryption and/or without
inspecting the detached payload. Another use case is using CWT claims
with payloads that are not CWT Claims Sets, including payloads that
are not CBOR at all.

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
Association Management Solutions, LLC