Intent to Ship: Attribution Reporting API feature (aggregation coordinator selection)

[Nan Lin]

Contact emails

lin...@chromium.org, john...@chromium.org

Explainer

Attribution Reporting with event-level reports

Attribution Reporting API with Aggregatable Reports

Aggregation Service for the Attribution Reporting API

Specification

https://wicg.github.io/attribution-reporting-api/

Blink component

Internals > AttributionReporting

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  

• **Note**: This change will also affect Private Aggregation API’s aggregatable reports by adding a new top-level field aggregation_coordinator_origin.

Explainer changes

• Add aggregation coordinator identifier to support multiple cloud providers

• Use aggregation coordinator origin instead of identifier

Spec changes

• Add aggregation coordinator identifier to aggregatable report

• Use aggregation coordinator origin instead of identifier

• Add aggregation_coordinator_origin to PAA serialized report

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.

              

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?

Yes

Estimated milestones

Chrome 119

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5197591256236032

Links to previous Intent discussions

Previous I2S: 

Intent to Ship: Attribution Reporting API

Intent to Ship: Attribution Reporting features M117

Intent to Ship: Attribution Reporting features M118

[Chris Harrelson]

Please fill out the 5 other review categories (security, privacy, etc) in chromestatus. Those will need to be started before the API owners can review.

--
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+...@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.

[Nan Lin]

Hi Chris,

I don't see the other review categories (security, privacy, etc) in the Prepare to Ship stage in chromestatus. 

How shall I edit and request review for those? Thanks.

Best,

Nan

[Nan Lin]

Thanks Chris.

I kicked off those reviews in chromestatus, and will ping this thread when those reviews are complete.

Thanks,

Nan

On Wed, Oct 11, 2023 at 10:53 AM Chris Harrelson <chri...@chromium.org> wrote:

[Chris Harrelson]

Great thank you!

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgP%3DzjLF2Qmp4k64LUiNnpS1GT7w5VjEYD44fXsbrUS7LLg%40mail.gmail.com.

[Mike Taylor]

Hi Nan, a few questions inline:

On 10/6/23 8:45 AM, Nan Lin wrote:

Contact emails

lin...@chromium.org, john...@chromium.org

Explainer

Attribution Reporting with event-level reports

Attribution Reporting API with Aggregatable Reports

Aggregation Service for the Attribution Reporting API

Specification

https://wicg.github.io/attribution-reporting-api/

Blink component

Internals > AttributionReporting

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  

• **Note**: This change will also affect 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

• Use aggregation coordinator origin instead of identifier

Spec changes

• Add aggregation coordinator identifier to aggregatable report

• Use aggregation coordinator origin instead of identifier

• Add aggregation_coordinator_origin to PAA serialized report

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?

Yes

Estimated milestones

Chrome 119

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5197591256236032

Links to previous Intent discussions

Previous I2S: 

Intent to Ship: Attribution Reporting API

Intent to Ship: Attribution Reporting features M117

Intent to Ship: Attribution Reporting features M118

[Nan Lin]

Thanks Mike, please see the inline comment.

This is about the transition period for releasing multiple cloud providers support. M119+ is going to fetch public keys from the new endpoint, whereas older versions still fetch from the old endpoint.

Therefore to ensure not breaking older versions, the public keys will be served on both endpoints for some time after M119 release.  

[Nan Lin]

A few more inline comments, thanks!

On Mon, Oct 16, 2023 at 10:41 AM Mike Taylor <mike...@chromium.org> wrote:

Hi Nan, a few questions inline:

On 10/6/23 8:45 AM, Nan Lin wrote:

Contact emails

lin...@chromium.org, john...@chromium.org

Explainer

Attribution Reporting with event-level reports

Attribution Reporting API with Aggregatable Reports

Aggregation Service for the Attribution Reporting API

Specification

https://wicg.github.io/attribution-reporting-api/

Blink component

Internals > AttributionReporting

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  

• **Note**: This change will also affect 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.

The TODO is actually related to the proposed change. We have a pending PR to expose the allowlist of the aggregation coordinator origins that will be used to verify the aggregation coordinator origin specified in the API surface. Any origins not included in the allowlist will be rejected. 

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?

This is not resolved yet and the proposed spec change is here. The aggregation coordinator selection is not supported in Private Aggregation API yet, which is being spec'ed and implemented,

but the aggregatable reports created by the API will include the aggregation_coordinator_origin field with the default value.

[Mike Taylor]

On 10/16/23 7:57 AM, Nan Lin wrote:

A few more inline comments, thanks!

On Mon, Oct 16, 2023 at 10:41 AM Mike Taylor <mike...@chromium.org> wrote:

Hi Nan, a few questions inline:

On 10/6/23 8:45 AM, Nan Lin wrote:

Contact emails

lin...@chromium.org, john...@chromium.org

Explainer

Attribution Reporting with event-level reports

Attribution Reporting API with Aggregatable Reports

Aggregation Service for the Attribution Reporting API

Specification

https://wicg.github.io/attribution-reporting-api/

Blink component

Internals > AttributionReporting

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  

• **Note**: This change will also affect 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.

The TODO is actually related to the proposed change. We have a pending PR to expose the allowlist of the aggregation coordinator origins that will be used to verify the aggregation coordinator origin specified in the API surface. Any origins not included in the allowlist will be rejected.

Thanks for the pointer to the updated explainer (PR...). I see that the PR is approved - landing it ASAP may make reviews easier for others.

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?

This is not resolved yet and the proposed spec change is here. The aggregation coordinator selection is not supported in Private Aggregation API yet, which is being spec'ed and implemented,

but the aggregatable reports created by the API will include the aggregation_coordinator_origin field with the default value.

I see - thanks.

[Mike Taylor]

LGTM1

On 10/16/23 7:48 AM, Nan Lin wrote:

Thanks Mike, please see the inline comment.

On Mon, Oct 16, 2023 at 10:41 AM Mike Taylor <mike...@chromium.org> wrote:

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?

This is about the transition period for releasing multiple cloud providers support. M119+ is going to fetch public keys from the new endpoint, whereas older versions still fetch from the old endpoint.

Therefore to ensure not breaking older versions, the public keys will be served on both endpoints for some time after M119 release. 

OK - got it. At some future point you'll send an Intent to Deprecate & Remove sending public keys from the old endpoint. :)

[Yoav Weiss]

LGTM2

--

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+...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4616eb26-41c2-4186-b93a-9a8934097116%40chromium.org.

[Chris Harrelson]

LGTM3 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfU4-w7D%2Bf4RDMv-WiJ7UBFKKysecyWv0Ukr0%2BZuwwd%3D_g%40mail.gmail.com.