Editiorial: Move Priv/Sec into normative parts of spec - #245
Merged
Conversation
This was referenced Jul 1, 2022
ewilligers
approved these changes
Jul 1, 2022
This was referenced Aug 10, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Closes #187
Closes #186
Closes #64
As requested by @melanierichards on behalf of PING, I've moved all the security stuff into the appropriate parts of the spec and made them normative.
I left the specific privacy considerations in place, but also made them normative. The consideration that the API doesn't leak the share targets is a statement of fact (i.e., it would be redundant to state it normatively because that's the design of the API already).
Preview | Diff