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
Move the Individualization section out of the Privacy section #301
Milestone
Comments
I agree, the Implementation Requirements section is a better fit. This could follow the model of "Support Multiple Keys" e.g. "Implementations must support Key Systems which send the individualization-request message type." |
Makes sense. |
This was referenced Aug 15, 2016
ddorwin
added a commit
to ddorwin/encrypted-media
that referenced
this issue
Aug 16, 2016
PR #306. |
ddorwin
added a commit
to ddorwin/encrypted-media
that referenced
this issue
Aug 30, 2016
…anent Identifiers Also reference the concerns and mitigations related to individualization, which was extracted from this section for issue w3c#301.
ddorwin
added a commit
that referenced
this issue
Sep 6, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Individualization is currently a subset of the Privacy User Tracking section, but it is more than just a privacy topic. There is a TODO in the source related to this.
There isn't an obvious place for it, but Implementation Requirements (after the Identifiers subsection) is probably better. We can reference the requirements in that section from the User Tracking section.
The text was updated successfully, but these errors were encountered: