-
Notifications
You must be signed in to change notification settings - Fork 15
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
Comments
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 |
Closing this on the assumption that you'll merge #43 |
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. |
@sandandsnow, for your attention |
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.
The text was updated successfully, but these errors were encountered: