Last Call Review of draft-murdock-nato-nid-02
review-murdock-nato-nid-02-secdir-lc-laurie-2014-10-30-00
| Request | Review of | draft-murdock-nato-nid |
|---|---|---|
| Requested revision | No specific revision (document currently at 03) | |
| Type | IETF Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2014-11-19 | |
| Requested | 2014-10-23 | |
| Authors | Aidan Murdock | |
| I-D last updated | 2015-10-14 (Latest revision 2015-01-05) | |
| Completed reviews |
Genart IETF Last Call review of -02
by Dan Romascanu
(diff)
Secdir IETF Last Call review of -02 by Ben Laurie (diff) Opsdir IETF Last Call review of -02 by Tina Tsou (Ting ZOU) (diff) |
|
| Assignment | Reviewer | Ben Laurie |
| State | Completed | |
| Request | IETF Last Call review on draft-murdock-nato-nid by Security Area Directorate Assigned | |
| Reviewed revision | 02 (document currently at 03) | |
| Result | Ready | |
| Completed | 2014-10-30 |
review-murdock-nato-nid-02-secdir-lc-laurie-2014-10-30-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. The I-D says: "This document introduces no additional security considerations beyond those associated with the use and resolution of URNs in general." For a change, I agree. It goes on to say: "Distribution of NATO information in any form is subject to its security policies. Nonetheless, this specification is for public use and not subject to any NATO security policies." Which seems to involve some magical thinking (how do those security policies magically follow the information?), but this is not a matter I think we should concern ourselves with.