Last Call Review of draft-ietf-sacm-requirements-15
review-ietf-sacm-requirements-15-secdir-lc-leiba-2017-05-30-00

Request Review of draft-ietf-sacm-requirements
Requested rev. no specific revision (document currently at 18)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2017-06-05
Requested 2017-05-22
Draft last updated 2017-05-30
Completed reviews Genart Last Call review of -15 by Francis Dupont (diff)
Secdir Last Call review of -15 by Barry Leiba (diff)
Opsdir Last Call review of -16 by Ron Bonica (diff)
Assignment Reviewer Barry Leiba
State Completed
Review review-ietf-sacm-requirements-15-secdir-lc-leiba-2017-05-30
Reviewed rev. 15 (document currently at 18)
Review result Has Nits
Review completed: 2017-05-30

Review
review-ietf-sacm-requirements-15-secdir-lc-leiba-2017-05-30

While I'm calling this document "ready", I really don't see why it should be published in the RFC series at all.  It's well written, and it seems to be important material for the working group to use as it develops the SACM  architecture, data model and transport protocols, but does not seem to be of lasting interest after those are done.  I'd rather see it in the working group wiki, and used that way.

That said, I know the working group wants it published and that my comment here is likely not to go far, so I'll say that if it's to be published as an RFC, it's ready.  The one nit I note is that in the XML "title" element you appear to have abbrev="Abbreviated Title", rather than the more likely abbrev="SACM Requirements".