Re: [woes] Proposed JOSE Charter

Joe Hildebrand <joe.hildebrand@webex.com> Thu, 18 August 2011 07:19 UTC

Return-Path: <Joe.Hildebrand@webex.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 CDF3F5E8007 for <woes@ietfa.amsl.com>; Thu, 18 Aug 2011 00:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 qmXS2k44BK3T for <woes@ietfa.amsl.com>; Thu, 18 Aug 2011 00:19:37 -0700 (PDT)
Received: from gw1.webex.com (gw1.webex.com [64.68.122.208]) by ietfa.amsl.com (Postfix) with SMTP id E65085E8002 for <woes@ietf.org>; Thu, 18 Aug 2011 00:19:36 -0700 (PDT)
Received: from SRV-EXSC03.webex.local ([192.168.252.197]) by gw1.webex.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 18 Aug 2011 00:20:30 -0700
Received: from 10.21.118.126 ([10.21.118.126]) by SRV-EXSC03.webex.local ([192.168.252.200]) with Microsoft Exchange Server HTTP-DAV ; Thu, 18 Aug 2011 07:20:29 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Thu, 18 Aug 2011 00:20:28 -0700
From: Joe Hildebrand <joe.hildebrand@webex.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>, "woes@ietf.org" <woes@ietf.org>, Sean Turner <turners@ieca.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <CA720B4C.E941%joe.hildebrand@webex.com>
Thread-Topic: [woes] Proposed JOSE Charter
Thread-Index: Acxdd04eHMMW78EHC0OWDkKqJicZuw==
In-Reply-To: <60A80A8A-B8B5-461E-814B-7A243213995E@bbn.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 18 Aug 2011 07:20:30.0220 (UTC) FILETIME=[4F7104C0:01CC5D77]
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: Thu, 18 Aug 2011 07:19:38 -0000

+1


On 8/17/11 10:34 AM, "Richard L. Barnes" <rbarnes@bbn.com> 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

-- 
Joe Hildebrand