[Pearg] Privacy preserving data collection

Eric Rescorla <ekr@rtfm.com> Tue, 17 July 2018 23:09 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: pearg@ietfa.amsl.com
Delivered-To: pearg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2A7D130E7E for <pearg@ietfa.amsl.com>; Tue, 17 Jul 2018 16:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 9U0JQ5dLtrKQ for <pearg@ietfa.amsl.com>; Tue, 17 Jul 2018 16:09:21 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 C0C90130E4D for <pearg@irtf.org>; Tue, 17 Jul 2018 16:09:20 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id s12-v6so2410188ljj.0 for <pearg@irtf.org>; Tue, 17 Jul 2018 16:09:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=qK/mvMwjgyKP4gOKD8pFfaaB6DLTj8YrLzBRjblwsO8=; b=Dt0eRHlHHtc93624p8VYYDtkMFu/7gD402yxO504RCOlljMPSfAUrm9sQ/nu2us5xk KnSTIKXXPoDhPhxZlCK84Xvwz4jl6gx6JHF+7tqxxhlGkUMookmDNwAJQPMjl3n2bruu Wcz0DsNXfnZQ2dGnPB/WUAjyADBif+vAzqFb9NZxBMoLUppkKh+sEixJ8GPcJY7Dmu8e 8kQQnPNfIItZjsmihtNY1QlkActdN6OVmw2avmPYPZlWQH3TXKtun3NZcWemUfLRi5a1 fC7TfU/dhwDZQLb9e13CN6yydWXG5bO8F6JJPUkGah2bLjaND7NA4mycFd1UvEKfBU/1 NAPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=qK/mvMwjgyKP4gOKD8pFfaaB6DLTj8YrLzBRjblwsO8=; b=VPXoYFymPRCmBXBTycVS+G8R6eDIIgMlNbtEOnMfzbxmrpU4iv90JFTCu2MCspKBWM /Oob7hARbsyxJG/IbUSAGRSiWa9OAi3YjA0cMtU4aWtypO/1M6ZiYOnrUP7YDULCGeNx p4gnn1wdugQnzmABdIY3vWX6uw2jMmLHsP6Oowl/YndYHptzBvRpKiLoK3bc0OJa7OtY yooyl4JbuJcb7z2i82WnXL0YGV35fQBh3XvMkTmLxfg1tPZEgSI4dWczkepi9qDLGvEm 7uIIZk78R7C7ZC4uRVd23xy6pKlA6VVRY5hUntT91Qd+fNnU+4rB5O3EmX/tdI5HB6vp jV8w==
X-Gm-Message-State: AOUpUlGRH8EeL3Ftm3XkdOXdCY/xhwRe2+4Hr07xvmTAjqdyEywc4yQy kPxt/ML08/xf0balhgydhNQQnWjuEcsIrlYdSPkvfB4gIWc=
X-Google-Smtp-Source: AAOMgpejCw9BFVFRFQV5ayfDzzylR8oQHPHixiMneQZl96Q1/2Wnry8WY4DPwpUTj7L467Yj+yGD8BssH1s7Rq41xIE=
X-Received: by 2002:a2e:2096:: with SMTP id g22-v6mr2634628lji.37.1531868958581; Tue, 17 Jul 2018 16:09:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ab3:4091:0:0:0:0:0 with HTTP; Tue, 17 Jul 2018 16:08:37 -0700 (PDT)
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Jul 2018 16:08:37 -0700
Message-ID: <CABcZeBNQgANP_=JHJev1Yoc-bFAaBy0cHeXhpi2EUzCtj0JMPA@mail.gmail.com>
To: pearg@irtf.org
Content-Type: multipart/alternative; boundary="0000000000001e8b1205713a09a9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/NAtohqxJnDe469ruBcTS8EHy0AY>
Subject: [Pearg] Privacy preserving data collection
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <pearg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/pearg>, <mailto:pearg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pearg/>
List-Post: <mailto:pearg@irtf.org>
List-Help: <mailto:pearg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pearg>, <mailto:pearg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2018 23:09:24 -0000

Here's the technique I was referring to at today's meeting about Google's
new technique:

https://ai.google/research/pubs/pub46411

I don't know what Google's plans are, but the paper compares Prochlo
favorably to RAPPOR
"

We introduce the Encode, Shuffle, Analyze (ESA) archi- tecture for
privacy-preserving software monitoring, and its PROCHLO implementation.1 The
ESA architecture is in- formed by our experience building, operating, and
maintain- ing the RAPPOR privacy-preserving monitoring system for the
Chrome Web browser [28]. Over the last 3 years, RAP- POR has processed up
to billions of daily, randomized re- ports in a manner that guarantees
local differential privacy, without assumptions about users’ trust; similar
techniques have since gained increased attention [6, 7, 70, 74]. However,
these techniques have limited utility, both in theory and in our
experience, and their statistical nature makes them ill- suited to standard
software engineering practice."


-Ekr