RFC 7165 on Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)
rfc-editor@rfc-editor.org Tue, 15 April 2014 04:58 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7E81A063F; Mon, 14 Apr 2014 21:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level:
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 W-TFspY5pqnS; Mon, 14 Apr 2014 21:58:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id BD2AF1A0304; Mon, 14 Apr 2014 21:58:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3282518000D; Mon, 14 Apr 2014 21:58:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7165 on Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140415045818.3282518000D@rfc-editor.org>
Date: Mon, 14 Apr 2014 21:58:18 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/IWe4kU-UDUfW2sRRI82lj_se1tI
Cc: drafts-update-ref@iana.org, jose@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 15 Apr 2014 04:58:44 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7165
Title: Use Cases and Requirements for
JSON Object Signing and Encryption (JOSE)
Author: R. Barnes
Status: Informational
Stream: IETF
Date: April 2014
Mailbox: rlb@ipv.sx
Pages: 25
Characters: 58324
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-jose-use-cases-06.txt
URL: http://www.rfc-editor.org/rfc/rfc7165.txt
Many Internet applications have a need for object-based security
mechanisms in addition to security mechanisms at the network layer or
transport layer. For many years, the Cryptographic Message Syntax
(CMS) has provided a binary secure object format based on ASN.1.
Over time, binary object encodings such as ASN.1 have become less
common than text-based encodings, such as the JavaScript Object
Notation (JSON). This document defines a set of use cases and
requirements for a secure object format encoded using JSON, drawn
from a variety of application security mechanisms currently in
development.
This document is a product of the Javascript Object Signing and Encryption Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
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