Re: [perpass] privacy/PM reviews of existing stuff

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Wed, 29 January 2014 16:06 UTC

Return-Path: <spencerdawkins.ietf@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 8A01E1A029B for <perpass@ietfa.amsl.com>; Wed, 29 Jan 2014 08:06:08 -0800 (PST)
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 wpPC5S10tHOx for <perpass@ietfa.amsl.com>; Wed, 29 Jan 2014 08:06:07 -0800 (PST)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 355501A02C8 for <perpass@ietf.org>; Wed, 29 Jan 2014 08:06:06 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id i7so2233210oag.36 for <perpass@ietf.org>; Wed, 29 Jan 2014 08:06:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=W9edKPKgCyAKbxICmMLJO5MVO6KRLwsRiFzgw0RGSBA=; b=ZUvsIScMhQd8Jg11KOlAKs6tAHQ3t98pdieNUloRxdbdebkRQo1Q7LskGgihetfbsM 4a97vI6FjfyTpmUjMV3bguAUplJ+M1roJvtM5Vne1wlz9QbINadPCiO/IL6cSzShjjAw P+N/1NK1DBtk8v+c/PjdP/MyvuvnLVozXDAZ7V+/aCwJAHXslYsMV5sVlK3L6Z9uwF3s jwKSiYX9K/HryVNRli7AdBs9+8khasbYLAZSgVxQRECjebfJ244O7MtgjfcxGi+4GuVA xQuxl50ROrPOAmMhIORTHCD+Kdj60kQoYbqQUT2gm6n8uiPKCXeLMIl/RjQ8/7tcoDAb t5cw==
X-Received: by 10.182.142.37 with SMTP id rt5mr1034037obb.76.1391011563266; Wed, 29 Jan 2014 08:06:03 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id m7sm4674880obo.7.2014.01.29.08.06.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 08:06:02 -0800 (PST)
Message-ID: <52E926E8.4040803@gmail.com>
Date: Wed, 29 Jan 2014 10:06:00 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, perpass <perpass@ietf.org>
References: <52E90863.5070805@cs.tcd.ie> <52E9235C.2030601@bbiw.net>
In-Reply-To: <52E9235C.2030601@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [perpass] privacy/PM reviews of existing stuff
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: Wed, 29 Jan 2014 16:06:08 -0000

I should be assuming that everyone else has already thought of this, but ...

On 01/29/2014 09:50 AM, Dave Crocker wrote:
> On 1/29/2014 5:55 AM, Stephen Farrell wrote:
>> One idea that came up in Vancouver and that we (meaning at least
>> me:-) haven't had a chance to progress was the idea of trying to
>> get a team of folks together to go do privacy reviews of existing
>> RFCs. Or perhaps slightly differently, reviews that explicitly
>> consider pervasive monitoring, which might be more constrained
>> and a bit easier.
> ...
>> Now that we're in the run up to the London IETF, if some of you
>> had time to try self-organise that kind of thing that'd be great.
>> Any takers for trying to organise that?
>
>
> Doing reviews for attention to PM is really an experimental activity. 
> We don't have a track record of those specific types of reviews and I 
> believe we are some distance away from having a shared, usable model 
> of what to review for.
>
> But we do need to develop it.
>
> So I think what you are proposing actually ought to be its own 
> development project, with the goal of producing a document in the 
> realm of "Guidelines for doing Pervasive Monitoring Reviews of IETF 
> Specifications."

Dave's suggestion is likely a great second-wave suggestion.

I took Stephen's suggestion and offer of a room as a great first-wave 
suggestion, and I had assumed that we weren't talking about reviewing 
all 7000-odd existing RFCs, but that people likely have a few widely 
deployed protocols in mind where they're already worrying about privacy 
aspects, reviewing widely deployed protocols that people are already 
worried about would be useful on its own, and might very well be the 
basis for developing guidelines that Dave is suggesting.

So, the worriers would self-organize in London as a first step.

If I got that wrong, my bad, and I'll go annoy people about transport 
issues, of course :-)

Spencer