
From nobody Wed Dec  1 11:42:48 2021
Return-Path: <stpeter@mozilla.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C453A0A39 for <ppm@ietfa.amsl.com>; Wed,  1 Dec 2021 11:42:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 5vbdSaB08-cm for <ppm@ietfa.amsl.com>; Wed,  1 Dec 2021 11:42:42 -0800 (PST)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 C93683A0A4F for <ppm@ietf.org>; Wed,  1 Dec 2021 11:42:42 -0800 (PST)
Received: by mail-il1-x133.google.com with SMTP id a11so26311581ilj.6 for <ppm@ietf.org>; Wed, 01 Dec 2021 11:42:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=message-id:date:mime-version:user-agent:content-language:to:from :subject:content-transfer-encoding; bh=6cwYkCkimkeIsbln3PXM1KRYR/r886f2I/k6LfSyWHg=; b=ISR7Aydiwo9K7V4XoVDRYRH9oa+KFeALq70Bo8iouIaGc5fuoyuKXzdYb3Q5QN+rex UtYQRmE55ILCkUZwJHISCfo39lPtp6blEFLYKPFH8HQz96dOxgS3ep0cOD1FZzAvgWrT wvuyA9aeeOnvleeB3sR0NEahaDL6u8eoxAfAM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:to:from:subject:content-transfer-encoding; bh=6cwYkCkimkeIsbln3PXM1KRYR/r886f2I/k6LfSyWHg=; b=rO/vARmIgZqd0jvvLmn3v3GlFdT2URcFrunrI9eFiiXwWwAEd/6NJDTPBJzcoBqHrx 3TE4GWa1Xzo35R6qg5YFmTRS3v74uAxEEf4WPg05OUtp7OTZ2pwbNsjVcWS6mk/Pce1t 8hxb7amofEZaCD3WS9rO/HXZTrlFMZki3YgDz6ikVQRTvLQ9WB8MTpD3YezuqAgsVWVd ec6HaVV6B2bJVm6DqNge3crXcopgfBIC+2J4XvvjMBLeOUB/zTUPqoE9cKelEqky8BSy bx3czFwnnnBK1lTtojDVWpQpHwnY7voAFnDVy+2naWdpE0ogkrtyyAXzPScqgrVvrOcH q+LQ==
X-Gm-Message-State: AOAM532fyUKyfsgVWj9wF3O4wVyKZQhMw4Vd9d9xfGOx+u4GdbJJx72C Ivg+vTPXd77mnqttCd7cHGZ6Tjkuwb87rQ==
X-Google-Smtp-Source: ABdhPJwiB2izDo8fkUqyQNdghMgSveIqHKdNMhH74QLnrDGujJjKwInPntj2rPDt+PnWXpHebC3YBA==
X-Received: by 2002:a05:6e02:2191:: with SMTP id j17mr9758228ila.120.1638387760669;  Wed, 01 Dec 2021 11:42:40 -0800 (PST)
Received: from [192.168.1.13] (c-76-25-154-156.hsd1.co.comcast.net. [76.25.154.156]) by smtp.gmail.com with ESMTPSA id k9sm355367ilv.61.2021.12.01.11.42.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 01 Dec 2021 11:42:40 -0800 (PST)
Message-ID: <f7dae850-f0dc-97b3-ae48-eb629aa46177@mozilla.com>
Date: Wed, 1 Dec 2021 12:42:39 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
Content-Language: en-US
To: ppm@ietf.org
From: Peter Saint-Andre <stpeter@mozilla.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/ua0fMr3_Hct_rF5ZzxKH88uiHpw>
Subject: [Ppm] Slack channel for implementers
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2021 19:42:46 -0000

Hi all,

I've created a Slack channel for implementers to compare notes and share 
insights regarding privacy-preserving measurement, as we've done in the 
past for technologies like QUIC and TLS. The channel is #ppm on 
ietf.slack.com. Naturally that channel does not supersede this mailing 
list for substantive discussions, either before or after a WG is formed.

Peter


From nobody Wed Dec  1 11:48:22 2021
Return-Path: <stpeter@mozilla.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D99BC3A09F3 for <ppm@ietfa.amsl.com>; Wed,  1 Dec 2021 11:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.951
X-Spam-Level: 
X-Spam-Status: No, score=-3.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.852, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 ohBepx8Qe7BM for <ppm@ietfa.amsl.com>; Wed,  1 Dec 2021 11:48:16 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 D10343A0987 for <ppm@ietf.org>; Wed,  1 Dec 2021 11:48:16 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id z18so32420914iof.5 for <ppm@ietf.org>; Wed, 01 Dec 2021 11:48:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=message-id:date:mime-version:user-agent:subject:content-language :from:to:references:in-reply-to:content-transfer-encoding; bh=x4VU7pKW05REAEwwinYG4GI9EmjEXGs+vYjZNHbTqFQ=; b=CQrPQL+2TVjXDKMokVQrP9/sVftnCT5U3N58Eax9DHupRFVte0RKRZQ5jvm3w8aMm7 Um+JN2k0zJ7/zlOTr6vUm2MjAidJ91w6Ab7b/Ev2O/T4Uz+cuQs+sHRHY41lCJrPvKFi LUxUDWgF1mw0gjq0iFnZ9p9gvYlno6ZPCY8eI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:references:in-reply-to :content-transfer-encoding; bh=x4VU7pKW05REAEwwinYG4GI9EmjEXGs+vYjZNHbTqFQ=; b=YDZyFvbpsiG3u+92kK7rD2bY8PkL6NO2XHiNIsJ0cPbYrm4FH7XVCVc2iV10Pfdi+d q88Phq03J2MuwgLVKXIB7skN9UlVZwe7G7fnaOUh1rKn+cE1IEggD1zagCpxNvzy49uB qy7e+OIwj1+MOz9CbCY0LEbm1RPDgkQMcv5Z8y0jkw+3MYpA9TrQSy+BGwu4fTENCh91 g8/Ok7llnblZ9BSr5aq0f6Cwo4ypjtUIuxGcKxoOHJFF6TOx3GhY+YovGQN4XcbW2DWk 1JvCRQUAPLVwILdwLoUxP4fseF9pQ+NgM3OucIPr6MLAAp30QrnNrnuq1MMYB/Q7+97A 5Prw==
X-Gm-Message-State: AOAM533gV4vSGx6/dga+nadVQYjuTpipthiWBwOdQHjVy+RpA+VSjUpB Z2PuBHWTt77TC4FfcI0fI8qD4qJUaaBmLg==
X-Google-Smtp-Source: ABdhPJy7ifbO/2LCGzUutisq/GuYX4zazxr2QbgxkhH7wNQtR7omETMLUWtFEPF4rQWtofJgILFrtQ==
X-Received: by 2002:a05:6602:2b89:: with SMTP id r9mr11033819iov.32.1638388095038;  Wed, 01 Dec 2021 11:48:15 -0800 (PST)
Received: from [192.168.1.13] (c-76-25-154-156.hsd1.co.comcast.net. [76.25.154.156]) by smtp.gmail.com with ESMTPSA id o1sm337899ilj.41.2021.12.01.11.48.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 01 Dec 2021 11:48:14 -0800 (PST)
Message-ID: <58883f9e-dda9-bb0b-8f3b-de31bdf0ba4c@mozilla.com>
Date: Wed, 1 Dec 2021 12:48:13 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
Content-Language: en-US
From: Peter Saint-Andre <stpeter@mozilla.com>
To: ppm@ietf.org
References: <f7dae850-f0dc-97b3-ae48-eb629aa46177@mozilla.com>
In-Reply-To: <f7dae850-f0dc-97b3-ae48-eb629aa46177@mozilla.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/RY-JTAuSk1dBD-8JmPN_ObqjIBU>
Subject: Re: [Ppm] Slack channel for implementers
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2021 19:48:21 -0000

P.S. Apparently one needs an invite to join the IETF Slack instance, so 
ping me offlist if you require an invite.

On 12/1/21 12:42 PM, Peter Saint-Andre wrote:
> Hi all,
> 
> I've created a Slack channel for implementers to compare notes and share 
> insights regarding privacy-preserving measurement, as we've done in the 
> past for technologies like QUIC and TLS. The channel is #ppm on 
> ietf.slack.com. Naturally that channel does not supersede this mailing 
> list for substantive discussions, either before or after a WG is formed.
> 
> Peter


From nobody Thu Dec  2 16:04:33 2021
Return-Path: <cpatton@cloudflare.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 700B13A08CC for <ppm@ietfa.amsl.com>; Thu,  2 Dec 2021 16:04:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 1brd6jbTlRYm for <ppm@ietfa.amsl.com>; Thu,  2 Dec 2021 16:04:27 -0800 (PST)
Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 5F5443A08C7 for <ppm@ietf.org>; Thu,  2 Dec 2021 16:04:27 -0800 (PST)
Received: by mail-qv1-xf32.google.com with SMTP id g9so1177076qvd.2 for <ppm@ietf.org>; Thu, 02 Dec 2021 16:04:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=2CtRLy1BVxVx1DrIfKgknfFK92GLGapu7wSuW/qVHG8=; b=O54PHoBrRJMPWDBtIk1ut7EJnaW7MZj3GF7+/im9IUfC4q3q0IHJhQblXtUGW/fDwY Sua8pw62Zn3i8v4elYTjrMvkw1nbam0DNDHwAEchxjmcMV7ePDCLHiRPIDGukjUrOH53 w1zjFSHMlEHmWURFikr3kwOKM+X2Pwnk2a9Ho=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2CtRLy1BVxVx1DrIfKgknfFK92GLGapu7wSuW/qVHG8=; b=sS8iCQhzmfe4BqPNcXQ+HeBW/t/sN8X1BQD+YQr1pb22SqYFpKkaNpyvb8etCuwC5w 5yrEoDLiY3YZiwgYKPcARQt4r8fXaeoqi/Xn2qUktEO6wwoj23AznBolcelf5E7lUzOE RTyAnNIIvyH1XZSLrBo53M0Ybd9/XE5hgLtA8mdt5AwxQfmFdm53Vk7mIr+r2Wu7b9cw B3QkYaAsyZdxrKof9ZZH4APzeSlc3Hsgjnq/IdjWAJkINeyXJW1yvmtEXJ4F0IMDK94q Bc8gvo0xaMDOp0WFDzVaCNLZlHDM6aS4QmkgbWiMH1JZcRQiIJUuurPqT3tI5bZ5ea+0 6CFQ==
X-Gm-Message-State: AOAM5337HUjGijRVQhsf5Q2Xp4urexExGj3NwkuJBp29Pz1rTORgG2QK vOog75XF57kPK67eyFhBJUImrY53PKCxIXdg6D/qEXdRLRkoog==
X-Google-Smtp-Source: ABdhPJxpSL/tcskNvjcOZbM81+SDmfywQnXniniahTuPwh1IHGSOIg9OMeJYZbJXZPcw5GHJEzqz8+fYJvPtrCuTqvc=
X-Received: by 2002:a05:6214:f2e:: with SMTP id iw14mr16153168qvb.21.1638489865225;  Thu, 02 Dec 2021 16:04:25 -0800 (PST)
MIME-Version: 1.0
From: Christopher Patton <cpatton@cloudflare.com>
Date: Thu, 2 Dec 2021 16:04:14 -0800
Message-ID: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com>
To: ppm@ietf.org
Content-Type: multipart/alternative; boundary="00000000000062a45d05d232a63e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/oDCOJ-cUR8NQFG6At3byH1fdcd4>
Subject: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Dec 2021 00:04:33 -0000

--00000000000062a45d05d232a63e
Content-Type: text/plain; charset="UTF-8"

Hi everyone,

I've begun an implementation of the PPM spec with `prio3` [1]. One of the
design goals of the sepc was to make it as easy as possible for a Helper to
participate in the protocol, even at the expense of higher resource
requirements for the Leader. Based on my experience so far, I think we may
have over-indexed on this goal a bit. I propose that we revisit this and
consider balancing the work between the Aggregators more evenly. While at
it, we may be able to resolve [2].

The spec requires that reports be processed in strictly ascending order,
where the order is defined in [3]. The ordering is based on a timestamp and
random number generated by the client and included in the report. I'll
refer to thus (time, rand) pair as the nonce. Ordering reports based on the
nonce allows the Helper to prevent replay attacks* without needing to store
the nonces. In fact, the only long-term storage it needs for anti-replay is
the most recently processed nonce. The downside is that the Leader has to
sort reports as they arrive, which makes horizontally scaling the Leader
more challenging.

A simpler alternative that we had discussed previously is just having each
of the Aggregators remember the nonces of the reports they have processed.
This removes the Leader's coordination problem, at the cost of additional
storage requirements. In fact, both Aggregators need to store the set of
processed nonces for the duration of a task. This cost can be mitigated by
refusing to process reports that arrive, say, a day or two late. (Of
course, this would need to be a parameter that the Aggregators agree on in
advance.)

Let's call these schemes option #1 and option #2 respectively. Previously I
was in favor of option #1, but after getting my hands a little dirty and
conferring with some of my colleagues, I've come to the conclusion that the
costs of #1 outweigh the costs of #2. I'm curious if others have thought
about this and whether they are strongly in favor of either option.

Now, if we take option #2, we might also consider revisiting the question
raised in [2]. The spec currently requires the Clients to upload their
encrypted input shares to the Leader, who then piggy-backs the Helper's
input shares on its aggregate requests. Egress fees from cloud providers is
typically higher than ingress, which makes the status quo more expensive to
deploy than if the Clients uploaded their encrypted input shares directly
to each Aggregator.

What might an alternative look like? The client would generate a nonce as
usual and upload the nonce and an encrypted input share to each of the
Aggregators. The aggregation flow would largely be the same: The Leader
sends an Aggregate Request to the Helper, which contains the nonce of the
report it wants to aggregate as usual. The difference now is that the
Helper may not have yet received the report before the Leader's request. In
this case the Leader would just try again later.

Another advantage of this alternative is that it prevents a fairly weak
Sybil attack, whereby the Leader makes up `n-1` bogus reports that are
processed into the batch.**


Thanks for your consideration,
Chris P.


* Anti-replay is required to prevent privacy violations. See [3].
** The Leader can still mount a slightly stronger attack: Just upload the
`n-1` encrypted input shares to the Helper, impersonating the Clients.
Though this can be mitigated slightly by rate-limiting requests from the
Leader's IP address.

[1]
https://datatracker.ietf.org/doc/html/draft-patton-cfrg-vdaf-00#section-6
[2] https://github.com/abetterinternet/ppm-specification/issues/130
[3] https://datatracker.ietf.org/doc/html/draft-gpew-priv-ppm#section-4.4.2

--00000000000062a45d05d232a63e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi everyone,</div><div><br></div><div>I&#39;ve begun =
an implementation of the PPM spec with `prio3` [1]. One of the design goals=
 of the sepc was to make it as easy as possible for a Helper to participate=
 in the protocol, even at the expense of higher resource requirements for t=
he Leader. Based on my experience so far, I think we may have over-indexed =
on this goal a bit. I propose that we revisit this and consider balancing t=
he work between the Aggregators more evenly. While at it, we may be able to=
 resolve [2].</div><div><br></div><div>The spec requires that reports be pr=
ocessed in strictly ascending order, where the order is defined in [3]. The=
 ordering is based on a timestamp and random number generated by the client=
 and included in the report. I&#39;ll refer to thus (time, rand) pair as th=
e nonce. Ordering reports based on the nonce allows the Helper to prevent r=
eplay attacks* without needing to store the nonces. In fact, the only long-=
term storage it needs for anti-replay is the most recently processed nonce.=
 The downside is that the Leader has to sort reports as they arrive, which =
makes horizontally scaling the Leader more challenging.</div><div><br></div=
><div>A simpler alternative that we had discussed previously is just having=
 each of the Aggregators remember the nonces of the reports they have proce=
ssed. This removes the Leader&#39;s coordination problem, at the cost of ad=
ditional storage requirements. In fact, both Aggregators need to store the =
set of processed nonces for the duration of a task. This cost can be mitiga=
ted by refusing to process reports that arrive, say, a day or two late. (Of=
 course, this would need to be a parameter that the Aggregators agree on in=
 advance.)<br></div><div><br></div><div>Let&#39;s call these schemes option=
 #1 and option #2 respectively. Previously I was in favor of option #1, but=
 after getting my hands a little dirty and conferring with some of my colle=
agues, I&#39;ve come to the conclusion that the costs of #1 outweigh the co=
sts of #2. I&#39;m curious if others have thought about this and whether th=
ey are strongly in favor of either option.</div><div><br></div><div>Now, if=
 we take option #2, we might also consider revisiting the question raised i=
n [2]. The spec currently requires the Clients to upload their encrypted in=
put shares to the Leader, who then piggy-backs the Helper&#39;s input share=
s on its aggregate requests. Egress fees from cloud providers is typically =
higher than ingress, which makes the status quo more expensive to deploy th=
an if the Clients uploaded their encrypted input shares directly to each Ag=
gregator.</div><div><br></div><div>What might an alternative look like? The=
 client would generate a nonce as usual and upload the nonce and an encrypt=
ed input share to each of the Aggregators. The aggregation flow would large=
ly be the same: The Leader sends an Aggregate Request to the Helper, which =
contains the nonce of the report it wants to aggregate as usual. The differ=
ence now is that the Helper may not have yet received the report before the=
 Leader&#39;s request. In this case the Leader would just try again later.<=
br></div><div><br></div><div>Another advantage of this alternative is that =
it prevents a fairly weak Sybil attack, whereby the Leader makes up `n-1` b=
ogus reports that are processed into the batch.**</div><div><br></div><div>=
<br></div><div>Thanks for your consideration,</div><div>Chris P.<br></div><=
div></div><div><br></div><div><br></div><div>* Anti-replay is required to p=
revent privacy violations. See [3].</div><div>** The Leader can still mount=
 a slightly stronger attack: Just upload the=20
`n-1` encrypted input shares to the Helper, impersonating the Clients. Thou=
gh this can be mitigated slightly by rate-limiting requests from the Leader=
&#39;s IP address.<br></div><div><br></div><div>[1] <a href=3D"https://data=
tracker.ietf.org/doc/html/draft-patton-cfrg-vdaf-00#section-6">https://data=
tracker.ietf.org/doc/html/draft-patton-cfrg-vdaf-00#section-6</a></div><div=
>[2] <a href=3D"https://github.com/abetterinternet/ppm-specification/issues=
/130">https://github.com/abetterinternet/ppm-specification/issues/130</a></=
div><div>[3] <a href=3D"https://datatracker.ietf.org/doc/html/draft-gpew-pr=
iv-ppm#section-4.4.2">https://datatracker.ietf.org/doc/html/draft-gpew-priv=
-ppm#section-4.4.2</a></div><div><br></div></div>

--00000000000062a45d05d232a63e--


From nobody Thu Dec  2 21:28:29 2021
Return-Path: <mt@lowentropy.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48E233A12F4 for <ppm@ietfa.amsl.com>; Thu,  2 Dec 2021 21:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=mt29Uklf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=NzB6FWeQ
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 3-TAwblO22Cy for <ppm@ietfa.amsl.com>; Thu,  2 Dec 2021 21:28:22 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2288E3A12F2 for <ppm@ietf.org>; Thu,  2 Dec 2021 21:28:22 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 1DEE35C036E; Fri,  3 Dec 2021 00:28:21 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Fri, 03 Dec 2021 00:28:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=rkS7mCAbSfFIjYv8/DuLuphYzPkkPGU Ze9jGcMA6FFk=; b=mt29UklfmR8zSrqiTCgW9XCT3adm9S7dep5xSXS3kHUpij/ EdL9oyHWdx2HWHKttwpBlGOX36DnQVLHpQ76G5RFdtn6hXxTCnc5KhsemzC7ZGFU WHdLXQ0sRbqtd4cxyks5E6HO33CiFFpDhwgOKJFuK7KGHrRUbwHLGBgQdjCJwWwS rk2Yi/r20gJwAigExpqDTZlPNihkWnH2iEkGIZrr0udQ3smm1nRjyUQHZb/fl6xt 4xTOzYE338kRVcVSOfDFnLHY9EXGSbJraDfs/Xfo+ambkeGKKuIeSzU/nogrAivW GUUGdElB3xBWo4zAiBx2F7nmRltn5hu5eEQuzUg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rkS7mC AbSfFIjYv8/DuLuphYzPkkPGUZe9jGcMA6FFk=; b=NzB6FWeQwgrbaac0Hntv1+ 8BG4GJ+Zsu3zQ6ChIrihmPu3mLSBSKznkggtCLG5ni3gxJbXJr/vcUGgeksalQMG 7oF6mQs4su16gEIdvwDXVGJ/Y822LKROmeiCQBmGutoqr/GbEs3Dl5lh+sHmqdAq 8Oex6KUBetKMtdcYUpeonS4nCak76JYq0bKyhSZHW/KfPEvJ9/QlKkF1ZyFNcPaR wtK6X03dk+xfk07LHePWVXTwHPn/CjqznI+rw2zbT+tE6wZBp3UNO8f7ZR8o3YX+ r6nu6QlzHKl438IvpeaY2dmy0+bXf0beUXj+9lAR0Tro479TP8t/KWA9AhWaHNtw ==
X-ME-Sender: <xms:9KqpYSwKC00JEuwA0E12eJxbD3-GIzAraIhQ4hgVsSuTy1Yythx_Fw> <xme:9KqpYeT4XInn8T3GC_dM36Ffvny8W669Nwi_MW7xFZR9_BTXM72_V2xyGH0IEgm9s TWnkWGFVGtPDpb14Bg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrieeigdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:9KqpYUUpwyXmWWzQ36pIgHFNclfi56o1VKjlC52dy7tNlmKHlzHfdQ> <xmx:9KqpYYj8q5G7kMY6jRUBZrh3ZGwShfVa6cAyOeH4vaHnNqx4VJiLhA> <xmx:9KqpYUB6wIREnj0ZAyPRqgpapm2-Y7ixOApwx1VbQu3PT_6iLERQlA> <xmx:9aqpYT_kSXgM-pYj-Z0G7GGxBfBSKdn1Tpc0skqM7v8hVK3FAa8Q5Q>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id D61263C0F83; Fri,  3 Dec 2021 00:28:20 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4458-g51a91c06b2-fm-20211130.004-g51a91c06
Mime-Version: 1.0
Message-Id: <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com>
In-Reply-To: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com>
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com>
Date: Fri, 03 Dec 2021 16:27:55 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: "Christopher Patton" <cpatton=40cloudflare.com@dmarc.ietf.org>, ppm@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/WP7PF6y_dr_VY9yHWc8hZOuIZWQ>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Dec 2021 05:28:27 -0000

Hi Chris,

When you say

> This removes the Leader's coordination problem, at the cost 
> of additional storage requirements. In fact, both Aggregators need to 
> store the set of processed nonces for the duration of a task.

Having independent enforcement of anti-replay seems like it is important enough for this state to persist beyond the scope of a task.

Maybe stepping back and looking at how anti-replay is managed would help.  You don't want the same thing to be counted more than once.  The original design requires a total ordering of inputs, with a strict enforcement of that ordering.  That uses what is in effect a high resolution timestamp to ensuring that ordering is sensible.  It also means that tasks cannot be initiated out of order (or with overlapping inputs).  That seems unworkable to me.  Perfect global ordering, particularly when you consider helpers that serve multiple customers, is probably infeasible.

I think that #2 is the only reasonable outcome here.  However, you also need to use the timestamp (or part of it) to bound the time period during which you need to remember nonces.

That is, you use the time of an input to select from three different discard treatments:
1. discard because it is too old
2. discard because it is too new (which might be impossible, but you don't want something as simple as clock skew to be why your anti-replay was defeated)
3. discard if it has the same nonce as something you have previously accepted

In code:

if t < now() - window:
  discard as too old
else if t > now():
  discard as from the future
else if nonce in nonces_in_window:
  discard as duplicate
else:
  add nonce to nonces_in_window
  accept the measurement

(There's an interesting potential attack here in that a client provides different nonces or timestamps to each helper with a goal of spoiling results. Accepting half a share could be disastrous.  The validation process catches those pretty naturally, I think, probably.  This is something we should be careful to check any time that independent processing occurs like this.)

Separately, I've been looking at less simplistic applications of something like anti-replay.  I hope to be able to talk about that in more detail soon, but it might be that the anti-replay design you have is too restrictive for what we have in mind, no matter the outcome of this specific decision.


From nobody Sat Dec  4 15:18:04 2021
Return-Path: <cpatton@cloudflare.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 825EE3A0C29 for <ppm@ietfa.amsl.com>; Sat,  4 Dec 2021 15:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 hMQubXV6HSCI for <ppm@ietfa.amsl.com>; Sat,  4 Dec 2021 15:17:56 -0800 (PST)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (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 85D163A0C27 for <ppm@ietf.org>; Sat,  4 Dec 2021 15:17:56 -0800 (PST)
Received: by mail-qv1-xf2d.google.com with SMTP id kl8so6463011qvb.3 for <ppm@ietf.org>; Sat, 04 Dec 2021 15:17:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ooFUrlNx45pq1qfk/f4YLeAA22r00I8H6B39kQ5Y23E=; b=xRre45WzMy6z2tBX426cdHMbSZdX8uUAPEgEcdb/l3alLAgK9sntOSaIZnIC7Gq73M bjNePKofCKTLgY8vjuTY8lX2MlJH6FpxCntzqiodUcd/xBuO2EXJpkPvz2pc6JbTKc9d hwbTHTUBbx2FgxoQPCSy8ys8BDNe9q3ThIrrA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ooFUrlNx45pq1qfk/f4YLeAA22r00I8H6B39kQ5Y23E=; b=aTWO7VV2NmUFTrgMDEGWIF/lFkdQFPcTVcey4Y3Z72AMVzQEgyJfBT76DzbGjprdBM klLtwG1k6UNPu02I+o3xY+zGmFJdz6VjRuQ7JqSmQq8vnY8tg3RH9/3SWwFHryI+jgvA ID8NcCa3rBRg2GZn1sFoQ7YluDb08W+HENR6Vtb9fa7vKLVf86De5KzuuuKgKq2Tfzt6 /CnljuKkd7XI52yTFZ0zfwaLpWnBCo3xkJA5RMyBoCSXwil2tHB183srBy2CjYsfUStg 0JEfSoZdkdwYAQRcumPJ8dIEfPj/bEtyULOl5NakgPDy+PqyzSulhRBZ8hYOrtVlsd8E r68w==
X-Gm-Message-State: AOAM531Tqe39iem3Qy/UT5EkMtLartnUwc+VXT6rD7evsirznCyAtEko Tqq2jHEyKiIqe4xtLhTbe/y54tuwFYodPo7xfQrRnGWNvu4=
X-Google-Smtp-Source: ABdhPJwNAQScXH8i6/2ALbVi31ljikEkjYC1kAXOg5c3poAatu6hs8WZTDrAhAD+UPDetiAiLNAhAJdQrHZ/u4OkE4M=
X-Received: by 2002:a05:6214:d01:: with SMTP id 1mr27235902qvh.113.1638659874816;  Sat, 04 Dec 2021 15:17:54 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com>
In-Reply-To: <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Sat, 4 Dec 2021 15:17:43 -0800
Message-ID: <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: Christopher Patton <cpatton=40cloudflare.com@dmarc.ietf.org>, ppm@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bf87ed05d25a3b5d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/JoCUTr94snGk_KtFsNmBPJJqzbM>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Dec 2021 23:18:02 -0000

--000000000000bf87ed05d25a3b5d
Content-Type: text/plain; charset="UTF-8"

Hi Martin, thanks for your thoughtful reply. I really like your suggestion.
I'd like to hear what others think, and in absence of a reason not to take
it I think we should make this a PR :)

Best,
Chris P.

On Thu, Dec 2, 2021 at 9:28 PM Martin Thomson <mt@lowentropy.net> wrote:

> Hi Chris,
>
> When you say
>
> > This removes the Leader's coordination problem, at the cost
> > of additional storage requirements. In fact, both Aggregators need to
> > store the set of processed nonces for the duration of a task.
>
> Having independent enforcement of anti-replay seems like it is important
> enough for this state to persist beyond the scope of a task.
>
> Maybe stepping back and looking at how anti-replay is managed would help.
> You don't want the same thing to be counted more than once.  The original
> design requires a total ordering of inputs, with a strict enforcement of
> that ordering.  That uses what is in effect a high resolution timestamp to
> ensuring that ordering is sensible.  It also means that tasks cannot be
> initiated out of order (or with overlapping inputs).  That seems unworkable
> to me.  Perfect global ordering, particularly when you consider helpers
> that serve multiple customers, is probably infeasible.
>
> I think that #2 is the only reasonable outcome here.  However, you also
> need to use the timestamp (or part of it) to bound the time period during
> which you need to remember nonces.
>
> That is, you use the time of an input to select from three different
> discard treatments:
> 1. discard because it is too old
> 2. discard because it is too new (which might be impossible, but you don't
> want something as simple as clock skew to be why your anti-replay was
> defeated)
> 3. discard if it has the same nonce as something you have previously
> accepted
>
> In code:
>
> if t < now() - window:
>   discard as too old
> else if t > now():
>   discard as from the future
> else if nonce in nonces_in_window:
>   discard as duplicate
> else:
>   add nonce to nonces_in_window
>   accept the measurement
>
> (There's an interesting potential attack here in that a client provides
> different nonces or timestamps to each helper with a goal of spoiling
> results. Accepting half a share could be disastrous.  The validation
> process catches those pretty naturally, I think, probably.  This is
> something we should be careful to check any time that independent
> processing occurs like this.)
>
> Separately, I've been looking at less simplistic applications of something
> like anti-replay.  I hope to be able to talk about that in more detail
> soon, but it might be that the anti-replay design you have is too
> restrictive for what we have in mind, no matter the outcome of this
> specific decision.
>
> --
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm
>

--000000000000bf87ed05d25a3b5d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Martin, thanks for your thoughtful reply. I really=
 like your suggestion. I&#39;d like to hear what others think, and in absen=
ce of a reason not to take it I think we should make this a PR :)</div><div=
><br></div><div>Best,</div><div>Chris P.<br></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 2, 2021 at 9:=
28 PM Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy=
.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">Hi Chris,<br>
<br>
When you say<br>
<br>
&gt; This removes the Leader&#39;s coordination problem, at the cost <br>
&gt; of additional storage requirements. In fact, both Aggregators need to =
<br>
&gt; store the set of processed nonces for the duration of a task.<br>
<br>
Having independent enforcement of anti-replay seems like it is important en=
ough for this state to persist beyond the scope of a task.<br>
<br>
Maybe stepping back and looking at how anti-replay is managed would help.=
=C2=A0 You don&#39;t want the same thing to be counted more than once.=C2=
=A0 The original design requires a total ordering of inputs, with a strict =
enforcement of that ordering.=C2=A0 That uses what is in effect a high reso=
lution timestamp to ensuring that ordering is sensible.=C2=A0 It also means=
 that tasks cannot be initiated out of order (or with overlapping inputs).=
=C2=A0 That seems unworkable to me.=C2=A0 Perfect global ordering, particul=
arly when you consider helpers that serve multiple customers, is probably i=
nfeasible.<br>
<br>
I think that #2 is the only reasonable outcome here.=C2=A0 However, you als=
o need to use the timestamp (or part of it) to bound the time period during=
 which you need to remember nonces.<br>
<br>
That is, you use the time of an input to select from three different discar=
d treatments:<br>
1. discard because it is too old<br>
2. discard because it is too new (which might be impossible, but you don&#3=
9;t want something as simple as clock skew to be why your anti-replay was d=
efeated)<br>
3. discard if it has the same nonce as something you have previously accept=
ed<br>
<br>
In code:<br>
<br>
if t &lt; now() - window:<br>
=C2=A0 discard as too old<br>
else if t &gt; now():<br>
=C2=A0 discard as from the future<br>
else if nonce in nonces_in_window:<br>
=C2=A0 discard as duplicate<br>
else:<br>
=C2=A0 add nonce to nonces_in_window<br>
=C2=A0 accept the measurement<br>
<br>
(There&#39;s an interesting potential attack here in that a client provides=
 different nonces or timestamps to each helper with a goal of spoiling resu=
lts. Accepting half a share could be disastrous.=C2=A0 The validation proce=
ss catches those pretty naturally, I think, probably.=C2=A0 This is somethi=
ng we should be careful to check any time that independent processing occur=
s like this.)<br>
<br>
Separately, I&#39;ve been looking at less simplistic applications of someth=
ing like anti-replay.=C2=A0 I hope to be able to talk about that in more de=
tail soon, but it might be that the anti-replay design you have is too rest=
rictive for what we have in mind, no matter the outcome of this specific de=
cision.<br>
<br>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>

--000000000000bf87ed05d25a3b5d--


From nobody Sun Dec  5 00:41:36 2021
Return-Path: <do_not_reply@mnot.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9D23A1277 for <ppm@ietfa.amsl.com>; Sun,  5 Dec 2021 00:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=W1iXv7SY; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=AQZR7ixJ
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 OFmlwxifJFTK for <ppm@ietfa.amsl.com>; Sun,  5 Dec 2021 00:41:27 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B7D63A1271 for <ppm@ietf.org>; Sun,  5 Dec 2021 00:41:27 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 46AC03200C10 for <ppm@ietf.org>; Sun,  5 Dec 2021 02:39:42 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sun, 05 Dec 2021 02:39:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm1; bh=X2M5hRIQGAk WxltW2ir4MfDIU1grFwTdM9eY7v9qIhI=; b=W1iXv7SYnPD61RUYrm0bBOzVla+ ZDNK4kG34bDO+0ClX50/5ZDEpU8YNdgx0c7EsW1kRPNPY5RhbntUZz97bbTbL8N4 YUZoAqgElW/wGgnXsq8nQAFpqzTYsUVZ6oUQs8vYzYTEFQKV4pmulh6UaJMUREkF ch6HF+HqW56oZKpBgMmykU4GBfOOO2TANU/OA+WltdKOh0b4qr86ACi5ChQCnIm/ 5YBA/E2KELO3+V5O9xmJD2k3X0T1VEM+63fNWfDQHOikQgOok7NLiBynlseXlE8V W+uyTcKzt85libK5hpo/njhqVh0NSXMI9C+/Iiky/f9Cna3Nv3rOTBwzkhg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=X2M5hRIQGAkWxltW2ir4MfDIU1grFwTdM9eY7v9qIhI=; b=AQZR7ixJ nYYtMcjYzeBcotGqoGA/FbTjlz/6YPz6MhT/MEbRsyJJAw5Wt1eHwi9WG5tIgP8q jrOCMFUtTAtbokSb2T1gFJQ9oza4eWp0LRUqmZfsOO6JxIuhzg6N7t1dMIojT2Rb WFIJS7H8L20sFLncXMSsmt97V0JabwTtIXmXWqeQDUJQ/cX276w7Pe3AqRCqxhjD VO0Gt4hNYc8qggsV0EbORtq54nBBo6VtHM4t8ZAmAbDLaT0P9I8A1968uhcrILQ+ cauX0qhQIeH7O/03nfmONyEhOCUsq/EFdTwTjaei680fjanNh3BDOzT2mk1PK+t9 Nu8aGIBUpaFkdQ==
X-ME-Sender: <xms:vWysYa52HvyRLRNJcBxIEYnLNo2zZgd-DwFs5pHVFh8u2nsO4gLCXw> <xme:vWysYT749kubllhxyMoU7ZUo1plLiUrbHiomMhdegMCRQ78vYLbiV-H_6ulowWVan 9C31pRjC4PLKeAXZQ>
X-ME-Received: <xmr:vWysYZe-t89i0mGYWa53_ZcTIYeudPkSirBTwBC5KFYXB_xjfB3MNE0EGKnTEh3AsYiUhgTI_ZQ9KSAAaWws_eVEqBc7OKQAB7nBTK5SxLgqlYyU-Z3XLbK4w94-stesZQjUAg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrjedtgddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenuc fjughrpegtggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicu tegtthhivhhithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihse hmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeefvdduteejvdefkeehieevuefg fefhteetveegffekffefteffvdelheduieetnecuffhomhgrihhnpehgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:vWysYXI8j3D5yasiXbSSOGxcYx6rG7xiosszqSWGhIQ-1WiC8m2rgg> <xmx:vWysYeLspm7cuXxTXC6gReCbdvdtp5O3Te1tVZfhuOZW-kEsNT4oRA> <xmx:vWysYYyEJPNp99RKRIwvgcd3EGQte3OLw4qqToJ8ul3F219CNBjiFA> <xmx:vWysYVX0GUgsAwAjaEJ0Kh5flAl_u2UJaYxFQdXMne7SfuPdZ6X-_g>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ppm@ietf.org>;  Sun, 5 Dec 2021 02:39:41 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============9008548784319003262=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: ppm@ietf.org
Message-Id: <20211205084127.4B7D63A1271@ietfa.amsl.com>
Date: Sun,  5 Dec 2021 00:41:27 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/B6G5Fk4ZedbKi5iHERRxsYSKBUI>
Subject: [Ppm] Weekly github digest (Privacy Preserving Measurement Activity Summary)
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Dec 2021 08:41:33 -0000

--===============9008548784319003262==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events=20



Pull requests
-------------
* abetterinternet/ppm-specification (+0/-1/=F0=9F=92=AC0)
  1 pull requests merged:
  - Update charter.md
    https://github.com/abetterinternet/ppm-specification/pull/165=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/abetterinternet/ppm-specification

--===============9008548784319003262==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (Privacy Preserving Measurement Activity Summar=
y)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday December 05, 2021</h1>

<p>Events </p>



<h2>Pull requests</h2>
<h3>abetterinternet/ppm-specification (+0/-1/=F0=9F=92=AC0)</h3>


  <p>1 pull requests merged:</p>
  <ul>
  <li>#165 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/165">Update charter.md</a> </li>
  </ul>


  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/abetterinternet/ppm-specification">http=
s://github.com/abetterinternet/ppm-specification</a></li>
</ul>
</details>
</body>
</html>

--===============9008548784319003262==--


From nobody Mon Dec  6 10:45:06 2021
Return-Path: <erik.taubeneck@gmail.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DFDB3A0D28 for <ppm@ietfa.amsl.com>; Mon,  6 Dec 2021 10:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.687
X-Spam-Level: 
X-Spam-Status: No, score=-0.687 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9j0EE_D8txng for <ppm@ietfa.amsl.com>; Mon,  6 Dec 2021 10:44:59 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 73CF33A0D25 for <ppm@ietf.org>; Mon,  6 Dec 2021 10:44:59 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id u3so27667687lfl.2 for <ppm@ietf.org>; Mon, 06 Dec 2021 10:44:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/+7HWrsfoOO04tqnsh2pav72mi6wOUXMpivnPhRZj0Y=; b=mqv4/4QlfVPTGy2zTmcp8NK1B+ffoaXl9rr3nnJ2wjmJpY7rWwCulWt1ofV2pDNVQy OqRmHPvrfVTfSH/m4+CJBTMicMy9ofDG+LUgmMGKn4S/CGZDvFWDLUndKQoBSBzord4e czlZoOfBIluX0WX4eOrW5IRe2m1q2erGyN4MG9ZhFaMDtBT3W/4wKdTXy4+poUcuV25f NR1fS8xaaz26O/q7dBg/ZfXd3YUFGkgEReesi9A+meRtyPgSxPTnyunU9AxLrfXf2fqm 3JqjnsGQm/H0nFV0Mla7LYdPx1MOiJq+2zj5mlvkUIio8tgGB7IXcRFY2CDgNzZpYRgl P0Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/+7HWrsfoOO04tqnsh2pav72mi6wOUXMpivnPhRZj0Y=; b=DWj4NVdiIkpIryB3f4PhxFViV7ExvrzfB5PEi9zIE+l2D4UFNEuvNaHy9s1iQTHkRg kvcx0ojzvzbCYXHqvShX6u1ky6n2kch7Q8oV3WxNqI9JpytQnBh1WPvRCCdQ1zIe21Na azHlcCvuPQRoxWxwQEsrE8bnxG1gLCWAqs8ltl9wRoEhVCk1ThiW0VF6/89t/1KQOwpE rDEUKYSRK/cm0bH9BXcdqIgID24CkVALvudGmIYm34AHnQeHSxzlnxlNIU5hPqDA+PcZ bqxSSiY5kcpTB03OzvS4r/D1dzuGqaysYOLra+GEvd6AxH9gv9n6xaxUN8jpOVbsraxr XGcA==
X-Gm-Message-State: AOAM532LPBl6yhSo11TdY+goaEnjKJzGi/qvLLsNaX15aAdvJNlzWv1D n0u6wFpy3+RU/9Pnu3CDdj9vRzqnTOsVJX5MWJ7RAVBpbEo=
X-Google-Smtp-Source: ABdhPJxSbQdlX5c7JYSLnPi9d8pQdcaY6onXLftgx805G37a8jgDa6V5lB3fjW2KqsXuU41TQgswBmMhgldx+c9ULvs=
X-Received: by 2002:a19:c350:: with SMTP id t77mr36972022lff.152.1638816295758;  Mon, 06 Dec 2021 10:44:55 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com>
In-Reply-To: <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com>
From: Erik Taubeneck <erik.taubeneck@gmail.com>
Date: Mon, 6 Dec 2021 10:44:44 -0800
Message-ID: <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com>
To: Christopher Patton <cpatton=40cloudflare.com@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, ppm@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002930e105d27ea79b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/-SxwMJV1stHbfnqO8_aO8suSZ04>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2021 18:45:05 -0000

--0000000000002930e105d27ea79b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Martin said:

> Having independent enforcement of anti-replay seems like it is important
> enough for this state to persist beyond the scope of a task.


I strongly agree here, and it seems worthwhile to include in the spec. This
will be important for other privacy mechanisms, beyond anti-replay. For
example, if I understand correctly, the proposed WICG spec Attribution
Reporting API with Aggregate Reports
<https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.md>
aims to follow the PPM spec, and would require persistent state to manage a
privacy budget. In addition, that API may even allow replay in a controlled
manner within the privacy budget. From their proposal draft
<https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.md#=
privacy-budgeting>
:

Note: The design for the aggregation service also requires some amount of
> budgeting to ensure records aren=E2=80=99t processed too many times.


Charlie Harrison can likely provide more context on that specific proposal,
but I agree overall that we likely want to support more than just
anti-replay to enforce the privacy of the PPM results.

Cheers,

Erik


On Sat, Dec 4, 2021 at 3:18 PM Christopher Patton <cpatton=3D
40cloudflare.com@dmarc.ietf.org> wrote:

> Hi Martin, thanks for your thoughtful reply. I really like your
> suggestion. I'd like to hear what others think, and in absence of a reaso=
n
> not to take it I think we should make this a PR :)
>
> Best,
> Chris P.
>
> On Thu, Dec 2, 2021 at 9:28 PM Martin Thomson <mt@lowentropy.net> wrote:
>
>> Hi Chris,
>>
>> When you say
>>
>> > This removes the Leader's coordination problem, at the cost
>> > of additional storage requirements. In fact, both Aggregators need to
>> > store the set of processed nonces for the duration of a task.
>>
>> Having independent enforcement of anti-replay seems like it is important
>> enough for this state to persist beyond the scope of a task.
>>
>> Maybe stepping back and looking at how anti-replay is managed would
>> help.  You don't want the same thing to be counted more than once.  The
>> original design requires a total ordering of inputs, with a strict
>> enforcement of that ordering.  That uses what is in effect a high
>> resolution timestamp to ensuring that ordering is sensible.  It also mea=
ns
>> that tasks cannot be initiated out of order (or with overlapping inputs)=
.
>> That seems unworkable to me.  Perfect global ordering, particularly when
>> you consider helpers that serve multiple customers, is probably infeasib=
le.
>>
>> I think that #2 is the only reasonable outcome here.  However, you also
>> need to use the timestamp (or part of it) to bound the time period durin=
g
>> which you need to remember nonces.
>>
>> That is, you use the time of an input to select from three different
>> discard treatments:
>> 1. discard because it is too old
>> 2. discard because it is too new (which might be impossible, but you
>> don't want something as simple as clock skew to be why your anti-replay =
was
>> defeated)
>> 3. discard if it has the same nonce as something you have previously
>> accepted
>>
>> In code:
>>
>> if t < now() - window:
>>   discard as too old
>> else if t > now():
>>   discard as from the future
>> else if nonce in nonces_in_window:
>>   discard as duplicate
>> else:
>>   add nonce to nonces_in_window
>>   accept the measurement
>>
>> (There's an interesting potential attack here in that a client provides
>> different nonces or timestamps to each helper with a goal of spoiling
>> results. Accepting half a share could be disastrous.  The validation
>> process catches those pretty naturally, I think, probably.  This is
>> something we should be careful to check any time that independent
>> processing occurs like this.)
>>
>> Separately, I've been looking at less simplistic applications of
>> something like anti-replay.  I hope to be able to talk about that in mor=
e
>> detail soon, but it might be that the anti-replay design you have is too
>> restrictive for what we have in mind, no matter the outcome of this
>> specific decision.
>>
>> --
>> Ppm mailing list
>> Ppm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppm
>>
> --
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm
>

--0000000000002930e105d27ea79b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><span id=3D"gmail-docs-internal-guid-f877=
2bca-7fff-f6ef-01d5-a9c94f99824e"><p dir=3D"ltr" style=3D"line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><span style=3D"font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-variant-numeric:normal;font-vari=
ant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">Martin =
said:</span></p><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex" class=3D"gmail_quote"><span sty=
le=3D"font-family:Arial;font-variant-numeric:normal;font-variant-east-asian=
:normal;vertical-align:baseline;white-space:pre-wrap">Having independent en=
forcement of anti-replay seems like it is important enough for this state t=
o persist beyond the scope of a task.</span></blockquote><br><p dir=3D"ltr"=
 style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D=
"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-varia=
nt-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;wh=
ite-space:pre-wrap">I strongly agree here, and it seems worthwhile to inclu=
de in the spec. This will be important for other privacy mechanisms, beyond=
 anti-replay. For example, if I understand correctly, the proposed WICG spe=
c </span><a href=3D"https://github.com/WICG/conversion-measurement-api/blob=
/main/AGGREGATE.md" style=3D"text-decoration-line:none"><span style=3D"font=
-family:Arial;background-color:transparent;font-variant-numeric:normal;font=
-variant-east-asian:normal;text-decoration-line:underline;vertical-align:ba=
seline;white-space:pre-wrap">Attribution Reporting API with Aggregate Repor=
ts</span></a><span style=3D"font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;font-variant-numeric:normal;font-variant-east-asian:normal=
;vertical-align:baseline;white-space:pre-wrap"> aims to follow the PPM spec=
, and would require persistent state to manage a privacy budget. In additio=
n, that API may even allow replay in a controlled manner within the privacy=
 budget. From their </span><a href=3D"https://github.com/WICG/conversion-me=
asurement-api/blob/main/AGGREGATE.md#privacy-budgeting" style=3D"text-decor=
ation-line:none"><span style=3D"font-family:Arial;background-color:transpar=
ent;font-variant-numeric:normal;font-variant-east-asian:normal;text-decorat=
ion-line:underline;vertical-align:baseline;white-space:pre-wrap">proposal d=
raft</span></a><span style=3D"font-family:Arial;color:rgb(0,0,0);background=
-color:transparent;font-variant-numeric:normal;font-variant-east-asian:norm=
al;vertical-align:baseline;white-space:pre-wrap">:</span></p><br><blockquot=
e style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex" class=3D"gmail_quote"><span style=3D"font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-weight:700;font-variant-nu=
meric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-s=
pace:pre-wrap">Note:</span><span style=3D"font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-variant-numeric:normal;font-variant-eas=
t-asian:normal;vertical-align:baseline;white-space:pre-wrap"> The design fo=
r the aggregation service also requires some amount of budgeting to ensure =
records aren=E2=80=99t processed too many times.</span></blockquote><div><b=
r></div><div>Charlie Harrison can likely provide more context on that speci=
fic proposal, but I agree overall that we likely want to support more than =
just anti-replay to enforce the privacy of the PPM results.=C2=A0</div><br>=
<p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpar=
ent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-ali=
gn:baseline;white-space:pre-wrap">Cheers,</span></p><p dir=3D"ltr" style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-fam=
ily:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeri=
c:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space=
:pre-wrap">Erik</span></p></span><br class=3D"gmail-Apple-interchange-newli=
ne"></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Sat, Dec 4, 2021 at 3:18 PM Christopher Patton &lt;cpatton=3D<a href=
=3D"mailto:40cloudflare.com@dmarc.ietf.org">40cloudflare.com@dmarc.ietf.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><div>Hi Martin, thanks for your thoughtful reply. I really=
 like your suggestion. I&#39;d like to hear what others think, and in absen=
ce of a reason not to take it I think we should make this a PR :)</div><div=
><br></div><div>Best,</div><div>Chris P.<br></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 2, 2021 at 9:=
28 PM Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_bl=
ank">mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">Hi Chris,<br>
<br>
When you say<br>
<br>
&gt; This removes the Leader&#39;s coordination problem, at the cost <br>
&gt; of additional storage requirements. In fact, both Aggregators need to =
<br>
&gt; store the set of processed nonces for the duration of a task.<br>
<br>
Having independent enforcement of anti-replay seems like it is important en=
ough for this state to persist beyond the scope of a task.<br>
<br>
Maybe stepping back and looking at how anti-replay is managed would help.=
=C2=A0 You don&#39;t want the same thing to be counted more than once.=C2=
=A0 The original design requires a total ordering of inputs, with a strict =
enforcement of that ordering.=C2=A0 That uses what is in effect a high reso=
lution timestamp to ensuring that ordering is sensible.=C2=A0 It also means=
 that tasks cannot be initiated out of order (or with overlapping inputs).=
=C2=A0 That seems unworkable to me.=C2=A0 Perfect global ordering, particul=
arly when you consider helpers that serve multiple customers, is probably i=
nfeasible.<br>
<br>
I think that #2 is the only reasonable outcome here.=C2=A0 However, you als=
o need to use the timestamp (or part of it) to bound the time period during=
 which you need to remember nonces.<br>
<br>
That is, you use the time of an input to select from three different discar=
d treatments:<br>
1. discard because it is too old<br>
2. discard because it is too new (which might be impossible, but you don&#3=
9;t want something as simple as clock skew to be why your anti-replay was d=
efeated)<br>
3. discard if it has the same nonce as something you have previously accept=
ed<br>
<br>
In code:<br>
<br>
if t &lt; now() - window:<br>
=C2=A0 discard as too old<br>
else if t &gt; now():<br>
=C2=A0 discard as from the future<br>
else if nonce in nonces_in_window:<br>
=C2=A0 discard as duplicate<br>
else:<br>
=C2=A0 add nonce to nonces_in_window<br>
=C2=A0 accept the measurement<br>
<br>
(There&#39;s an interesting potential attack here in that a client provides=
 different nonces or timestamps to each helper with a goal of spoiling resu=
lts. Accepting half a share could be disastrous.=C2=A0 The validation proce=
ss catches those pretty naturally, I think, probably.=C2=A0 This is somethi=
ng we should be careful to check any time that independent processing occur=
s like this.)<br>
<br>
Separately, I&#39;ve been looking at less simplistic applications of someth=
ing like anti-replay.=C2=A0 I hope to be able to talk about that in more de=
tail soon, but it might be that the anti-replay design you have is too rest=
rictive for what we have in mind, no matter the outcome of this specific de=
cision.<br>
<br>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div></div>

--0000000000002930e105d27ea79b--


From nobody Tue Dec  7 15:18:35 2021
Return-Path: <cpatton@cloudflare.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38DF93A199E for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 15:18:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level: 
X-Spam-Status: No, score=-2.089 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 6SLaOmAOTKoz for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 15:18:28 -0800 (PST)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 B21E03A0A4E for <ppm@ietf.org>; Tue,  7 Dec 2021 15:18:28 -0800 (PST)
Received: by mail-qk1-x736.google.com with SMTP id t83so432117qke.8 for <ppm@ietf.org>; Tue, 07 Dec 2021 15:18:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rxAAilE82eJbc0PML4ZXjfH8UAIfGhSHpy7h0rG4FM4=; b=f+r3NnWr7SJdC5Sz66Ifpw0UXqYJAjeQrQvTuzVyaqjnULwos3SBsvHVCCvf9UZPA6 ONFCvo8txK6Cbv0nBRc047apqRPmoNngNDl/PtHesNv0ThiKsKqpme87Q00ZLJ33Ljv2 qcfejMERMTdeFBcEgN/Rbwu9TJUWBVY6+PYvQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rxAAilE82eJbc0PML4ZXjfH8UAIfGhSHpy7h0rG4FM4=; b=uzrUgxcjRySvzeWzP/W6nrERit/5ECcIYReNXTVP0qktkH/+EPRMnHf9tyIc17iPMI OMnzzHaohvUMj8QRAoaAk25QuRQfJVpPyM0+UoVrlXEWYlxncY9nntFv27VmxeMNThr8 RWOMtyvPZpxlubi+qQaF5Q0U5Wk2iwKveqcbiudo12Wf+ws6yZgXOmptGJoml5p2pWtZ /cK6YgfECwdZjNX9xbfpP6p86IPZIwthYaIcR+gTyLBc0lxm3ulJ+uebWWs1iFhStdta 4ZBkx5l4UmL5jEH2x2bJYjTkzjyR3I4rwfcAeKapNlYKWBd/2I54Qm1A5erNRia75HDJ VVFQ==
X-Gm-Message-State: AOAM530Hd4iB029uQAHuJSvLOs5jkoOsT1ztZhLS5f3S7eu9U4gfIwkm 9DJLgQeKxyW2DyRx7jpOXiylDR26nIcy7U+iWJPgTw==
X-Google-Smtp-Source: ABdhPJx0x/1ygJNnh4F55b4FkWOhbCXZxwOrHc5X3ivTfvdIN5jLHy0jCIq1Z+5FKflllxq/286GgY9cY9ha0wI3FI0=
X-Received: by 2002:a05:620a:4548:: with SMTP id u8mr2801561qkp.614.1638919106763;  Tue, 07 Dec 2021 15:18:26 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com>
In-Reply-To: <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Tue, 7 Dec 2021 15:18:15 -0800
Message-ID: <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com>
To: Erik Taubeneck <erik.taubeneck@gmail.com>
Cc: Christopher Patton <cpatton=40cloudflare.com@dmarc.ietf.org>,  Martin Thomson <mt@lowentropy.net>, ppm@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002cbd8e05d29697a1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/wG6otuiod-tAtHaOPrxNOCMHafY>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Dec 2021 23:18:34 -0000

--0000000000002cbd8e05d29697a1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Erik, yeah brought up this consideration early on in the process and
is indeed the reason we have this mechanism.

Here's a PR for implementing Martin's suggestion:
https://github.com/abetterinternet/ppm-specification/pull/169

Reviews appreciated!
Chris P.

On Mon, Dec 6, 2021 at 10:45 AM Erik Taubeneck <erik.taubeneck@gmail.com>
wrote:

> Martin said:
>
>> Having independent enforcement of anti-replay seems like it is important
>> enough for this state to persist beyond the scope of a task.
>
>
> I strongly agree here, and it seems worthwhile to include in the spec.
> This will be important for other privacy mechanisms, beyond anti-replay.
> For example, if I understand correctly, the proposed WICG spec Attributio=
n
> Reporting API with Aggregate Reports
> <https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.m=
d>
> aims to follow the PPM spec, and would require persistent state to manage=
 a
> privacy budget. In addition, that API may even allow replay in a controll=
ed
> manner within the privacy budget. From their proposal draft
> <https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.m=
d#privacy-budgeting>
> :
>
> Note: The design for the aggregation service also requires some amount of
>> budgeting to ensure records aren=E2=80=99t processed too many times.
>
>
> Charlie Harrison can likely provide more context on that specific
> proposal, but I agree overall that we likely want to support more than ju=
st
> anti-replay to enforce the privacy of the PPM results.
>
> Cheers,
>
> Erik
>
>
> On Sat, Dec 4, 2021 at 3:18 PM Christopher Patton <cpatton=3D
> 40cloudflare.com@dmarc.ietf.org> wrote:
>
>> Hi Martin, thanks for your thoughtful reply. I really like your
>> suggestion. I'd like to hear what others think, and in absence of a reas=
on
>> not to take it I think we should make this a PR :)
>>
>> Best,
>> Chris P.
>>
>> On Thu, Dec 2, 2021 at 9:28 PM Martin Thomson <mt@lowentropy.net> wrote:
>>
>>> Hi Chris,
>>>
>>> When you say
>>>
>>> > This removes the Leader's coordination problem, at the cost
>>> > of additional storage requirements. In fact, both Aggregators need to
>>> > store the set of processed nonces for the duration of a task.
>>>
>>> Having independent enforcement of anti-replay seems like it is importan=
t
>>> enough for this state to persist beyond the scope of a task.
>>>
>>> Maybe stepping back and looking at how anti-replay is managed would
>>> help.  You don't want the same thing to be counted more than once.  The
>>> original design requires a total ordering of inputs, with a strict
>>> enforcement of that ordering.  That uses what is in effect a high
>>> resolution timestamp to ensuring that ordering is sensible.  It also me=
ans
>>> that tasks cannot be initiated out of order (or with overlapping inputs=
).
>>> That seems unworkable to me.  Perfect global ordering, particularly whe=
n
>>> you consider helpers that serve multiple customers, is probably infeasi=
ble.
>>>
>>> I think that #2 is the only reasonable outcome here.  However, you also
>>> need to use the timestamp (or part of it) to bound the time period duri=
ng
>>> which you need to remember nonces.
>>>
>>> That is, you use the time of an input to select from three different
>>> discard treatments:
>>> 1. discard because it is too old
>>> 2. discard because it is too new (which might be impossible, but you
>>> don't want something as simple as clock skew to be why your anti-replay=
 was
>>> defeated)
>>> 3. discard if it has the same nonce as something you have previously
>>> accepted
>>>
>>> In code:
>>>
>>> if t < now() - window:
>>>   discard as too old
>>> else if t > now():
>>>   discard as from the future
>>> else if nonce in nonces_in_window:
>>>   discard as duplicate
>>> else:
>>>   add nonce to nonces_in_window
>>>   accept the measurement
>>>
>>> (There's an interesting potential attack here in that a client provides
>>> different nonces or timestamps to each helper with a goal of spoiling
>>> results. Accepting half a share could be disastrous.  The validation
>>> process catches those pretty naturally, I think, probably.  This is
>>> something we should be careful to check any time that independent
>>> processing occurs like this.)
>>>
>>> Separately, I've been looking at less simplistic applications of
>>> something like anti-replay.  I hope to be able to talk about that in mo=
re
>>> detail soon, but it might be that the anti-replay design you have is to=
o
>>> restrictive for what we have in mind, no matter the outcome of this
>>> specific decision.
>>>
>>> --
>>> Ppm mailing list
>>> Ppm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ppm
>>>
>> --
>> Ppm mailing list
>> Ppm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppm
>>
> --
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm
>

--0000000000002cbd8e05d29697a1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks Erik, yeah brought up this consideration early=
 on in the process and is indeed the reason we have this mechanism.</div><d=
iv><br></div><div>Here&#39;s a PR for implementing Martin&#39;s suggestion:=
 <a href=3D"https://github.com/abetterinternet/ppm-specification/pull/169">=
https://github.com/abetterinternet/ppm-specification/pull/169</a></div><div=
><br></div><div>Reviews appreciated!</div><div>Chris P.<br></div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, De=
c 6, 2021 at 10:45 AM Erik Taubeneck &lt;<a href=3D"mailto:erik.taubeneck@g=
mail.com">erik.taubeneck@gmail.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><span i=
d=3D"gmail-m_6811398081823229146gmail-docs-internal-guid-f8772bca-7fff-f6ef=
-01d5-a9c94f99824e"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><span style=3D"font-family:Arial;color:rgb(0,0,0);backg=
round-color:transparent;font-variant-numeric:normal;font-variant-east-asian=
:normal;vertical-align:baseline;white-space:pre-wrap">Martin said:</span></=
p><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex" class=3D"gmail_quote"><span style=3D"font-fam=
ily:Arial;font-variant-numeric:normal;font-variant-east-asian:normal;vertic=
al-align:baseline;white-space:pre-wrap">Having independent enforcement of a=
nti-replay seems like it is important enough for this state to persist beyo=
nd the scope of a task.</span></blockquote><br><p dir=3D"ltr" style=3D"line=
-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-family:A=
rial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:nor=
mal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-=
wrap">I strongly agree here, and it seems worthwhile to include in the spec=
. This will be important for other privacy mechanisms, beyond anti-replay. =
For example, if I understand correctly, the proposed WICG spec </span><a hr=
ef=3D"https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGAT=
E.md" style=3D"text-decoration-line:none" target=3D"_blank"><span style=3D"=
font-family:Arial;background-color:transparent;font-variant-numeric:normal;=
font-variant-east-asian:normal;text-decoration-line:underline;vertical-alig=
n:baseline;white-space:pre-wrap">Attribution Reporting API with Aggregate R=
eports</span></a><span style=3D"font-family:Arial;color:rgb(0,0,0);backgrou=
nd-color:transparent;font-variant-numeric:normal;font-variant-east-asian:no=
rmal;vertical-align:baseline;white-space:pre-wrap"> aims to follow the PPM =
spec, and would require persistent state to manage a privacy budget. In add=
ition, that API may even allow replay in a controlled manner within the pri=
vacy budget. From their </span><a href=3D"https://github.com/WICG/conversio=
n-measurement-api/blob/main/AGGREGATE.md#privacy-budgeting" style=3D"text-d=
ecoration-line:none" target=3D"_blank"><span style=3D"font-family:Arial;bac=
kground-color:transparent;font-variant-numeric:normal;font-variant-east-asi=
an:normal;text-decoration-line:underline;vertical-align:baseline;white-spac=
e:pre-wrap">proposal draft</span></a><span style=3D"font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-v=
ariant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">:</s=
pan></p><br><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex" class=3D"gmail_quote"><span style=
=3D"font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:700;font-variant-numeric:normal;font-variant-east-asian:normal;vertica=
l-align:baseline;white-space:pre-wrap">Note:</span><span style=3D"font-fami=
ly:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric=
:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:=
pre-wrap"> The design for the aggregation service also requires some amount=
 of budgeting to ensure records aren=E2=80=99t processed too many times.</s=
pan></blockquote><div><br></div><div>Charlie Harrison can likely provide mo=
re context on that specific proposal, but I agree overall that we likely wa=
nt to support more than just anti-replay to enforce the privacy of the PPM =
results.=C2=A0</div><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top=
:0pt;margin-bottom:0pt"><span style=3D"font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-variant-numeric:normal;font-variant-east-a=
sian:normal;vertical-align:baseline;white-space:pre-wrap">Cheers,</span></p=
><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"=
><span style=3D"font-family:Arial;color:rgb(0,0,0);background-color:transpa=
rent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-al=
ign:baseline;white-space:pre-wrap">Erik</span></p></span><br></div><br><div=
 class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Dec 4,=
 2021 at 3:18 PM Christopher Patton &lt;cpatton=3D<a href=3D"mailto:40cloud=
flare.com@dmarc.ietf.org" target=3D"_blank">40cloudflare.com@dmarc.ietf.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><div>Hi Martin, thanks for your thoughtful reply. I really=
 like your suggestion. I&#39;d like to hear what others think, and in absen=
ce of a reason not to take it I think we should make this a PR :)</div><div=
><br></div><div>Best,</div><div>Chris P.<br></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 2, 2021 at 9:=
28 PM Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_bl=
ank">mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">Hi Chris,<br>
<br>
When you say<br>
<br>
&gt; This removes the Leader&#39;s coordination problem, at the cost <br>
&gt; of additional storage requirements. In fact, both Aggregators need to =
<br>
&gt; store the set of processed nonces for the duration of a task.<br>
<br>
Having independent enforcement of anti-replay seems like it is important en=
ough for this state to persist beyond the scope of a task.<br>
<br>
Maybe stepping back and looking at how anti-replay is managed would help.=
=C2=A0 You don&#39;t want the same thing to be counted more than once.=C2=
=A0 The original design requires a total ordering of inputs, with a strict =
enforcement of that ordering.=C2=A0 That uses what is in effect a high reso=
lution timestamp to ensuring that ordering is sensible.=C2=A0 It also means=
 that tasks cannot be initiated out of order (or with overlapping inputs).=
=C2=A0 That seems unworkable to me.=C2=A0 Perfect global ordering, particul=
arly when you consider helpers that serve multiple customers, is probably i=
nfeasible.<br>
<br>
I think that #2 is the only reasonable outcome here.=C2=A0 However, you als=
o need to use the timestamp (or part of it) to bound the time period during=
 which you need to remember nonces.<br>
<br>
That is, you use the time of an input to select from three different discar=
d treatments:<br>
1. discard because it is too old<br>
2. discard because it is too new (which might be impossible, but you don&#3=
9;t want something as simple as clock skew to be why your anti-replay was d=
efeated)<br>
3. discard if it has the same nonce as something you have previously accept=
ed<br>
<br>
In code:<br>
<br>
if t &lt; now() - window:<br>
=C2=A0 discard as too old<br>
else if t &gt; now():<br>
=C2=A0 discard as from the future<br>
else if nonce in nonces_in_window:<br>
=C2=A0 discard as duplicate<br>
else:<br>
=C2=A0 add nonce to nonces_in_window<br>
=C2=A0 accept the measurement<br>
<br>
(There&#39;s an interesting potential attack here in that a client provides=
 different nonces or timestamps to each helper with a goal of spoiling resu=
lts. Accepting half a share could be disastrous.=C2=A0 The validation proce=
ss catches those pretty naturally, I think, probably.=C2=A0 This is somethi=
ng we should be careful to check any time that independent processing occur=
s like this.)<br>
<br>
Separately, I&#39;ve been looking at less simplistic applications of someth=
ing like anti-replay.=C2=A0 I hope to be able to talk about that in more de=
tail soon, but it might be that the anti-replay design you have is too rest=
rictive for what we have in mind, no matter the outcome of this specific de=
cision.<br>
<br>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div></div>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>

--0000000000002cbd8e05d29697a1--


From nobody Tue Dec  7 16:03:58 2021
Return-Path: <mt@lowentropy.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D64C3A03FA for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 16:03:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=DEMp7CKI; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=HBmb/OHk
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 PmsC13X5nFGh for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 16:03:52 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC9C73A03F8 for <ppm@ietf.org>; Tue,  7 Dec 2021 16:03:51 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 1344E5C04C1 for <ppm@ietf.org>; Tue,  7 Dec 2021 19:03:51 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Tue, 07 Dec 2021 19:03:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm1; bh=mVv9j /JSk9QSTtPggXtZfKrZXNgUy/3tgCIdR7Z1LLo=; b=DEMp7CKIMcHVULqGaDtK+ DsVNnoqp61J1Z/EmFKGHi6yso2NVP0g7ECO4kPUP6VOlTZvpE3J0UhwlXMHv1Gxv L6EcUJJTbda3Fg7w+1XjX5ok+GuyfLXIZr5jtD4/z/zS97uNWs/J4fYSxh5Xt05K vVghrrq4uKvFTX70zfLJ8Cx58blbRcCCgDsreF7QJza0RkS4axT8Nu0fiwZtT+Zu VmAcf+y5dgKkXRAsR5/ozU57/0DsgXei1HCOJkiUcDJAfa7L5Q2Dpmy8TPrp8e5Z 2Lck2gz3SNRKRs6rq4pHKiVo+4Vtf1chzIpw0nMzvIMObIS/YzWXCrvKcuIgLH7x A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=mVv9j/JSk9QSTtPggXtZfKrZXNgUy/3tgCIdR7Z1L Lo=; b=HBmb/OHkVdnRx5TEK0GTP0LWEOtXlqTPE4w9+4kSJlL8tPTEsEMlWCZgI hv1IdrfXY6wEjmnCjzZZSDych2nb8zqRh56E1ni2+JiU6ZQWuUns/pXm6PKgU/Sk knsNCR2icjUCZkDEoXh2ApXIhxZxB6ttEdTuHpMDHUqdb62OII9KsCHYaWx9iT5d 03zG5kGALe2M5mjV+ISRDbaYHEyojRHnQu1XmumBFaYIsI5G1TuO+gdEceMkAV13 tssRx/L1t/IlBQynPpgNN12JyHENfNn9j0H2Varu/6usonsI8/aJkhG1PmCmbLtP S4F9HV5/J+BSoWo3kTirHgSB15JyQ==
X-ME-Sender: <xms:ZvavYR3fvBGZLOk91nc7CgxKrZu3hnqK_DQQQddx06rtBm2Ha_zhgw> <xme:ZvavYYEpkVoKy8pMPKYwSMPfdLXC0WazwL46aFT84aa5QoOl10Z7VmbRXLcI13rNU MCg6gdbmBCyTKrCHuo>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrjeeigddujecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpedujeevueejgfehgeehff ekueefjeeuheeutedvteegtddviedugffhheejtdeuieenucffohhmrghinhepghhithhh uhgsrdgtohhmpdgrghhgrhgvghgrthgvrdhmugdpihgvthhfrdhorhhgnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhr ohhphidrnhgvth
X-ME-Proxy: <xmx:Z_avYR7qZBN5in5SgRc54_1BINswHBzRSTMPQRy546ZHEoP8ak32yw> <xmx:Z_avYe0O2ggol88b1vn-djXBaGn033-Qkcy9UXB2fUye2KiqSlPHQw> <xmx:Z_avYUENATMiZihCYP8tzs2Uinbcd6FTbfAshbEnoHncEi4xIRycXg> <xmx:Z_avYYQwbWav8RJVw8iuMiog9gJsqyqVBQsQbUGYOr83YpQOPh8GcA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id F1C613C04A3; Tue,  7 Dec 2021 19:03:50 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4492-g121c2470aa-fm-20211206.001-g121c2470
Mime-Version: 1.0
Message-Id: <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com>
In-Reply-To: <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com>
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com>
Date: Wed, 08 Dec 2021 11:03:31 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: ppm@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/9E8nWx-LbT0g9jXc6PdTT6mtDXU>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 00:03:57 -0000

Thanks for putting this together Chris,

There is an implicit assumption in this design that says that reports ar=
e bound to a task that is known when the report is generated.  To that e=
nd, this design is probably not the best design that we might come up wi=
th.

If you assume this operating model, there are two sort of natural ways t=
o approach the report collection process:

1. You publicize a task ID at some time.  Clients produce reports over s=
ome period and when you have enough you close the task and generate an a=
ggregate.  In this model, individual reports could be evenly distributed=
 over the period fairly evenly, so using a timestamp as part of your non=
ce is a good way to improve collision resistance.

2. Reports are generated on demand.  Perhaps you have a polling process =
that contacts clients at certain times, gives them a task ID and asks fo=
r a report.  In this model, reports might be generated all at once, whic=
h makes times less useful for avoiding collision.

In both cases, the task ID is what prevents any individual report from b=
eing used for multiple reports.  Replay within the task is assured by th=
e uniqueness of the nonce, not the value of the timestamp. =20

Of course, you could reuse a task ID, but we might reasonably assume tha=
t the aggregation service will not accept that.  Or, you could design a =
system in which the task ID is usable for multiple aggregation runs, but=
 that seems like it defeats the purpose of having a high entropy task ID=
 in the first place.  My thought is that it might be even better to have=
 a leader assign task IDs so that uniqueness can be assured more easily.=
  If I'm right in that the task ID is central to the anti-replay design,=
 then that is a more robust design.

With that in mind, I'm not sure that you even need a timestamp at all.  =
At least for this design.  I think that if we want to consider designs w=
here the use of a single report is not so strictly Boolean, then we coul=
d need timestamps.

On Wed, Dec 8, 2021, at 10:18, Christopher Patton wrote:
> Thanks Erik, yeah brought up this consideration early on in the proces=
s=20
> and is indeed the reason we have this mechanism.
>
> Here's a PR for implementing Martin's suggestion:=20
> https://github.com/abetterinternet/ppm-specification/pull/169
>
> Reviews appreciated!
> Chris P.
>
> On Mon, Dec 6, 2021 at 10:45 AM Erik Taubeneck <erik.taubeneck@gmail.c=
om> wrote:
>> Martin said:
>>=20
>>> Having independent enforcement of anti-replay seems like it is impor=
tant enough for this state to persist beyond the scope of a task.
>> I strongly agree here, and it seems worthwhile to include in the spec=
. This will be important for other privacy mechanisms, beyond anti-repla=
y. For example, if I understand correctly, the proposed WICG spec Attrib=
ution Reporting API with Aggregate Reports <https://github.com/WICG/conv=
ersion-measurement-api/blob/main/AGGREGATE.md> aims to follow the PPM sp=
ec, and would require persistent state to manage a privacy budget. In ad=
dition, that API may even allow replay in a controlled manner within the=
 privacy budget. From their proposal draft <https://github.com/WICG/conv=
ersion-measurement-api/blob/main/AGGREGATE.md#privacy-budgeting>:
>>=20
>>=20
>>> Note: The design for the aggregation service also requires some amou=
nt of budgeting to ensure records aren=E2=80=99t processed too many time=
s.
>>=20
>> Charlie Harrison can likely provide more context on that specific pro=
posal, but I agree overall that we likely want to support more than just=
 anti-replay to enforce the privacy of the PPM results.=20
>>=20
>> Cheers,
>>=20
>> Erik
>>=20
>>=20
>>=20
>> On Sat, Dec 4, 2021 at 3:18 PM Christopher Patton <cpatton=3D40cloudf=
lare.com@dmarc.ietf.org> wrote:
>>> Hi Martin, thanks for your thoughtful reply. I really like your sugg=
estion. I'd like to hear what others think, and in absence of a reason n=
ot to take it I think we should make this a PR :)
>>>=20
>>> Best,
>>> Chris P.
>>>=20
>>> On Thu, Dec 2, 2021 at 9:28 PM Martin Thomson <mt@lowentropy.net> wr=
ote:
>>>> Hi Chris,
>>>>=20
>>>> When you say
>>>>=20
>>>> > This removes the Leader's coordination problem, at the cost=20
>>>> > of additional storage requirements. In fact, both Aggregators nee=
d to=20
>>>> > store the set of processed nonces for the duration of a task.
>>>>=20
>>>> Having independent enforcement of anti-replay seems like it is impo=
rtant enough for this state to persist beyond the scope of a task.
>>>>=20
>>>> Maybe stepping back and looking at how anti-replay is managed would=
 help.  You don't want the same thing to be counted more than once.  The=
 original design requires a total ordering of inputs, with a strict enfo=
rcement of that ordering.  That uses what is in effect a high resolution=
 timestamp to ensuring that ordering is sensible.  It also means that ta=
sks cannot be initiated out of order (or with overlapping inputs).  That=
 seems unworkable to me.  Perfect global ordering, particularly when you=
 consider helpers that serve multiple customers, is probably infeasible.
>>>>=20
>>>> I think that #2 is the only reasonable outcome here.  However, you =
also need to use the timestamp (or part of it) to bound the time period =
during which you need to remember nonces.
>>>>=20
>>>> That is, you use the time of an input to select from three differen=
t discard treatments:
>>>> 1. discard because it is too old
>>>> 2. discard because it is too new (which might be impossible, but yo=
u don't want something as simple as clock skew to be why your anti-repla=
y was defeated)
>>>> 3. discard if it has the same nonce as something you have previousl=
y accepted
>>>>=20
>>>> In code:
>>>>=20
>>>> if t < now() - window:
>>>>   discard as too old
>>>> else if t > now():
>>>>   discard as from the future
>>>> else if nonce in nonces_in_window:
>>>>   discard as duplicate
>>>> else:
>>>>   add nonce to nonces_in_window
>>>>   accept the measurement
>>>>=20
>>>> (There's an interesting potential attack here in that a client prov=
ides different nonces or timestamps to each helper with a goal of spoili=
ng results. Accepting half a share could be disastrous.  The validation =
process catches those pretty naturally, I think, probably.  This is some=
thing we should be careful to check any time that independent processing=
 occurs like this.)
>>>>=20
>>>> Separately, I've been looking at less simplistic applications of so=
mething like anti-replay.  I hope to be able to talk about that in more =
detail soon, but it might be that the anti-replay design you have is too=
 restrictive for what we have in mind, no matter the outcome of this spe=
cific decision.
>>>>=20
>>>> --=20
>>>> Ppm mailing list
>>>> Ppm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ppm
>>> --=20
>>> Ppm mailing list
>>> Ppm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ppm
>> --=20
>> Ppm mailing list
>> Ppm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppm
> --=20
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm


From nobody Tue Dec  7 16:37:46 2021
Return-Path: <timg@letsencrypt.org>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4997D3A05F8 for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 16:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.701, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=letsencrypt.org
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 3qYFxyny0plk for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 16:37:39 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 97EA83A0603 for <ppm@ietf.org>; Tue,  7 Dec 2021 16:37:39 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id m186so602130qkb.4 for <ppm@ietf.org>; Tue, 07 Dec 2021 16:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=letsencrypt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uz6MI80s9W1StJUCuTdBmDNyq0cCqRoAXdaaxT4USgI=; b=P5qp2tX9hRCE77HDrJRWHIBr32NrQ8wjv2osCZa3mnYCrbnwcPcdHdxPWnlpkJJ5Ae jIOrsMHEoOuHjD4iZo17zBJEVodCPmcN5XBClC9zrZ3BzsABzqAx88j3Vq5Bw91ZPcVN NwoedZRMLm8Dd3rO7vUBAvqAiB7KB4eVS4CbU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uz6MI80s9W1StJUCuTdBmDNyq0cCqRoAXdaaxT4USgI=; b=XiuyOHg/Y292ZxOGeYbhL2SrDP50cvZut4ryUcaGOXTuJftlZoK6dNFNl4pdaShV+V U3CTa93j1BZO3EUbDsgRVlhS7ueBk9IVtJ1yDxrzjbLnYZNF7qUr8mf5RWYyLgffUsEC KEcCCovxh+86IuWFAxMXezbie1YURPrz/qgbd3D9by3gI0gVuIlpP3zFoATxnc88dtmm gAuue9AnYTg0TPubCuitvjNXgNEBtq8Q0LVAiF8BcG1K5ybWeea38lGbKvaDVyLECVLL E739BSiPFoZzqFKeeQFnPvArIm+GzuNVzT84UL5bTqup5YoihCS2p/x7HypJmPMQnERj WJgw==
X-Gm-Message-State: AOAM530F86l7z+B6mQZCecHMj8driBdj/OgD5IBk3GrlfLW7DIA7/7vL DjQe0pc+mdQGpS2A/xRaD0hElGDLTBkYEVsgPAgL0nY2H0wyNA==
X-Google-Smtp-Source: ABdhPJznqV5HCO5kiqjirH8PDPRKEALterUMQ5c6GxUsXbpGlZRVDhkiWgRfUGncXRW+NgQ0fnoy4255CANTT1jxScA=
X-Received: by 2002:a05:620a:85e:: with SMTP id u30mr3072153qku.765.1638923856967;  Tue, 07 Dec 2021 16:37:36 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com>
In-Reply-To: <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com>
From: Tim Geoghegan <timg@letsencrypt.org>
Date: Tue, 7 Dec 2021 16:37:26 -0800
Message-ID: <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: ppm@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004f0e8d05d297b2cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/PZST9-eTkHTgQ0gjEZuAwZwDGCA>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 00:37:44 -0000

--0000000000004f0e8d05d297b2cc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Martin,

I think you may be misunderstanding the purpose or scope of the task ID (or
perhaps I should say: the draft is not sufficiently clear about how task ID
works). You write:

>You publicize a task ID at some time.  Clients produce reports over some
period and when you have enough you close the task and generate an
aggregate.

...suggesting a 1:1 relationship between a task ID and an aggregate emitted
by a PPM deployment. Rather, a task ID describes a long-running report
collection and aggregation task, for which aggregates are emitted
periodically (the period or _aggregation window_ is one of the parameters
associated with a task ID). Further, many clients may be contributing
reports under a single task ID.

So for example, imagine a web browser measuring whether users press a
certain button. The browser vendor would configure a PPM task and
distribute its parameters to two aggregators (n.b. the mechanism for task
parameter distribution is explicitly out of scope for the PPM protocol).
Then, the browser vendor ships a version of the browser to all its users
that knows about the task ID (the task ID could be compiled into the
browser or maybe the browser vendor has some secure configuration
mechanism). Browser installations then start submitting reports to
aggregators using the task ID.

>Reports are generated on demand.  Perhaps you have a polling process that
contacts clients at certain times, gives them a task ID and asks for a
report.  In this model, reports might be generated all at once, which makes
times less useful for avoiding collision.

In PPM, clients push reports into aggregators rather than having reports
pulled (or scraped, as Prometheus would put it) from clients by
aggregators. This is necessary because clients will frequently be behind
NAT or egress only firewalls or unable to keep a port open for metrics
pulls for some other reason.

Thanks,
Tim

On Tue, Dec 7, 2021 at 4:04 PM Martin Thomson <mt@lowentropy.net> wrote:

> Thanks for putting this together Chris,
>
> There is an implicit assumption in this design that says that reports are
> bound to a task that is known when the report is generated.  To that end,
> this design is probably not the best design that we might come up with.
>
> If you assume this operating model, there are two sort of natural ways to
> approach the report collection process:
>
> 1. You publicize a task ID at some time.  Clients produce reports over
> some period and when you have enough you close the task and generate an
> aggregate.  In this model, individual reports could be evenly distributed
> over the period fairly evenly, so using a timestamp as part of your nonce
> is a good way to improve collision resistance.
>
> 2. Reports are generated on demand.  Perhaps you have a polling process
> that contacts clients at certain times, gives them a task ID and asks for=
 a
> report.  In this model, reports might be generated all at once, which mak=
es
> times less useful for avoiding collision.
>
> In both cases, the task ID is what prevents any individual report from
> being used for multiple reports.  Replay within the task is assured by th=
e
> uniqueness of the nonce, not the value of the timestamp.
>
> Of course, you could reuse a task ID, but we might reasonably assume that
> the aggregation service will not accept that.  Or, you could design a
> system in which the task ID is usable for multiple aggregation runs, but
> that seems like it defeats the purpose of having a high entropy task ID i=
n
> the first place.  My thought is that it might be even better to have a
> leader assign task IDs so that uniqueness can be assured more easily.  If
> I'm right in that the task ID is central to the anti-replay design, then
> that is a more robust design.
>
> With that in mind, I'm not sure that you even need a timestamp at all.  A=
t
> least for this design.  I think that if we want to consider designs where
> the use of a single report is not so strictly Boolean, then we could need
> timestamps.
>
> On Wed, Dec 8, 2021, at 10:18, Christopher Patton wrote:
> > Thanks Erik, yeah brought up this consideration early on in the process
> > and is indeed the reason we have this mechanism.
> >
> > Here's a PR for implementing Martin's suggestion:
> > https://github.com/abetterinternet/ppm-specification/pull/169
> >
> > Reviews appreciated!
> > Chris P.
> >
> > On Mon, Dec 6, 2021 at 10:45 AM Erik Taubeneck <erik.taubeneck@gmail.co=
m>
> wrote:
> >> Martin said:
> >>
> >>> Having independent enforcement of anti-replay seems like it is
> important enough for this state to persist beyond the scope of a task.
> >> I strongly agree here, and it seems worthwhile to include in the spec.
> This will be important for other privacy mechanisms, beyond anti-replay.
> For example, if I understand correctly, the proposed WICG spec Attributio=
n
> Reporting API with Aggregate Reports <
> https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.md=
>
> aims to follow the PPM spec, and would require persistent state to manage=
 a
> privacy budget. In addition, that API may even allow replay in a controll=
ed
> manner within the privacy budget. From their proposal draft <
> https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.md=
#privacy-budgeting
> >:
> >>
> >>
> >>> Note: The design for the aggregation service also requires some amoun=
t
> of budgeting to ensure records aren=E2=80=99t processed too many times.
> >>
> >> Charlie Harrison can likely provide more context on that specific
> proposal, but I agree overall that we likely want to support more than ju=
st
> anti-replay to enforce the privacy of the PPM results.
> >>
> >> Cheers,
> >>
> >> Erik
> >>
> >>
> >>
> >> On Sat, Dec 4, 2021 at 3:18 PM Christopher Patton <cpatton=3D
> 40cloudflare.com@dmarc.ietf.org> wrote:
> >>> Hi Martin, thanks for your thoughtful reply. I really like your
> suggestion. I'd like to hear what others think, and in absence of a reaso=
n
> not to take it I think we should make this a PR :)
> >>>
> >>> Best,
> >>> Chris P.
> >>>
> >>> On Thu, Dec 2, 2021 at 9:28 PM Martin Thomson <mt@lowentropy.net>
> wrote:
> >>>> Hi Chris,
> >>>>
> >>>> When you say
> >>>>
> >>>> > This removes the Leader's coordination problem, at the cost
> >>>> > of additional storage requirements. In fact, both Aggregators need
> to
> >>>> > store the set of processed nonces for the duration of a task.
> >>>>
> >>>> Having independent enforcement of anti-replay seems like it is
> important enough for this state to persist beyond the scope of a task.
> >>>>
> >>>> Maybe stepping back and looking at how anti-replay is managed would
> help.  You don't want the same thing to be counted more than once.  The
> original design requires a total ordering of inputs, with a strict
> enforcement of that ordering.  That uses what is in effect a high
> resolution timestamp to ensuring that ordering is sensible.  It also mean=
s
> that tasks cannot be initiated out of order (or with overlapping inputs).
> That seems unworkable to me.  Perfect global ordering, particularly when
> you consider helpers that serve multiple customers, is probably infeasibl=
e.
> >>>>
> >>>> I think that #2 is the only reasonable outcome here.  However, you
> also need to use the timestamp (or part of it) to bound the time period
> during which you need to remember nonces.
> >>>>
> >>>> That is, you use the time of an input to select from three different
> discard treatments:
> >>>> 1. discard because it is too old
> >>>> 2. discard because it is too new (which might be impossible, but you
> don't want something as simple as clock skew to be why your anti-replay w=
as
> defeated)
> >>>> 3. discard if it has the same nonce as something you have previously
> accepted
> >>>>
> >>>> In code:
> >>>>
> >>>> if t < now() - window:
> >>>>   discard as too old
> >>>> else if t > now():
> >>>>   discard as from the future
> >>>> else if nonce in nonces_in_window:
> >>>>   discard as duplicate
> >>>> else:
> >>>>   add nonce to nonces_in_window
> >>>>   accept the measurement
> >>>>
> >>>> (There's an interesting potential attack here in that a client
> provides different nonces or timestamps to each helper with a goal of
> spoiling results. Accepting half a share could be disastrous.  The
> validation process catches those pretty naturally, I think, probably.  Th=
is
> is something we should be careful to check any time that independent
> processing occurs like this.)
> >>>>
> >>>> Separately, I've been looking at less simplistic applications of
> something like anti-replay.  I hope to be able to talk about that in more
> detail soon, but it might be that the anti-replay design you have is too
> restrictive for what we have in mind, no matter the outcome of this
> specific decision.
> >>>>
> >>>> --
> >>>> Ppm mailing list
> >>>> Ppm@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/ppm
> >>> --
> >>> Ppm mailing list
> >>> Ppm@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/ppm
> >> --
> >> Ppm mailing list
> >> Ppm@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ppm
> > --
> > Ppm mailing list
> > Ppm@ietf.org
> > https://www.ietf.org/mailman/listinfo/ppm
>
> --
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm
>

--0000000000004f0e8d05d297b2cc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Martin,</div><div><br></div><div>I think you may b=
e misunderstanding the purpose or scope of the task ID (or perhaps I should=
 say: the draft is not sufficiently clear about how task ID works). You wri=
te:</div><div><br></div><div>&gt;You publicize a task ID at some time.=C2=
=A0 Clients produce reports over some
 period and when you have enough you close the task and generate an=20
aggregate. <br></div><div><br></div><div>...suggesting a 1:1 relationship b=
etween a task ID and an aggregate emitted by a PPM deployment. Rather, a ta=
sk ID describes a long-running report collection and aggregation task, for =
which aggregates are emitted periodically (the period or _aggregation windo=
w_ is one of the parameters associated with a task ID). Further, many clien=
ts may be contributing reports under a single task ID.<br></div><div><br></=
div><div>So for example, imagine a web browser measuring whether users pres=
s a certain button. The browser vendor would configure a PPM task and distr=
ibute its parameters to two aggregators (n.b. the mechanism for task parame=
ter distribution is explicitly out of scope for the PPM protocol). Then, th=
e browser vendor ships a version of the browser to all its users that knows=
 about the task ID (the task ID could be compiled into the browser or maybe=
 the browser vendor has some secure configuration mechanism). Browser insta=
llations then start submitting reports to aggregators using the task ID.</d=
iv><div><br></div><div>&gt;Reports are generated on demand.=C2=A0 Perhaps y=
ou have a polling process=20
that contacts clients at certain times, gives them a task ID and asks=20
for a report.=C2=A0 In this model, reports might be generated all at once,=
=20
which makes times less useful for avoiding collision.</div><div><br></div><=
div>In PPM, clients push reports into aggregators rather than having report=
s pulled (or scraped, as Prometheus would put it) from clients by aggregato=
rs. This is necessary because clients will frequently be behind NAT or egre=
ss only firewalls or unable to keep a port open for metrics pulls for some =
other reason.</div><div><br></div><div>Thanks,</div><div>Tim<br></div></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tu=
e, Dec 7, 2021 at 4:04 PM Martin Thomson &lt;<a href=3D"mailto:mt@lowentrop=
y.net">mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">Thanks for putting this together Chris,<br>
<br>
There is an implicit assumption in this design that says that reports are b=
ound to a task that is known when the report is generated.=C2=A0 To that en=
d, this design is probably not the best design that we might come up with.<=
br>
<br>
If you assume this operating model, there are two sort of natural ways to a=
pproach the report collection process:<br>
<br>
1. You publicize a task ID at some time.=C2=A0 Clients produce reports over=
 some period and when you have enough you close the task and generate an ag=
gregate.=C2=A0 In this model, individual reports could be evenly distribute=
d over the period fairly evenly, so using a timestamp as part of your nonce=
 is a good way to improve collision resistance.<br>
<br>
2. Reports are generated on demand.=C2=A0 Perhaps you have a polling proces=
s that contacts clients at certain times, gives them a task ID and asks for=
 a report.=C2=A0 In this model, reports might be generated all at once, whi=
ch makes times less useful for avoiding collision.<br>
<br>
In both cases, the task ID is what prevents any individual report from bein=
g used for multiple reports.=C2=A0 Replay within the task is assured by the=
 uniqueness of the nonce, not the value of the timestamp.=C2=A0 <br>
<br>
Of course, you could reuse a task ID, but we might reasonably assume that t=
he aggregation service will not accept that.=C2=A0 Or, you could design a s=
ystem in which the task ID is usable for multiple aggregation runs, but tha=
t seems like it defeats the purpose of having a high entropy task ID in the=
 first place.=C2=A0 My thought is that it might be even better to have a le=
ader assign task IDs so that uniqueness can be assured more easily.=C2=A0 I=
f I&#39;m right in that the task ID is central to the anti-replay design, t=
hen that is a more robust design.<br>
<br>
With that in mind, I&#39;m not sure that you even need a timestamp at all.=
=C2=A0 At least for this design.=C2=A0 I think that if we want to consider =
designs where the use of a single report is not so strictly Boolean, then w=
e could need timestamps.<br>
<br>
On Wed, Dec 8, 2021, at 10:18, Christopher Patton wrote:<br>
&gt; Thanks Erik, yeah brought up this consideration early on in the proces=
s <br>
&gt; and is indeed the reason we have this mechanism.<br>
&gt;<br>
&gt; Here&#39;s a PR for implementing Martin&#39;s suggestion: <br>
&gt; <a href=3D"https://github.com/abetterinternet/ppm-specification/pull/1=
69" rel=3D"noreferrer" target=3D"_blank">https://github.com/abetterinternet=
/ppm-specification/pull/169</a><br>
&gt;<br>
&gt; Reviews appreciated!<br>
&gt; Chris P.<br>
&gt;<br>
&gt; On Mon, Dec 6, 2021 at 10:45 AM Erik Taubeneck &lt;<a href=3D"mailto:e=
rik.taubeneck@gmail.com" target=3D"_blank">erik.taubeneck@gmail.com</a>&gt;=
 wrote:<br>
&gt;&gt; Martin said:<br>
&gt;&gt; <br>
&gt;&gt;&gt; Having independent enforcement of anti-replay seems like it is=
 important enough for this state to persist beyond the scope of a task.<br>
&gt;&gt; I strongly agree here, and it seems worthwhile to include in the s=
pec. This will be important for other privacy mechanisms, beyond anti-repla=
y. For example, if I understand correctly, the proposed WICG spec Attributi=
on Reporting API with Aggregate Reports &lt;<a href=3D"https://github.com/W=
ICG/conversion-measurement-api/blob/main/AGGREGATE.md" rel=3D"noreferrer" t=
arget=3D"_blank">https://github.com/WICG/conversion-measurement-api/blob/ma=
in/AGGREGATE.md</a>&gt; aims to follow the PPM spec, and would require pers=
istent state to manage a privacy budget. In addition, that API may even all=
ow replay in a controlled manner within the privacy budget. From their prop=
osal draft &lt;<a href=3D"https://github.com/WICG/conversion-measurement-ap=
i/blob/main/AGGREGATE.md#privacy-budgeting" rel=3D"noreferrer" target=3D"_b=
lank">https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGAT=
E.md#privacy-budgeting</a>&gt;:<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt;&gt; Note: The design for the aggregation service also requires som=
e amount of budgeting to ensure records aren=E2=80=99t processed too many t=
imes.<br>
&gt;&gt; <br>
&gt;&gt; Charlie Harrison can likely provide more context on that specific =
proposal, but I agree overall that we likely want to support more than just=
 anti-replay to enforce the privacy of the PPM results. <br>
&gt;&gt; <br>
&gt;&gt; Cheers,<br>
&gt;&gt; <br>
&gt;&gt; Erik<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; On Sat, Dec 4, 2021 at 3:18 PM Christopher Patton &lt;cpatton=3D<a=
 href=3D"mailto:40cloudflare.com@dmarc.ietf.org" target=3D"_blank">40cloudf=
lare.com@dmarc.ietf.org</a>&gt; wrote:<br>
&gt;&gt;&gt; Hi Martin, thanks for your thoughtful reply. I really like you=
r suggestion. I&#39;d like to hear what others think, and in absence of a r=
eason not to take it I think we should make this a PR :)<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Best,<br>
&gt;&gt;&gt; Chris P.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; On Thu, Dec 2, 2021 at 9:28 PM Martin Thomson &lt;<a href=3D"m=
ailto:mt@lowentropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt; wrote:=
<br>
&gt;&gt;&gt;&gt; Hi Chris,<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; When you say<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; &gt; This removes the Leader&#39;s coordination problem, a=
t the cost <br>
&gt;&gt;&gt;&gt; &gt; of additional storage requirements. In fact, both Agg=
regators need to <br>
&gt;&gt;&gt;&gt; &gt; store the set of processed nonces for the duration of=
 a task.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Having independent enforcement of anti-replay seems like i=
t is important enough for this state to persist beyond the scope of a task.=
<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Maybe stepping back and looking at how anti-replay is mana=
ged would help.=C2=A0 You don&#39;t want the same thing to be counted more =
than once.=C2=A0 The original design requires a total ordering of inputs, w=
ith a strict enforcement of that ordering.=C2=A0 That uses what is in effec=
t a high resolution timestamp to ensuring that ordering is sensible.=C2=A0 =
It also means that tasks cannot be initiated out of order (or with overlapp=
ing inputs).=C2=A0 That seems unworkable to me.=C2=A0 Perfect global orderi=
ng, particularly when you consider helpers that serve multiple customers, i=
s probably infeasible.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; I think that #2 is the only reasonable outcome here.=C2=A0=
 However, you also need to use the timestamp (or part of it) to bound the t=
ime period during which you need to remember nonces.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; That is, you use the time of an input to select from three=
 different discard treatments:<br>
&gt;&gt;&gt;&gt; 1. discard because it is too old<br>
&gt;&gt;&gt;&gt; 2. discard because it is too new (which might be impossibl=
e, but you don&#39;t want something as simple as clock skew to be why your =
anti-replay was defeated)<br>
&gt;&gt;&gt;&gt; 3. discard if it has the same nonce as something you have =
previously accepted<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; In code:<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; if t &lt; now() - window:<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0discard as too old<br>
&gt;&gt;&gt;&gt; else if t &gt; now():<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0discard as from the future<br>
&gt;&gt;&gt;&gt; else if nonce in nonces_in_window:<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0discard as duplicate<br>
&gt;&gt;&gt;&gt; else:<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0add nonce to nonces_in_window<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0accept the measurement<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; (There&#39;s an interesting potential attack here in that =
a client provides different nonces or timestamps to each helper with a goal=
 of spoiling results. Accepting half a share could be disastrous.=C2=A0 The=
 validation process catches those pretty naturally, I think, probably.=C2=
=A0 This is something we should be careful to check any time that independe=
nt processing occurs like this.)<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Separately, I&#39;ve been looking at less simplistic appli=
cations of something like anti-replay.=C2=A0 I hope to be able to talk abou=
t that in more detail soon, but it might be that the anti-replay design you=
 have is too restrictive for what we have in mind, no matter the outcome of=
 this specific decision.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; -- <br>
&gt;&gt;&gt;&gt; Ppm mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf=
.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm=
</a><br>
&gt;&gt;&gt; -- <br>
&gt;&gt;&gt; Ppm mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org=
</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><=
br>
&gt;&gt; -- <br>
&gt;&gt; Ppm mailing list<br>
&gt;&gt; <a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a>=
<br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
&gt; -- <br>
&gt; Ppm mailing list<br>
&gt; <a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
<br>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>

--0000000000004f0e8d05d297b2cc--


From nobody Tue Dec  7 20:30:26 2021
Return-Path: <mt@lowentropy.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 421BB3A0962 for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 20:30:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=sJBiaO37; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KLQY3ERX
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 vn6XiCynp-GH for <ppm@ietfa.amsl.com>; Tue,  7 Dec 2021 20:30:19 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 084DB3A0964 for <ppm@ietf.org>; Tue,  7 Dec 2021 20:30:19 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 07D975C01F0 for <ppm@ietf.org>; Tue,  7 Dec 2021 23:30:17 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Tue, 07 Dec 2021 23:30:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm1; bh=Q79ve Z3WyOX985QlVcIGmlk4qy5KOlypTkpfSJzeM4Y=; b=sJBiaO37j70lHtQeigK/+ XfnvutaoReA0mp2ksR2+S1m2cnhcv2dmParGegKPfKc6PCA1CslPBG5nM6dcPpNf vw3yj26c7DN5EfC1CM9J/TUtJkkOQzSsmQDDw62ibMWJfUgugTcRG1SqlbY7xU6V 9r3E1e12Npl8ofon55H1EEFXUN6ZO3NdnhqtY5Pv/UEEYbaQi61czjXQnZDIaSJ0 DCqhpSE2oxcDYdKx0/5+iYPKWFnsWxwj8JUzply4dcwNWKVc+7OYmziqT4rUrvBO Rge/Hazy5IYSSX3um8ePY13zhFWXTxnW9VIgOBaxBDWxVXAljMgQ37RLB7bbkbHA g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Q79veZ3WyOX985QlVcIGmlk4qy5KOlypTkpfSJzeM 4Y=; b=KLQY3ERXUo5mTFTpCe/N1d/KKx9IClTIEb+/BD+XljNTuMzQuLUPBcWwj +7ZDHVG11TheO1qpgLhLX9ac0FmNGbOVfSHhLK7OvkJ1/ggvDpFsQHmOJvLnfYs/ Q6hZA9o4U2EQhvT60c0R5fszPjJFo7y5n8r5skzkU4diFGVWdYzifsQoGr9LT9Se ThyEMsSnkE+4RmCkpoOwpQyMHhfUDJhp3EAbe5AoE9HWDIUOLYp3t7c9gCMMIlal tS7xkh2tY+E+6cs35Es80XUGQbisxP0K54KCgRvK3fj8B22lwnWrKEtmJqTmZf15 Re8jEBppTO6bdYh6Jb7vwg09JUzrQ==
X-ME-Sender: <xms:2DSwYarrkInFvtlLRDvlOS_4RW9lCIxQHj2zTQv8fIfTr9tbSKDPkg> <xme:2DSwYYovHbtaKVx4Cpu9oqnkS-Rc_0fQehg2_dd439i6DOGTtW8VPPSacy7MktBQ- 8u1GSoUt4socxsO9cQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrjeejgdeglecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpedujeevueejgfehgeehff ekueefjeeuheeutedvteegtddviedugffhheejtdeuieenucffohhmrghinhepghhithhh uhgsrdgtohhmpdgrghhgrhgvghgrthgvrdhmugdpihgvthhfrdhorhhgnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhr ohhphidrnhgvth
X-ME-Proxy: <xmx:2DSwYfORu1qPOCVaIWmDGaX9LzstJ1NrgrBos7XWGBextYckd6xwGQ> <xmx:2DSwYZ7i5LFAcwMVlLkmZqylvZ7Qg5Qa-gS3FbB7n3IlmthV2vEmpQ> <xmx:2DSwYZ41-ovg-51wtmRTYAbCFo674xcNwdS_G7L_mYCG0UnKPsy5iw> <xmx:2TSwYbFh7-9W1le-H5hIkE-f1KDoQq2OOdqQW_0t0fCJgxNktGlm1w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id CA3B43C0D56; Tue,  7 Dec 2021 23:30:16 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4492-g121c2470aa-fm-20211206.001-g121c2470
Mime-Version: 1.0
Message-Id: <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com>
In-Reply-To: <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com>
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com>
Date: Wed, 08 Dec 2021 15:29:57 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: ppm@ietf.org
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/RzCSO8oIcbGAkQBu7VuLuSYhTT8>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 04:30:24 -0000

Thanks Tim,

I had not internalized the naming scheme, so you are right.  It's clear =
(ish), but "task" is entirely the wrong concept to pair this to.  Of cou=
rse, if it were structured in the way I describe, then it would be fine.=
  It's not, so let's talk about how it is structured.

The PR sets a narrow window about the current time over which the report=
s can be accepted.  A little into the past, a different amount into the =
future.  This isn't really helpful as it relates to anti-replay.  All yo=
u need here is a rolling window over which you are willing to track nonc=
es for the purposes of anti-replay.  (Multiple discrete slices of time i=
s probably best as that allows you to have entries fall off the back che=
aply.)  Under that model, it's OK if the report was generated days or ev=
en weeks ago, as long as you are still tracking for that period.  If you=
 want to ensure that your ingress system is able to take in reports and =
just stash them for processing later, then this design forces you to con=
sider that ingress system to be part of what you trust. This check is do=
ne in real time, so it has to be done now.

There's no reason to do real-time checks.  You could build an ingress sy=
stem that just sucks reports in and stores them without thinking too muc=
h.  Then, when you initiate processing you pass them to trusted componen=
ts that do the anti-replay checks and the other validation tasks.  None =
of that requires invoking now().

You also don't really need to worry about time tolerance factors.  At le=
ast not as described in the PR.  You need some allowance for reports to =
arrive into the future, because clock skew is a real thing.  But you can=
 get that by including a little overflow into the future.  The only way =
in which you need the current time is in determining

The design I implemented for TLS looks something like this:

At any given time you have T windows of time, each W seconds wide.  That=
 means you accept reports for a window of about T*W seconds around the c=
urrent time.  Each window has a collection of nonces.  As all reports ha=
ve a unique timestamp you use that to find which collection to use (w =3D=
 floor(t / W)).  New reports are accepted and added to the corresponding=
 collection if they are not present; or they are dropped if the nonce is=
 present.  On a fixed W second interval (i.e., when (now() + skew_adjust=
ment) % W =3D=3D 0) you empty out the oldest window.  Anything older tha=
n now() + skew_adjustment - T*W or newer than now() + skew_adjustment (c=
areful with fenceposts here) is automatically dropped.

Note that this means that while the window is T*W seconds, you are alway=
s accepting timestamps between skew_adjustment and W+skew_adjustment int=
o the future.  The integrity of the system doesn't care about time trave=
l, so that's fine, you just want to avoid rejecting reports just because=
 a client has a dodgy clock. =20

Another aspects of this is that you don't really care if the time is acc=
urate or not.  Clients could give you time that is rounded to W and thin=
gs would work fine under this scheme: you just end up leaning on the ran=
domness a little harder.  (I say this because the fine details of the ti=
me series of events could, in some circumstances, be information that a =
customer of the PPM system might not want to entrust to the system.)

I'm not getting any of that from the pull request.

BTW, regarding the pull vs. push model for submissions, I remind you tha=
t we're not documenting a system, we're standardizing something that is =
hopefully useful for other things.


On Wed, Dec 8, 2021, at 11:37, Tim Geoghegan wrote:
> Hi Martin,
>
> I think you may be misunderstanding the purpose or scope of the task I=
D=20
> (or perhaps I should say: the draft is not sufficiently clear about ho=
w=20
> task ID works). You write:
>
>>You publicize a task ID at some time.  Clients produce reports over so=
me period and when you have enough you close the task and generate an ag=
gregate.=20
>
> ...suggesting a 1:1 relationship between a task ID and an aggregate=20
> emitted by a PPM deployment. Rather, a task ID describes a long-runnin=
g=20
> report collection and aggregation task, for which aggregates are=20
> emitted periodically (the period or _aggregation window_ is one of the=20
> parameters associated with a task ID). Further, many clients may be=20
> contributing reports under a single task ID.
>
> So for example, imagine a web browser measuring whether users press a=20
> certain button. The browser vendor would configure a PPM task and=20
> distribute its parameters to two aggregators (n.b. the mechanism for=20
> task parameter distribution is explicitly out of scope for the PPM=20
> protocol). Then, the browser vendor ships a version of the browser to=20
> all its users that knows about the task ID (the task ID could be=20
> compiled into the browser or maybe the browser vendor has some secure=20
> configuration mechanism). Browser installations then start submitting=20
> reports to aggregators using the task ID.
>
>>Reports are generated on demand.  Perhaps you have a polling process t=
hat contacts clients at certain times, gives them a task ID and asks for=
 a report.  In this model, reports might be generated all at once, which=
 makes times less useful for avoiding collision.
>
> In PPM, clients push reports into aggregators rather than having=20
> reports pulled (or scraped, as Prometheus would put it) from clients b=
y=20
> aggregators. This is necessary because clients will frequently be=20
> behind NAT or egress only firewalls or unable to keep a port open for=20
> metrics pulls for some other reason.
>
> Thanks,
> Tim
>
> On Tue, Dec 7, 2021 at 4:04 PM Martin Thomson <mt@lowentropy.net> wrot=
e:
>> Thanks for putting this together Chris,
>>=20
>> There is an implicit assumption in this design that says that reports=
 are bound to a task that is known when the report is generated.  To tha=
t end, this design is probably not the best design that we might come up=
 with.
>>=20
>> If you assume this operating model, there are two sort of natural way=
s to approach the report collection process:
>>=20
>> 1. You publicize a task ID at some time.  Clients produce reports ove=
r some period and when you have enough you close the task and generate a=
n aggregate.  In this model, individual reports could be evenly distribu=
ted over the period fairly evenly, so using a timestamp as part of your =
nonce is a good way to improve collision resistance.
>>=20
>> 2. Reports are generated on demand.  Perhaps you have a polling proce=
ss that contacts clients at certain times, gives them a task ID and asks=
 for a report.  In this model, reports might be generated all at once, w=
hich makes times less useful for avoiding collision.
>>=20
>> In both cases, the task ID is what prevents any individual report fro=
m being used for multiple reports.  Replay within the task is assured by=
 the uniqueness of the nonce, not the value of the timestamp. =20
>>=20
>> Of course, you could reuse a task ID, but we might reasonably assume =
that the aggregation service will not accept that.  Or, you could design=
 a system in which the task ID is usable for multiple aggregation runs, =
but that seems like it defeats the purpose of having a high entropy task=
 ID in the first place.  My thought is that it might be even better to h=
ave a leader assign task IDs so that uniqueness can be assured more easi=
ly.  If I'm right in that the task ID is central to the anti-replay desi=
gn, then that is a more robust design.
>>=20
>> With that in mind, I'm not sure that you even need a timestamp at all=
.  At least for this design.  I think that if we want to consider design=
s where the use of a single report is not so strictly Boolean, then we c=
ould need timestamps.
>>=20
>> On Wed, Dec 8, 2021, at 10:18, Christopher Patton wrote:
>> > Thanks Erik, yeah brought up this consideration early on in the pro=
cess=20
>> > and is indeed the reason we have this mechanism.
>> >
>> > Here's a PR for implementing Martin's suggestion:=20
>> > https://github.com/abetterinternet/ppm-specification/pull/169
>> >
>> > Reviews appreciated!
>> > Chris P.
>> >
>> > On Mon, Dec 6, 2021 at 10:45 AM Erik Taubeneck <erik.taubeneck@gmai=
l.com> wrote:
>> >> Martin said:
>> >>=20
>> >>> Having independent enforcement of anti-replay seems like it is im=
portant enough for this state to persist beyond the scope of a task.
>> >> I strongly agree here, and it seems worthwhile to include in the s=
pec. This will be important for other privacy mechanisms, beyond anti-re=
play. For example, if I understand correctly, the proposed WICG spec Att=
ribution Reporting API with Aggregate Reports <https://github.com/WICG/c=
onversion-measurement-api/blob/main/AGGREGATE.md> aims to follow the PPM=
 spec, and would require persistent state to manage a privacy budget. In=
 addition, that API may even allow replay in a controlled manner within =
the privacy budget. From their proposal draft <https://github.com/WICG/c=
onversion-measurement-api/blob/main/AGGREGATE.md#privacy-budgeting>:
>> >>=20
>> >>=20
>> >>> Note: The design for the aggregation service also requires some a=
mount of budgeting to ensure records aren=E2=80=99t processed too many t=
imes.
>> >>=20
>> >> Charlie Harrison can likely provide more context on that specific =
proposal, but I agree overall that we likely want to support more than j=
ust anti-replay to enforce the privacy of the PPM results.=20
>> >>=20
>> >> Cheers,
>> >>=20
>> >> Erik
>> >>=20
>> >>=20
>> >>=20
>> >> On Sat, Dec 4, 2021 at 3:18 PM Christopher Patton <cpatton=3D40clo=
udflare.com@dmarc.ietf.org> wrote:
>> >>> Hi Martin, thanks for your thoughtful reply. I really like your s=
uggestion. I'd like to hear what others think, and in absence of a reaso=
n not to take it I think we should make this a PR :)
>> >>>=20
>> >>> Best,
>> >>> Chris P.
>> >>>=20
>> >>> On Thu, Dec 2, 2021 at 9:28 PM Martin Thomson <mt@lowentropy.net>=
 wrote:
>> >>>> Hi Chris,
>> >>>>=20
>> >>>> When you say
>> >>>>=20
>> >>>> > This removes the Leader's coordination problem, at the cost=20
>> >>>> > of additional storage requirements. In fact, both Aggregators =
need to=20
>> >>>> > store the set of processed nonces for the duration of a task.
>> >>>>=20
>> >>>> Having independent enforcement of anti-replay seems like it is i=
mportant enough for this state to persist beyond the scope of a task.
>> >>>>=20
>> >>>> Maybe stepping back and looking at how anti-replay is managed wo=
uld help.  You don't want the same thing to be counted more than once.  =
The original design requires a total ordering of inputs, with a strict e=
nforcement of that ordering.  That uses what is in effect a high resolut=
ion timestamp to ensuring that ordering is sensible.  It also means that=
 tasks cannot be initiated out of order (or with overlapping inputs).  T=
hat seems unworkable to me.  Perfect global ordering, particularly when =
you consider helpers that serve multiple customers, is probably infeasib=
le.
>> >>>>=20
>> >>>> I think that #2 is the only reasonable outcome here.  However, y=
ou also need to use the timestamp (or part of it) to bound the time peri=
od during which you need to remember nonces.
>> >>>>=20
>> >>>> That is, you use the time of an input to select from three diffe=
rent discard treatments:
>> >>>> 1. discard because it is too old
>> >>>> 2. discard because it is too new (which might be impossible, but=
 you don't want something as simple as clock skew to be why your anti-re=
play was defeated)
>> >>>> 3. discard if it has the same nonce as something you have previo=
usly accepted
>> >>>>=20
>> >>>> In code:
>> >>>>=20
>> >>>> if t < now() - window:
>> >>>>   discard as too old
>> >>>> else if t > now():
>> >>>>   discard as from the future
>> >>>> else if nonce in nonces_in_window:
>> >>>>   discard as duplicate
>> >>>> else:
>> >>>>   add nonce to nonces_in_window
>> >>>>   accept the measurement
>> >>>>=20
>> >>>> (There's an interesting potential attack here in that a client p=
rovides different nonces or timestamps to each helper with a goal of spo=
iling results. Accepting half a share could be disastrous.  The validati=
on process catches those pretty naturally, I think, probably.  This is s=
omething we should be careful to check any time that independent process=
ing occurs like this.)
>> >>>>=20
>> >>>> Separately, I've been looking at less simplistic applications of=
 something like anti-replay.  I hope to be able to talk about that in mo=
re detail soon, but it might be that the anti-replay design you have is =
too restrictive for what we have in mind, no matter the outcome of this =
specific decision.
>> >>>>=20
>> >>>> --=20
>> >>>> Ppm mailing list
>> >>>> Ppm@ietf.org
>> >>>> https://www.ietf.org/mailman/listinfo/ppm
>> >>> --=20
>> >>> Ppm mailing list
>> >>> Ppm@ietf.org
>> >>> https://www.ietf.org/mailman/listinfo/ppm
>> >> --=20
>> >> Ppm mailing list
>> >> Ppm@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/ppm
>> > --=20
>> > Ppm mailing list
>> > Ppm@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ppm
>>=20
>> --=20
>> Ppm mailing list
>> Ppm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppm
> --=20
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm


From nobody Wed Dec  8 09:14:27 2021
Return-Path: <cpatton@cloudflare.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4B913A0776 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 09:14:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 Hf2ndO3nj3Rb for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 09:14:20 -0800 (PST)
Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (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 593463A0765 for <ppm@ietf.org>; Wed,  8 Dec 2021 09:14:20 -0800 (PST)
Received: by mail-qv1-xf33.google.com with SMTP id j9so2767293qvm.10 for <ppm@ietf.org>; Wed, 08 Dec 2021 09:14:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ogbCHb1TLF0+UgoYmfswzF8exl1gbhxt8nafu3HUTaU=; b=Bi0Q93DV3n+u41Av/7iFme15W15cxeW0DRQ1i7VTvyxVzea3DfqbDx+c+PxMXl2u/1 wRSbHOQTBFK/svClCaU+hwLpM4t36BRZ2E11waJejUT9erx7C49QFx6ZmhKAF/UHNhLa OnCwHhY9gTDb0IPCCvabv+0IlUATT5SITgVQQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ogbCHb1TLF0+UgoYmfswzF8exl1gbhxt8nafu3HUTaU=; b=bPPYgDazo1PDMYT0UHyJ4/7rWU/tk5NuDa/TrYOUJXXmpSc7vhFquhsH1hxnnd6aJo jWeg4Wa8rXLqTyBH6jiPF2+R2ZPpYuIMIKFGFU1COu5dH4fQV2fSdJvw+ZVASBZlLntP +/HNR7i2cvE7et7/xYzwxT1AzXSWDPMIr4+dXMxhWbzbZ9AX22yGVEbxTeGdV4eMjHb4 ACqNkrzGe936v4Ai8d5CpaP4uiuDMrkwDKHgWixWD46l2aIPmZzVLUNknifViIe2SXLo KGQI1uhgMVu7kX457WUjMS2AlZ06kIxu7TuPUTXzivkFCt8XIGKmMjb5/UZXUno8THxJ /tlg==
X-Gm-Message-State: AOAM533iXSEmPqMF8LJQfQpOh+Sw7NewJfkx1+bLd+3jZ+rkvtvhXQgA hv+LVQC8yjc0NIqfoQdzEi6JK4D17LJGpia61wigepg22MI7pA==
X-Google-Smtp-Source: ABdhPJzgrYUZ4F4B+jcGFyECG3PBn0bQrEQbpIUazc/3aoRqCPgHZAnWZ8FQoXOs8LOCcwm1nM28XOPcLe1OMQu1Fi4=
X-Received: by 2002:a05:6214:f2e:: with SMTP id iw14mr9069254qvb.21.1638983658313;  Wed, 08 Dec 2021 09:14:18 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com>
In-Reply-To: <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Wed, 8 Dec 2021 09:14:07 -0800
Message-ID: <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: ppm@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bf3bef05d2a59edf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/muXQ0sbeyykDbdu4m6xUYzszlQE>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 17:14:25 -0000

--000000000000bf3bef05d2a59edf
Content-Type: text/plain; charset="UTF-8"

Hi Martin,

I had basically the same vision for storing reports, so I think it's just a
matter of making the PR more clear and maybe remove the requirement to
enforce the time boundaries. Detailed comments in-line.


> The PR sets a narrow window about the current time over which the reports
> can be accepted.  A little into the past, a different amount into the
> future.


max_report_backward_offset is intended to define the duration for which an
aggregator MUST remember a nonce for the purpose of anti-replay. Reports
with timestamps too far in the past are ignored so that we don't have to
check for replay.

max_report_forward_offset has a different purpose, as it is intended to
prevent the aggregators from having to hang on to reports for a long time.
The PR conflates this with anti-replay.


> This isn't really helpful as it relates to anti-replay.  All you need here
> is a rolling window over which you are willing to track nonces for the
> purposes of anti-replay.  (Multiple discrete slices of time is probably
> best as that allows you to have entries fall off the back cheaply.)  Under
> that model, it's OK if the report was generated days or even weeks ago, as
> long as you are still tracking for that period.  If you want to ensure that
> your ingress system is able to take in reports and just stash them for
> processing later, then this design forces you to consider that ingress
> system to be part of what you trust. This check is done in real time, so it
> has to be done now.
>
> There's no reason to do real-time checks.  You could build an ingress
> system that just sucks reports in and stores them without thinking too
> much.  Then, when you initiate processing you pass them to trusted
> components that do the anti-replay checks and the other validation tasks.
> None of that requires invoking now().


I agree that we want to be able to decouple the ingress system. The
fundamental purpose of the time boundaries is to reduce storage
requirements. The current spec says that the leader SHOULD ignore reports
from too far in the future. We could keep that, and perhaps say that
aggregators MAY ignore reports from too far in the past. The trouble is
that the leader and helper may disagree on how long they're willing to keep
the nonce set around. For instance, if the leader keeps reports around for
7 days and wants to bulk-aggregate the reports all at once, but the helper
ignores reports that are more than a day old, then most of the reports will
get ignored.


At any given time you have T windows of time, each W seconds wide.  That
> means you accept reports for a window of about T*W seconds around the
> current time.  Each window has a collection of nonces.  As all reports have
> a unique timestamp you use that to find which collection to use (w =
> floor(t / W)).  New reports are accepted and added to the corresponding
> collection if they are not present; or they are dropped if the nonce is
> present.  On a fixed W second interval (i.e., when (now() +
> skew_adjustment) % W == 0) you empty out the oldest window.  Anything older
> than now() + skew_adjustment - T*W or newer than now() + skew_adjustment
> (careful with fenceposts here) is automatically dropped.
>
> Note that this means that while the window is T*W seconds, you are always
> accepting timestamps between skew_adjustment and W+skew_adjustment into the
> future.  The integrity of the system doesn't care about time travel, so
> that's fine, you just want to avoid rejecting reports just because a client
> has a dodgy clock.
>

This is basically what I had in mind for report storage at the leader. But
what about storing the nonce set of processed reports at the helper? The
aggregators should be able to prune the oldest windows in a similar way,
but what happens when the leader sends a report to the helper with a
timestamp is in a previously pruned window? The helper will have to to
ignore it since it can't determine if the report was replayed. The problem
that arises is that the aggregators may not agree on how far in the past is
acceptable.

We solve this in the current PR by having both aggregators enforce
max_report_backward_offset. Perhaps there's another way to solve this
problem? (Or maybe there isn't an actual problem here!)

Chris P.

--000000000000bf3bef05d2a59edf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Martin,</div><div><br></div><div>I had basically t=
he same vision for storing reports, so I think it&#39;s just a matter of ma=
king the PR more clear and maybe remove the requirement to enforce the time=
 boundaries. Detailed comments in-line.<br></div><div><div><div class=3D"gm=
ail_quote"><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
The PR sets a narrow window about the current time over which the reports c=
an be accepted.=C2=A0 A little into the past, a different amount into the f=
uture.</blockquote><div></div><div><br></div><div><span><span>max_report_ba=
ckward_offset is intended to define the duration for which an aggregator MU=
ST remember a nonce for the purpose of anti-replay. Reports with timestamps=
 too far in the past are ignored so that we don&#39;t have to check for rep=
lay.</span></span></div><div><span><span><br></span></span></div><div><span=
><span> max_report_forward_offset has a different purpose, as it is intende=
d to prevent the aggregators from having to hang on to reports for a long t=
ime. The PR conflates this with anti-replay.</span></span></div><div>=C2=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"> This isn&#39;t rea=
lly helpful as it relates to anti-replay.=C2=A0 All you need here is a roll=
ing window over which you are willing to track nonces for the purposes of a=
nti-replay.=C2=A0 (Multiple discrete slices of time is probably best as tha=
t allows you to have entries fall off the back cheaply.)=C2=A0 Under that m=
odel, it&#39;s OK if the report was generated days or even weeks ago, as lo=
ng as you are still tracking for that period.=C2=A0 If you want to ensure t=
hat your ingress system is able to take in reports and just stash them for =
processing later, then this design forces you to consider that ingress syst=
em to be part of what you trust. This check is done in real time, so it has=
 to be done now.<br>
<br>
There&#39;s no reason to do real-time checks.=C2=A0 You could build an ingr=
ess system that just sucks reports in and stores them without thinking too =
much.=C2=A0 Then, when you initiate processing you pass them to trusted com=
ponents that do the anti-replay checks and the other validation tasks.=C2=
=A0 None of that requires invoking now().</blockquote><div><br></div><div>I=
 agree that we want to be able to decouple the ingress system. The fundamen=
tal purpose of the time boundaries is to reduce storage requirements. The c=
urrent spec says that the leader SHOULD ignore reports from too far in the =
future. We could keep that, and perhaps say that aggregators MAY ignore rep=
orts from too far in the past. The trouble is that the leader and helper ma=
y disagree on how long they&#39;re willing to keep the nonce set around. Fo=
r instance, if the leader keeps reports around for 7 days and wants to bulk=
-aggregate the reports all at once, but the helper ignores reports that are=
 more than a day old, then most of the reports will get ignored.<br></div><=
div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
At any given time you have T windows of time, each W seconds wide.=C2=A0 Th=
at means you accept reports for a window of about T*W seconds around the cu=
rrent time.=C2=A0 Each window has a collection of nonces.=C2=A0 As all repo=
rts have a unique timestamp you use that to find which collection to use (w=
 =3D floor(t / W)).=C2=A0 New reports are accepted and added to the corresp=
onding collection if they are not present; or they are dropped if the nonce=
 is present.=C2=A0 On a fixed W second interval (i.e., when (now() + skew_a=
djustment) % W =3D=3D 0) you empty out the oldest window.=C2=A0 Anything ol=
der than now() + skew_adjustment - T*W or newer than now() + skew_adjustmen=
t (careful with fenceposts here) is automatically dropped.<br>
<br>
Note that this means that while the window is T*W seconds, you are always a=
ccepting timestamps between skew_adjustment and W+skew_adjustment into the =
future.=C2=A0 The integrity of the system doesn&#39;t care about time trave=
l, so that&#39;s fine, you just want to avoid rejecting reports just becaus=
e a client has a dodgy clock.<br></blockquote><div><br></div><div>This is b=
asically what I had in mind for report storage at the leader. But what abou=
t storing the nonce set of processed reports at the helper? The aggregators=
 should be able to prune the oldest windows in a similar way, but what happ=
ens when the leader sends a report to the helper with a=C2=A0 timestamp is =
in a previously pruned window? The helper will have to to ignore it since i=
t can&#39;t determine if the report was replayed. The problem that arises i=
s that the aggregators may not agree on how far in the past is acceptable.<=
br></div><div><br></div><div>We solve this in the current PR by having both=
 aggregators enforce=20
max_report_backward_offset. Perhaps there&#39;s another way to solve this=
=20
problem? (Or maybe there isn&#39;t an actual problem here!)</div><div><br><=
/div><div>Chris P.<br></div></div></div></div></div>

--000000000000bf3bef05d2a59edf--


From nobody Wed Dec  8 10:38:12 2021
Return-Path: <mt@lowentropy.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2927D3A08D5 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 10:38:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=rOzXR581; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=hloJaZBG
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 bpy7ZVuz4qT3 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 10:38:05 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BDCE3A08D2 for <ppm@ietf.org>; Wed,  8 Dec 2021 10:38:05 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 49B005C0235; Wed,  8 Dec 2021 13:38:04 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Wed, 08 Dec 2021 13:38:04 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm1; bh=exTnCcJlbz7FmW5fkljXEBJwTjMU t8FF6K8HP0WCKLU=; b=rOzXR581gHXWm9/kQsfEcun8eM4iTyfWZ4fUqk3Q0sA3 Q/UPxS6DQjruD8TTNM+Hgnn8zJUTqnFPfZzzOdc5P7R/IXyG59A0vuhKMow/AhRS xfIjukkt000+aKuisrA8zzrbh0Hr77L41m6EDQV4wTlQ2uaxdSGwBceG9IdoxTpA tF0zM3Wljw7+I2ZNXZa4bpymxUl1bvLc0w3k05YpZBYE5drMxUha4i1NiCoNeMCH 8EjgPyqoWv2NAdBZvcTCNaEwwZs1e863EC592IIg1muXAL8Syih8Psh2pBO5Abk+ daAjEkZnAkGDsdfAhvfqbZN96RsBfvmoN5VWsHBk4A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=exTnCc Jlbz7FmW5fkljXEBJwTjMUt8FF6K8HP0WCKLU=; b=hloJaZBG10rcxWKKOUMSpd C81dqrEdPhHdazrkjYLIGGTSB/FRLlTJ6P7o/hiHXB7EnwvGM/dUug2zs9GsNL2J VVFOPC6wksQiVvnEJt5R1s9Tx6gHlzFe221X65+VaWQ/dMJF000CTzgKG6FxNUd+ nMhCqn/wpsyEWnCqmxRmyPJOGeMihEJDLSNlpGQjBYcRPHZO+j52DWt0mgrICwmF DYdGc1953cIhBEgywIUYfFZVY8mY3BpyQIie44qZSm87YdbHE7gJyiwgs/X5OEkJ 2L8PFHSAChSz9qRR1Tlm/Zj76KeBSayj42rfJpvp1FnYHSD3llPg4gSKWZ80Stbg ==
X-ME-Sender: <xms:jPuwYcLjwrrqovmgm3l-u8_bzU9eelrDOKYImouNHQRwR_wdcOiFOg> <xme:jPuwYcJhaRjtgMr75o0mEpnLMGU4Bvfho6zAHvoRtG03v_igyxBYfR3zgk_HInbhe wEhb1hNxaHnx5mv-w4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrjeekgdduudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecugg ftrfgrthhtvghrnhepkeetueeikedtkeelfeekvefhkeffvedvvefgkefgleeugfdvjeej geffieegtdejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:jPuwYctD62Q_czwpmJmdDC85g7zjVfhuO0EGsO0wSnT0LoSGRDsK5A> <xmx:jPuwYZarGyVwDznRThWEdVDaxQJqX7u3wGdcVP0zdx7PxOkw3mCGkg> <xmx:jPuwYTaXfCcUk9ORWb5JyxRgxjqSfEsEFZlELrtFuGqPxlkLbUpYLQ> <xmx:jPuwYd1KG6gK62hFL8wtA1AQiERrW0y_en6gk9GXg1PP03QGvYrP1Q>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 115003C031B; Wed,  8 Dec 2021 13:38:04 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4492-g121c2470aa-fm-20211206.001-g121c2470
Mime-Version: 1.0
Message-Id: <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com>
In-Reply-To: <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com>
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com> <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com>
Date: Thu, 09 Dec 2021 05:37:40 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: "Christopher Patton" <cpatton@cloudflare.com>
Cc: ppm@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/N_quBveMofXwfLCrdvRhRfsLqIU>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 18:38:10 -0000

On Thu, Dec 9, 2021, at 04:14, Christopher Patton wrote:
> But what about storing the nonce set of processed reports at the 
> helper? The aggregators should be able to prune the oldest windows in a 
> similar way, but what happens when the leader sends a report to the 
> helper with a  timestamp is in a previously pruned window? 

Two options:

1. The leader and helpers agree about the nonce retention window.
2. Any server can reject a report and all others have to accept that choice.


From nobody Wed Dec  8 14:21:26 2021
Return-Path: <erik.taubeneck@gmail.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83F4F3A05A4 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 14:21:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 UGlSGNpR1Df1 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 14:21:19 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 3DE013A0770 for <ppm@ietf.org>; Wed,  8 Dec 2021 14:21:19 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id g14so13008009edb.8 for <ppm@ietf.org>; Wed, 08 Dec 2021 14:21:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=db1ImNj4W+Iw8byuoMAPCK3/QoKL37eCGD6Gu4Ngowo=; b=fZPiWcI46IxJ6zyM2ypEuMtUveOGgbmAdbK504FqZ6NcjdHNA76Qf9LXRwWOyZwFJ7 B+HtCI8yUJC/n/NaahtrvXjKUKuZaX0BbRmAmHdGDL/lUmF8meYBku7+dkYIhDwiT8Iy pRKmbME4DrvNtM94OOalA8S6nypbdBZ25iY5sc+SZssIJJaUc2LgjKmIR9G/4D7GWAP1 jMxsyHFbOcKcvyrkRXg/TX0gRUPYUocbZZjPCT+DUYzy4TReNDsuS1wzToOm1FTHI9jn 6ziNr0NMn8iy9FHxGN83gdl5FUPMIMyYmOOPTkUVDM5LIBfjZZmM4S1lYrBaGPCV+3S0 MIIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=db1ImNj4W+Iw8byuoMAPCK3/QoKL37eCGD6Gu4Ngowo=; b=kUIiZslAupjJLPR5rzU25Jm+1AkxEBishPj7PG9wnul3SjMrfAB+FMWZ7Owywrj52P oXdrW4bUyMHTP9PMKEn36MJnBRyKF2/t2lF+cHVWBfuxMwkkj9bRTLavviK6b8aqnbGN v68cpQbPyy+kzmZ3ZQE0jszuUF42I9aEN299VvSgoQxe0x227PmWUfRN8vCRFHB6+6Gl agYSBgQxh/i6Y/AeR1Fvh9XY0JCtvB6D8os6PJN1Bv7d+Ytxw9sNaRylELbNm43GhdQe +GsIjubxp/9ynzwh9wszQuyDxfmkwe+WiQeQOwhGInFbIPMWTuKnH/8tzWnbu2A7E/3r s2QQ==
X-Gm-Message-State: AOAM530w7TAmI0qgcub1Cuu652LR+vjJsJh81yxkPJiwXE3PnDohYR/a +80hjkvDW1yF3Yu7gHcSEs6I0guhY/+h9yOeUAY=
X-Google-Smtp-Source: ABdhPJzPNpw7LQl7ln2UEPpB05w2ZqKA0d1yJqjmAK6z2FQJ7BpYMM+WBXLYeLldAeKiUQyUxMb4Qsym2TpT00nuX4A=
X-Received: by 2002:a05:6402:270a:: with SMTP id y10mr23536974edd.108.1639002076079;  Wed, 08 Dec 2021 14:21:16 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com> <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com> <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com>
In-Reply-To: <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com>
From: Erik Taubeneck <erik.taubeneck@gmail.com>
Date: Wed, 8 Dec 2021 14:21:05 -0800
Message-ID: <CANzuiCifdR_zdMjnzSoze-Odj=rBzHiuGNAERSp6M+uCrPjVZA@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: Christopher Patton <cpatton@cloudflare.com>, ppm@ietf.org
Content-Type: multipart/alternative; boundary="00000000000087e86205d2a9e8e2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/Yuboy6-iI3C2A4S8bR3evZGQGpA>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 22:21:24 -0000

--00000000000087e86205d2a9e8e2
Content-Type: text/plain; charset="UTF-8"

Given the two options, it seems like we actually need both.


> 1. The leader and helpers agree about the nonce retention window.

The retention window should be a globally accepted fact, for a specific
"task ID".  (Agreed with Martin that it might be useful to bikeshed the use
of "task" here.) The leader, helpers, clients, and collector should all be
aware of the window.


> 2. Any server can reject a report and all others have to accept that
> choice.

If the window is a known value, then ideally all servers would reject the
same reports. The same should be true about checking the nonces. Rejecting
the report if any server rejects it is the most conservative case (secure
up to n-1 dishonest parties). Does the standard aim to be secure up to that
threshold, or could we consider other consensus protocols here?


On Wed, Dec 8, 2021 at 10:38 AM Martin Thomson <mt@lowentropy.net> wrote:

> On Thu, Dec 9, 2021, at 04:14, Christopher Patton wrote:
> > But what about storing the nonce set of processed reports at the
> > helper? The aggregators should be able to prune the oldest windows in a
> > similar way, but what happens when the leader sends a report to the
> > helper with a  timestamp is in a previously pruned window?
>
> Two options:
>
> 1. The leader and helpers agree about the nonce retention window.
> 2. Any server can reject a report and all others have to accept that
> choice.
>
> --
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm
>

--00000000000087e86205d2a9e8e2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Given the two options, it seems like we actually need=
 both.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">1. The leader and helpers agree about the nonce retention window.=C2=A0=
</blockquote><div>The retention window should be a globally accepted fact, =
for a specific &quot;task ID&quot;.=C2=A0 (Agreed with Martin that it might=
 be useful to bikeshed the use of &quot;task&quot; here.) The leader, helpe=
rs, clients, and collector should all be aware of the window.</div><div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">2. Any serv=
er can reject a report and all others have to accept that choice.</blockquo=
te><div>If the window is a known value, then ideally all servers would reje=
ct the same reports. The same should be true about checking the nonces. Rej=
ecting the report if any server rejects it is the most conservative case (s=
ecure up to n-1 dishonest parties). Does the standard aim to be secure up t=
o that threshold, or could we consider other consensus protocols here?</div=
><div>=C2=A0</div></div></div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Wed, Dec 8, 2021 at 10:38 AM Martin Thomson &lt;=
<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Dec 9, 2021, =
at 04:14, Christopher Patton wrote:<br>
&gt; But what about storing the nonce set of processed reports at the <br>
&gt; helper? The aggregators should be able to prune the oldest windows in =
a <br>
&gt; similar way, but what happens when the leader sends a report to the <b=
r>
&gt; helper with a=C2=A0 timestamp is in a previously pruned window? <br>
<br>
Two options:<br>
<br>
1. The leader and helpers agree about the nonce retention window.<br>
2. Any server can reject a report and all others have to accept that choice=
.<br>
<br>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>

--00000000000087e86205d2a9e8e2--


From nobody Wed Dec  8 15:09:00 2021
Return-Path: <mt@lowentropy.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78D293A0807 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 15:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=M7/BVISa; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WkWfM3oO
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 GLwhItYnYzMi for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 15:08:54 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B60C3A0805 for <ppm@ietf.org>; Wed,  8 Dec 2021 15:08:54 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 432105C02C4 for <ppm@ietf.org>; Wed,  8 Dec 2021 18:08:53 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Wed, 08 Dec 2021 18:08:53 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=1m1bRLJVzeLgyqpb6D8B2APLG+0PK8s F9civVzw6Hws=; b=M7/BVISa7oi1WwKWHlEmUX/9FXQF5DnGosWSFssFOqvzgcK 57vrToIF1ifCT5RuTMsATRdtqSfTOD7gPjTp7IgWkOEeqwIvNLHskp+9DL/VL+G6 rSOnJh46D8xe4qhxsI9iWGrPm1tBCpwWYlRQiZKxG5RAiHYvKWEyvnfpUnWtTigX n7mMiBq09LXSJB21JlEDSoFlar6giLSuAbnAgZq+1KX/qfm/ubDQfemevbYiKAcn VKPmJ3ICpdZbtS+RQERRZlBzAT2HabVbgdUVY9tvHv6giizYXsN4H2dSkDxyAtGg Cfa201ENTDgmL9WoZbJXXC7+isCiksuZhXGmONw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=1m1bRL JVzeLgyqpb6D8B2APLG+0PK8sF9civVzw6Hws=; b=WkWfM3oOLtoCJWjwmUdyp5 VMrJHRgiGxiepGGOVr6OBBNEap1VO/6Ne7D+H7zgE+0IbX7QI2gewa54nsb+Jd2p /G5SiLXd25wD+HkyybuoTOND3zXOa/YiyfUgOxKY8dO6D12Z02JSgtCNYetqbM3h czTl+jmcnjahZHLDpTxNDBam/K+sIz1DgZu1Pbfe1ly2F/EgFuyP3v7JvLIH9Xqr iX9itLSATblMY7XhzfYwQ2KLcdJDdpiKD8RcrasZnGt0yFCIMJeoGG1JjOatR8R5 GCO2alpnQAbcfaZdBqyvtkyDKib55pA6gABtWVASBE/Y+a8UHn7U9NSYKrcHKnoQ ==
X-ME-Sender: <xms:BTuxYQBBQbBJv2NPlmLUtLzPSbZBWAZS72lrP8qMoJwkUrcgZJNaaA> <xme:BTuxYSjJJOBoQD5FjtUmv3IxfLeLXKbvaBFjbFoO9SfWQNq1HhGHp1DubovBgmcFW uibee2sa0npYUArb3o>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrjeelgddtjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhephfeitddtveeihfejjefgve efuedugffgkeevkeehueeggeelveekveektdfhueeinecuffhomhgrihhnpehivghtfhdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hmtheslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:BTuxYTnuo5SUrTbw6f6NEwRaQbB45KLY7pR2butU-h1mSfuauT8tfQ> <xmx:BTuxYWwQQ-Gfcahy_nKZDJJ6-zEjtw83Ua0AJLSNejtqCvQAho4vVQ> <xmx:BTuxYVTKIjJwKhc9EZkvhbsgfYsaKGL1P-tsd3FTBnKbxAMzsFtw_w> <xmx:BTuxYcfLGDGIOEcA6mGx3qAZHjYi6XFmFxenyRIgkXVRYMSaUA22Ew>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 111613C031B; Wed,  8 Dec 2021 18:08:53 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4492-g121c2470aa-fm-20211206.001-g121c2470
Mime-Version: 1.0
Message-Id: <4a59ee08-8733-49b4-a9a9-3c7b5b0560ce@www.fastmail.com>
In-Reply-To: <CANzuiCifdR_zdMjnzSoze-Odj=rBzHiuGNAERSp6M+uCrPjVZA@mail.gmail.com>
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com> <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com> <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com> <CANzuiCifdR_zdMjnzSoze-Odj=rBzHiuGNAERSp6M+uCrPjVZA@mail.gmail.com>
Date: Thu, 09 Dec 2021 10:08:34 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: ppm@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/Vjj24RTCMvdbZaCXsMwWnan_wpo>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 23:08:59 -0000

This seems sensible to me.  I think that the problem I had with the PR is that the definition of the window was anchored on the current time.  This is because it was anchored on the notion of a "task", which is long-running.  However, I think that we want a different concept, that of a "query" perhaps (which is a task in my mind), that governs the batch of things that are being aggregated.  At that point, the time range can be made absolute and agreed.

Then they can all agree to be tracking nonces between t_start and t_end, with values outside that range being uniformly rejected.  You can expect them to all consistently reject or accept everything.  The value of now() doesn't need to come into it.

On Thu, Dec 9, 2021, at 09:21, Erik Taubeneck wrote:
> Given the two options, it seems like we actually need both.
> 
>> 1. The leader and helpers agree about the nonce retention window. 
> The retention window should be a globally accepted fact, for a specific 
> "task ID".  (Agreed with Martin that it might be useful to bikeshed the 
> use of "task" here.) The leader, helpers, clients, and collector should 
> all be aware of the window.
> 
>> 2. Any server can reject a report and all others have to accept that choice.
> If the window is a known value, then ideally all servers would reject 
> the same reports. The same should be true about checking the nonces. 
> Rejecting the report if any server rejects it is the most conservative 
> case (secure up to n-1 dishonest parties). Does the standard aim to be 
> secure up to that threshold, or could we consider other consensus 
> protocols here?
> 
>
> On Wed, Dec 8, 2021 at 10:38 AM Martin Thomson <mt@lowentropy.net> wrote:
>> On Thu, Dec 9, 2021, at 04:14, Christopher Patton wrote:
>> > But what about storing the nonce set of processed reports at the 
>> > helper? The aggregators should be able to prune the oldest windows in a 
>> > similar way, but what happens when the leader sends a report to the 
>> > helper with a  timestamp is in a previously pruned window? 
>> 
>> Two options:
>> 
>> 1. The leader and helpers agree about the nonce retention window.
>> 2. Any server can reject a report and all others have to accept that choice.
>> 
>> -- 
>> Ppm mailing list
>> Ppm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppm
> -- 
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm


From nobody Wed Dec  8 15:32:52 2021
Return-Path: <caw@heapingbits.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB453A0864 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 15:32:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=heapingbits.net header.b=e/LVZaKA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Ck6RnK9W
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 L0j8EPB27Cgz for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 15:32:46 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29B653A086A for <ppm@ietf.org>; Wed,  8 Dec 2021 15:32:46 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 14F865C0132 for <ppm@ietf.org>; Wed,  8 Dec 2021 18:32:45 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute1.internal (MEProxy); Wed, 08 Dec 2021 18:32:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=GYf/LXrlEN6NQ2ta54Sv/K3BkCY8M+i WpMcWWg3nEfI=; b=e/LVZaKAU7R9/qG7nw+DK1e07Vcd8dSMqorq8j54omn1PJN Ixrar+NPmRCpo3r+Y4ltjjZn9JRHVUeiTWBKUsCHLstK8YIpjErve/NEFbhejdgD wVubOv/wgiD7J9TRUZIMpCHw0HLM2q8jshhNhw1vdkdR9OXO7X6xAvCS0p/A/wWM j4LeYnCMnOOMim2tx3dbjb4H3+tWGX+97D2wBlItKQ4GRYU95ythB/NA8pfpLrfC hvjIBPsY1nS7d4agAVG/WuWzFZvjk8hOAPjnDdh7upQCld20HPwRDCGpToHrX5bT 6gJVgpjQd7xMi9sT7iq5KMKzTJDmc1vrYZJM2dw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=GYf/LX rlEN6NQ2ta54Sv/K3BkCY8M+iWpMcWWg3nEfI=; b=Ck6RnK9WQxvHp3a8GTLZ2s sGGP/BV8AXiiE9JYuFauEERvXxGpO/ve4ENut1lRrHrvy+71KYHnW+XkngbXFuaP nU/ahn/RiTO9peV7xl5n2p4viX8j4/Jdg/IifrbzjQb+/oPI3gAFFckf/Zb0MjWN 1TnVU9U4kSVv1RPYhuF5GsTOjU+WuJ4sO8LlvYEAYSsMadJO+iOWVc+UtKJ/xgfd GWqqGFa9QmyKz47byJa4GMuEjMSo4zDN+xJpnbeP3tJqzo2mj1Ljj0pFCWqDr3rl DUfKZbV9RZ0r21uRjduVrWKY6tlGV0qmXzuZeDTBRjJK5/OKUMgmdMeIzT+UM2VA ==
X-ME-Sender: <xms:nECxYct_9Enma7w2P5I7Ytu6Mvyh_gLVK7XDURaXyQxuh8IKwkV7xw> <xme:nECxYZfnBEkm022MzSibN3vQcoKld-y7fc15Z9rGK5-CbBE8huZQ1XbLLcWsVsfPz q1px5gcISLsaSXwlGQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrjeelgdduudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdevhhhrihhsthhophhhvghrucghohhougdfuceotggrfies hhgvrghpihhnghgsihhtshdrnhgvtheqnecuggftrfgrthhtvghrnhepgfevgeegffdvue egveevgfevffeludelffegjedufffhfeekgeeuudegtdevffdtnecuffhomhgrihhnpehi vghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpegtrgifsehhvggrphhinhhgsghithhsrdhnvght
X-ME-Proxy: <xmx:nECxYXydvOf7QRcSfvQwdd7PNqPrsFQBNE4Uvmana5szArUKNtBU3w> <xmx:nECxYfPh_xus5h2lQzaIZuHLebETucnSnCcHj-9Sn_HDvqdV3_QjWw> <xmx:nECxYc9KOxPI58B1_BM9ICVEe5iwjHsmT3ZPVzlaAZL9z4MIW_Cxng> <xmx:nUCxYfL4in3zvIB57VHcf3jHFYbKiHbBSRcAIOywWVbmqUVAKPwmVQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id CDBE23C031B; Wed,  8 Dec 2021 18:32:44 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4492-g121c2470aa-fm-20211206.001-g121c2470
Mime-Version: 1.0
Message-Id: <a4c3712e-c149-4fcb-a3e2-cae0c7bd14cc@www.fastmail.com>
In-Reply-To: <4a59ee08-8733-49b4-a9a9-3c7b5b0560ce@www.fastmail.com>
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com> <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com> <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com> <CANzuiCifdR_zdMjnzSoze-Odj=rBzHiuGNAERSp6M+uCrPjVZA@mail.gmail.com> <4a59ee08-8733-49b4-a9a9-3c7b5b0560ce@www.fastmail.com>
Date: Wed, 08 Dec 2021 15:32:24 -0800
From: "Christopher Wood" <caw@heapingbits.net>
To: ppm@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/xvXroqaFq5sSqWcIE1ZLt6VG8Eo>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 23:32:51 -0000

On Wed, Dec 8, 2021, at 3:08 PM, Martin Thomson wrote:
> This seems sensible to me.  I think that the problem I had with the PR 
> is that the definition of the window was anchored on the current time.  
> This is because it was anchored on the notion of a "task", which is 
> long-running.  However, I think that we want a different concept, that 
> of a "query" perhaps (which is a task in my mind), that governs the 
> batch of things that are being aggregated.  At that point, the time 
> range can be made absolute and agreed.
>
> Then they can all agree to be tracking nonces between t_start and 
> t_end, with values outside that range being uniformly rejected.  You 
> can expect them to all consistently reject or accept everything.  The 
> value of now() doesn't need to come into it.

This does seem like a reasonable simplification for the aggregation protocol. It moves the boundary question out of the main flow and closer to configuration. I suppose a task (or query) would have well-defined windows marking t_start and t_end, clients would include a timestamp in the report flow, and aggregators would check that against the known window bounds. Is that the idea?

Best,
Chris

>
> On Thu, Dec 9, 2021, at 09:21, Erik Taubeneck wrote:
>> Given the two options, it seems like we actually need both.
>> 
>>> 1. The leader and helpers agree about the nonce retention window. 
>> The retention window should be a globally accepted fact, for a specific 
>> "task ID".  (Agreed with Martin that it might be useful to bikeshed the 
>> use of "task" here.) The leader, helpers, clients, and collector should 
>> all be aware of the window.
>> 
>>> 2. Any server can reject a report and all others have to accept that choice.
>> If the window is a known value, then ideally all servers would reject 
>> the same reports. The same should be true about checking the nonces. 
>> Rejecting the report if any server rejects it is the most conservative 
>> case (secure up to n-1 dishonest parties). Does the standard aim to be 
>> secure up to that threshold, or could we consider other consensus 
>> protocols here?
>> 
>>
>> On Wed, Dec 8, 2021 at 10:38 AM Martin Thomson <mt@lowentropy.net> wrote:
>>> On Thu, Dec 9, 2021, at 04:14, Christopher Patton wrote:
>>> > But what about storing the nonce set of processed reports at the 
>>> > helper? The aggregators should be able to prune the oldest windows in a 
>>> > similar way, but what happens when the leader sends a report to the 
>>> > helper with a  timestamp is in a previously pruned window? 
>>> 
>>> Two options:
>>> 
>>> 1. The leader and helpers agree about the nonce retention window.
>>> 2. Any server can reject a report and all others have to accept that choice.
>>> 
>>> -- 
>>> Ppm mailing list
>>> Ppm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ppm
>> -- 
>> Ppm mailing list
>> Ppm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppm
>
> -- 
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm


From nobody Wed Dec  8 20:04:54 2021
Return-Path: <mt@lowentropy.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2593A0DD6 for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 20:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=ADNvjKgK; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=R26cR0v1
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 6lP5yzCIl4QI for <ppm@ietfa.amsl.com>; Wed,  8 Dec 2021 20:04:47 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 298123A0DD5 for <ppm@ietf.org>; Wed,  8 Dec 2021 20:04:46 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 461495C0325 for <ppm@ietf.org>; Wed,  8 Dec 2021 23:04:45 -0500 (EST)
Received: from imap41 ([10.202.2.91]) by compute3.internal (MEProxy); Wed, 08 Dec 2021 23:04:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=1+WGrpqZe3fcrVI+EbAw9NrRbs9MUSn vV5JJhDA/MDw=; b=ADNvjKgKJgdEiHuqAhHDwhunhmckgWkpuIwt4obJqwWiTxF L9eC/1L6WnpkKb/M3rHEHNIbYQCRB9ZNKhwRgynl828uyM8H0NDo6o7RXtK9x06Y 1e1X9q/Aml276UEgwM9dX9oBN+LYS9hWMvHrqERGW5lCk+6iPsV6sA1TwdbdEywB Pfc+EWpEDE5XMvOS5gJMTOjYYcTFLq1lSdwgiWQNmrrmK9gJXTutIGZviQK/SpXl odB9I4GSE4E8ckkCRqIdH3cLV8ZBo7hvBFLLbVKg3c6YOhmid84DDCtorG2WB+BF t4a7g79PtfH0Jp3JUh/QUiKDOZkiBq5d+InfHoQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=1+WGrp qZe3fcrVI+EbAw9NrRbs9MUSnvV5JJhDA/MDw=; b=R26cR0v1Bj3Sa+AAG/plKO 39/BHF1QRX1mFGwbt1D2Ggms8GAqUF39ZHPs1WhWzRW3rzRbxg1qpLODk81e2mUS mIC2PpzA20v0OvK55UZy7Bs2+m91+gF8kODDYCMsVRsPI1ltOTafEc2fTwNy7WN+ bHbVkOiO+a4LU8A56vXnMpoP1e2b1oPFkY5M/fLJhXW85WTYBxv/C9qD2CuoQjJe UuF04BIfjFaXFU1h32+zDBekommB4SwTgQxKOShi/aZINzWkqqjokXvjy7CTVyZa QvPuwuNWyiWEt9Z91dhbgXRicZz+5+5UB+27v/mSFASFWi4RDvGqf0DaU22wf6aA ==
X-ME-Sender: <xms:XYCxYYjzY_LVyGngcuUaR3KVdjKoIHk5fHj8uqbD_O2jtvgePuD2aw> <xme:XYCxYRD9sLq0ZaAHaslITGS6gQec-6L01w3cNLhg4RFsi3WZSdXCaJagdR6dZ2p1i ebEw1DNXZZ-Nyrgcis>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrjeelgdeikecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:XYCxYQF42KK8FNNPaHrp1vZggPtZ2TKSX4fe2RCSagBiqpa8Ba3P6Q> <xmx:XYCxYZRqy5Ua7cmgS00Bz_SJRjTZOPrR466YnKBZJfpUWx8UJesMcg> <xmx:XYCxYVwdEV4dG1VeaInu-gyL_USOXFu5GU41rahjERUqFxv-wFBanA> <xmx:XYCxYU9HHIoJK9Ty7NN8gSYyCXsxGfeC8eNW9pOnRMtcbXaoBqK-vg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1CBC03C031B; Wed,  8 Dec 2021 23:04:45 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-4506-g4374de3f18-fm-20211208.001-g4374de3f
Mime-Version: 1.0
Message-Id: <4fed7080-5313-4c84-9763-70a64dad2b3e@www.fastmail.com>
In-Reply-To: <a4c3712e-c149-4fcb-a3e2-cae0c7bd14cc@www.fastmail.com>
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com> <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com> <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com> <CANzuiCifdR_zdMjnzSoze-Odj=rBzHiuGNAERSp6M+uCrPjVZA@mail.gmail.com> <4a59ee08-8733-49b4-a9a9-3c7b5b0560ce@www.fastmail.com> <a4c3712e-c149-4fcb-a3e2-cae0c7bd14cc@www.fastmail.com>
Date: Thu, 09 Dec 2021 15:04:27 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: ppm@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/tm9RpKwgkyWb_0b8hZqRUgRVsBc>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Dec 2021 04:04:53 -0000

On Thu, Dec 9, 2021, at 10:32, Christopher Wood wrote:
> This does seem like a reasonable simplification for the aggregation 
> protocol. It moves the boundary question out of the main flow and 
> closer to configuration. I suppose a task (or query) would have 
> well-defined windows marking t_start and t_end, clients would include a 
> timestamp in the report flow, and aggregators would check that against 
> the known window bounds. Is that the idea?

That's the general idea, yes.  The good part is that it buries all the complexity in the implementations.  The bad part is that it buries complexity in the implementations, which have to deal with it either way.


From nobody Thu Dec  9 07:48:37 2021
Return-Path: <cpatton@cloudflare.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 041AB3A0D8D for <ppm@ietfa.amsl.com>; Thu,  9 Dec 2021 07:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 WWw8LghhSxmu for <ppm@ietfa.amsl.com>; Thu,  9 Dec 2021 07:48:31 -0800 (PST)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 59C173A09E9 for <ppm@ietf.org>; Thu,  9 Dec 2021 07:48:31 -0800 (PST)
Received: by mail-qk1-x72b.google.com with SMTP id w14so5229181qkf.5 for <ppm@ietf.org>; Thu, 09 Dec 2021 07:48:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VQD4ajIcb71l1zdZ6z4v9Dawjxe9wkbZGkBfYKnUM/M=; b=saK7SOXlsyRQieJtrcbC81gxHn0/fZk2ZvzIzMNUQI1rK9awjAkxQw62OB6cH01dvP UED+G7NvBvn0zZ+U5hUg+8Ns8GQc+cRjz2C4zeKVYwb7RxYvCg2w429T+UW+A5Uhtl9D CkKfEhzUWimidzZ0tSNJPcHlL5zPVL5Qzcziw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VQD4ajIcb71l1zdZ6z4v9Dawjxe9wkbZGkBfYKnUM/M=; b=8RcFUwPDdRW/XaL4cIRYdLmtKhywWVvimNvi+7u1GNWhYYSfruDwGC65/Ucz05NRBR bDFNqAUC4abssLbOQCequS/gq+BWVFl4MYuxjzu6wbXg+h6kxpkvOwS6wuYlfcFavH9O Jx8YeSlFLeRkwUsg1834GenoEAYafgPm8LUg64RWdYbFlpBaHja7W08aNr+5oLOyDifM 2be8yaYOz4ifKag5JB9rSJ8GwAY+pufubv4usGyXUIFTbcPjbsWuTKOrR6/oeOrYyoFm qygeL9VWEV9srxGMitqjQgx/0PV1hLT/A7DJb1m3l0Wo2dK33EG+MtIGbwjRfWH31kse yBGw==
X-Gm-Message-State: AOAM530P/aVIpyH3XCYT/mTJCA/xtNmM09uQr4NBnd05Wxvln4r4p8B3 a2VbizBWx00INV/wPQm++iOdwDowUs3vtmpeW086Vl9RtYJ1zA==
X-Google-Smtp-Source: ABdhPJwgwbUfip+ARXuineeQOPMGueL9HhnykczixOw4YHkD8JJzkrrCrfURl7ddUYsS032Odf9Z844onNwP/A7VGjY=
X-Received: by 2002:a05:620a:4244:: with SMTP id w4mr14614764qko.215.1639064909668;  Thu, 09 Dec 2021 07:48:29 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com> <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com> <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com> <CANzuiCifdR_zdMjnzSoze-Odj=rBzHiuGNAERSp6M+uCrPjVZA@mail.gmail.com> <4a59ee08-8733-49b4-a9a9-3c7b5b0560ce@www.fastmail.com> <a4c3712e-c149-4fcb-a3e2-cae0c7bd14cc@www.fastmail.com> <4fed7080-5313-4c84-9763-70a64dad2b3e@www.fastmail.com>
In-Reply-To: <4fed7080-5313-4c84-9763-70a64dad2b3e@www.fastmail.com>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Thu, 9 Dec 2021 07:48:19 -0800
Message-ID: <CAG2Zi20jt3TT5fPO1Cx0tLgCDjKREUiQDSCv7PfFRZKTD7834w@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: ppm@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b489ac05d2b88997"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/9_UX1dsO_v8qF_lUk20d0-knMV4>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Dec 2021 15:48:36 -0000

--000000000000b489ac05d2b88997
Content-Type: text/plain; charset="UTF-8"

The collect-request already specifies a "batch interval", which defines the
range of timestamps of reports that will be aggregated. The start and end
time needs to align with time boundaries that the aggregators and collector
agree on:
https://abetterinternet.github.io/ppm-specification/draft-gpew-priv-ppm.html#name-validating-batch-parameters

This collect-request is what I've been thinking of as a "query". I guess
the observation here is that we only need to keep track of nonces for batch
intervals that have not been "collected"?

On Wed, Dec 8, 2021 at 8:04 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Thu, Dec 9, 2021, at 10:32, Christopher Wood wrote:
> > This does seem like a reasonable simplification for the aggregation
> > protocol. It moves the boundary question out of the main flow and
> > closer to configuration. I suppose a task (or query) would have
> > well-defined windows marking t_start and t_end, clients would include a
> > timestamp in the report flow, and aggregators would check that against
> > the known window bounds. Is that the idea?
>
> That's the general idea, yes.  The good part is that it buries all the
> complexity in the implementations.  The bad part is that it buries
> complexity in the implementations, which have to deal with it either way.
>
> --
> Ppm mailing list
> Ppm@ietf.org
> https://www.ietf.org/mailman/listinfo/ppm
>

--000000000000b489ac05d2b88997
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>The collect-request already specifies a &quot;batch i=
nterval&quot;, which defines the range of timestamps of reports that will b=
e aggregated. The start and end time needs to align with time boundaries th=
at the aggregators and collector agree on:</div><div><a href=3D"https://abe=
tterinternet.github.io/ppm-specification/draft-gpew-priv-ppm.html#name-vali=
dating-batch-parameters">https://abetterinternet.github.io/ppm-specificatio=
n/draft-gpew-priv-ppm.html#name-validating-batch-parameters</a></div><div><=
br></div><div>This collect-request is what I&#39;ve been thinking of as a &=
quot;query&quot;. I guess the observation here is that we only need to keep=
 track of nonces for batch intervals that have not been &quot;collected&quo=
t;?<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Wed, Dec 8, 2021 at 8:04 PM Martin Thomson &lt;<a href=3D"m=
ailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">On Thu, Dec 9, 2021, at 10:32, Ch=
ristopher Wood wrote:<br>
&gt; This does seem like a reasonable simplification for the aggregation <b=
r>
&gt; protocol. It moves the boundary question out of the main flow and <br>
&gt; closer to configuration. I suppose a task (or query) would have <br>
&gt; well-defined windows marking t_start and t_end, clients would include =
a <br>
&gt; timestamp in the report flow, and aggregators would check that against=
 <br>
&gt; the known window bounds. Is that the idea?<br>
<br>
That&#39;s the general idea, yes.=C2=A0 The good part is that it buries all=
 the complexity in the implementations.=C2=A0 The bad part is that it burie=
s complexity in the implementations, which have to deal with it either way.=
<br>
<br>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>

--000000000000b489ac05d2b88997--


From nobody Fri Dec 10 14:59:52 2021
Return-Path: <cpatton@cloudflare.com>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0353C3A0929 for <ppm@ietfa.amsl.com>; Fri, 10 Dec 2021 14:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.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 fz7_hWpOuzdu for <ppm@ietfa.amsl.com>; Fri, 10 Dec 2021 14:59:44 -0800 (PST)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 4FA043A091E for <ppm@ietf.org>; Fri, 10 Dec 2021 14:59:44 -0800 (PST)
Received: by mail-qt1-x834.google.com with SMTP id l8so9882738qtk.6 for <ppm@ietf.org>; Fri, 10 Dec 2021 14:59:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OJXyNDSXfEgECAwmGwwg51wv4SiDIFP94478UD0+3f8=; b=pws4L3RvZes4p82nAS95AmtL+GTYQfWHNHMF21+Mgbs2sla3RAkSFSvNue670Oo1zH HZeDZYDLqca+KQWeZP3QqRPtEGMxusfUL6I6Dz52hoS3DFK2DVFrKSdh9WriSXKdAvZS PWBDtXih87fWHHkwMtLYqeQFkx4kCp/EkESz8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OJXyNDSXfEgECAwmGwwg51wv4SiDIFP94478UD0+3f8=; b=25aVT81aJZPNqxCE1jVExvaldD3f58mxR5bfcQXF2RxomIVG+8IHKc6juybKdoaNxy B786lCg3zeYH78y73mvjnu+c1gizSK11Jpb18HcfNemYpj2bVDyoo36XGNCF5bt/SceW UQ/TDoJJ6pg6Of3cYyQLuXFFu34rfEqq82RJM2SXvu+9h2SBscByzaOi+nSk7FErN7p9 7N2FZ8Gv11MNUecQUGRic5QkSMaYe6OANxYg+5/G5teDGI6/IqcHWkm6E+6LxWk3JY7T L2Fj6YDIGtjDQy0Mi5AtUXhpPq2/ZS08WwVnNdeV3C+xTIcsjNROilXLCo92RvLGNDnb 8wfQ==
X-Gm-Message-State: AOAM531F/q3fGvkmBjyQ2kQmoH3A8UmbqZS9MzzrPjQSvApdjDgAzcpu nPIdvxJYt2tsXbfJL+QwL6GXFOAHlvzelvt0XDxYlRC8quY=
X-Google-Smtp-Source: ABdhPJzGSa1zIt7RzoI/1KHARW94PwK7I+CEcdWXuoP2+Fb+pvgYO0QmaP3XAs6m+lWHqAvxycVkg+c3e+w76N0evMI=
X-Received: by 2002:a05:622a:151:: with SMTP id v17mr30453473qtw.167.1639177182668;  Fri, 10 Dec 2021 14:59:42 -0800 (PST)
MIME-Version: 1.0
References: <CAG2Zi20oarjT6jBbtFtvQUMy5uRZTK6Z2YgBSE+wT33xQbkb+A@mail.gmail.com> <b79ab552-af97-4281-baee-4560d65eab1f@www.fastmail.com> <CAG2Zi21inwbTBc2xH9a3iajMpAiOs8hwc=eXkwrcpkKS1Tn4HA@mail.gmail.com> <CANzuiCiQVgT3L0w0jQdEJ7V8zpF2eGwys_gBOpATQ4O8ww0s4w@mail.gmail.com> <CAG2Zi220178bj=8ncx6oKQ3x7cJqhvDTi99WEoyLsAJ8VwT=0Q@mail.gmail.com> <16665bbd-abea-4ad9-8caa-cb07d8e5f804@www.fastmail.com> <CABN231q06UYLLwHJ3ymKOP-x75f32yj4OTZZ8sXXmc7x0fEb1Q@mail.gmail.com> <bec4fd7f-c0ee-4ff1-93bf-0f1e2ed8c205@www.fastmail.com> <CAG2Zi205aecefAzwsy1fN+ce7mw241rPZb5oBk8XBcmBY5GPww@mail.gmail.com> <fcdf3904-213f-4db3-a9b9-5029e77d26c6@www.fastmail.com> <CANzuiCifdR_zdMjnzSoze-Odj=rBzHiuGNAERSp6M+uCrPjVZA@mail.gmail.com> <4a59ee08-8733-49b4-a9a9-3c7b5b0560ce@www.fastmail.com> <a4c3712e-c149-4fcb-a3e2-cae0c7bd14cc@www.fastmail.com> <4fed7080-5313-4c84-9763-70a64dad2b3e@www.fastmail.com> <CAG2Zi20jt3TT5fPO1Cx0tLgCDjKREUiQDSCv7PfFRZKTD7834w@mail.gmail.com>
In-Reply-To: <CAG2Zi20jt3TT5fPO1Cx0tLgCDjKREUiQDSCv7PfFRZKTD7834w@mail.gmail.com>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Fri, 10 Dec 2021 14:59:31 -0800
Message-ID: <CAG2Zi20FkoUq0XgBkU2hPLgLLKVJqQ=k98Qcw5QiRDC4YAakKg@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: ppm@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b289cd05d2d2ad18"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/JwXKZKrpmT9-rPs-GJa7l3YUxGY>
Subject: Re: [Ppm] Revisit the operational requirements for the Helper?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Dec 2021 22:59:50 -0000

--000000000000b289cd05d2d2ad18
Content-Type: text/plain; charset="UTF-8"

Hi all, I've updated the PR to remove the requirement for time
synchronization.

On Thu, Dec 9, 2021 at 7:48 AM Christopher Patton <cpatton@cloudflare.com>
wrote:

> The collect-request already specifies a "batch interval", which defines
> the range of timestamps of reports that will be aggregated. The start and
> end time needs to align with time boundaries that the aggregators and
> collector agree on:
>
> https://abetterinternet.github.io/ppm-specification/draft-gpew-priv-ppm.html#name-validating-batch-parameters
>
> This collect-request is what I've been thinking of as a "query". I guess
> the observation here is that we only need to keep track of nonces for batch
> intervals that have not been "collected"?
>
> On Wed, Dec 8, 2021 at 8:04 PM Martin Thomson <mt@lowentropy.net> wrote:
>
>> On Thu, Dec 9, 2021, at 10:32, Christopher Wood wrote:
>> > This does seem like a reasonable simplification for the aggregation
>> > protocol. It moves the boundary question out of the main flow and
>> > closer to configuration. I suppose a task (or query) would have
>> > well-defined windows marking t_start and t_end, clients would include a
>> > timestamp in the report flow, and aggregators would check that against
>> > the known window bounds. Is that the idea?
>>
>> That's the general idea, yes.  The good part is that it buries all the
>> complexity in the implementations.  The bad part is that it buries
>> complexity in the implementations, which have to deal with it either way.
>>
>> --
>> Ppm mailing list
>> Ppm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppm
>>
>

--000000000000b289cd05d2d2ad18
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all, I&#39;ve updated the PR to remove the requirement =
for time synchronization. <br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Dec 9, 2021 at 7:48 AM Christopher Pa=
tton &lt;<a href=3D"mailto:cpatton@cloudflare.com">cpatton@cloudflare.com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div>The collect-request already specifies a &quot;batch int=
erval&quot;, which defines the range of timestamps of reports that will be =
aggregated. The start and end time needs to align with time boundaries that=
 the aggregators and collector agree on:</div><div><a href=3D"https://abett=
erinternet.github.io/ppm-specification/draft-gpew-priv-ppm.html#name-valida=
ting-batch-parameters" target=3D"_blank">https://abetterinternet.github.io/=
ppm-specification/draft-gpew-priv-ppm.html#name-validating-batch-parameters=
</a></div><div><br></div><div>This collect-request is what I&#39;ve been th=
inking of as a &quot;query&quot;. I guess the observation here is that we o=
nly need to keep track of nonces for batch intervals that have not been &qu=
ot;collected&quot;?<br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Wed, Dec 8, 2021 at 8:04 PM Martin Thomson=
 &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank">mt@lowentropy.n=
et</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">On Thu, Dec 9, 2021, at 10:32, Christopher Wood wrote:<br>
&gt; This does seem like a reasonable simplification for the aggregation <b=
r>
&gt; protocol. It moves the boundary question out of the main flow and <br>
&gt; closer to configuration. I suppose a task (or query) would have <br>
&gt; well-defined windows marking t_start and t_end, clients would include =
a <br>
&gt; timestamp in the report flow, and aggregators would check that against=
 <br>
&gt; the known window bounds. Is that the idea?<br>
<br>
That&#39;s the general idea, yes.=C2=A0 The good part is that it buries all=
 the complexity in the implementations.=C2=A0 The bad part is that it burie=
s complexity in the implementations, which have to deal with it either way.=
<br>
<br>
-- <br>
Ppm mailing list<br>
<a href=3D"mailto:Ppm@ietf.org" target=3D"_blank">Ppm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ppm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/ppm</a><br>
</blockquote></div>
</blockquote></div>

--000000000000b289cd05d2d2ad18--


From nobody Sun Dec 12 00:35:57 2021
Return-Path: <do_not_reply@mnot.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85F3A3A08A6 for <ppm@ietfa.amsl.com>; Sun, 12 Dec 2021 00:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Afo4bvvJ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=j76jlCyP
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 r5ibndJXEQdf for <ppm@ietfa.amsl.com>; Sun, 12 Dec 2021 00:35:50 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A76B53A08A4 for <ppm@ietf.org>; Sun, 12 Dec 2021 00:35:50 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 8B57F5C0159 for <ppm@ietf.org>; Sun, 12 Dec 2021 02:39:29 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 12 Dec 2021 02:39:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm1; bh=gQOBI6xcvuo Z4Qld0c4sAQrUEH2sgBPpwhuYIIkCJyQ=; b=Afo4bvvJ3h1pYVrTUbrMTwS8aj+ v+ZLuvqt273FpTdiTxaHlngnNDjqZ1XwptaK0fr8e867spr7pn7YAvG6opclAnQn 1TWCT56kTFpOLJ0e+wNr+v9TMsq4lQYgnZVOydefH7Lps1gyqZjR1uoto6Zed3OC E1kSDtmbWeaQAQVY8wyyzlLtpds5b+CjGstgYDCIFf4lETXL4OnZbybrrhoptoj4 9s51P4M4R3Gmqh2HhBCly+T5ZJk5DW3GAzYqnYyGc2w5evXUAV+sMNb+vSmu3Nqv IrUhLOnQfJh8Gx87WJSQI00nqgsvEaOCjrt8l6KLzq1kYJDlGR9T2M5Hv8g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=gQOBI6xcvuoZ4Qld0c4sAQrUEH2sgBPpwhuYIIkCJyQ=; b=j76jlCyP ktSPwRrz+dWqMbSdbWv2VJOWY7Lta8GhbsccQ+C3gN08w8q7MF1WBsZbi2MhXTz9 rIzP17hie4ducdnmVjLYng0H4pJyaVWCjtNkXwLdfQWOl/1dG9sz3Ayruf3lgt+t QJoMO6QDSANKMmJiWpvonssPMYEvLshcOpU4r96ZAk9bVd7iCrBGgNY/gKBgIv6y dq6/DEHUBKYeky12d5dF2RwqIKY4c67AWfQg/KSPCq6Gw6M9sjgQIXmIL9d84y0X BnkaNeDbRQkqT7ZjRfCMA+/oxc4G9bPsvK3W5/PtwGGayV+orft6W2gzDuEILLwC QFAvW75sMW5n1A==
X-ME-Sender: <xms:Mae1YYUmMFCtQefWwvMtet6dlRIwhygGYuiW4rKWeZBDo6xCpK0YTw> <xme:Mae1YckArofTYuNWxkC0dOBhpoHEHLKM-hQtX_VgXmv3gWlpJsIj2tgZB0av6ekrC D_hTU-TTZBPtnCoKA>
X-ME-Received: <xmr:Mae1YcZDdxger-dMWnlVgwcnKScQrX6socywt9f5542OkUDi1lFIzXfSL8X5oVh8eS4TlYDHg03KcrX9bjRpdVd4r6tk3o1WeJ-5ApDzcRok7N1PsVgKZ7vWl3mOXb1znEZP2w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrkeehgddutdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenuc fjughrpegtggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicu tegtthhivhhithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihse hmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeefvdduteejvdefkeehieevuefg fefhteetveegffekffefteffvdelheduieetnecuffhomhgrihhnpehgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:Mae1YXUrFwVAAeyhMWGwMqnGvZsn16cbYDTfaKpKMPbGx2K1N3nmuA> <xmx:Mae1YSljCL5BVLprAa8UFfe7oQjEBUEApniWiG62IhBkOegk1LiSgQ> <xmx:Mae1YceqW-s839iPuixgItYK775Mmm5fjHcyyG-eB8nhBlvNhQ1Dng> <xmx:Mae1YXxMYz0CHeoOaZUKjhiIi1L1tu4Sk66qKKvJLu6_eXxu6hxxOg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ppm@ietf.org>;  Sun, 12 Dec 2021 02:39:29 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============2156519066752811665=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: ppm@ietf.org
Message-Id: <20211212083550.A76B53A08A4@ietfa.amsl.com>
Date: Sun, 12 Dec 2021 00:35:50 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/FLsIxEk04PPr_apIfSMtNYXNE8I>
Subject: [Ppm] Weekly github digest (Privacy Preserving Measurement Activity Summary)
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Dec 2021 08:35:56 -0000

--===============2156519066752811665==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events=20

Issues
------
* abetterinternet/ppm-specification (+0/-1/=F0=9F=92=AC0)
  1 issues closed:
  - Need LICENSE.md https://github.com/abetterinternet/ppm-specification/is=
sues/144=20



Pull requests
-------------
* abetterinternet/ppm-specification (+3/-2/=F0=9F=92=AC5)
  3 pull requests submitted:
  - Simplify overview text about the aggregation function (by cjpatton)
    https://github.com/abetterinternet/ppm-specification/pull/170=20
  - Revise anti-replay mechanism (by cjpatton)
    https://github.com/abetterinternet/ppm-specification/pull/169=20
  - Refer to VDAF instead of "PPM scheme" (by cjpatton)
    https://github.com/abetterinternet/ppm-specification/pull/168=20

  3 pull requests received 5 new comments:
  - #169 Revise anti-replay mechanism (3 by cjpatton)
    https://github.com/abetterinternet/ppm-specification/pull/169=20
  - #168 Refer to VDAF instead of "PPM scheme" (1 by cjpatton)
    https://github.com/abetterinternet/ppm-specification/pull/168=20
  - #154 Specify the protocol in terms of VDAF evaluation (1 by cjpatton)
    https://github.com/abetterinternet/ppm-specification/pull/154=20

  2 pull requests merged:
  - Simplify overview text about the aggregation function
    https://github.com/abetterinternet/ppm-specification/pull/170=20
  - Refer to VDAF instead of "PPM scheme"
    https://github.com/abetterinternet/ppm-specification/pull/168=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/abetterinternet/ppm-specification

--===============2156519066752811665==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (Privacy Preserving Measurement Activity Summar=
y)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday December 12, 2021</h1>

<p>Events </p>

<h2>Issues</h2>

<h3>abetterinternet/ppm-specification (+0/-1/=F0=9F=92=AC0)</h3>


  <p>1 issues closed:</p>
  <ul>
  <li>#144 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
issues/144">Need LICENSE.md</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>abetterinternet/ppm-specification (+3/-2/=F0=9F=92=AC5)</h3>
  <p class=3D"new">3 pull requests submitted:</p>
  <ul>
  <li>#170 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/170">Simplify overview text about the aggregation function</a> (by cjp=
atton) </li>
 =20
  <li>#169 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/169">Revise anti-replay mechanism</a> (by cjpatton) </li>
 =20
  <li>#168 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/168">Refer to VDAF instead of &quot;PPM scheme&quot;</a> (by cjpatton)=
 </li>
  </ul>

  <p>3 pull requests received 5 new comments:</p>
  <ul>
  <li>#169 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/169">Revise anti-replay mechanism</a> (3 by cjpatton) </li>
 =20
  <li>#168 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/168">Refer to VDAF instead of &quot;PPM scheme&quot;</a> (1 by cjpatto=
n) </li>
 =20
  <li>#154 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/154">Specify the protocol in terms of VDAF evaluation</a> (1 by cjpatt=
on) </li>
  </ul>

  <p>2 pull requests merged:</p>
  <ul>
  <li>#170 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/170">Simplify overview text about the aggregation function</a> </li>
 =20
  <li>#168 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/168">Refer to VDAF instead of &quot;PPM scheme&quot;</a> </li>
  </ul>


  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/abetterinternet/ppm-specification">http=
s://github.com/abetterinternet/ppm-specification</a></li>
</ul>
</details>
</body>
</html>

--===============2156519066752811665==--


From nobody Sun Dec 19 00:56:05 2021
Return-Path: <do_not_reply@mnot.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21613A0B8F for <ppm@ietfa.amsl.com>; Sun, 19 Dec 2021 00:56:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=bgigWzYy; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Y96G9cTU
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 DHMbog2z1xIw for <ppm@ietfa.amsl.com>; Sun, 19 Dec 2021 00:55:57 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE7463A0B80 for <ppm@ietf.org>; Sun, 19 Dec 2021 00:55:57 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id D17123200C20 for <ppm@ietf.org>; Sun, 19 Dec 2021 02:40:01 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 19 Dec 2021 02:40:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm1; bh=Nko/HfFlcYM SM1opNP3DSiz5fT5YP8NFXneY6RZMoy8=; b=bgigWzYym9L8IAY/8ZVMjs1JTH0 sryM0q6wb29Pn3VW3J0y1ZivxS54mfK6s0hXSj1aClEx99UVSvF8+nsQ2yXNUl1a 9SUDUjgbocqqRnslUXUyAcNQ7s4MyXcseRFNfB+xF74ZQW+2u5dLmfCQQqVr85n9 lerRpDgoVBj7R26m5mhhO2pgEXfxaePyAMGfvP9RuzzVC1WSCbZDG/5brlh3RcL3 J5p7c+BwiNb97D/J2B7CREF8iDPqgC+ANajQ/NnTIJEG5WMHsx+nGBhObh0TNHpt /aFkaePG9Q2O+l4R/ELvNCSKQ6W1tJHr/lmTN23ldTBroB83X0XxXile7Aw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=Nko/HfFlcYMSM1opNP3DSiz5fT5YP8NFXneY6RZMoy8=; b=Y96G9cTU Kr0dNh/imiBdcOWtjkhhhDJfHgp81Ti8eugRk/kcfstjcAU8u3pixRrHOU+unXJ+ akylDojveFcKVCBap/wh0+2GH08c7opI7u1ci8K01n3ylj5pRdxTc/aKQtnD7x8Q 9CnVreNX2160sSvsroz1RmcYUY90Cwg1Bu7BHrkKszBjElq+GjXoGZt/N5U+88oM M1usRMkzgup1CXpFovdx8GBl9FGhr3i5w48jG9t/Lhw2B9sd7eEkkUaSpWICkhak hLKTvmO61XC2wJELtq+goj4pT/F1Ro5twXs8N4Fu5SW0MNP3kb/3Wu5t1/XOye7Z OtUzk5qmMt8tyQ==
X-ME-Sender: <xms:0eG-YX85W3PxQVWGg3rOObyiEVdVIdtbCsjSwj2cRk1zGnZzru3W8Q> <xme:0eG-YTuxiX4RhXUMC1UAd3Ibk-Wt0eEM2SwpsnzEU1pvLNweQALrmFwBoEmt_Ny70 k1uvE8G0J2hTnZT5A>
X-ME-Received: <xmr:0eG-YVDQnxlZSyXlASzNIRvSOKT5Ns65MDqfiIcHa0CZYOh6XyWcDH1eBsmYJJmoDudwICXM9_y10MC1i8eANvwDfpVJnpRFmuDUN-Hfn7v02gVplGwxLAhdn1Y5LQ7m2W77ag>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrleelgddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenuc fjughrpegtggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicu tegtthhivhhithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihse hmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeefvdduteejvdefkeehieevuefg fefhteetveegffekffefteffvdelheduieetnecuffhomhgrihhnpehgihhthhhusgdrtg homhenucevlhhushhtvghrufhiiigvpeefnecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:0eG-YTf-1iwCTdmWp8bt8BYCgP9mG_qWFOPVSZhKeuUpercgyi52XQ> <xmx:0eG-YcNr54jfLW6HMWW5UlqnXTyROShu0zPfZnoTB-drh0f9mlgTaA> <xmx:0eG-YVmwBChMYjsIADXZ_CpiUUGcepmsVrdqL-vL4dcA-lIQMx6bHg> <xmx:0eG-YVYOvc6ikbuQqQWy_03i1UrHzGLtgT7p48VJZ-01IbnFhd2Unw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ppm@ietf.org>;  Sun, 19 Dec 2021 02:40:01 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============8911045642978417018=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: ppm@ietf.org
Message-Id: <20211219085557.BE7463A0B80@ietfa.amsl.com>
Date: Sun, 19 Dec 2021 00:55:57 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/90MJtMzFHSScUseGcbE0gHNnrKU>
Subject: [Ppm] Weekly github digest (Privacy Preserving Measurement Activity Summary)
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Dec 2021 08:56:03 -0000

--===============8911045642978417018==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events=20



Pull requests
-------------
* abetterinternet/ppm-specification (+2/-2/=F0=9F=92=AC0)
  2 pull requests submitted:
  - Final edits for Roman (by ekr)
    https://github.com/abetterinternet/ppm-specification/pull/172=20
  - Reformat charter.md and ignore more files (by cjpatton)
    https://github.com/abetterinternet/ppm-specification/pull/171=20

  2 pull requests merged:
  - Final edits for Roman
    https://github.com/abetterinternet/ppm-specification/pull/172=20
  - Reformat charter.md and ignore more files
    https://github.com/abetterinternet/ppm-specification/pull/171=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/abetterinternet/ppm-specification

--===============8911045642978417018==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (Privacy Preserving Measurement Activity Summar=
y)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday December 19, 2021</h1>

<p>Events </p>



<h2>Pull requests</h2>
<h3>abetterinternet/ppm-specification (+2/-2/=F0=9F=92=AC0)</h3>
  <p class=3D"new">2 pull requests submitted:</p>
  <ul>
  <li>#172 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/172">Final edits for Roman</a> (by ekr) </li>
 =20
  <li>#171 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/171">Reformat charter.md and ignore more files</a> (by cjpatton) </li>
  </ul>


  <p>2 pull requests merged:</p>
  <ul>
  <li>#172 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/172">Final edits for Roman</a> </li>
 =20
  <li>#171 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
pull/171">Reformat charter.md and ignore more files</a> </li>
  </ul>


  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/abetterinternet/ppm-specification">http=
s://github.com/abetterinternet/ppm-specification</a></li>
</ul>
</details>
</body>
</html>

--===============8911045642978417018==--


From nobody Mon Dec 20 19:04:02 2021
Return-Path: <ndoty@cdt.org>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C33513A1080 for <ppm@ietfa.amsl.com>; Mon, 20 Dec 2021 19:04:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 zf6o1muMWuCu for <ppm@ietfa.amsl.com>; Mon, 20 Dec 2021 19:03:55 -0800 (PST)
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230]) (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 C61F33A107F for <ppm@ietf.org>; Mon, 20 Dec 2021 19:03:55 -0800 (PST)
Received: by mail-oi1-x230.google.com with SMTP id t19so18828472oij.1 for <ppm@ietf.org>; Mon, 20 Dec 2021 19:03:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=+y1Uvt3nmwn4VnC+m+k7mk82vSRJ025nJ8pOTChX/Xc=; b=ZaBFpzf2+5kQyaX4Lu445/0z9xKvJHKQMUS1ffRp8csNdf0ybnenf76L9QzbAw7ZEy ag8fs6am+B+bhDzBqSLAUQBlvsS2x8caGDe0rUSadDsWTDRsWAJqEbRCsyUiJPF0Wfm7 wr7+I9gmVi81mDHkQkRz2fR9g42uO5sJ7gjpo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+y1Uvt3nmwn4VnC+m+k7mk82vSRJ025nJ8pOTChX/Xc=; b=Xjfi6EBdkZW2ev1dq9Es6OFkq+TxXTVTcjFIv3U3t8Q3hvzdzIBCRNxmRtaorg2yUg FeWxftgbtlEWzfB57K34dWIs3o9usFNdqbSMmRELlXFDZ8dhx5pezV8iYd485vnVcxrC XH6hTr2XYHSz2qXbG/CObK4NyKml9K1wJJC/9+rg0KwUTSsKqjn9OwrUnymhlG5qbFxW YbyEunLqYVpwhvqdwFtXq4f8qZZ5AssL0ihFgOnAXNIEK48DjUSDGGph/MUhtx1obJ4e 9D1feR7ZIiMR12kCyiZjABFdsGwTi+5trRvvl1CuSvwFlCmuXfWnccJ0HwRGs8O/l9L0 DSwA==
X-Gm-Message-State: AOAM530q6qskPS30TdwZZ/q6jFpMrR//VjivX3fM5Dvd33MRO09aVxUt 7q6iWge8Cq5lzmwX9bZ6kROXx7N5cNAqK5jLGo38qKvGFox+hA==
X-Google-Smtp-Source: ABdhPJxFfm2fnNnFAFLxKSRnN8XQsPtQylenJQrRuZewlieEHp1wc94wYZoyZ87ujNnekrgIQzc2dHRr7zrATXmsENE=
X-Received: by 2002:a05:6808:114a:: with SMTP id u10mr823810oiu.159.1640055833297;  Mon, 20 Dec 2021 19:03:53 -0800 (PST)
MIME-Version: 1.0
From: Nick Doty <ndoty@cdt.org>
Date: Mon, 20 Dec 2021 22:03:42 -0500
Message-ID: <CA+tYtvFLkB9a-xZfAdBKwGrn5VoTHnXZxd350LBP8MoZKypf7g@mail.gmail.com>
To: ppm@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/oel17RTV160JnQX3lC_ThyaARAo>
Subject: Re: [Ppm] Name suggestion
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Dec 2021 03:04:01 -0000

One way to distinguish the acronym and add something informative might
be to clarify that this work is about privacy-preserving *aggregate*
measurement. I believe that's what all the current proposals are
describing (although secure multi-party computations can perform other
kinds of operations, I don't think that's in scope here) and would
help a newcomer know what kind of techniques the group is looking at
to support privacy. And maybe PPAM is less likely to have conflict or
confusion with other acronyms.

> Strong support for PPM. Seems the most intuitive. This is peak
> bikeshedding, but I'm surprised by the supposed clash with IPPM - when I
> read that acronym I read "IP" first :) PPM immediately makes me think of
> privacy preserving measurement.

I also don't mind PPM (I wasn't familiar with IPPM anyway though), I
was just concerned by PRIV.

Apologies, I meant to follow-up on this name suggestion right away but
got distracted and wasn't subscribed to the right mailing list.

Cheers,
Nick


From nobody Sun Dec 26 00:16:01 2021
Return-Path: <do_not_reply@mnot.net>
X-Original-To: ppm@ietfa.amsl.com
Delivered-To: ppm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 479FB3A145A for <ppm@ietfa.amsl.com>; Sun, 26 Dec 2021 00:15:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=hEn6YNrm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=h0zMk52e
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 dsUbL0gKEmQP for <ppm@ietfa.amsl.com>; Sun, 26 Dec 2021 00:15:51 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A76B3A1458 for <ppm@ietf.org>; Sun, 26 Dec 2021 00:15:50 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0A5975C0153 for <ppm@ietf.org>; Sun, 26 Dec 2021 02:39:50 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 26 Dec 2021 02:39:50 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject; s=fm1; bh=cblMG6R5wlw yqH3hwtdUz+QA1sN1efvjnO7H+gveolo=; b=hEn6YNrmfW1utq9lIcl0DSHDz4u rPJk/UPw+EIxmXepYHp9nbwSihqKHpQgHI0jfkRYUNyaTjjHsB5CYBt/DXq59667 pRaTPODjnII4vMAqXRlMXk1ERmb5723+96AYQsHLHj9fIhtTXWJO+wTApML+07Wb 3hyQ9cyOlwqIwIBWvFyNREmXYZQitEoijJjtUK6kmFpwFKLjMAlja1kPB2iEF60A 1lL/XbUwLkViAAEaEOlkYOMjS4UuqSgwYXivmjz2oni57FSdvrK+qDFQosCptjM2 iurUyJYiAaVllLz2djd+BsieTalwTHoyyxdX54LEXMICGZm7OGMPjkMAW9A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:from:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=cblMG6R5wlwyqH3hwtdUz+QA1sN1efvjnO7H+gveolo=; b=h0zMk52e r0QPivRE9knQv+AbMpqLcDb4v2wlmv8Oh3ZLd2yKMYuiqbsWXMA+XYFUCdWSZ6YL sSDkXwTikTWOPPZGeuwAtbZoNCpn/eD5nbppmm2HmKh5fsg214haxuWDOwVONOFU Jwn4dsuLJL9zUF8RAWNp+U9XzgmjHLaqlDLksxktBRVNHFNK2N7OAB9ySBeoqKWn 70x1OxKpwURmiIpwxtYpJhR83pWUoT7kFQd3i2wxRscbirPKTdipl+OgP4Z9IKya Glw/7tVUPr2Y9X+0ogTkTzScAqFZgnqHsrXI7qd2Xp1lYl0lCts5MLupRZqKxKkc Udg+V8/xLw1jJA==
X-ME-Sender: <xms:RRzIYeRYWhzbutJjLeH4VodDa9K5FG5grze4Cub-gpdHVKLo27aClg> <xme:RRzIYTzNejDXrY3c2mKWPhPqO5_UESUxPFpySTlFt8-AGetIc5slHIT8tZ01Wq-AB UYzPxxYgWtELgiXRw>
X-ME-Received: <xmr:RRzIYb2iXSsoUKnCPm-8z8WxLJZSY44aQJ2RPO_iUK7AC1H9QyUZkLWLb2AvozcGL_k4vKq-SJFiyT62MAPCdZYiw01pAn7Q4jYtHOQRbjDaYG5wH1jbKv_09fVwQj-qoJebow>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddruddufedguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgepvdenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:RRzIYaCEM8i0RcZed9lleH5WeBo34MK-wSeFng89jjCG6N7n_7q0Cg> <xmx:RRzIYXj82sYC1zZz9mqz29cb-EHBblveJl--9TjbfH2dZ25iRQFoTw> <xmx:RRzIYWrrl7mjLpNNg_E-IUh2TobrQr5lIYwOUk3kQ5thymnWhNwJ0g> <xmx:RhzIYasgLGeByptSUAJwfmsTvLV_jRVQr7SyBck7BLAwn1pK6747Hg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ppm@ietf.org>;  Sun, 26 Dec 2021 02:39:49 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============4589193489077070729=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: ppm@ietf.org
Message-Id: <20211226081550.9A76B3A1458@ietfa.amsl.com>
Date: Sun, 26 Dec 2021 00:15:50 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/c4NqfhqNep4kunJvWXBWq-QBLTw>
Subject: [Ppm] Weekly github digest (Privacy Preserving Measurement Activity Summary)
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Preserving Measurement technologies <ppm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppm>, <mailto:ppm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ppm/>
List-Post: <mailto:ppm@ietf.org>
List-Help: <mailto:ppm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppm>, <mailto:ppm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Dec 2021 08:15:58 -0000

--===============4589193489077070729==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events=20

Issues
------
* abetterinternet/ppm-specification (+1/-0/=F0=9F=92=AC0)
  1 issues created:
  - addressing collusion (by npdoty)
    https://github.com/abetterinternet/ppm-specification/issues/173=20




Repositories tracked by this digest:
-----------------------------------
* https://github.com/abetterinternet/ppm-specification

--===============4589193489077070729==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (Privacy Preserving Measurement Activity Summar=
y)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday December 26, 2021</h1>

<p>Events </p>

<h2>Issues</h2>

<h3>abetterinternet/ppm-specification (+1/-0/=F0=9F=92=AC0)</h3>
  <p class=3D"new">1 issues created:</p>
  <ul>
  <li>#173 <a href=3D"https://github.com/abetterinternet/ppm-specification/=
issues/173">addressing collusion</a> (by npdoty) </li>
  </ul>






  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/abetterinternet/ppm-specification">http=
s://github.com/abetterinternet/ppm-specification</a></li>
</ul>
</details>
</body>
</html>

--===============4589193489077070729==--

