Last Call Review of draft-ietf-i2rs-pub-sub-requirements-06
review-ietf-i2rs-pub-sub-requirements-06-opsdir-lc-jiang-2016-05-03-00
Request | Review of | draft-ietf-i2rs-pub-sub-requirements |
---|---|---|
Requested revision | No specific revision (document currently at 09) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2016-05-03 | |
Requested | 2016-04-18 | |
Authors | Eric Voit , Alexander Clemm , Alberto Gonzalez Prieto | |
I-D last updated | 2016-05-03 | |
Completed reviews |
Genart Last Call review of -06
by Francis Dupont
(diff)
Secdir Telechat review of -05 by Scott G. Kelly (diff) Opsdir Last Call review of -06 by Sheng Jiang (diff) Rtgdir Early review of -03 by Julien Meuric (diff) Rtgdir Early review of -03 by Dan Frost (diff) |
|
Assignment | Reviewer | Sheng Jiang |
State | Completed Snapshot | |
Review |
review-ietf-i2rs-pub-sub-requirements-06-opsdir-lc-jiang-2016-05-03
|
|
Reviewed revision | 06 (document currently at 09) | |
Result | Has nits | |
Completed | 2016-05-03 |
review-ietf-i2rs-pub-sub-requirements-06-opsdir-lc-jiang-2016-05-03-00
Hi, OPS-DIR, Authors, 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. This Informational document presents requirements for a service that allows client applications to subscribe to updates of a YANG datastore. This document is well written. I don't see any major issues from the operations and management perspective. It is ready to be published with a couple of minor comments below: There are normative language/key works definitions and usages while it is an Informational document. I am raising this as a minor concern since I don ’ t think there is an unified “ standard ” on this. But I personally prefer not use mormative key works in an informational document There are many abbreviations have not given the full name, even in the first appearance. Typo: Last paragraph of section 2: defacto/default “ SNMP and MIBs will remain widely deployed and the defacto choice for many monitoring solutions. ” Regards, Sheng