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

Hal Lockhart <hal.lockhart@oracle.com> Thu, 04 August 2011 20:42 UTC

Return-Path: <hal.lockhart@oracle.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 6078A21F8B53 for <woes@ietfa.amsl.com>; Thu, 4 Aug 2011 13:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 H0DUCSoj4pz4 for <woes@ietfa.amsl.com>; Thu, 4 Aug 2011 13:42:15 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by ietfa.amsl.com (Postfix) with ESMTP id CF2E421F8B4F for <woes@ietf.org>; Thu, 4 Aug 2011 13:42:15 -0700 (PDT)
Received: from rtcsinet22.oracle.com (rtcsinet22.oracle.com [66.248.204.30]) by rcsinet15.oracle.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id p74KgShJ021220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 4 Aug 2011 20:42:30 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by rtcsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id p74KgQiF023252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Aug 2011 20:42:27 GMT
Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p74KgK28020321; Thu, 4 Aug 2011 15:42:21 -0500
MIME-Version: 1.0
Message-ID: <6663f860-9de7-4960-8e7b-1c2d23142009@default>
Date: Thu, 4 Aug 2011 13:41:54 -0700 (PDT)
From: Hal Lockhart <hal.lockhart@oracle.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Eric Rescorla <ekr@rtfm.com>
In-Reply-To: <9F29C631-D1A7-4113-9DCE-2BF86B649884@vpnc.org>
X-Priority: 3
X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.4.1.0 (410211) [OL 9.0.0.6627]
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable
X-Source-IP: rtcsinet22.oracle.com [66.248.204.30]
X-CT-RefId: str=0001.0A090207.4E3B0437.0037,ss=1,re=0.000,fgs=0
Cc: woes@ietf.org
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: Thu, 04 Aug 2011 20:42:16 -0000

+1

> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org]
> Sent: Thursday, August 04, 2011 12:03 PM
> To: Eric Rescorla
> Cc: woes@ietf.org
> Subject: Re: [woes] Proposed charter, post-Quebec edition
> 
> 
> 
> On Aug 4, 2011, at 8:52 AM, Eric Rescorla wrote:
> 
> > IMO, symmetric integrity protection is a useful primitive, and it's
> > already part of the
> > JWT spec. I think all that's required here in the charter is to
> > wordsmith it to separate
> > out symmetric from asymmetric integrity algorithms,
> 
> Current:
> 1) A Standards Track document specifying how to apply a 
> JSON-structured digital signature to data, including (but not 
> limited to) JSON data structures. "Digital signature" is 
> defined as a hash operation followed by a signature operation 
> using asymmetric keys.
> 
> It sounds like you would prefer something like:
> 1) A Standards Track document specifying how to apply 
> integrity protection to data, including (but not limited to) 
> JSON data structures. This integrity protection can be 
> achieved with both symmetric and asymmetric algorithms.
> 
> Is that right?
> 
> --Paul Hoffman
> 
> _______________________________________________
> woes mailing list
> woes@ietf.org
> https://www.ietf.org/mailman/listinfo/woes
>