Re: [nel] privacy+security spec feedback

Based on feedback from our perf call today, landed updates to address the
above issues (plus a few other nitpicks):
https://github.com/w3c/network-error-logging/compare/gh-pages@%7B2015-03-18%7D...gh-pages@%7B2015-03-25%7D

If you see any issues with above language and/or related issues, let me
know!
ig

P.S. On a related note, Blink intent-to-implement:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/4VNY6Hf_ZB8/QsaEOUvP6wIJ


On Fri, Mar 20, 2015 at 11:02 AM, Ilya Grigorik <igrigorik@google.com>
wrote:

> Received lots of great spec feedback from Chrome's security/privacy review
> this week, plus feedback from Marcos & Patrick @ Mozilla (thanks guys!).
> Corresponding bugs:
>
> -----
>
> (a) Clarify report delivery to be restricted to https scheme
> https://github.com/w3c/network-error-logging/issues/46
>
> (b) "MUST log error" -> "SHOULD log error"
>
> https://github.com/w3c/network-error-logging/commit/35fe1c564d180f1fd32d32e64223af8d3cb471a5
>
> (c) Restrict report-uri's to absolute URIs
> https://github.com/w3c/network-error-logging/issues/44
>
> (d) Referer reporting should be subject to Referer policy
> https://github.com/w3c/network-error-logging/issues/43
>
> (e) NEL registration should be based on origin & restricted to HTTPS
> https://github.com/w3c/network-error-logging/issues/42
>
> (f) Provide privacy section
> https://github.com/w3c/network-error-logging/issues/45
>
> -----
>
> If you have any thoughts or comments on any of the above, please ping the
> appropriate GH threads! I'll try to have the pulls to address all of the
> above in time for our conf call next week.
>
> ig
>