[Ppm] Adding support to DAP for fixed-chunk tasks

Christopher Patton <cpatton@cloudflare.com> Wed, 03 August 2022 18:42 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 5B433C14F73B for <ppm@ietfa.amsl.com>; Wed, 3 Aug 2022 11:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 (1024-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 1iB45bQKMxbY for <ppm@ietfa.amsl.com>; Wed, 3 Aug 2022 11:42:55 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 CECFCC14F73A for <ppm@ietf.org>; Wed, 3 Aug 2022 11:42:55 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id e13so3641457edj.12 for <ppm@ietf.org>; Wed, 03 Aug 2022 11:42:55 -0700 (PDT)
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=O0ePt8fRf+RqZdbmO7jshG6L4Rmvi7ogzZlGFrMD1Ns=; b=W88dOCHfeU3F/Mfa3XMNKu4IURrVmi/RXN7TGRj6LBE4Q/OGfzDjyepNd+NbkKlmsz q8OSWvqzUywh/vnFIwXEUJVLaSw+hBNncwIffoBVZ3Uld9nmdqhztvKTEwPQ4bssAxf4 XOpAvJ3ZLwgHfKbmx/r1/WVMhx1z2WJDiEGWY=
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=O0ePt8fRf+RqZdbmO7jshG6L4Rmvi7ogzZlGFrMD1Ns=; b=StKzccFVzSEh0/IEN45U9QkSmNrquukR7OybtX19XvB0K/2rHX6GxgN072ECY1BW7d caBOLv66IoK+n4+hGdajl076jbehblH1GLhClQrLaUDQwy8/oztSp7Ge73F8EEs/D4Lf 6YUhfOFrjbETTSVYssbm9yy91rQbKXtXdyhLm/xJOYUQNl6FQaiPClqvgu+FTvc2YdJJ 8Rd2Nk0kuDHQYYucjVB6MebFmmqqeg7V49NDxqzczYruhy5lnFLjGpbndGydFq6HAVbN YhQrwr94ZNb38S6+fbOWdNd8drXVQQcL+9fTdrhLf81521C6K51ygZM1lSAclMZ2lqdH XK0Q==
X-Gm-Message-State: ACgBeo2fG5pQN+NwRwb1m+CoaOdKYnWbQ399qVZTz1fF3jG+vdVDD5pB KKLCwnvp7Cj09qp3esNhThlHPylq868xx9Jkk9oT9DBkihe/TQ==
X-Google-Smtp-Source: AA6agR4y15hmPfF2JpLod053/zgmOQ37R+MGk7P79PoYxcm9UV8X7pUsz9cow2AKTJiDAbvDIe8eFR9JC0Ki+goETJs=
X-Received: by 2002:a05:6402:27d3:b0:43e:5490:27ca with SMTP id c19-20020a05640227d300b0043e549027camr3178665ede.307.1659552173981; Wed, 03 Aug 2022 11:42:53 -0700 (PDT)
MIME-Version: 1.0
From: Christopher Patton <cpatton@cloudflare.com>
Date: Wed, 03 Aug 2022 11:42:43 -0700
Message-ID: <CAG2Zi23ekOPa9f=kPH973GXc5kjSwRmki_ndSrZbVOd6gG0aiA@mail.gmail.com>
To: ppm <ppm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d19bf805e55a9938"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppm/BM0w4TfwSLN9V92RiKq5V-rtdaY>
Subject: [Ppm] Adding support to DAP for fixed-chunk tasks
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, 03 Aug 2022 18:42:59 -0000

Hi all,

I've created a PR [1] to add support for the use case described in [2]. The
PR Is designed to fulfill the following requirements, which were discussed
in the PPM meeting at IETF 114. (Refer to the slides for the use cases
presentation [3].)

1. Enumerates all query types and defines the behavior of the Client,
Leader, Helper, and Collector for each.
2. Two query types are defined, one that supports the "time-series
telemetry" use case envisioned by the current draft. The other supports the
use case discussed in [2], which requires the collector to be able to
strictly control the batch size.
3. Punts on the "drill down by client property" use case discussed in [4].
We decided in the meeting that we have not yet fleshed out the requirements
enough to warrant changes at this time.
4. Allows both Aggregators to ensure that each report in a batch satisfies
the query.
5. Allows implementations to add new query types as needed.
6. Permits only one query type per task, which allows us to punt on the
complexity of composing different query types. The query type is configured
out-of-band, along with the rest of the task configuration.

If folks have questions or concerns about these requirements, I think it
would be best to discuss them here rather than on the PR. Otherwise, review
of the PR itself is greatly appreciated!

Best,
Chris P.

[1] https://github.com/ietf-wg-ppm/draft-ietf-ppm-dap/pull/297
[2] https://github.com/ietf-wg-ppm/draft-ietf-ppm-dap/issues/273
[3]
https://datatracker.ietf.org/meeting/114/materials/slides-114-ppm-dap-use-cases-00
[4] https://github.com/ietf-wg-ppm/draft-ietf-ppm-dap/issues/183