Last Call Review of draft-ietf-dime-overload-reqs-10
review-ietf-dime-overload-reqs-10-secdir-lc-wallace-2013-09-12-00

Request Review of draft-ietf-dime-overload-reqs
Requested revision No specific revision (document currently at 13)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2013-09-24
Requested 2013-08-08
Authors Eric McMurry , Ben Campbell
I-D last updated 2013-09-12
Completed reviews Genart Last Call review of -10 by David L. Black (diff)
Genart Telechat review of -12 by David L. Black (diff)
Secdir Last Call review of -10 by Carl Wallace (diff)
Assignment Reviewer Carl Wallace
State Completed
Request Last Call review on draft-ietf-dime-overload-reqs by Security Area Directorate Assigned
Reviewed revision 10 (document currently at 13)
Result Has nits
Completed 2013-09-12
review-ietf-dime-overload-reqs-10-secdir-lc-wallace-2013-09-12-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.

This document describes the limitations of the existing Diameter overload
mechanisms and provides requirements for new overload management
mechanisms.  The document is very well written and clear.  I had just two
comments:

1) The last sentence of Requirement 13 is a bit hard to parse.

2) Requirement 31 requires indication of overload at specified
granularities (realm, application, node).  Should overload status
mechanisms have similar granularity requirements (see requirements 10 or
24)?