Skip to main content

Last Call Review of draft-west-webappsec-csp-reg-03
review-west-webappsec-csp-reg-03-secdir-lc-sparks-2015-10-22-00

Request Review of draft-west-webappsec-csp-reg
Requested revision No specific revision (document currently at 04)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2015-11-09
Requested 2015-10-15
Authors Mike West
I-D last updated 2015-10-22
Completed reviews Secdir Last Call review of -03 by Robert Sparks (diff)
Assignment Reviewer Robert Sparks
State Completed
Request Last Call review on draft-west-webappsec-csp-reg by Security Area Directorate Assigned
Reviewed revision 03 (document currently at 04)
Result Ready
Completed 2015-10-22
review-west-webappsec-csp-reg-03-secdir-lc-sparks-2015-10-22-00
I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

Summary: Ready for publication as Informational



This draft establishes a registry (specification required/expert 


review), and populates it with an initial set of values defined in and 


used by a w3c specification that is security-centric. Creating the 


registry introduces no new security concerns itself.




One thing (not particularly security related) to consider:



The BNF for directive-name, as copied into this draft, allows a 


directive name of -, or --, ---, etc.



Are you expecting an expert to disallow these, or are they ok?
Is the answer the same for the name 42?