I-D Publication Request: draft-ietf-rmonmib-raqmon-mib-08.txt
Andy Bierman <[email protected]>
| Newsgroups | gmane.ietf.rmonmib |
|---|---|
| Message-ID | <[email protected]> |
[Area] OPS-NM [WG] RMONMIB [I-D] draft-ietf-rmonmib-raqmon-mib-08.txt [Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt [Shep] Andy Bierman <[email protected]> 1.a) Yes, the WG Chair has reviewed this version of the document. 1.b) Yes it has had adequate review; no concerns about review except that it took too long. 1.c) MIB Doctor review of the RAQMON MIB modules would be helpful. 1.d) None, the RAQMON MIB does not overlap with any related work. 1.e) This document is tightly coupled to the RAQMON Framework document and there haven't been any significant issues with this MIB for some time. There is strong WG consensus that this MIB meets its intended requirements. 1.f) No appeals have been threatened. 1.g) Yes, but there are some minor nits that will be fixed before RFC publication. (See ID-nit log below). 1.h) Yes, references are split. Yes, there are references to unpublished documents, (the other RAQMON drafts), but they are also ready for publication. 1.j) I-D Submission Summary Technical Summary This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Remote Monitoring MIB - RFC 2819. In particular, it describes managed objects used for real-time application Quality of Service (QoS) monitoring. Working Group Summary The RMONMIB Working Group has consensus to publish this document as a Proposed Standard. Protocol Quality This document has been reviewed by Andy Bierman, Alan Clark, and Randy Presuhn, and Steve Waldbusser. ---------------- [ID-nit log] idnits 1.73 tmp/draft-ietf-rmonmib-raqmon-mib-08.txt: tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(515): Line is too long: the offending characters are ',' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(555): Line is too long: the offending characters are 'ss' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(557): Line is too long: the offending characters are 't.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(572): Line is too long: the offending characters are 'pe' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(576): Line is too long: the offending characters are 'y' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(586): Line is too long: the offending characters are '.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(632): Line is too long: the offending characters are '."' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(794): Line is too long: the offending characters are 'n' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(795): Line is too long: the offending characters are 's' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1100): Line is too long: the offending characters are 'n.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1113): Line is too long: the offending characters are 'n.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1331): Line is too long: the offending characters are 're' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1345): Line is too long: the offending characters are 'ved.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1381): Line is too long: the offending characters are '.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1406): Line is too long: the offending characters are '.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1625): Line is too long: the offending characters are 'is' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1626): Line is too long: the offending characters are '.5.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1627): Line is too long: the offending characters are 'and' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1629): Line is too long: the offending characters are 'can' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1638): Line is too long: the offending characters are 't' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1639): Line is too long: the offending characters are 'like' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1640): Line is too long: the offending characters are 'by the' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1766): Line has weird spacing: '...ialized befor...' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1834): Line is too long: the offending characters are 'etween' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(1835): Line is too long: the offending characters are 'nated."' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2001): Line is too long: the offending characters are ' the' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2002): Line is too long: the offending characters are '.' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2022): Line is too long: the offending characters are 't' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2024): Line is too long: the offending characters are 'es' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2062): Line is too long: the offending characters are 'of' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2063): Line is too long: the offending characters are 'as' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2079): Line is too long: the offending characters are 'g' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2127): Line is too long: the offending characters are ',' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2128): Line is too long: the offending characters are 'n' tmp/draft-ietf-rmonmib-raqmon-mib-08.txt(2130): Line is too long: the offending characters are ',' Checking nits according to http://www.ietf.org/ID-Checklist.html: Checking conformance with RFC 3978/3979 boilerplate... * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? (Expected a match on the following text: "By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79." ... but found this: "By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668.") (The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted.) Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt: - It seems as if not all pages are separated by form feeds - found 0 form feeds but 40 pages Miscellaneous warnings: None.