Re: [woes] WOES Charter Proposal

Peter Saint-Andre <stpeter@stpeter.im> Thu, 16 June 2011 21:03 UTC

Return-Path: <stpeter@stpeter.im>
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 0F41311E82AD for <woes@ietfa.amsl.com>; Thu, 16 Jun 2011 14:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.224
X-Spam-Level:
X-Spam-Status: No, score=-102.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, 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 nUCuiekqZc02 for <woes@ietfa.amsl.com>; Thu, 16 Jun 2011 14:03:30 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1B3BD11E8268 for <woes@ietf.org>; Thu, 16 Jun 2011 14:03:30 -0700 (PDT)
Received: from dhcp-64-101-72-207.cisco.com (dhcp-64-101-72-207.cisco.com [64.101.72.207]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 2136B400A5; Thu, 16 Jun 2011 15:03:53 -0600 (MDT)
Message-ID: <4DFA6F9F.4010006@stpeter.im>
Date: Thu, 16 Jun 2011 15:03:27 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Joe Hildebrand <joe.hildebrand@webex.com>
References: <CA1FC3CF.58FE1%joe.hildebrand@webex.com>
In-Reply-To: <CA1FC3CF.58FE1%joe.hildebrand@webex.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms010003000100030708060801"
Cc: "woes@ietf.org" <woes@ietf.org>, Peter Saint-Andre <Peter.SaintAndre@webex.com>, gary.court@gmail.com, "<kris@sitepen.com>" <kris@sitepen.com>, Pete Resnick <presnick@qualcomm.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 21:03:31 -0000

Sure, it seems reasonable to discuss draft-zyp-json-schema-03 in the
Apps Area. It recently expired, so I'll ping the authors about bringing
it back to life.

On 6/16/11 2:29 PM, Joe Hildebrand wrote:
> Kris has most of what we need already in his JSON Schema draft.
> 
> 
> On 6/16/11 2:14 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
> 
>> I guess I'd worry about the added time if its a dependency but maybe there're
>> ways around that. (Developing new schema stuff sounds to me like a slooow
>> thing;-)
>>
>> S
>>
>> On 16 Jun 2011, at 20:43, "Peter Saint Andre" <Peter.SaintAndre@webex.com>
>> wrote:
>>
>>> Yes, that seems not unreasonable.
>>>
>>> ----- Original Message -----
>>> From: Joe Hildebrand
>>> To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
>>> Cc: Mike Jones <Michael.Jones@microsoft.com>; Tschofenig, Hannes (NSN -
>>> FI/Espoo) <hannes.tschofenig@nsn.com>; ext Manger, James H
>>> <James.H.Manger@team.telstra.com>; Sean Turner <turners@ieca.com>;
>>> woes@ietf.org <woes@ietf.org>; kris@sitepen.com <kris@sitepen.com>; Peter
>>> Saint Andre; Pete Resnick <presnick@qualcomm.com>
>>> Sent: Thu Jun 16 12:21:56 2011
>>> Subject: Re: [woes] WOES Charter Proposal
>>>
>>> Agree that 4 is scope creep that is outside of the scope of normal security
>>> area stuff, but it's likely to be a prereq.  I'm fine with dropping it from
>>> the charter, potentially getting support from the Apps ADs to move stuff
>>> like JSON Schema through the Apps AWG.
>>>
>>>
>>> On 6/16/11 11:51 AM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
>>>
>>>>
>>>> 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.
>>>>>
>>>
>>> -- 
>>> Joe Hildebrand
>>>