Hi Nan, a few questions inline:
On 10/6/23 8:45 AM, Nan Lin wrote:
Contact emails
lin...@chromium.org <mailto:lin...@chromium.org>, johni...@chromium.org
Explainer
Attribution Reporting with event-level reports
<https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md>
Attribution Reporting API with Aggregatable Reports
<https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md>
Aggregation Service for the Attribution Reporting API
<https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATION_SERVICE_TEE.md>
Specification
https://wicg.github.io/attribution-reporting-api/
<https://wicg.github.io/attribution-reporting-api/>
Blink component
Internals > AttributionReporting
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EAttributionReporting>
Summary
We plan on landing one change to the Attribution Reporting API focused on:
*
Multiple cloud providers support for aggregate reporting,
supporting AWS and GCP
o
**Note**: This change will also affect Private Aggregation API
<https://github.com/patcg-individual-drafts/private-aggregation-api>’s
aggregatable reports by adding a new top-level field
aggregation_coordinator_origin.
Does this proposed change correspond to the TODO at the bottom of
https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md#data-processing-through-a-secure-aggregation-service?
I think no, but I'm not entirely sure.
In the Private Aggregation API,
https://patcg-individual-drafts.github.io/private-aggregation-api/#serializing-reports
seems to define this aggregation_coordinator_origin but there's an open
inline spec issue just after (pointing to a closed issue 78). Is that
entirely resolved, or are there still open questions that may change the
API?
Explainer changes
*
Add aggregation coordinator identifier to support multiple cloud
providers <https://github.com/WICG/attribution-reporting-api/pull/622>
*
Use aggregation coordinator origin instead of identifier
<https://github.com/WICG/attribution-reporting-api/pull/829>
Spec changes
*
Add aggregation coordinator identifier to aggregatable report
<https://github.com/WICG/attribution-reporting-api/pull/728>
*
Use aggregation coordinator origin instead of identifier
<https://github.com/WICG/attribution-reporting-api/pull/829>
*
Add aggregation_coordinator_origin to PAA serialized report
<https://github.com/patcg-individual-drafts/private-aggregation-api/pull/105>
Risks
Interoperability and Compatibility
The change is backwards compatible, and allows developers to select
the deployment option for the aggregation service. By default, the AWS
coordinator will be used (the existing behavior), and the public keys
will be served on both old and new endpoints during the transition period.
Can you say more about this transition period? Is this related to
"transitional debugging reports", or something else entirely?
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
All except Android WebView
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
Estimated milestones
Chrome 119
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5197591256236032
<https://chromestatus.com/feature/5197591256236032>
Links to previous Intent discussions
Previous I2S:
Intent to Ship: Attribution Reporting API
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2Rmj5V6FSaY>
Intent to Ship: Attribution Reporting features M117
<https://groups.google.com/a/chromium.org/g/blink-dev/c/nWF61c8xu-M/m/uMmH1ewcAQAJ>
Intent to Ship: Attribution Reporting features M118
<https://groups.google.com/a/chromium.org/g/blink-dev/c/Mh-mJiyJZFk/m/HlgzpphYBQAJ>
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgPkpNoOJk60RjTsK2u%2BbCMbM2VkDwjPzqFUEaP7oZ2egoQ%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgPkpNoOJk60RjTsK2u%2BbCMbM2VkDwjPzqFUEaP7oZ2egoQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4f9762d5-0d6a-457a-83f2-fb25cd9a9dcc%40chromium.org.
