IETF Logo Mail Archive

Re: [woes] New WOES charter proposal

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 07 July 2011 23:43 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 C2EA521F8A6B for <woes@ietfa.amsl.com>; Thu, 7 Jul 2011 16:43:07 -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 FYLygkPf656H for <woes@ietfa.amsl.com>; Thu, 7 Jul 2011 16:43:06 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 83C0521F8A69 for <woes@ietf.org>; Thu, 7 Jul 2011 16:43:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 7F876171C05; Fri, 8 Jul 2011 00:42:53 +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=1310082172; bh=cWRxQliLdPfwOh MVKtXI/qmosR8CochgUd57dmLHcyE=; b=fLF157LAv3Qr0Fh2FVa7r6vj15+V4Z o6Kj4KA1jTAow5k5CefJcfkLjXxCrfy38WjuDIxGNatb1YfH+y4gJTqG/jpTlxgH kHSsAz5fAeXLbbaQZZHOUL48M1JghX2Z7mw1jQoUVYpX6rK0SLfDNucOkIIiEP/u tYb4TcYTTg1EeS8LJngmC4rL+rjtRT+A4bboP8lot8E9SIkkv4dA+fab/lZa12zd YXi1oPREdbOJ/JJoElZ36LwEARcSvgjv+2KJQo33/DQ0kccyGoVbIKmJRgerGDMr N6eW8W1+hbPeUOBIzouvgbiAmw3SqND5hbO4HGDYncpo6EC10pVMBBeA==
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 wT58LLngxtF7; Fri, 8 Jul 2011 00:42:52 +0100 (IST)
Received: from [10.125.17.25] (host-90-239-66-189.mobileonline.telia.com [90.239.66.189]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C3D4317200D; Fri, 8 Jul 2011 00:42:36 +0100 (IST)
Message-ID: <4E164455.9020309@cs.tcd.ie>
Date: Fri, 08 Jul 2011 00:42:13 +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: Mike Jones <Michael.Jones@microsoft.com>
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>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394348D3F7F1@TK5EX14MBXC201.redmond.corp.microsoft.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Anthony Nadalin <tonynad@microsoft.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "woes@ietf.org" <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: Thu, 07 Jul 2011 23:43:07 -0000

On 08/07/11 00:21, Mike Jones wrote:
> There are other requirements not met by CMS for many of our use cases.  For instance, having a compact representation and having a URL-safe implementation.
> 
> I'm fine with CMS being *one* of the input documents, but I believe it's too strong a statement to say that we've decided up-front that the goal is to "JSONize CMS" or to have the charter reflect that narrowing of the mission.

Can you say what is not in CMS that might be needed here?
I find it hard to think of anything myself, but if there
are things, (specific features, that is) that'd be good
to know.

S.

> 
> 				-- Mike
> 
> -----Original Message-----
> From: woes-bounces@ietf.org [mailto:woes-bounces@ietf.org] On Behalf Of Paul Hoffman
> Sent: Thursday, July 07, 2011 4:18 PM
> To: Hannes Tschofenig
> Cc: Anthony Nadalin; woes@ietf.org
> Subject: Re: [woes] New WOES charter proposal
> 
> On Jul 7, 2011, at 4:06 PM, Hannes Tschofenig wrote:
> 
>> And what does it mean to "base it on CMS"? 
>>
>> It could, for example, mean that 
>> 1) the same functionality as CMS has to be provided (but with a JSON encoding)
>> 2) folks should look at CMS to get inspired
>> 3) for a chosen subset of CMS that the JSON-based realization must be semantically equivalent (for example, to make translation easy or so)
>> 4) re-use of parts is encouraged (such as registries, etc.) 
>>
>> What did you had in mind, Paul? 
> 
> I was reflecting an earlier message from our AD. On Jun 14, 2011, at 9:31 AM, Sean Turner wrote:
> 
>> In Prague, I thought the goal was pretty straightforward: JSONize CMS.
> 
> 
> That seems clear to me. It's closer to your #1 above, but the rest of the proposed charter makes it clear that it is a subset of CMS, namely signing and encrypting.
> 
> --Paul Hoffman
> 
> _______________________________________________
> woes mailing list
> woes@ietf.org
> https://www.ietf.org/mailman/listinfo/woes
> 
> _______________________________________________
> woes mailing list
> woes@ietf.org
> https://www.ietf.org/mailman/listinfo/woes
>

v2.23.0 | Report a Bug | By Email