I see - thanks for the info Paul. It seems like an unintentional mixup.
When I approved the previous extension I wrote: "I would like to see
draft specifications and progress on making this testable via WPTs"
Russ thanks for linking to
https://pr-preview.s3.amazonaws.com/brusshamilton/turtledove/pull/1200.html
- based on this draft PR
<https://github.com/WICG/turtledove/pull/1200/files>. You wrote that it
describes _some_ of the changes, can you speak to what is missing (that
you will presumably spec ahead of an I2S)?
And thanks for beginning to land WPTs
<https://chromium-review.googlesource.com/c/chromium/src/+/5622101>.
On 6/28/24 1:59 PM, Paul Jensen wrote:
Mike,
It looks like we did continue the OT during M122-124 before sending
the first I2EE, despite initially only asking for approval for
M119-121. I wonder if someone went off of the current OT policy of
"An initial origin trial or experiment for a feature may only run for
6 milestones"
<https://www.chromium.org/blink/launching-features/#widen-review:~:text=An%20initial%20origin%20trial%20or%20experiment%20for%20a%20feature%20may%20only%20run%20for%206%20milestones>
without knowing my initial ask was for just 3 milestones. I apologize
for that and am going to seek updating internal processes to add a
check to prevent this oversight from happening again, even if the
initial I2EE is "fairly mechanical" as you said originally.
On Wednesday, June 26, 2024 at 1:53:56 PM UTC-4 Mike Taylor wrote:
Hi Russ,
I'm trying to refresh my memory on the history of this experiment.
Experiment first approved on 10/19/23 for M119 to M121,
https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/BzI3_qoCAwAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/BzI3_qoCAwAJ>
Request on 4/4/24 to renew from M124 to M127,
https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/xaJHFJ_uAAAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/xaJHFJ_uAAAJ>
Approved 4/12/24 (“for another 3 milestones”),
https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/Pm842qm_AAAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/Pm842qm_AAAJ>
Requesting M127 to M130 on 6/20/24,
https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/RigQFZilAgAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/RigQFZilAgAJ>
Question: what happened between M122 and M124? Was the experiment
not running?
On 6/20/24 2:52 PM, 'Russ Hamilton' via blink-dev wrote:
(Now *To* blink-dev instead of just CC)
Contact emails
pauljen...@chromium.org, behamil...@google.com
Explainer
Chrome:
https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md
<https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md>
Services:
https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md
<https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md>
Note that this explainer has a helpful onboarding section
<https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md#onboarding-and-alpha-testing-guide>for
setting up the services.
Specification
A work-in-progress pull request
<https://pr-preview.s3.amazonaws.com/brusshamilton/turtledove/pull/1200.html>on
the Protected Audience spec
<https://wicg.github.io/turtledove/>describes some of the changes
to the W3C spec. We are reaching out to the IETF ART Area
Directors for assistance beginning the standardization process
for some of the server-side aspects of this API.
Summary
We propose extending the Bidding and Auction Services origin
trial currently operating on 1% stable.
Recent changes:
*
Prompted by developer concerns about scalability, we have
recently added support in M127 for limiting the size of the
Bidding and Auction request payload
*
We also added controls to enable sellers to select which
buyers are included in the payload when it doesn’t affect the
outwardly visible size of the encrypted data.
*
Additionally the Bidding and Auction server has recently
added support for features such as buyerReportingId and bid
currency.
We have decided to extend the experiment to give developers time
to experiment with the new features. We would like to request
extending the end milestone from M127 to M130.
Blink component
Blink>InterestGroups
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInterestGroups>
TAG review
For Protected Audience:
https://github.com/w3ctag/design-reviews/issues/723
<https://github.com/w3ctag/design-reviews/issues/723>
TAG review status
Completed for Protected Audience, resolved unsatisfied.
Interoperability and Compatibility
Gecko & WebKit: No signal on parent proposal, Protected
Audience. Asked in the Mozilla forumhere
<https://github.com/mozilla/standards-positions/issues/770>,
and in the Webkit forum here
<https://github.com/WebKit/standards-positions/issues/158>.
Edge: Microsoft has proposed their Ad Selection API
(https://github.com/WICG/privacy-preserving-ads/
<https://github.com/WICG/privacy-preserving-ads/tree/main>)
as a similar TEE on-server auction API. That API looks
like it would have an identical Web Platform API as the
Bidding and Auction Services API. We have biweekly
meetings with Microsoft, and are open to collaborating on
specifying the API.
WPT Tests
We have started to implement some tests
<https://chromium-review.googlesource.com/c/chromium/src/+/5622101?>,
but work is still ongoing.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4649601971257344
<https://chromestatus.com/feature/4649601971257344>
Links to previous Intent discussions
Intent to prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnSdvf7RgK2wxsmC6rWc8eRoqDZOvgwVFuEx1r2nqmAJg%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnSdvf7RgK2wxsmC6rWc8eRoqDZOvgwVFuEx1r2nqmAJg%40mail.gmail.com>
Intent to Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/BwMKwPP6GQAJ>
Intent to Extend Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/xaJHFJ_uAAAJ
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/xaJHFJ_uAAAJ>
Thanks,
–Benjamin “Russ” Hamilton
--
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
<mailto:blink-dev+unsubscr...@chromium.org>.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU1Euju6f97P1kjqTfggWUBZEgEdPA43KL25ZUzHqJ_9uQ%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU1Euju6f97P1kjqTfggWUBZEgEdPA43KL25ZUzHqJ_9uQ%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/682701b9-6350-442b-9f68-e9921cfd319c%40chromium.org.
