Last Call Review of draft-ietf-clue-data-model-schema-13
review-ietf-clue-data-model-schema-13-secdir-lc-salz-2016-05-26-00
| Request | Review of | draft-ietf-clue-data-model-schema |
|---|---|---|
| Requested rev. | no specific revision (document currently at 17) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2016-05-23 | |
| Requested | 2016-05-12 | |
| Authors | Roberta Presta, Simon Romano | |
| Draft last updated | 2016-05-26 | |
| Completed reviews |
Genart Last Call review of -13 by Francis Dupont
(diff)
Genart Last Call review of -14 by Francis Dupont (diff) Secdir Last Call review of -13 by Rich Salz (diff) Opsdir Last Call review of -13 by Stefan Winter (diff) |
|
| Assignment | Reviewer | Rich Salz |
| State | Completed | |
| Review | review-ietf-clue-data-model-schema-13-secdir-lc-salz-2016-05-26 | |
| Reviewed rev. | 13 (document currently at 17) | |
| Review result | Has Nits | |
| Review completed: | 2016-05-26 |
Review
review-ietf-clue-data-model-schema-13-secdir-lc-salz-2016-05-26
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: this document is ready, perhaps with nits. You might consider reducing the security considerations part, just to increase emphasis on the fact that while the data described by this schema is potentially very privacy-impacting, it is the *protocol(s)* that need to address those issues. Perhaps adding an intro sentence like that to the Sec 15 would be useful. Thanks for the trip down my personal memory line. Haven't deal with XML Schema since WS-star days :) -- Senior Architect, Akamai Technologies IM: richsalz at jabber.at Twitter: RichSalz