IETF Logo Mail Archive

Re: draft minutes: W3C/IETF liaison call 2011-11-29

Sean Turner <turners@ieca.com> Wed, 30 November 2011 15:59 UTC

Return-Path: <turners@ieca.com>
X-Original-To: w3c-policy@ietfa.amsl.com
Delivered-To: w3c-policy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3D5121F8922 for <w3c-policy@ietfa.amsl.com>; Wed, 30 Nov 2011 07:59:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.096
X-Spam-Level:
X-Spam-Status: No, score=-102.096 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzJ+EVXNP7cN for <w3c-policy@ietfa.amsl.com>; Wed, 30 Nov 2011 07:59:40 -0800 (PST)
Received: from gateway.websitewelcome.com (gateway11.websitewelcome.com [67.18.21.16]) by ietfa.amsl.com (Postfix) with ESMTP id E5F0721F85F2 for <w3c-policy@ietf.org>; Wed, 30 Nov 2011 07:59:39 -0800 (PST)
Received: by gateway.websitewelcome.com (Postfix, from userid 5011) id 2F024639CA8E4; Wed, 30 Nov 2011 09:59:39 -0600 (CST)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway.websitewelcome.com (Postfix) with ESMTP id 20FFA639CA8B5 for <w3c-policy@ietf.org>; Wed, 30 Nov 2011 09:59:39 -0600 (CST)
Received: from [96.231.117.24] (port=47615 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <turners@ieca.com>) id 1RVmZO-00084f-Pe; Wed, 30 Nov 2011 09:59:39 -0600
Message-ID: <4ED652E9.6040601@ieca.com>
Date: Wed, 30 Nov 2011 10:59:37 -0500
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft minutes: W3C/IETF liaison call 2011-11-29
References: <8778239E-3267-45AD-9539-0D502D3EA169@w3.org> <83B608D6-D625-4BC5-BFA1-3FBB0F6DF428@vigilsec.com>
In-Reply-To: <83B608D6-D625-4BC5-BFA1-3FBB0F6DF428@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-96-231-117-24.washdc.east.verizon.net (thunderfish.local) [96.231.117.24]:47615
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 12
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: W3C/IETF <w3c-policy@ietf.org>
X-BeenThere: w3c-policy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Administration of the W3C/IETF liaison <w3c-policy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/w3c-policy>
List-Post: <mailto:w3c-policy@ietf.org>
List-Help: <mailto:w3c-policy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/w3c-policy>, <mailto:w3c-policy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 15:59:40 -0000

On 11/30/11 10:25 AM, Russ Housley wrote:
> - JOSE WG
>
> Basic goal: support for key features from CMS (~ XADES) but in a
> JSON/JavaScript-friendly representation.
>
> Discussions were productive, three documents appear to be close to
> acceptance as WG items (small changes requested before publication).
> Several application working groups (CORE, ALTO, XMPP, etc.) provided
> input and are interested in using the output of the WG. A use cases
> document might be one result of that input.
>
> Open issue is whether serialization is needed.
>
> ===========
>
> Really?  How can this be an open issue?  If there is ever a situation where a signer passes a message to an intermediary that might under some circumstance make a change to the encoding before it arrives to the validator, then a canonical form is needed.  This happens all of the time in IM and email today...

I guess this could be rephrased as the WG needs to decide how they're 
going to support serialization.  Jim brought it up as a CMS feature and 
it wasn't clear whether the proposed solution addressed it or not.

spt

v2.8.7 | Report a Bug | By Email