I-D Publication Request: draft-ietf-rmonmib-raqmon-pdu-10.txt

[Area] OPS-NM
[WG]   RMONMIB
[I-D]  draft-ietf-rmonmib-raqmon-pdu-10.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) A security review of this document would be helpful.

1.d) There is a potential overlap between the RAQMON protocol 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) The WG initially attempted to avoid creating a new
     protocol, and tried to use RTCP as an application
     transport, but this turned out to be an inappropriate
     application for RTCP.  SNMP Notifications were also
     specified as a transport, and still remains in the
     document, although it is not clear how widely deployed
     this transport will become.  The WG finally created a
     TCP based transport for RAQMON PDUs, and after significant
     debate, there is strong WG consensus that this document
     meets the needs of the data source to data collector
     communications component of the RAQMON Framework.

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 specifies two transport mappings of the Real-time
   Application Quality of Service Monitoring (RAQMON) information model
   defined in [RAQMON-FRAMEWORK] using TCP as a native transport and the
   Simple Network Management Protocol (SNMP) to carry the RAQMON
   information from a RAQMON Data Source (RDS) to a RAQMON Report
   Collector (RRC).

Working Group Summary
 
   The RMONMIB Working Group has consensus to publish this document
   as a Proposed Standard.

Protocol Quality

   The RAQMON protocol 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.

----------------

idnits 1.73

tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt:

tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(70):
  Line is too long: the offending characters are '1'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(71):
  Line is too long: the offending characters are '1'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(72):
  Line is too long: the offending characters are '3'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(73):
  Line is too long: the offending characters are '3'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(74):
  Line is too long: the offending characters are '0'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(75):
  Line is too long: the offending characters are '1'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(76):
  Line is too long: the offending characters are '1'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(77):
  Line is too long: the offending characters are '3'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(78):
  Line is too long: the offending characters are '4'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(79):
  Line is too long: the offending characters are '4'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(80):
  Line is too long: the offending characters are '5'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(81):
  Line is too long: the offending characters are '7'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(82):
  Line is too long: the offending characters are '7'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(458):
  Line is too long: the offending characters are 'TT)'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(462):
  Line is too long: the offending characters are 'nt'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(463):
  Line is too long: the offending characters are 'ceived'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(464):
  Line is too long: the offending characters are 't'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(465):
  Line is too long: the offending characters are 'eived'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(985):
  Line is too long: the offending characters are 'It'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(990):
  Line is too long: the offending characters are 'are'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(992):
  Line is too long: the offending characters are 'ulk'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(998):
  Line is too long: the offending characters are 'the'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1049):
  Line is too long: the offending characters are 'e,'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1052):
  Line is too long: the offending characters are 's'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1053):
  Line is too long: the offending characters are '5.'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1054):
  Line is too long: the offending characters are 'nd'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1064):
  Line is too long: the offending characters are 's.'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1122):
  Line is too long: the offending characters are 'n'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1148):
  Line is too long: the offending characters are '."'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1178):
  Line is too long: the offending characters are 'n'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1213):
  Line is too long: the offending characters are 'ved."'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1245):
  Line is too long: the offending characters are 's'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1353):
  Line is too long: the offending characters are 'til'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1367):
  Line is too long: the offending characters are 'l'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1422):
  Line is too long: the offending characters are 'en'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1447):
  Line is too long: the offending characters are 'l'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1449):
  Line is too long: the offending characters are '."'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1540):
  Line is too long: the offending characters are 'y'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1578):
  Line is too long: the offending characters are 'ion."'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1589):
  Line is too long: the offending characters are 'zation."'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1599):
  Line is too long: the offending characters are ' by an'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1602):
  Line is too long: the offending characters are 'd'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1603):
  Line is too long: the offending characters are 'on'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1628):
  Line is too long: the offending characters are ','
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1690):
  Line is too long: the offending characters are ' of'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1699):
  Line is too long: the offending characters are '.'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1701):
  Line is too long: the offending characters are '}'
tmp/draft-ietf-rmonmib-raqmon-pdu-10.txt(1768):
  Line is too long: the offending characters are 'nce'


  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, we certify that any applicable
    patent or other IPR claims of which we are aware have been disclosed,
    and any of which we 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 38 pages

  Miscellaneous warnings:
    None.