RFC 8230 on Using RSA Algorithms with CBOR Object Signing and Encryption (COSE) Messages
rfc-editor@rfc-editor.org Tue, 05 September 2017 20:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2B4C12895E for <ietf-announce@ietfa.amsl.com>; Tue, 5 Sep 2017 13:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzqmogOtxb0Q for <ietf-announce@ietfa.amsl.com>; Tue, 5 Sep 2017 13:40:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89710126B6D for <ietf-announce@ietf.org>; Tue, 5 Sep 2017 13:40:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 057ECB81341; Tue, 5 Sep 2017 13:40:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8230 on Using RSA Algorithms with CBOR Object Signing and Encryption (COSE) Messages
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170905204036.057ECB81341@rfc-editor.org>
Date: Tue, 05 Sep 2017 13:40:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/rv95KY3cnb-huUwgUDPG2D8BPz0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Sep 2017 20:40:42 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8230
Title: Using RSA Algorithms with
CBOR Object Signing and Encryption (COSE)
Messages
Author: M. Jones
Status: Standards Track
Stream: IETF
Date: September 2017
Mailbox: mbj@microsoft.com
Pages: 12
Characters: 21655
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-jones-cose-rsa-05.txt
URL: https://www.rfc-editor.org/info/rfc8230
DOI: 10.17487/RFC8230
The CBOR Object Signing and Encryption (COSE) specification defines
cryptographic message encodings using Concise Binary Object
Representation (CBOR). This specification defines algorithm
encodings and representations enabling RSA algorithms to be used for
COSE messages. Encodings are specified for the use of RSA
Probabilistic Signature Scheme (RSASSA-PSS) signatures, RSA
Encryption Scheme - Optimal Asymmetric Encryption Padding
(RSAES-OAEP) encryption, and RSA keys.
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