[pkix] Fwd: [Spasm] side meeting at IETF95 on possible PKIX/SMIME work (and new spasm list)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 15 April 2016 14:17 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0293F12E0C7 for <pkix@ietfa.amsl.com>; Fri, 15 Apr 2016 07:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FdrIIwv7c6Go for <pkix@ietfa.amsl.com>; Fri, 15 Apr 2016 07:17:11 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68AB712E05B for <pkix@ietf.org>; Fri, 15 Apr 2016 07:17:11 -0700 (PDT)
Received: from localhost (localhost []) by mercury.scss.tcd.ie (Postfix) with ESMTP id E3993BE3F for <pkix@ietf.org>; Fri, 15 Apr 2016 15:17:09 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([]) by localhost (mercury.scss.tcd.ie []) (amavisd-new, port 10024) with ESMTP id fxIIEjglCqKo for <pkix@ietf.org>; Fri, 15 Apr 2016 15:17:08 +0100 (IST)
Received: from [] (unknown []) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5E57EBE25 for <pkix@ietf.org>; Fri, 15 Apr 2016 15:17:07 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460729827; bh=it3+OZLYtjVDHz0lbmp9qRt/bDz0yr6EpfqNe7j3LAg=; h=Subject:References:To:From:Date:In-Reply-To:From; b=aw8524CLS65gceYDqAYPzlsIaJKf+5ZEh2RG8vroaDEp74cqoBv/B7Aqmz4eBuRkw LqFpZAcYYHJ2fqYb3qVoIQT9yoLhTj0RIPXxZTgHdg3KQCbRXv/BOHv+4DXGbmj+wB kT/n5Rb9ZAozOKYxXiaQ6mDeMKcPOJaZkm74ZuKk=
References: <5710F7A0.8020108@cs.tcd.ie>
To: pkix <pkix@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
X-Forwarded-Message-Id: <5710F7A0.8020108@cs.tcd.ie>
Message-ID: <5710F7E3.2000703@cs.tcd.ie>
Date: Fri, 15 Apr 2016 15:17:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <5710F7A0.8020108@cs.tcd.ie>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms070003090005040304040108"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/eqI6aK-xnXRNsLkfYNVDE6SEn4A>
Subject: [pkix] Fwd: [Spasm] side meeting at IETF95 on possible PKIX/SMIME work (and new spasm list)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2016 14:17:13 -0000

-------- Forwarded Message --------
Subject: [Spasm] side meeting at IETF95 on possible PKIX/SMIME work (and
new spasm list)
Date: Fri, 15 Apr 2016 15:16:00 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: spasm@ietf.org


About 10 of us who were at IETF95 had a side meeting to continue
the recent discussion about potential work items that would have
been handled in the PKIX and SMIME working groups before those
closed. A number of such work items in this space have recently
been proposed on the PKIX and SMIME mailing lists.

In the discussion we concluded that it might be a good plan to
try charter a WG to (initially) handle a small number of these
tasks. We also recognised that there is a bit of a history in
this space of people proposing work that doesn't end up being
implemented and deployed (and I'm as guilty of that as anyone;-)
so we wanted to not do that this time around.

To that end I said that I'd be happy to help with seeing if we
have consensus to charter a working group to tackle a smallish
list of specific work items where:

- the proposal is sane
- we're pretty confident the proposal will be implemented in a
  real way (not a toy, but doesn't have to be on every phone)
- to the extent we can, we think there's a good chance that the
  proposal will be deployed
- each proposal has an I-D already published that is called out
  in the charter as the starting point for the work

If we start that WG and if it turns out to do good work well and
in a timely fashion then I'd guess that it could be re-chartered
to add additional items that meet the above criteria.

We also figured that a new list (spasm [1]) would be a better way
to handle this as it crosses two previous lists (which will
remain open) with much broader topics.

Russ Housley, Stefan Santesson and Wei Chuang have agreed to try
to craft charter text for that so they'll send that to the spasm
list [1] in a few days once folks have had a chance to sign up.
So please hold off discussion of this for a few days and then
continue the discussion on the spasm list.


[1]  https://www.ietf.org/mailman/listinfo/spasm