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

make privacy mitigations normative #27

Closed
samuelweiler opened this issue Dec 3, 2020 · 4 comments · Fixed by #43
Closed

make privacy mitigations normative #27

samuelweiler opened this issue Dec 3, 2020 · 4 comments · Fixed by #43
Labels
privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.

Comments

@samuelweiler
Copy link
Member

Please either mark section 4 as normative (remove the non-normative mark) or move the mitigations from section 4 into normative parts of the document.

@anssiko
Copy link
Member

anssiko commented Aug 27, 2021

Thanks @samuelweiler. Given the RFC 2119 terms used in this section are SHOULD and MAY, current implementations should remain conformant if we'd remove the non-normative mark. PTAL #43

@samuelweiler
Copy link
Member Author

Closing this on the assumption that you'll merge #43

@anssiko
Copy link
Member

anssiko commented Aug 31, 2021

I merged #43. We'll also discuss this change at TPAC 2021 w3c/devicesensors-wg#47 thus I tagged you in the planning issue (timing TBD). Feel free to propose other privacy and security folks who you think we should talk to.

As you know, we are working on revising the security and privacy aspects of the group's specs before we request new horizontal reviews. Having a discussion on the current expectations of these reviews would be helpful. We've scheduled a full session focused on "Privacy, security and architecture" for TPAC.

@samuelweiler
Copy link
Member Author

@sandandsnow, for your attention

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants