Skip to main content

Last Call Review of draft-ietf-opsawg-coman-probstate-reqs-03
review-ietf-opsawg-coman-probstate-reqs-03-opsdir-lc-chittimaneni-2015-02-10-00

Request Review of draft-ietf-opsawg-coman-probstate-reqs
Requested revision No specific revision (document currently at 05)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2015-02-17
Requested 2015-01-02
Authors Mehmet Ersue , Dan Romascanu , Jürgen Schönwälder , Ulrich Herberg
I-D last updated 2015-02-10
Completed reviews Genart Last Call review of -03 by Joel M. Halpern (diff)
Secdir Last Call review of -03 by Alexey Melnikov (diff)
Opsdir Last Call review of -03 by Kiran K. Chittimaneni (diff)
Assignment Reviewer Kiran K. Chittimaneni
State Completed
Request Last Call review on draft-ietf-opsawg-coman-probstate-reqs by Ops Directorate Assigned
Reviewed revision 03 (document currently at 05)
Result Ready
Completed 2015-02-10
review-ietf-opsawg-coman-probstate-reqs-03-opsdir-lc-chittimaneni-2015-02-10-00
Hi,

I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written with the intent of improving the
operational aspects of the IETF drafts. Comments that are not
addressed in last call may be included in AD reviews during the IESG
review.  Document editors and WG chairs should treat these comments
just like any other last call comments.

Summary: This document is ready.

This document provides a problem statement on the issue of the
management of networked constrained devices. It also describes various
deployment and management topology options along with potential
requirements for the management of networks where constrained devices
are involved.

I just have one comment that pertains to the flow of the document.
It's just a personal preference so not a blocker by any means -- I'd
have liked it if the document followed the flow as set by the Abstract
section, i.e. Problem statement (Section 2), followed by deployment
and management topology options (Section 1.4 and 1.5), followed by
potential requirements (Section 3). I got a bit lost initially as I
started reading the doc and waited to read the problem statement.

Regards,
KK