Thanks Russ.

LGTM to extend another 3 milestones. I would like to see draft specifications and progress on making this testable via WPTs, at the very least, before any further extensions are requested.

On 4/12/24 2:52 PM, Russ Hamilton wrote:

To follow up on my previous email, I’d like to add some more details to clarify the state and progress of the Origin Trial:

In the past 6  months the server has added support for event-level reporting, multiple coordinators, currencies, multi-seller auctions, and hybrid on-device/on-server Protected Audience auctions. We've made 20+ changes to Chrome in the past 6 months to support new features for Bidding and Auction Services and address issues discovered during testing.

The discussions needed to begin the specification work represent significant progress relative to where we were before, as now we have a plan and work has started on implementation.

The TAG review for Protected Audience finished in February.

Although we haven't heard from Webkit <https://github.com/WebKit/standards-positions/issues/158>or Gecko <https://github.com/mozilla/standards-positions/issues/770>, Microsoft has proposed their Ad Selection API (https://github.com/WICG/privacy-preserving-ads/tree/main <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.

Although we don't have WPT, we have been working on integration testing with the existing implementation. Also, there is a substantial barrier to writing effective WPTs in our case due to the use of Hybrid Public Key Encryption (HPKE) in sending requests and responses. That said, we are thinking about ways to extend WPTs to make it possible to improve test coverage.


On Fri, Apr 12, 2024 at 1:24 PM Mike Taylor <miketa...@chromium.org> wrote:

    Russ and I had a conversation offline about the progress here -
    mind summarizing, Russ?

    On 4/9/24 4:12 PM, Russ Hamilton wrote:


            Specification

    We are just beginning writing the spec. We're drafting a
    WICG spec for the browser components and an IETF spec for the
    server interface.



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


    *WPT Tests*

    *
    *

    We have not started on WPT tests for this feature.



    On Mon, Apr 8, 2024 at 11:40 AM Mike Taylor
    <miketa...@chromium.org> wrote:

        Hi Russ,

        Could you summarize progress on the following, per the
        extension process:

        Draft spec (early draft is ok, but must be spec-like and
        associated with the appropriate standardization venue, or WICG)
        TAG review
        bit.ly/blink-signals <http://bit.ly/blink-signals> requests
        Outreach for feedback from the spec community
        WPT tests

        I recognize some of this is touched on in your email - but
        having it explicitly in one spot would be helpful, thanks.

        On 4/4/24 12:19 PM, 'Russ Hamilton' via blink-dev wrote:


                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

        Influenced by Origin Trial feedback, so work has just
        started.  Protected Audience auctions running on Bidding &
        Auction Services provide functionality very similar to
        existing on-device auctions so much of the existing spec
        <https://wicg.github.io/turtledove/>applies.


                Summary

        We propose extending the Bidding and Auction Services origin
        trial currently operating on 1% stable. We have decided to
        extend the experiment given developers need more time to
        onboard and to keep experimenting with new features. We
        would like to request extending the end milestone from M124
        to M127.


                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.


                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>

-- 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/CAAG-DU2FmKivx3FF%3Dn0BZge_0n10ihizanpgrZVkPaeWtzaCbA%40mail.gmail.com
        
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU2FmKivx3FF%3Dn0BZge_0n10ihizanpgrZVkPaeWtzaCbA%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/8f565156-3e70-4e79-ac3d-9049d3bd8e38%40chromium.org.

Reply via email to