Re: [Geopriv] Stephen Farrell's Block on charter-ietf-geojson-00-01: (with BLOCK)

Robin Wilton <> Thu, 03 September 2015 16:15 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E745B1A8AAD; Thu, 3 Sep 2015 09:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FC3H7rSrp33C; Thu, 3 Sep 2015 09:15:11 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fc10::1:681]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 023B91B4118; Thu, 3 Sep 2015 09:14:58 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Thu, 3 Sep 2015 16:14:53 +0000
Received: from ([]) by ([]) with mapi id 15.01.0256.013; Thu, 3 Sep 2015 16:14:53 +0000
From: Robin Wilton <>
To: Stephen Farrell <>
Thread-Topic: [Geopriv] Stephen Farrell's Block on charter-ietf-geojson-00-01: (with BLOCK)
Date: Thu, 3 Sep 2015 16:14:53 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
authentication-results: spf=none (sender IP is );
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; SN1PR06MB1838; 5:0u2826gLj9qA0WGeqa9o34I+B6FxCts1eXtA1QJ3veUoYu0GnxXX9Hg3Km5ttjTOkdEvaLgMVocfc6D64LPrUtR2IrTsXaVHRjf2mlQK+b2wITwJA4oGi83uq6qOqUwHNQm51bcpu2oLkg1M+tGm4A==; 24:aqzgLyTEeB5cl0MJqkOEtPlFgV/1XKOAECYMG+fpCaatxjwIk8OUZdxF3iMA3zhLNhKineeDcpy1LkorWcKjaOPn+LCHZrFscmJP4gqPQUc=; 20:f/gttgbLNrxSIjlSCMPkPob/HRo+lP9B14URFuJMfcB1IiJWgVqol6dmsCNIK9I1uyTmmTYr48rG7AfASZyo2w==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR06MB1838;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(8121501046)(5005006)(3002001); SRVR:SN1PR06MB1838; BCL:0; PCL:0; RULEID:; SRVR:SN1PR06MB1838;
x-forefront-prvs: 0688BF9B46
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(252514010)(24454002)(377454003)(479174004)(189002)(164054003)(199003)(5001860100001)(66066001)(230783001)(5001830100001)(64706001)(16236675004)(101416001)(68736005)(15975445007)(99936001)(77096005)(102836002)(189998001)(36756003)(97736004)(81156007)(33656002)(4001540100001)(76176999)(40100003)(99286002)(19580405001)(19580395003)(5002640100001)(10400500002)(105586002)(106356001)(106116001)(86362001)(82746002)(62966003)(46102003)(5001960100002)(2950100001)(54356999)(110136002)(50986999)(87936001)(2900100001)(93886004)(5004730100002)(5007970100001)(92566002)(83716003)(77156002)(122556002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR06MB1838;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_FFC9DF87-E5EA-48A3-A86C-C490433FB122"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Sep 2015 16:14:53.0385 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR06MB1838
Archived-At: <>
Cc: "" <>, "" <>, Erik Wilde <>, IESG <>
Subject: Re: [Geopriv] Stephen Farrell's Block on charter-ietf-geojson-00-01: (with BLOCK)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Geographic Location/Privacy <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 03 Sep 2015 16:15:15 -0000

Sorry, only just seen this thread - but I have read back through the dialogue.

I don’t want to propose a change to the final suggested text, but I would like to check an assumption (of mine) about privacy risk.

In one of his replies, Stephen gave a timeline to illustrate how something might be developed in compliance with the GeoJSON spec and *not*, in itself, give rise to privacy concerns, but might subsequently be extended/modified in such a way *did* give rise to privacy concerns.

The assumption I wanted to check was this: I assume (having been through a similar cycle in another standards development context) that this is another instance of a recurring problem - namely, that if you design specs to be “composable”, you have to deal with the possibility that one apparently innocuous element could be combined with another element in ways that make it more harmful. The question then is, what level of (in this case privacy-related) warning/disclaimer should you put on the element that, on its own, is harmless.

As I say, I don’t want to change the text proposed, just to check if the problem, here, is of the species I’ve described above.


Robin Wilton
Technical Outreach Director - Identity and Privacy
Internet Society

Phone: +44 705 005 2931
Twitter: @futureidentity

On 3 Sep 2015, at 16:03, Stephen Farrell <> wrote:

> Lovely.
> Thanks,
> S.
> On 03/09/15 16:02, Alissa Cooper wrote:
>> Ok, one more try and we’re there I think:
>> OLD
>> As the WG considers extensibility it will be careful not to
>> preclude extensions that would allow GeoJSON objects to become location objects
>> unless the group determines such extensibility would be harmful.
>> NEW
>> Extensions that would allow GeoJSON objects to become location objects are not expected to be defined in the WG. Should that be needed, re-chartering will be required.
>>> On Sep 3, 2015, at 7:58 AM, Stephen Farrell <> wrote:
>>> Better again. You could maybe add that's not expected to happen
>>> during the lifetime of this wg but that'd be fine.
>>> S
>>> On 03/09/15 15:57, Alissa Cooper wrote:
>>>> NEW Should extensions that would allow GeoJSON objects to become
>>>> location objects be needed, re-chartering will be required.
> _______________________________________________
> Geopriv mailing list