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

[Area] OPS-NM
[WG]   RMONMIB
[I-D]  draft-ietf-rmonmib-raqmon-pdu-12.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 the review.

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.  RAQMON is a complete, distributed
      SNMP-based monitoring system, integrated with the RMON
      family of MIBs.  As such, it is intended to be applicable
      to many different types of protocols.  If a specialized
      protocol for VoIP monitoring is desired, then RTCP-XR
      should probably be used instead.  If SNMP and/or RMON
      integration are not desired, then IPFIX would be a
      suitable choice.

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 is one minor nit 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.85

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


   Checking nits according to http://www.ietf.org/ID-Checklist.html:

     Checking conformance with RFC 3978/3979 boilerplate...

     the boilerplate looks good.

     No nits found.

   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.

     No nits found.