Re: [woes] New WOES charter proposal

Mike Jones <Michael.Jones@microsoft.com> Thu, 07 July 2011 23:21 UTC

Return-Path: <Michael.Jones@microsoft.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 2C33521F8986 for <woes@ietfa.amsl.com>; Thu, 7 Jul 2011 16:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 w+VTaT9SQv44 for <woes@ietfa.amsl.com>; Thu, 7 Jul 2011 16:21:45 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by ietfa.amsl.com (Postfix) with ESMTP id A37E321F897D for <woes@ietf.org>; Thu, 7 Jul 2011 16:21:45 -0700 (PDT)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 7 Jul 2011 16:21:41 -0700
Received: from TK5EX14MBXC201.redmond.corp.microsoft.com ([169.254.8.198]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.01.0289.008; Thu, 7 Jul 2011 16:21:41 -0700
From: Mike Jones <Michael.Jones@microsoft.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Hannes Tschofenig <hannes.tschofenig@gmx.net>
Thread-Topic: [woes] New WOES charter proposal
Thread-Index: AQHMO1RWUGM/TGyrVEadNI6Ha28vK5ThnKoAgAA4ngCAAB5hAIAAAz+A//+K+8A=
Date: Thu, 07 Jul 2011 23:21:40 +0000
Message-ID: <4E1F6AAD24975D4BA5B168042967394348D3F7F1@TK5EX14MBXC201.redmond.corp.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>
In-Reply-To: <A42506AF-BE66-4308-AD7B-03B4323D87CE@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.32]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Anthony Nadalin <tonynad@microsoft.com>, "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:21:46 -0000

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.

				-- 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