RFC 9679 on CBOR Object Signing and Encryption (COSE) Key Thumbprint

rfc-editor@rfc-editor.org Fri, 20 December 2024 22:13 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 C1B24C18870B; Fri, 20 Dec 2024 14:13:59 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 32F4C1E8EA4; Fri, 20 Dec 2024 14:13:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9679 on CBOR Object Signing and Encryption (COSE) Key Thumbprint
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20241220221359.32F4C1E8EA4@rfcpa.rfc-editor.org>
Date: Fri, 20 Dec 2024 14:13:59 -0800
Message-ID-Hash: BNAI4CGFA2EYKSXGTYQLWMQN65NQXJW7
X-Message-ID-Hash: BNAI4CGFA2EYKSXGTYQLWMQN65NQXJW7
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/jkhr9MJtGbbQBb7f6BdRNTaocTY>
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 9679

        Title:      CBOR Object Signing and Encryption 
                    (COSE) Key Thumbprint 
        Author:     K. Isobe,
                    H. Tschofenig,
                    O. Steele
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2024
        Mailbox:    isobekohei@gmail.com,
                    Hannes.Tschofenig@gmx.net,
                    orie@transmute.industries
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cose-key-thumbprint-06.txt

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

        DOI:        10.17487/RFC9679

This specification defines a method for computing a hash value over a
CBOR Object Signing and Encryption (COSE) Key. It specifies which
fields within the COSE Key structure are included in the
cryptographic hash computation, the process for creating a canonical
representation of these fields, and how to hash the resulting byte
sequence. The resulting hash value, referred to as a "thumbprint",
can be used to identify or select the corresponding key.

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