Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Iterate on aggregator selection #39

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Iterate on aggregator selection #39

wants to merge 1 commit into from

Conversation

martinthomson
Copy link
Member

Use of setlike seems to be the right general approach for this, even if the spelling is a bit more verbose than is ideal.

I've filled in more of the details of the protocol and improved some of the linking and references.

With apologies to @bmcase, who will be affected in #29.

Use of `setlike` seems to be the right general approach for this,
even if the spelling is a bit more verbose than is ideal.

I've filled in more of the details of the protocol and improved some of
the linking and references.
Comment on lines +450 to +458
The <dfn enum>PrivateAttributionProtocol</dfn> describes the submission protocol
used by different [=aggregation services=]. This document defines two protocols:

<dl dfn-for=PrivateAttributionProtocol dfn-type=enum-value>
<dt><dfn>dap-11</dfn></dt>
<dd>A DAP-based protocol [[DAP]] that uses [=MPC=]; see [[#s-mpc]].</dd>
<dt><dfn>tee-00</dfn></dt>
<dd>A protocol for submission to a [=TEE=]; see [[#s-tee]].</dd>
</dl>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe dap-11-histogram, with the possibility that we might add dap-11-sketch in the future? It seems like the report format is an additional variable beyond just the aggregation protocol. (Also see #10 (comment))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants