Consensus on server-side data join #48
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
At the last face-to-face PAT-CG call, we discussed this design dimension: the location of data join (between source and trigger events). There was consensus that the group was potentially open to data join happening server-side, so long as the system was able to achieve our desired privacy and security goals.
martinthomson
approved these changes
Jun 20, 2023
| @@ -14,6 +14,10 @@ This document serves to capture the dimensions with general agreement from the C | |||
|
|
|||
| The community group has reached general agreement that the _Private Measurement Technical Specification MVP_ may include server processing dependencies, however any server architecture must achieve both a high level of security (which the editors will align with the ongoing [Threat Model](../threat-model) work) as well as ability to explain the privacy and security properties of the system to end users. | |||
|
|
|||
| ### Location of Data Join | |||
|
|
|||
| The community group has reached general agreement that data join could potentially occur off device within a some type of server side architecture. | |||
There was a problem hiding this comment.
Want to preface this with something like:
Attribution requires joining data from the site of an impression (source) and the site of a conversion (trigger).
?
AramZS
added
the
call-for-consensus
|
As discussed, these PRs have been open long enough to acquire consensus that they accurately describe our conversations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the last face-to-face PAT-CG call, we discussed this design dimension: the location of data join (between source and trigger events).
There was consensus that the group was potentially open to data join happening server-side, so long as the system was able to achieve our desired privacy and security goals.