Re: [Ppm] Interim topic: Shall DAP support heavy hitters?

Christopher Patton <cpatton@cloudflare.com> Wed, 17 April 2024 19:37 UTC

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 8AC92C14F6A3 for <ppm@ietfa.amsl.com>; Wed, 17 Apr 2024 12:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cloudflare.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xeKJvyRsQ1j for <ppm@ietfa.amsl.com>; Wed, 17 Apr 2024 12:37:15 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69AD5C14F6B9 for <ppm@ietf.org>; Wed, 17 Apr 2024 12:37:15 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3c60adf3474so113380b6e.1 for <ppm@ietf.org>; Wed, 17 Apr 2024 12:37:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google09082023; t=1713382634; x=1713987434; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=LZxSrfgw7LMH8of67frF1po4rLj4aCr5hh0SXJkI+k8=; b=QX4Z0b+DO2ok3tj2mZd1IiTp2TzMepQeS1ur7g5rXWyfPZQitajcaUEx/6H7Fa+8zb qg2m2sTh5EArY0vqzdr3x6ixpYczRNftcJncG4FheEl+06sNnH4RB+9LNPZLxaYd54fv SP+CCJtMFbUNk2phdrINncK52wx7gqXEPw5w1aCZ6k08rmd/BRr2S5CTtDKpjE03Zymh jyI7KmiHAUny7HJxS4wEfUuTvJSlr0uqmV4JJ5hDWaDjPZkdKstwE2vt8ynVSUugY/3y Cwzmb3tFrQudTBmnNjq34wLy6VegTlRm+2ifBPE7X6egrE9gpyV3WK0YMb8ecsJ7k9O2 h3Tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713382634; x=1713987434; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=LZxSrfgw7LMH8of67frF1po4rLj4aCr5hh0SXJkI+k8=; b=Pa0uIRDi9WHTkV3emwcStoD+EAOkSh2B6wVEbZIaCU0OWkEKtZ8nf0J4jw3SI7l4Xv XEjbu0L/I4E6X9WPzZMHIwfX8MsHYx9PDTpoBiGlec7Mp55BtFJO9q4ulmeAd304B3zY +/N5YU5J/l8hjpPHRu0ckuDVHE3bXKZhWv6TMEwu/I0mOkqbxIqkVBkL6btcC7hSjYip fvJmTXlba8pidOl2bE4VHwiEMgJEmNYHHRlfY+GS/loFQU0iZFv8VR4r0aW0yJMXQg5N TVOqo7Emwqioe2Monje4ucUAXlY8Dc6Y1yp2G+XMr4nmYqU55vJIfeDo6V2ixOzq8mC+ inVA==
X-Gm-Message-State: AOJu0YzhHnm8QzqwLF1x3GgEXqvVbfnhakq3U7D6+mDVLlkwDHSHqi1F yTkt0vRVy2QvSwbQjHMksetZ2YZYQyeQspOeTQ91e2carW+sxjcehcagXwUudPWuAgSdHVk/X2T BRgv9/wpMWVZyoi7QyKUj3jM2eIzAV1N8FhsGJm5gUTI3CNfAvOQ=
X-Google-Smtp-Source: AGHT+IFotkt9YoiSWyd6W/YHEHH9esQLBlU25oOQraCigQ0hwb/+iIzbGRUDHGkB5DTMKhfyVFikir34hzTsFDkG1mg=
X-Received: by 2002:a05:6808:23d5:b0:3c7:ac9:5429 with SMTP id bq21-20020a05680823d500b003c70ac95429mr749252oib.0.1713382633932; Wed, 17 Apr 2024 12:37:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAG2Zi21sjDQ31S7MpKL92ZL9o9_OnqsYe_33RPvW3eMDh2Wzeg@mail.gmail.com> <CAG2Zi23xe03ahKSE1=ZZiuZrsop9yviWOUWzJfeYMA2YtWBRAQ@mail.gmail.com>
In-Reply-To: <CAG2Zi23xe03ahKSE1=ZZiuZrsop9yviWOUWzJfeYMA2YtWBRAQ@mail.gmail.com>
From: Christopher Patton <cpatton@cloudflare.com>
Date: Wed, 17 Apr 2024 12:37:03 -0700
Message-ID: <CAG2Zi201PDsq+ZLzV9LgEEA0H1VCDrewyDh3fDhggB+x+vYnWA@mail.gmail.com>
To: ppm <ppm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000430a6206164ffb75"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/1bFO8VnfD2tG3UqLRdPsgfaYXFE>
Subject: Re: [Ppm] Interim topic: Shall DAP support heavy hitters?
X-BeenThere: ppm@ietf.org
X-Mailman-Version: 2.1.39
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, 17 Apr 2024 19:37:19 -0000

Hi aggregators,

Just wanted to remind folks planning to attend the interim on Monday that
we're hoping to reach consensus on the following questions:
https://docs.google.com/document/d/1ZjXz-1kGsTDf2Vn2u-fwYqR8BSc3tOYlELVHAYvAfjk/edit#heading=h.c05ztkgnagl

I've also asked the chairs if we can do hums, just to make sure we hear
from everyone who cares about the heavy hitters use case.

Thanks,
Chris P.

On Thu, Apr 11, 2024 at 3:37 PM Christopher Patton <cpatton@cloudflare.com>
wrote:

> Hi everyone,
>
> I've prototyped most of the changes for Proposal #1 in Daphne:
> https://github.com/cloudflare/daphne/pull/575
>
> Lots of this would be reusable for #2. I hope this gives folks a sense of
> the scope of changes required for supporting heavy hitters.
>
> Chris P.
>
> On Mon, Apr 8, 2024 at 4:18 PM Christopher Patton <cpatton@cloudflare.com>
> wrote:
>
>> Hi folks,
>>
>> As noted at IETF 118, there are a number of issues for the DAP spec
>> related to supporting heavy hitters via Poplar1:
>>
>> https://datatracker.ietf.org/meeting/118/materials/slides-118-ppm-dap-open-issues
>>
>> We'd like to spend a significant chunk of time during the interim on
>> resolving these issues. To that end, Tim G. and I have been leading a small
>> design team over the last couple of months towards identifying a set
>> protocol changes to support this important use case. We need your help
>> deciding between three different options:
>>
>> - Proposal #0: Don't support heavy hitters in DAP (punt to a future
>> protocol spec)
>> - Proposal #1: Support heavy hitters with minimal changes to DAP
>> - Proposal #2: Support heavy hitters, but amend the collection
>> sub-protocol to minimize the amount of information revealed to the Collector
>>
>> Each proposal is detailed in the following google doc:
>>
>> https://docs.google.com/document/d/1ZjXz-1kGsTDf2Vn2u-fwYqR8BSc3tOYlELVHAYvAfjk/edit?usp=sharing
>>
>> It would be helpful if folks could spend some time ahead of the interim
>> (22 April, two weeks from now) digesting these options, providing feedback,
>> and figuring out what information you need, if any, to form an opinion. My
>> hope is that we'll be prepared to make a decision during the interim on the
>> questions enumerated in Section 6.
>>
>> Relatedly: If we decide to support heavy hitters, then we'll also need to
>> decide how to deal with a class of attacks against DAP/Poplar1 articulated
>> by Simon Friedberger and Phillipp Schoppmann. We call these "steering
>> attacks", as they exploit the fact that the attacker in our threat model
>> has partial control of the protocol execution that is not considered the
>> original Poplar paper (https://ia.cr/2021/017). There are a few
>> mitigations in the google doc that we'd like folks to mull over.
>>
>> I'm looking forward to seeing folks online in a couple of weeks.
>>
>> Thanks,
>> Chris P.
>>
>