Re: [woes] Proposed charter, post-Quebec edition

Phillip Hallam-Baker <hallam@gmail.com> Thu, 04 August 2011 04:11 UTC

Return-Path: <hallam@gmail.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 A595721F86C3 for <woes@ietfa.amsl.com>; Wed, 3 Aug 2011 21:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level:
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 Zmu5nvYJrTsf for <woes@ietfa.amsl.com>; Wed, 3 Aug 2011 21:11:03 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B26BD21F8640 for <woes@ietf.org>; Wed, 3 Aug 2011 21:11:03 -0700 (PDT)
Received: by vxi40 with SMTP id 40so1427267vxi.31 for <woes@ietf.org>; Wed, 03 Aug 2011 21:11:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=NkAM3PQU81HsaJFzWLIc1Jcdm5BteIzqiuH0QsmJGjA=; b=PaCFwnBWbHtKndUh2ghz6UAcEpuFzgnwT9eILR6phV6V+nNMaVZnvzk8s1r64yD8F+ dY8Z/KmA7aTviaJ4/I8dFFmjafKZnVdAfchrcZIoHoND1eo+GBFEgLmySw+vmj3hthaG UVBMkrfSYiN2p3V1uXYc582Xpm3lRZjt62Fs0=
Received: by 10.52.30.136 with SMTP id s8mr361596vdh.199.1312431076991; Wed, 03 Aug 2011 21:11:16 -0700 (PDT)
Received: from [10.0.1.9] (c-66-30-5-63.hsd1.ma.comcast.net [66.30.5.63]) by mx.google.com with ESMTPS id fc7sm739304vdc.0.2011.08.03.21.11.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 03 Aug 2011 21:11:15 -0700 (PDT)
References: <4F25253E-A870-4956-AAB1-20890B655984@vpnc.org>
In-Reply-To: <4F25253E-A870-4956-AAB1-20890B655984@vpnc.org>
Mime-Version: 1.0 (iPad Mail 8L1)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <15A4A9CD-FC3C-4D51-9EB5-6D05F372F5E2@gmail.com>
X-Mailer: iPad Mail (8L1)
From: Phillip Hallam-Baker <hallam@gmail.com>
Date: Thu, 4 Aug 2011 00:11:12 -0400
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: "woes@ietf.org" <woes@ietf.org>
Subject: Re: [woes] Proposed charter, post-Quebec edition
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, 04 Aug 2011 04:11:04 -0000

Is the object here to arrive at an RFC or to arrive at a standard with a broad base of support in the web services apps community?

If the latter the I suggest much more time so as to have the ability to get buy in from the relevant community.


Sent from my angry birds pad

On Aug 2, 2011, at 19:13, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> Here is a proposal for the charter based on the discussion in the BoF last week and later discussion with Sean Turner. Comments, praise, scorn, etc., are welcome.
> 
> --Paul and Richard
> 
> Javascript Object Signing and Encrypting (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 and digital signatures 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, encrypting and digitally signing, 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 a JSON-structured digital signature to data, including (but not limited to) JSON data structures. "Digital signature" is defined as a hash operation followed by a signature operation using asymmetric keys.
> 
> 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 
> --------------------
> 
> Aug 2011    Submit JSON object signing document as a WG item.
> 
> Aug 2011    Submit JSON object encryption document as a WG item.
> 
> Aug 2011    Submit JSON key format document as a WG item.
> 
> Aug 2011    Submit JSON algoritm document as a WG item.
> 
> Jan 2012    Start Working Group Last Call on JSON object signing document.
> 
> Jan 2012    Start Working Group Last Call on JSON object encryption document.
> 
> Jan 2012    Start Working Group Last Call on JSON key format document.
> 
> Jan 2012    Start Working Group Last Call on JSON algorithm document.
> 
> Feb 2012    Submit JSON object signing document to IESG for consideration as 
> Standards Track document.
> 
> Feb 2012    Submit JSON object encryption document to IESG for consideration 
> as Standards Track document.
> 
> Feb 2012    Submit JSON key format document to IESG for consideration 
> as Standards Track document.
> 
> Feb 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