[perpass] perpass: what next?
Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 17 April 2015 11:29 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA8F1A1A2E for <perpass@ietfa.amsl.com>; Fri, 17 Apr 2015 04:29:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.103
X-Spam-Level:
X-Spam-Status: No, score=-3.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOzL2R5rpzbo for <perpass@ietfa.amsl.com>; Fri, 17 Apr 2015 04:29:52 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F12061A1A1E for <perpass@ietf.org>; Fri, 17 Apr 2015 04:29:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9B0FBBF15 for <perpass@ietf.org>; Fri, 17 Apr 2015 12:29:50 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cd7dP4egqeFX for <perpass@ietf.org>; Fri, 17 Apr 2015 12:29:49 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.17.62]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7E7AFBF14 for <perpass@ietf.org>; Fri, 17 Apr 2015 12:29:49 +0100 (IST)
Message-ID: <5530EEAB.5050601@cs.tcd.ie>
Date: Fri, 17 Apr 2015 12:29:47 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: perpass <perpass@ietf.org>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/2FTrCQHaMwgZimSpYjexJ8BDcv0>
Subject: [perpass] perpass: what next?
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2015 11:29:53 -0000
Hiya, I think this list has been really useful since we started it back in August 2013. We initiated a bunch of new work on here (e.g. cfrg curves, tcpinc, dprive, rfc7258) and I think the concerns dealt with here have influenced lots of other work in the IETF as well. Many thanks for all that great input and of course most of the things above aren't finished, but even so, we're now looking for some more great input:-) The IESG will be meeting f2f in early May at our "retreat" and one of the topics on that agenda is "where next with perpass" so your ideas on that are very welcome. Please discuss those here and/or send 'em to the IESG or to some random AD or to me. But discussing 'em on this list is way better, and of course even betterer is to write an I-D (and please do point again at ones you've written, just to refresh folks' minds). While I do have some ideas, I'd rather not skew the discussion by throwing those out right now. I will also report back here after the IESG discussion. And just as a reminder, we've used this list mostly for very initial discussions and seen all chunky items of work handled elsewhere, be that in current WGs or by forming new WGs or whatever. I think that's been a good mode of operation so far, so we're not really asking here about how to change that, but rather for discussion of which topics we can usefully try handle in that same way over the coming year or two. So, fire away... Thanks, S.
- Re: [perpass] perpass: what next? John Levine
- [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Michael Richardson
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Watson Ladd
- Re: [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Tim Bray
- Re: [perpass] perpass: what next? Adam Caudill
- Re: [perpass] perpass: what next? Paul Wouters
- Re: [perpass] perpass: what next? carlo von lynX
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Watson Ladd
- Re: [perpass] perpass: what next? carlo von lynX
- Re: [perpass] perpass: what next? Joseph Lorenzo Hall
- Re: [perpass] perpass: what next? Christian Huitema
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Michael Richardson
- Re: [perpass] perpass: what next? Ted Lemon
- Re: [perpass] perpass: what next? Mike Liebhold
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Stefan Winter
- Re: [perpass] perpass: what next? Stephen Farrell
- Re: [perpass] perpass: what next? Kathleen Moriarty