Re: [perpass] perpass: what next?

Watson Ladd <watsonbladd@gmail.com> Sat, 18 April 2015 04:44 UTC

Return-Path: <watsonbladd@gmail.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 309821A9026 for <perpass@ietfa.amsl.com>; Fri, 17 Apr 2015 21:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 5jRcoknNHO4m for <perpass@ietfa.amsl.com>; Fri, 17 Apr 2015 21:44:16 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (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 EE8A81A9007 for <perpass@ietf.org>; Fri, 17 Apr 2015 21:44:15 -0700 (PDT)
Received: by wgsk9 with SMTP id k9so130707663wgs.3 for <perpass@ietf.org>; Fri, 17 Apr 2015 21:44:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9QbOaShjxOlwl2YEpEbDMEjTbr4mQYwDPCl0knVYUmw=; b=JqWr19mOjam+QuxfUR9yPyM2T4toEs9mWv1UQ2M6r6u7ftZTrk02jaToPoPheqEkFl RbGrC4kj4oG01disVCJtv4ODWRg6zGXEFg4KluDz7KJbsPGMBzUUdEZKhwyL8HA33hV7 M9B005Yk9GEEU48OgPRdLIIfR97y8eItfP/P6i1zHJwNX74EsoXfwqeJpWVWBrVxCwcJ /s/zFWPAZnPihZ+ScFp+fooaFA84aXOMhM3JT1TdXNfWWVwQ+VqHLigcQ7AKNp5fMW5B AAPzQJy7mps3UMdgaTnaDXE/6j5dG388Ky7qduYw5DcZHyfWpLf+89NCbn2YQ2H6KTGb ZljA==
MIME-Version: 1.0
X-Received: by 10.180.99.42 with SMTP id en10mr6770346wib.83.1429332254813; Fri, 17 Apr 2015 21:44:14 -0700 (PDT)
Received: by 10.194.20.97 with HTTP; Fri, 17 Apr 2015 21:44:14 -0700 (PDT)
In-Reply-To: <5530EEAB.5050601@cs.tcd.ie>
References: <5530EEAB.5050601@cs.tcd.ie>
Date: Fri, 17 Apr 2015 21:44:14 -0700
Message-ID: <CACsn0cn7sY8MFCumUknXfqPWqELUtLdyh55Z=av-0NSbMb3xYw@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/FugAYouIrthmETBMDsS6cPGyF2Q>
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: Sat, 18 Apr 2015 04:44:18 -0000

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

-Key discovery in email has been kicked around a bunch, but no
reasonable proposals yet. Doesn't seem that hard.
-Messaging might be premature to discuss, as there are various
approaches, but we should think about it.
-There has been talk of PGP refreshing, but I don't know if that
happened/is being worked on
-Much of the work on better SSH has been ignored in standards: would
be nice to see some things adopted (useable PKI, etc)
-Anonymity remains untouched.

Sincerely,
Watson Ladd

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



-- 
"Man is born free, but everywhere he is in chains".
--Rousseau.