Skip to main content

Last Call Review of draft-krishnan-nomcom-tools-
review-krishnan-nomcom-tools-secdir-lc-hallam-baker-2012-06-28-00

Request Review of draft-krishnan-nomcom-tools
Requested revision No specific revision (document currently at 02)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2012-07-11
Requested 2012-06-19
Authors Suresh Krishnan , Joel M. Halpern
I-D last updated 2012-06-28
Completed reviews Secdir Last Call review of -?? by Phillip Hallam-Baker
Assignment Reviewer Phillip Hallam-Baker
State Completed
Request Last Call review on draft-krishnan-nomcom-tools by Security Area Directorate Assigned
Result Ready
Completed 2012-06-28
review-krishnan-nomcom-tools-secdir-lc-hallam-baker-2012-06-28-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.


Surprisingly for a non protocol draft, this one actually is almost
completely security requirements. Unfortunately I find it rather hard
to tell if the security architecture meets the security goals because
they are not separated from each other.

I think the document should have a section stating the security goals
or reference another document that states them. Presumably these are
all derived from the Nomcom RFC.


The document specifies creation of a public key but not the algorithm
or strength. Given that this is an RFP, I think it would be
appropriate to completely and uniquely specify the cipher suite to be
supported.



-- 
Website: 

http://hallambaker.com/