Re: [woes] New WOES charter proposal

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 07 July 2011 23:18 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 F0C6B21F8854 for <woes@ietfa.amsl.com>; Thu, 7 Jul 2011 16:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.751
X-Spam-Level:
X-Spam-Status: No, score=-102.751 tagged_above=-999 required=5 tests=[AWL=-0.152, BAYES_00=-2.599, 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 dW1tvJ-FYJB9 for <woes@ietfa.amsl.com>; Thu, 7 Jul 2011 16:18:05 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1E48E21F8892 for <woes@ietf.org>; Thu, 7 Jul 2011 16:18:04 -0700 (PDT)
Received: from [10.20.30.101] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p67NHosh013507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Jul 2011 16:17:51 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <23656536-E4BA-41BE-AA61-A23654246826@gmx.net>
Date: Thu, 07 Jul 2011 16:17:59 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A42506AF-BE66-4308-AD7B-03B4323D87CE@vpnc.org>
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>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1084)
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:18:06 -0000

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