Re: [woes] Proposed JOSE Charter

"Paul C. Bryan" <paul.bryan@forgerock.com> Wed, 17 August 2011 18:29 UTC

Return-Path: <paul.bryan@forgerock.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 9C60D21F8B49 for <woes@ietfa.amsl.com>; Wed, 17 Aug 2011 11:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 1CTYRGgdvcTL for <woes@ietfa.amsl.com>; Wed, 17 Aug 2011 11:29:18 -0700 (PDT)
Received: from eu1sys200aog104.obsmtp.com (eu1sys200aog104.obsmtp.com [207.126.144.117]) by ietfa.amsl.com (Postfix) with SMTP id 9CAAF21F8B04 for <woes@ietf.org>; Wed, 17 Aug 2011 11:29:17 -0700 (PDT)
Received: from mail-pz0-f41.google.com ([209.85.210.41]) (using TLSv1) by eu1sys200aob104.postini.com ([207.126.147.11]) with SMTP ID DSNKTkwIousbDeEUxDhAgCA+M0eglJFrXycq@postini.com; Wed, 17 Aug 2011 18:30:09 UTC
Received: by pzk4 with SMTP id 4so1730069pzk.0 for <woes@ietf.org>; Wed, 17 Aug 2011 11:29:53 -0700 (PDT)
Received: by 10.142.50.19 with SMTP id x19mr19195wfx.340.1313605793058; Wed, 17 Aug 2011 11:29:53 -0700 (PDT)
Received: from [192.168.1.177] (S0106001346fbe4af.vf.shawcable.net [174.1.44.35]) by mx.google.com with ESMTPS id v2sm803362pbi.19.2011.08.17.11.29.52 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Aug 2011 11:29:52 -0700 (PDT)
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: woes@ietf.org
In-Reply-To: <60A80A8A-B8B5-461E-814B-7A243213995E@bbn.com>
References: <60A80A8A-B8B5-461E-814B-7A243213995E@bbn.com>
Content-Type: multipart/alternative; boundary="=-Zwo5b26p/ZAy4lE/XFwr"
Date: Wed, 17 Aug 2011 11:29:57 -0700
Message-ID: <1313605797.2410.26.camel@dynamo>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
Subject: Re: [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 18:29:19 -0000

+1

On Wed, 2011-08-17 at 13:34 -0400, Richard L. Barnes wrote:

> 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.
> 
> 
> _______________________________________________
> woes mailing list
> woes@ietf.org
> https://www.ietf.org/mailman/listinfo/woes