Re: [attribution] Feedback on Attribution Level 1 draft

On Wed, May 27, 2026 at 10:37 AM Tim Geoghegan <timgeog@gmail.com> wrote:
> In DAP, it's assumed that the task parameters have been distributed to all protocol participants before reports start being aggregated, and the leader and helper DAP URLs are among those parameters. Reports get uploaded to a path that includes the task ID, which the leader would use to figure out which helper is in play. Of course, now we might ask how the task gets provisioned into the DAP aggregators. AL1 uses the task ID derivation from taskprov (https://datatracker.ietf.org/doc/draft-ietf-ppm-dap-taskprov/), but not the actual provisioning mechanism, so it follows that someone is responsible for provisioning the task into aggregators before `measureConversion` gets called by a given site

Yep, that's all right.  So I guess the leader needs to have a way to
recover helper ID when presented with the task ID.

> Actually, now that I'm looking at "7.1.3. Report Encryption For DAP" again, I notice that the taskConfig structure described there has an empty task_info. What's the lifetime of the resulting DAP task?

task_info isn't used in this arrangement.  (We might use it; I
mentioned https://github.com/w3c/attribution/issues/363).

The lifetime is unbounded.  We're deliberately not using the task
lifetime (task_interval) extension, because we don't know how sites
want to aggregate and don't have a need to constrain that.  (Any
lifetime would ultimately force sites to split reports between one
task and another at the end/start of that lifetime.)

Received on Wednesday, 27 May 2026 00:44:25 UTC