I-D Publication Request: draft-ietf-rmonmib-raqmon-framework-11.txt

[Area] OPS-NM
[WG]   RMONMIB
[I-D]  draft-ietf-rmonmib-raqmon-framework-11.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 WG review; no concerns about review
     except that it took too long.

1.c) A security area review would be helpful.

1.d) There is a potential overlap between the RAQMON work and the
     IPFIX and/or RTCP-XR work, but there are enough differences
     in applicability and complexity that this should not be
     a significant issue.

1.e) Most WG members (other than the co-authors) have not shown
     much interest in the RAQMON work in the last year;
     this is probably due to the slow process of gaining WG
     consensus on various details such as metrics included in
     base RAQMON report.  The original attempts to use RTCP
     as a transport also significantly slowed down this work.
     There is probably significant implementation interest
     by at least 3 to 5 vendors.

1.f) No appeals have been threatened.

1.g) There are some minor ID-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

   There is a need to monitor end devices such as IP phones, pagers,
   Instant Messaging clients, mobile phones, and various other hand-held
   computing devices.  This memo extends the remote network monitoring
   (RMON) family of specifications to allow real-time quality of service
   (QoS) monitoring of various applications that run on these devices,
   and allows this information to be integrated with the RMON family
   using the Simple Network Management Protocol (SNMP).  This memo
   defines the framework, architecture, relevant metrics, and transport
   requirements for real-time quality of service monitoring of
   applications.

Working Group Summary
 
   The RMONMIB Working Group has consensus to publish this document
   as a Proposed Standard.  The WG had some difficulty in reaching
   consensus on the details of the base metrics included in RAQMON
   reports.

Protocol Quality

   RAQMON is based on a a proprietary version of technology
   implemented and deployed in products by Avaya, Inc.
   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-framework-11.txt:

tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(69):
  Line is too long: the offending characters are '1'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(70):
  Line is too long: the offending characters are '1'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(71):
  Line is too long: the offending characters are '3'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(72):
  Line is too long: the offending characters are '5'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(73):
  Line is too long: the offending characters are '2'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(74):
  Line is too long: the offending characters are '4'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(75):
  Line is too long: the offending characters are '4'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(76):
  Line is too long: the offending characters are '6'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(77):
  Line is too long: the offending characters are '7'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(78):
  Line is too long: the offending characters are '7'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(79):
  Line is too long: the offending characters are '8'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(80):
  Line is too long: the offending characters are '0'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(81):
  Line is too long: the offending characters are '0'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(82):
  Line is too long: the offending characters are '2'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(83):
  Line is too long: the offending characters are '2'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(84):
  Line is too long: the offending characters are '3'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(322):
  Line is too long: the offending characters are '-----+'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(323):
  Line is too long: the offending characters are 'ement|'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(324):
  Line is too long: the offending characters are 'on   |'
tmp/draft-ietf-rmonmib-raqmon-framework-11.txt(325):
  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 seems to lack an RFC 3978 Section 5.4 Copyright Line
    -- however, there's a paragraph with a matching beginning. Boilerplate
    error?

  (Expected a match on the following text:
    "Copyright (C) The Internet Society (2005)."
 
   ... but found this:
    "Copyright (C) The Internet Society (2004).  This document is subject
    to the rights, licenses and restrictions contained in BCP 78, and
    except as set forth therein, the authors retain all their rights.")


  * The document seems to lack an RFC 3978 Section 5.4 Reference to BCP
    78.

  (Expected a match on the following text:
    "This document is subject to the rights, licenses and restrictions
    contained in BCP 78, and except as set forth therein, the authors
    retain all their rights.")

    (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 34 pages

  Miscellaneous warnings:
    None.