Re: [perpass] perpass: what next?

Tim Bray <tbray@textuality.com> Sun, 19 April 2015 03:26 UTC

Return-Path: <tbray@textuality.com>
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 9F7101ACEC5 for <perpass@ietfa.amsl.com>; Sat, 18 Apr 2015 20:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 vfuVwYkHv6UN for <perpass@ietfa.amsl.com>; Sat, 18 Apr 2015 20:26:46 -0700 (PDT)
Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49A1A1ACEC2 for <perpass@ietf.org>; Sat, 18 Apr 2015 20:26:46 -0700 (PDT)
Received: by labbd9 with SMTP id bd9so105038366lab.2 for <perpass@ietf.org>; Sat, 18 Apr 2015 20:26:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=dhfBmFHQ99eZhyUNFLWUf87SiMwbJpg2jziJHKckQBI=; b=lbz8kvN4P74ynuwGxlonYPNo3LHZkGb5IrR8pONnF+LzSBN/Ekb68CVfl+s3IDgcI2 Jp4DuPM9Y9kU5TopYUlS3RrP1CNUOBGpZm0P0kGl2c6YjTQ8svTpm3PR8BNBv0BeNjfy f3n3k0V4YiLuB+sIi6M6r29PnJv2CAt/0VenLyqwmpuxBlF73tRdsEv2d94u3na9l4Ub PfXhuYFp8QZSNZLjqF1rc16FSiq91WPW8Sw8ewrb0zBLbZJKIgpEwIHHtqVzrcTyCts1 xLz1skdaI6QFk/Ac1OWCsvxmqfxqtvBll+zzFXQfPLm74gd3JrFETJQCCfuHQcudw1cS GlEg==
X-Gm-Message-State: ALoCoQnX9zBA75rosBgzC0X29s3rbBJERxk7j3rISIlCRTm6DSEWASH0qo914EsYpHYynomaW6T6
X-Received: by 10.112.126.136 with SMTP id my8mr10351717lbb.18.1429414004800; Sat, 18 Apr 2015 20:26:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.114.18.36 with HTTP; Sat, 18 Apr 2015 20:26:24 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <5530EEAB.5050601@cs.tcd.ie>
References: <5530EEAB.5050601@cs.tcd.ie>
From: Tim Bray <tbray@textuality.com>
Date: Sat, 18 Apr 2015 20:26:24 -0700
Message-ID: <CAHBU6itZw_1uVyENheTKVQxvgygce_gh=H+qnqKdcuOdB9UNHA@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="001a11c3799afe531e05140b6158"
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/JkaBUduG6DFzOirYwfuWE3nWx9c>
Cc: perpass <perpass@ietf.org>
Subject: Re: [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: Sun, 19 Apr 2015 03:26:48 -0000

I guess, since I submitted two revs of
https://tools.ietf.org/html/draft-bray-privacy-choices, it’s probably
self-evident that I think that’s a useful line of work.  But just to be
explicit: I do, and am available for editorial duties if there’s consensus
on moving it forward.



On Fri, Apr 17, 2015 at 4:29 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> 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.
>
> _______________________________________________
> perpass mailing list
> perpass@ietf.org
> https://www.ietf.org/mailman/listinfo/perpass
>



-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)