IETF Logo Mail Archive

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

Russ Housley <housley@vigilsec.com> Wed, 30 November 2011 15:25 UTC

Return-Path: <housley@vigilsec.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 342A821F8B48 for <w3c-policy@ietfa.amsl.com>; Wed, 30 Nov 2011 07:25:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level:
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, 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 aQIcBHV+7riB for <w3c-policy@ietfa.amsl.com>; Wed, 30 Nov 2011 07:25:41 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B5E4A21F8B43 for <w3c-policy@ietf.org>; Wed, 30 Nov 2011 07:25:41 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id ADB6D9A47B8; Wed, 30 Nov 2011 10:25:47 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 0P4ck+-X2wEz; Wed, 30 Nov 2011 10:25:37 -0500 (EST)
Received: from [38.127.208.180] (unknown [38.127.208.180]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 14E7C9A4749; Wed, 30 Nov 2011 10:25:47 -0500 (EST)
Subject: Re: draft minutes: W3C/IETF liaison call 2011-11-29
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <8778239E-3267-45AD-9539-0D502D3EA169@w3.org>
Date: Wed, 30 Nov 2011 10:25:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <83B608D6-D625-4BC5-BFA1-3FBB0F6DF428@vigilsec.com>
References: <8778239E-3267-45AD-9539-0D502D3EA169@w3.org>
To: Thomas Roessler <tlr@w3.org>
X-Mailer: Apple Mail (2.1084)
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:25:42 -0000

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

Russ

v2.8.7 | Report a Bug | By Email