Re: COVID-19 contacts tracker (Re: a brief pondering)

Dirk-Willem van Gulik <dirkx@webweaving.org> Wed, 15 April 2020 18:47 UTC

Return-Path: <dirkx@webweaving.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBED3A03FF for <ietf@ietfa.amsl.com>; Wed, 15 Apr 2020 11:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 8alPQuycYrty for <ietf@ietfa.amsl.com>; Wed, 15 Apr 2020 11:47:24 -0700 (PDT)
Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C327C3A03F4 for <ietf@ietf.org>; Wed, 15 Apr 2020 11:47:23 -0700 (PDT)
Received: from [10.11.0.224] (94-210-134-94.cable.dynamic.v4.ziggo.nl [94.210.134.94]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id 03FIk5r2033119 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 15 Apr 2020 20:46:06 +0200 (CEST) (envelope-from dirkx@webweaving.org)
X-Authentication-Warning: weser.webweaving.org: Host 94-210-134-94.cable.dynamic.v4.ziggo.nl [94.210.134.94] claimed to be [10.11.0.224]
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
Message-Id: <FD9C31D9-7113-40D7-8AB1-E581458DB02F@webweaving.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_890A0BB4-2D7D-405A-A91A-84967BFB3B46"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: COVID-19 contacts tracker (Re: a brief pondering)
Date: Wed, 15 Apr 2020 20:46:05 +0200
In-Reply-To: <24cd67ab-df5a-cc2f-745f-ace19d5325ea@network-heretics.com>
Cc: ietf@ietf.org
To: Keith Moore <moore@network-heretics.com>
References: <fd6b7ee2-cdbe-14a1-0087-ce61282b22f6@lear.ch> <29D0DCA7-1D72-428F-A6DD-05511D90C039@cable.comcast.com> <2fa6a8c8-7639-a378-2ff1-3f8697556b66@cisco.com> <24cd67ab-df5a-cc2f-745f-ace19d5325ea@network-heretics.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (weser.webweaving.org [148.251.234.232]); Wed, 15 Apr 2020 20:46:06 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KvUTQgJA2nYtMzwYnmQpHvQhvjI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2020 18:47:29 -0000

On 15 Apr 2020, at 18:42, Keith Moore <moore@network-heretics.com> wrote:
> On 4/15/20 12:07 PM, Benoit Claise wrote:
> 
>> Hi,
>>> 
>>> Which leads me to a question: what can this community (and similar/adjacent ones) do productively together to help? What new things are happening on the network from which we can learn and quickly adapt/improve?
>>> 
>> In my wish list, I would see this community helping with a COVID-19 contacts tracker:
>>     - with clear specifications
>>     - that respects the privacy concerns, for all parties
> 
> I don't think it's possible.  Anything that can be used to trace contacts for medical purposes can be used to trace contacts for political purposes.

I would beg to differ, though by no means perfect or yet there, the EU recommendations:

	https://ec.europa.eu/info/files/recommendation-apps-contact-tracing_en <https://ec.europa.eu/info/files/recommendation-apps-contact-tracing_en>

set out quite a 'hard' set of requirements; that by and large match the manifest/expectations of the CCC, de Waag and similar more activist/vigilant privacy groups:

	https://www.ccc.de/en/updates/2020/contact-tracing-requirements <https://www.ccc.de/en/updates/2020/contact-tracing-requirements> 

(I picked the DE one, as I could not find english version of the substancially similar NL, FR, SE and DK versions) and designs such as de DP3T design (with a few nits and warts) by and large meet those requirements. 

	https://github.com/DP-3T/documents/blob/master/DP3T%20White%20Paper.pdf <https://github.com/DP-3T/documents/blob/master/DP3T%20White%20Paper.pdf>

This is done by de-centralizing; and essentially constructing the cryptography such that only 'on' the phone is it possible to reconstruct 'has there been a contact' and limiting the scope/purpose to exactly that - have I been close. So no location, no tracking, no recording of position, etc. And with sufficient means for an outside observer to verify this.

The apple/google proposals are very similar - but are not as limited in `time and place'; potentially more generic.

Now obviously - there is nothing stopping someone of using the very same spec to accomplish something different; to spike the app, put hidden code in it, etc, etc.  But that is something that we have any way - those that control the phone in your pocket can put a spy in your pocket.

Dw