Re: [woes] Proposed charter, post-Quebec edition

"Paul C. Bryan" <paul.bryan@forgerock.com> Wed, 03 August 2011 21:13 UTC

Return-Path: <paul.bryan@forgerock.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 45E3E21F86B6 for <woes@ietfa.amsl.com>; Wed, 3 Aug 2011 14:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 1jYDZhZKVYww for <woes@ietfa.amsl.com>; Wed, 3 Aug 2011 14:13:27 -0700 (PDT)
Received: from eu1sys200aog107.obsmtp.com (eu1sys200aog107.obsmtp.com [207.126.144.123]) by ietfa.amsl.com (Postfix) with SMTP id 7318F21F86AC for <woes@ietf.org>; Wed, 3 Aug 2011 14:13:26 -0700 (PDT)
Received: from mail-pz0-f48.google.com ([209.85.210.48]) (using TLSv1) by eu1sys200aob107.postini.com ([207.126.147.11]) with SMTP ID DSNKTjm5+7YS7ihilJAf3oudnUVwVDrkGOGW@postini.com; Wed, 03 Aug 2011 21:13:39 UTC
Received: by pzk34 with SMTP id 34so1308876pzk.7 for <woes@ietf.org>; Wed, 03 Aug 2011 14:13:30 -0700 (PDT)
Received: by 10.142.6.1 with SMTP id 1mr4979241wff.267.1312406009952; Wed, 03 Aug 2011 14:13:29 -0700 (PDT)
Received: from [192.168.1.177] (S0106001346fbe4af.vf.shawcable.net [174.1.44.35]) by mx.google.com with ESMTPS id b4sm1438304pba.27.2011.08.03.14.13.28 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 03 Aug 2011 14:13:28 -0700 (PDT)
From: "Paul C. Bryan" <paul.bryan@forgerock.com>
To: woes@ietf.org
In-Reply-To: <5E1150D8-EF17-495C-BD48-965678026FB4@cisco.com>
References: <4F25253E-A870-4956-AAB1-20890B655984@vpnc.org> <DADD7EAD88AB484D8CCC328D40214CCD0E743D3330@EXPO10.exchange.mit.edu> <5E1150D8-EF17-495C-BD48-965678026FB4@cisco.com>
Content-Type: multipart/alternative; boundary="=-zoKmXg9GwgXEVl8WT2qS"
Date: Wed, 03 Aug 2011 14:13:48 -0700
Message-ID: <1312406028.32682.72.camel@dynamo>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
Subject: Re: [woes] Proposed charter, post-Quebec edition
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: Wed, 03 Aug 2011 21:13:30 -0000

On Wed, 2011-08-03 at 14:35 -0600, Matt Miller wrote:

> On Aug 3, 2011, at 14:33, Thomas Hardjono wrote:
> 
> > Paul,
> > 
> > Looks good.
> > 
> > Just my clarification, looking at 1) and 2) does it mean that the
> > resulting JOSE WG specifications can be applied to non-JSON data
> > structures? (I'm ok with this).
> 
> Yes; at least one of the desired uses is to sign/encrypt XMPP stanzas! (-:



For my edification, why would JOSE want to concern itself with
representations of other media types, rather than allowing other
transformations to deal with this?

Put another way, if there were a method of encapsulating and encoding
non-JSON media types in a JSON structure, would JOSE seek to reinvent
such a thing, or merely defer to using it?

Paul