Re: [ietf-privacy] Is there an official working definition for Privacy Online?

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 05 May 2016 13:30 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B23A612D647 for <ietf-privacy@ietfa.amsl.com>; Thu, 5 May 2016 06:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t1D4VEpOiDkv for <ietf-privacy@ietfa.amsl.com>; Thu, 5 May 2016 06:30:21 -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 22FDC12D661 for <ietf-privacy@ietf.org>; Thu, 5 May 2016 06:30:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D5D1EBE38; Thu, 5 May 2016 14:30:18 +0100 (IST)
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 1kT_EOiTc52d; Thu, 5 May 2016 14:30:18 +0100 (IST)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 16615BDD0; Thu, 5 May 2016 14:30:18 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1462455018; bh=Jdzy05+xygeDMxI8xeZ017DSRJID86u7w1j2lvB5oQQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=NoKa9pj6VFIagSsKWXA1rI4/hTDKErX5iNknHv84ltUfmUsDUsIxoIbn6KYrA+x9p n4jEYvT9pZU1wHEnIGL1AmveOUvMmMCkgE/rRs2yfBxadxRQREzV4ki4RXrIkwlxhS uLyg0BowFi1qiFC7/Mw4WSfoVpqjOd1s1wtYgAHU=
To: dcrocker@bbiw.net, Robin Wilton <wilton@isoc.org>, David Singer <singer@apple.com>
References: <552FCC84.6040305@gmail.com> <CA+9kkMCYuEGRidB1D=SGA0qxk+SuX6+HyqToYDmqQVmpBskWrw@mail.gmail.com> <5530329E.4060608@dcrocker.net> <01F784DA-5FD5-4D1F-8613-C2E668EDA765@isoc.org> <55311CE9.9040003@dcrocker.net> <DB3PR07MB138A042321BB99DF9AB94A4BCE30@DB3PR07MB138.eurprd07.prod.outlook.com> <55313140.9040400@dcrocker.net> <015a01d0798d$509954c0$f1cbfe40$@huitema.net> <CABtrr-X6CgN3J0dA1YBED0j6K7D5Mt2NAbUwGF5E67BoFX9JUQ@mail.gmail.com> <57268D25.3070708@dcrocker.net> <029801d1a4b9$c3b57850$4b2068f0$@huitema.net> <F285E90F-4E8B-47BE-A0BF-3A24212C39D9@apple.com> <2DDB1AF6-563C-48F3-BF1F-A45038711703@isoc.org> <572B4899.6080305@dcrocker.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <572B4AEF.8000000@cs.tcd.ie>
Date: Thu, 5 May 2016 14:30:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <572B4899.6080305@dcrocker.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030501000408090001050602"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-privacy/9c9WSJTJ7KsNstDpbVHAII3GPhA>
Cc: "ietf-privacy@ietf.org" <ietf-privacy@ietf.org>, Josh Howlett <Josh.Howlett@jisc.ac.uk>
Subject: Re: [ietf-privacy] Is there an official working definition for Privacy Online?
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-privacy/>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2016 13:30:22 -0000


On 05/05/16 14:20, Dave Crocker wrote:
> On 5/5/2016 1:30 AM, Robin Wilton wrote:
>> Privacy can also be a subjective thing (for instance, some people
>> think it's important to draw their curtains in the evening - others
>> don't). That subjectivity makes privacy a highly contextual thing,
> 
> This is an Alice, Through the Looking Glass perspective on the term.
> 
> At the least, it means it is not a technical term, in which case using
> it in technical contexts is mostly going to cause confusion, since one
> speaker's intended meaning will differ from another listener's...
> 
> Standards work is primarily an exercise in gaining group consensus on
> technical specifics.  If 'privacy' is to be a technical term, then we
> need to agree on its specifics.  That doesn't mean the term needs lots
> of fine-grained detail.  In fact, for something this important and this
> basic, it needs as little detail as possible, while still serving to
> guide technical choices.
> 
> 
>> Privacy is about retaining the ability to disclose data consensually,
>> and with expectations regarding the context and scope of sharing.
> ...
>> http://www.internetsociety.org/blog/2013/12/language-privacy
> 
> 
> This looks like an entirely reasonable and helpful definition, as I
> noted a year ago.

It's definitely not bad:-)

I think it misses a bit though, in our context. Sometimes we just
have to expose an identifier (e.g. a source IP address) and that
can be privacy-sensitive, but there's no real way in which it's
consensual, unless one considers even connecting to the network
as consenting in some form to such exposure, which'd be odd I
think.

So while Robin's text is pretty good when I think about payloads,
it doesn't seem to cover issues with meta-data and other protocol
artefacts so well. I'm also not sure how much that'd help when it
comes to considering re-identification issues which can be very
subtle (cf. netflix competition).

But it's a good start.

> 
> There are other, similarly short and focused, definitions. Each is
> reasonable.  And while the differences in the definitions probably
> matter, I think that the need to focus technical work requires choosing
> one.  If we want the term to have useful substance.
> 
> The fact that choosing one has some challenges is being used as a reason
> for not trying.  That's an ironic excuse, for an organization whose
> primary reason for being is the development of community consensus on
> non-trivial choices...

I'd be happy if someone wanted to try craft some definitional text
say in an I-D, with the goal of meeting Dave's challenge to define
privacy in a way that's useful for IETF work. I don't know
if that'd end up as an RFC, but it might, and if well-done, and if
it garnered consensus, it could be quite useful.

Cheers,
S.


> 
> 
> d/