[woes] Fwd: WG Review: Javascript Object Signing and Encryption (jose)

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 30 August 2011 23:01 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 1C64521F8E5D for <woes@ietfa.amsl.com>; Tue, 30 Aug 2011 16:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 VnbVLF7vmP3N for <woes@ietfa.amsl.com>; Tue, 30 Aug 2011 16:01:46 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1C05221F8E6B for <woes@ietf.org>; Tue, 30 Aug 2011 16:01:46 -0700 (PDT)
Received: from macbook-08.home (pool-173-54-49-237.nwrknj.fios.verizon.net [173.54.49.237]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p7UN3DJc022859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <woes@ietf.org>; Tue, 30 Aug 2011 16:03:14 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 30 Aug 2011 19:03:13 -0400
References: <20110830162837.9A99921F8B37@ietfa.amsl.com>
To: woes@ietf.org
Message-Id: <A0E3D9F2-40E3-4617-9338-B695A701929D@vpnc.org>
Mime-Version: 1.0 (Apple Message framework v1244.3)
X-Mailer: Apple Mail (2.1244.3)
Subject: [woes] Fwd: WG Review: Javascript Object Signing and Encryption (jose)
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: Tue, 30 Aug 2011 23:01:47 -0000

Begin forwarded message:

> From: IESG Secretary <iesg-secretary@ietf.org>
> Subject: WG Review: Javascript Object Signing and Encryption (jose) 
> Date: August 30, 2011 12:28:37 PM EDT
> To: IETF Announcement list <ietf-announce@ietf.org>
> Reply-To: iesg@ietf.org
> 
> A new IETF working group has been proposed in the Security Area.  The 
> IESG has not made any determination as yet. The following draft charter 
> was submitted, and is provided for informational purposes only. Please 
> send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, 
> September 6, 2011                            
> 
> Javascript Object Signing and Encryption (jose)
> =================================================
> Status: Proposed Working Group
> Last updated: 2011-08-18
> 
> Chairs
>    TBD
> 
> Security Area Directors:
>    Stephen Farrell <stephen.farrell@cs.tcd.ie>
>    Sean Turner <turners@ieca.com>
> 
> Security Area Advisor:
>    Sean Turner <turners@ieca.com>
> 
> Mailing Lists:
>   General Discussion: jose@ietf.org
>   To Subscribe: <https://www.ietf.org/mailman/listinfo/jose>
>   Archive: <http://www.ietf.org/mail-archive/web/jose/>
> 
> 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, 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 algorithm 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.
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce