IETF Logo Mail Archive

Re: [woes] WOES Charter Proposal

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 16 June 2011 17:52 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 084DC9E8025 for <woes@ietfa.amsl.com>; Thu, 16 Jun 2011 10:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level:
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 WasQaH+MN4KD for <woes@ietfa.amsl.com>; Thu, 16 Jun 2011 10:52:27 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1E67F9E8004 for <woes@ietf.org>; Thu, 16 Jun 2011 10:52:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id C11BF171C19; Thu, 16 Jun 2011 18:52:06 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1308246726; bh=SnOuCas468d+sv H8c7rPOe+wAtF/ms1qqFRC8ohrc38=; b=GExtyIpjofOWmNZv5Ldc6YMJHr+aRR 7SGaw7m7u0R3f5C4RCrwu/lNrwbSV8w+J7U8TcayaDAqKSmoxzh9PJARmnbLJsWv pDuONcdiF3lSKZuQeWFNXSFlfo2hA2tSIdC4JJR/6Jd3cZw7mJgdzHPqdYmkexUR tSf63D77EiV3pcy2U0J8C/kAPPEZpLzgaINJsW94JVR0IjLMf5CB6V5aa1JrlvoK fMFudElSBPFcNoztKttz5s7b6EB5sWk0euxc2iKUvBhq3c6qTqxSndYeZr0XTJR2 btuMTShy9HAjVYycQjKqhsCEa0aLGNM0/2XXIN8aqW2dTFHr71k+uBOw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id NDKs6xpVP7ND; Thu, 16 Jun 2011 18:52:06 +0100 (IST)
Received: from [134.226.36.137] (stephen-samy.dsg.cs.tcd.ie [134.226.36.137]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 8161E171C03; Thu, 16 Jun 2011 18:51:58 +0100 (IST)
Message-ID: <4DFA42BE.5040505@cs.tcd.ie>
Date: Thu, 16 Jun 2011 18:51:58 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: Joe Hildebrand <joe.hildebrand@webex.com>
References: <CA1F9A77.58EE4%joe.hildebrand@webex.com>
In-Reply-To: <CA1F9A77.58EE4%joe.hildebrand@webex.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "woes@ietf.org" <woes@ietf.org>, kris@sitepen.com
Subject: Re: [woes] WOES Charter Proposal
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, 16 Jun 2011 17:52:28 -0000

3 & 4 there look a bit like scope-creep to me

Why are they absolutely needed?

S.

On 16/06/11 18:33, Joe Hildebrand wrote:
> Slight tweaks
> 
> 
> On 6/16/11 11:26 AM, "Mike Jones" <Michael.Jones@microsoft.com> wrote:
> 
>>     1) A JSON-based method of applying digital signatures and keyed message
>> digests to data that may represent JSON data structures.
> 
> ... may represent arbitrary data, including JSON data structures and text
> 
>>     2) A JSON-based method of applying encryption to data that may represent
>> JSON data structures.
> 
> Same as 1) above.  Not just for JSON.
> 
>> Separately, we may want to consider whether the following should be in scope:
>>
>>     3) A JSON-based method of representing public keys.
>>
>> Also, please update and/or add these references (some were out of date, some
>> were missing):
> 
> Let's also add:
> 
> 4) Any JSON-specific prerequisite tooling such as JSON Schema
> 
> And add draft-zyp-json-schema as a reference.  I CC'd Kris Zyp to see if
> he's ok with that.  Kris: this might be a chance for a WG to pick up JSON
> Schema if you like.
>

v2.23.0 | Report a Bug | By Email