Encryption for DAP #217
Merged
Encryption for DAP #217
Conversation
This file contains hidden or 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
This does a more than thorough definition of what it takes to encrypt a report for DAP/MPC. This is probably a little TOO detailed, in that the DAP draft specifies most of this. However, I found it helpful to go to this level of detail because the draft doesn't pin down certain key parameters, like the choice of field and time resolution.
apasel422
requested changes
Jul 7, 2025
apasel422
reviewed
Jul 7, 2025
apasel422
reviewed
Jul 7, 2025
csharrison
reviewed
Jul 7, 2025
Co-authored-by: Andrew Paseltiner <apaseltiner@google.com> Co-authored-by: Charlie Harrison <csharrison@chromium.org>
martinthomson
commented
Jul 10, 2025
apasel422
approved these changes
Jul 10, 2025
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.
This does a more than thorough definition of what it takes to encrypt a report for DAP/MPC. This is probably a little TOO detailed, in that the DAP draft specifies most of this. However, I found it helpful to go to this level of detail because the draft doesn't pin down certain key parameters, like the choice of field and time resolution.
This updates the DAP definition to the latest draft and references the latest DAP report extensions (updated today also).
Preview | Diff