Last Call Review of draft-ietf-opsawg-service-model-explained-03
review-ietf-opsawg-service-model-explained-03-secdir-lc-salowey-2017-09-17-00
Request | Review of | draft-ietf-opsawg-service-model-explained |
---|---|---|
Requested revision | No specific revision (document currently at 05) | |
Type | Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2017-09-20 | |
Requested | 2017-09-06 | |
Authors | Qin Wu , Will (Shucheng) LIU , Adrian Farrel | |
I-D last updated | 2017-09-17 | |
Completed reviews |
Secdir Last Call review of -03
by Joseph A. Salowey
(diff)
Genart Last Call review of -03 by Robert Sparks (diff) Rtgdir Last Call review of -03 by Dave Sinicrope (diff) Secdir Telechat review of -04 by Joseph A. Salowey (diff) |
|
Assignment | Reviewer | Joseph A. Salowey |
State | Completed | |
Request | Last Call review on draft-ietf-opsawg-service-model-explained by Security Area Directorate Assigned | |
Reviewed revision | 03 (document currently at 05) | |
Result | Ready | |
Completed | 2017-09-17 |
review-ietf-opsawg-service-model-explained-03-secdir-lc-salowey-2017-09-17-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. The summary of the review is the document is ready for publication. I think the document could be improved slightly by touching on the fact that the service models themselves may involve security parameters. You could add a sentence to the security considerations section following the last sentence: "The service model should expose security related parameters where they are available to the customer." Cheers, Joe