[COSE] RFC 9360 on CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates
rfc-editor@rfc-editor.org Thu, 16 February 2023 22:50 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B17C0C134912; Thu, 16 Feb 2023 14:50:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IDtSaKcBZN0i; Thu, 16 Feb 2023 14:50:23 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (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 7AD46C15270B; Thu, 16 Feb 2023 14:50:23 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 65CC74C096; Thu, 16 Feb 2023 14:50:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, cose@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230216225023.65CC74C096@rfcpa.amsl.com>
Date: Thu, 16 Feb 2023 14:50:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/9MAxnUNNyzv2qpMt8p3_ghyxvvs>
Subject: [COSE] RFC 9360 on CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>, <mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>, <mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2023 22:50:27 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9360
Title: CBOR Object Signing and Encryption (COSE):
Header Parameters for Carrying and
Referencing X.509 Certificates
Author: J. Schaad
Status: Standards Track
Stream: IETF
Date: February 2023
Pages: 12
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-cose-x509-09.txt
URL: https://www.rfc-editor.org/info/rfc9360
DOI: 10.17487/RFC9360
The CBOR Object Signing and Encryption (COSE) message structure uses
references to keys in general. For some algorithms, additional
properties are defined that carry parameters relating to keys as
needed. The COSE Key structure is used for transporting keys outside
of COSE messages. This document extends the way that keys can be
identified and transported by providing attributes that refer to or
contain X.509 certificates.
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