[jose] draft revision to JOSE charter

Karen O'Donoghue <odonoghue@isoc.org> Fri, 11 January 2013 20:02 UTC

Return-Path: <odonoghue@isoc.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 619CF21F8843 for <jose@ietfa.amsl.com>; Fri, 11 Jan 2013 12:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.265
X-Spam-Level:
X-Spam-Status: No, score=-103.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TcQ7DZt00E-o for <jose@ietfa.amsl.com>; Fri, 11 Jan 2013 12:02:56 -0800 (PST)
Received: from smtp158.dfw.emailsrvr.com (smtp158.dfw.emailsrvr.com [67.192.241.158]) by ietfa.amsl.com (Postfix) with ESMTP id 5327A21F87BA for <jose@ietf.org>; Fri, 11 Jan 2013 12:02:56 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp32.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id CF161505D9 for <jose@ietf.org>; Fri, 11 Jan 2013 15:02:55 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp32.relay.dfw1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 94205504A8 for <jose@ietf.org>; Fri, 11 Jan 2013 15:02:55 -0500 (EST)
Message-ID: <50F06FEE.9060207@isoc.org>
Date: Fri, 11 Jan 2013 15:02:54 -0500
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: jose@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [jose] draft revision to JOSE charter
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: odonoghue@isoc.org
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jose>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 20:02:57 -0000

Folks,

Below is a draft update to our charter based on discussions at the last 
IETF meeting. The key changes are adding key representations and 
algorithm identifiers to the scope of work. This includes some minor 
language updates in the general section, the addition of deliverables 
5-8, and the addition and modification of a number of milestones related 
to these documents.

In addition, the phrase "using a compact URL-safe representation" has 
been added to the descriptions of the first two deliverables and 
"compact JSON object" used in the milestones.

Jim and I will be submitting a revised charter shortly, and we would 
like your comments by 18 January if possible.

Thanks,
Karen


Description of Working Group

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, message authentication codes (MACs), and 
key representations 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 four kinds of security services, integrity protection 
(signature and MAC), encryption, key representations, and algorithm 
identifiers, 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 eight documents:

(1) A Standards Track document specifying how to apply JSON-structured 
integrity protection to data, including (but not limited to) JSON data 
structures, using a compact URL-safe representation.  "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, 
using a compact URL-safe representation.

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

(4) A Standards Track document specifying algorithms and algorithm 
identifiers, including mandatory-to-implement algorithms for the 
previous three documents.

(5) A Standards Track document specifying how to apply JSON-structured 
integrity protection to data, including (but not limited to) JSON data 
structures, using a JSON representation supporting multiple recipients.  
This document will build upon the concepts and structures in (1).

(6) A Standards Track document specifying how to apply a JSON-structured 
encryption to data, including (but not limited to) JSON data structures, 
using a JSON representation supporting multiple recipients.  This 
document will build upon the concepts and structures in (2).

(7) A Standards Track document specifying how to encode private and 
symmetric keys as JSON-structured objects.  This document will build 
upon the concepts and structures in (3).

(8) A Standards Track application document specifying a means of 
protecting private and symmetric keys via encryption.  This document 
will build upon the concepts and structures in (2) and (7).  This 
document may register additional algorithms in registries defined by (4).

The working group may decide to address combinations of these goals in 
consolidated document(s), in which case the concrete milestones for 
these goals will be satisfied by the consolidated document(s).

Goals and Milestones

Jan 2012              Submit compact JSON object integrity document (1) 
as a WG item.

Jan 2012              Submit compact JSON object encryption document (2) 
as a WG item.

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

Jan 2012              Submit JSON algorithm document (4) as a WG item.

Feb 2013              Start Working Group Last Call on compact JSON 
object integrity document (1).

Feb 2013              Start Working Group Last Call on compact JSON 
object encryption document (2).

Feb 2013              Start Working Group Last Call on JSON key format 
document (3).

Feb 2013              Start Working Group Last Call on JSON algorithm 
document (4).

Mar 2013             Submit JSON object integrity document (1) to IESG 
for consideration as Standards Track document.

Mar 2013             Submit JSON object encryption document (2) to IESG 
for consideration as Standards Track document.

Mar 2013             Submit JSON key format document (3) to IESG for 
consideration as Standards Track document.

Mar 2013             Submit JSON algorithm document (4) to IESG for 
consideration as Standards Track document.

Mar 2013             Submit multi-recipient JSON object integrity 
document (5) as a WG item.

Mar 2013             Submit multi-recipient JSON object encryption 
document (6) as a WG item.

Mar 2013             Submit JSON private and symmetric key document (7) 
as a WG item.

Mar 2013             Submit JSON key protection application document (8) 
as a WG item.

Jun 2013              Start Working Group Last Call on multi-recipient 
JSON object integrity document (5).

Jun 2013              Start Working Group Last Call on multi-recipient 
JSON object encryption document (6).

Jun 2013              Start Working Group Last Call on JSON private and 
symmetric key document (7).

Jun 2013              Start Working Group Last Call on JSON key 
protection application document (8).

Jul 2013               Submit multi-recipient JSON object integrity 
document (5) to IESG for consideration as Standards Track document.

Jul 2013               Submit multi-recipient JSON object encryption 
document (6) to IESG for consideration as Standards Track document.

Jul 2013               Submit JSON private and symmetric key document 
(7) to IESG for consideration as Standards Track document.

Jul 2013               Submit JSON key protection application document 
(8) to IESG for consideration as Standards Track document.