- From: Christopher Patton via GitHub <noreply@w3.org>
- Date: Mon, 12 Jan 2026 23:51:10 +0000
- To: public-patwg@w3.org
A couple of thoughts on Slide 12: 1. Something to discuss is whether you'd be able to live with start_time and start_duration being set to some long lifetime, e.g., a few months to a year. The intent of letting tasks expire is to encourage periodic rotation of the Prio3 verification key, just as we would for any long lived secret we use in cryptography. (The VDAF verification key is used to verify each measurement before aggregating it.) 2. In draft-ietf-ppm-taskprov, the task parameters are used to derive the task ID. We might have two tasks with the same parameters that we want to have different IDs for. That's what task_info is used for in practice, but in general it's envisioned for whatever deployment specific metadata you might have. -- GitHub Notification of comment by cjpatton Please view or discuss this issue at https://github.com/w3c/patwg/issues/76#issuecomment-3741043258 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 January 2026 23:51:11 UTC