Re: [woes] New WOES charter proposal

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 16 July 2011 00:36 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 456BE21F8763 for <woes@ietfa.amsl.com>; Fri, 15 Jul 2011 17:36:52 -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=[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 3BGUK0IitduD for <woes@ietfa.amsl.com>; Fri, 15 Jul 2011 17:36:51 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 01AE821F86EB for <woes@ietf.org>; Fri, 15 Jul 2011 17:36:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 12143171C05; Sat, 16 Jul 2011 01:36:38 +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=1310776597; bh=7cGCzk1ruhOZaA Hj45omEAOBUoaw2NqoJj8yKgGVTFc=; b=XQBFUgVwnPSzcEk5KSHccQVwBK0GIB zYj8z2mBVj4obiZ2/pq+cAjrTKY+IrCB6L4crmEoJ+vUvgrZgZIeleZoHv+Dk1sm 48b/31OUfy4gzEXJ3zsArUSZXHlMC3yR97NJNifCAiQsjQCofI0RLRgteVBf/Wqv 6qIXpfnSI0SnwWmRw4Dqq9hUzDqDXdMkg8tluJtzs5loVNUwR4HWHua0iEyncZ0x yA0CxrnUSytOUnr3gl7gUeJkzY+pLqCCSoXT8xfBDkepIDO72vE+aJCSMpNryrJa FiZXtTkHQowAXpYh7r86LZfR6zOo4QFEktNPNLA5q2ptfS+qfJAV3U6Q==
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 MaWjHpY0i-fO; Sat, 16 Jul 2011 01:36:37 +0100 (IST)
Received: from [10.87.48.6] (unknown [86.41.15.89]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id AB3C8171C04; Sat, 16 Jul 2011 01:36:37 +0100 (IST)
Message-ID: <4E20DD0B.2080106@cs.tcd.ie>
Date: Sat, 16 Jul 2011 01:36:27 +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: Dave CROCKER <dcrocker@bbiw.net>
References: <B2ABF893-10E6-496A-8F63-FFA2C9C89541@vpnc.org> <0DE0E2DE-A2FC-40DF-978B-594658571658@vpnc.org> <B26C1EF377CB694EAB6BDDC8E624B6E723160841@CH1PRD0302MB115.namprd03.prod.outlook.com> <23656536-E4BA-41BE-AA61-A23654246826@gmx.net> <A42506AF-BE66-4308-AD7B-03B4323D87CE@vpnc.org> <4E1F6AAD24975D4BA5B168042967394348D3F7F1@TK5EX14MBXC201.redmond.corp.microsoft.com> <4E164455.9020309@cs.tcd.ie> <4E171C20.8000305@dcrocker.net> <4E1F557F.8030500@cs.tcd.ie> <4E20DA1E.1020201@bbiw.net>
In-Reply-To: <4E20DA1E.1020201@bbiw.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: woes@ietf.org
Subject: Re: [woes] New 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: Sat, 16 Jul 2011 00:36:52 -0000

On 16/07/11 01:23, Dave CROCKER wrote:
> 
> On 7/14/2011 1:45 PM, Stephen Farrell wrote:
>>> The first requirement is for proponents to provide much more explicit
>>> details about what is being proposed in the use of CMS.
> ...
>> Well, I don't really follow your logic there, but we're not
>> aiming to do a new thing here.
> ...
>> Anyway the path for developing yet another crypto format
>> is a pretty well trodden one and IMO CMS is the best current
>> starting point for that process, so I think its entirely
>> reasonable to ask people why they disagree with that.
>>
>> It does of course presume familiarity with CMS, but then
>> that should be a prerequisite for working on woes, really.
> 
> 
> Steve,
> 
> Oh.  This working group is merely a CMS encoding exercise?  That was not
> at all clear previously.
>  
> I suspect I am not the only one who missed this as the anchoring and
> inflexible premise to the work.  (For reference, that requires even
> stronger language than is in the current draft.)

Maybe you could put [] around the sarcasm, given that
this is JSON related? :-)

I asked for examples of what's not covered by CMS but
is needed here. I did that actually wanting to get an
answer since I may well be missing something. (So far,
no substantive answer has been offered.) I was not
trying to score some rhetorical points.

S.