[woes] Proposed JOSE Charter

"Richard L. Barnes" <rbarnes@bbn.com> Wed, 17 August 2011 17:33 UTC

Return-Path: <rbarnes@bbn.com>
X-Original-To: woes@ietfa.amsl.com
Delivered-To: woes@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7D621F8BD5 for <woes@ietfa.amsl.com>; Wed, 17 Aug 2011 10:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.53
X-Spam-Level:
X-Spam-Status: No, score=-106.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPyLkGRKwq6P for <woes@ietfa.amsl.com>; Wed, 17 Aug 2011 10:33:59 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9A88B21F8B84 for <woes@ietf.org>; Wed, 17 Aug 2011 10:33:58 -0700 (PDT)
Received: from [192.1.255.224] (port=50359 helo=col-dhcp-192-1-255-224.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Qtk0p-0001N3-NA; Wed, 17 Aug 2011 13:34:43 -0400
From: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Aug 2011 13:34:41 -0400
Message-Id: <60A80A8A-B8B5-461E-814B-7A243213995E@bbn.com>
To: woes@ietf.org, Sean Turner <turners@ieca.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Subject: [woes] Proposed JOSE Charter
X-BeenThere: woes@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Web Object Encryption and Signing \(woes\) BOF discussion list" <woes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/woes>, <mailto:woes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/woes>
List-Post: <mailto:woes@ietf.org>
List-Help: <mailto:woes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2011 17:33:59 -0000

Dear ADs,

Please find below an updated charter proposal for a working group on JSON integrity and encryption.  Based on working group discussions, I believe there is consensus around the current text.  

Changes from <http://www.ietf.org/mail-archive/web/woes/current/msg00160.html>:
-- Moved milestone dates forward 5 months
-- Changed "signing" to "integrity protection", to encompass asymmetric and symmetric

Thanks,
--Richard




Javascript Object Signing and Encryption (jose)
=================================================

Background 
----------

Javascript Object Notation (JSON) is a text format for the serialization of structured data described in RFC 4627. The JSON format is often used for serializing and transmitting structured data over a network connection. With the increased usage of JSON in protocols in the IETF and elsewhere, there is now a desire to offer security services such as encryption, digital signatures, and message authentication codes (MACs) for data that is being carried in JSON format.

Different proposals for providing such security services have already been defined and implemented. This Working Group's task is to standardize two security services, integrity protection (signature and MAC) and encryption, in order to increase interoperability of security features between protocols that use JSON.  The Working Group will base its work on well-known message security primitives (e.g., CMS), and will solicit input from the rest of the IETF Security Area to be sure that the security functionality in the JSON format is correct.

This group is chartered to work on four documents:

1) A Standards Track document specifying how to apply JSON-structured integrity protection to data, including (but not limited to) JSON data structures.  "Integrity protection" includes public-key digital signatures as well as symmetric-key MACs.

2) A Standards Track document specifying how to apply a JSON-structured encryption to data, including (but not limited to) JSON data structures.

3) A Standards Track document specifying how to encode public keys as JSON-structured objects.

4) A Standards Track document specifying mandatory-to-implement algorithms for the other three documents.

The working group may decide to address one or more of these goals in a single document, in which case the concrete milestones for signing/encryption below will both be satisfied by the single document.

Goals and Milestones 
--------------------

Jan 2012    Submit JSON object integrity document as a WG item.

Jan 2012    Submit JSON object encryption document as a WG item.

Jan 2012    Submit JSON key format document as a WG item.

Jan 2012    Submit JSON algoritm document as a WG item.

Jun 2012    Start Working Group Last Call on JSON object integrity document.

Jun 2012    Start Working Group Last Call on JSON object encryption document.

Jun 2012    Start Working Group Last Call on JSON key format document.

Jun 2012    Start Working Group Last Call on JSON algorithm document.

Jul 2012    Submit JSON object integrity document to IESG for consideration as 
Standards Track document.

Jul 2012    Submit JSON object encryption document to IESG for consideration 
as Standards Track document.

Jul 2012    Submit JSON key format document to IESG for consideration 
as Standards Track document.

Jul 2012    Submit JSON algorithm document to IESG for consideration 
as Standards Track document.