[meetings] Review baseline requirements for Private Measurement from participants (#91)

AramZS has just created a new issue for https://github.com/patcg/meetings:

== Review baseline requirements for Private Measurement from participants  ==
## Agenda+: What can we all agree upon in regards to private measurement? 

In advance of our upcoming meetings, we'd like to understand the baselines for particular design dimensions that browser vendors and participants would find acceptable, these issues are intended to describe particular dimensions [building off the document editors' work](https://github.com/patcg/docs-and-reports/blob/main/design-dimensions/README.md) and collect feedback from organizational participants to determine if, in a private measurement specification, they **could** accept this dimension. Answering no would mean you find such a feature totally unacceptable. Please also note if you consider such a feature to be *required*.

Optionally, but if possible, it would also be useful to know if they would prefer to accept this dimension.

Please respond in-thread, with yes or no answers to these questions. Especially if the answer to the first question is no.

This is needed to facilitate a smooth meeting in the upcoming month. 

1. An API using a trusted server is sufficient to ensure privacy of the output
2. The API requires requires in-browser as the primary site of operations to compute the output
3. Differential privacy used as a technique to assure privacy 
4. Information theoretic (e.g. entropy) used as a technique to assure privacy 
5. k-anonymity used as a technique to assure privacy
6. Data join / attribution occurs on-device 
7. Data join / attribution occurs off-device (on a trusted server)
8. Budgeting of data applied on a trusted server
9. Budgeting of data applied on the device 
10. Attribution across multiple channels / ad-tech
11. Scope of Privacy Budget includes time epoch 
12. Scope of Privacy Budget includes site domain 
13. Scope of Privacy Budget includes campaign
14. Scope of Privacy Budget is limited by delegation to another provider
15. Attribution can be done across devices
16. Attribution can be done across applications on the same device 
17. Can TEE be used as a private computation configuration?
18. Can MPC be used as a private computation configuration?
19. Can server-based data joining be handled by an MPC process? (If you require a specific number of parties, let us know) 
20. Can multiple third parties measure the same event with no restrictions? 
21. Can multiple third parties measure the same event with restrictions?
22. Can third parties invoke the measurement API? 
23. Can measure clicks 
24. Can measure views
25. Can measure avails 
26. Can measure interaction events that do not 'convert' (send the user to another domain). This could include general interactions (mouse over, non-converting click, scroll event) or specific defined interactions like 'started a form fill' or 'played the in-ad game'.
27. A time delay is enforced before the report is emitted 
28. Some level of preregistration to participate with a browser vendor. 

If there are particular use cases you wish to support, [you may want to check the document to understand their requirements](https://github.com/patcg/docs-and-reports/blob/main/design-dimensions/README.md#key-use-cases-that-differ).

Please view or discuss this issue at https://github.com/patcg/meetings/issues/91 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 18 January 2023 20:10:12 UTC