Last Modified: 2003-10-28
The RMON MIB Working Group is chartered to define a set of managed objects for remote monitoring of networks. These objects will be the minimum necessary to provide the ability to monitor multiple network layers of traffic in remote networks; providing fault, configuration, and performance management, and will be consistent with the SNMP framework and existing SNMP standards.
The following list of features for this RMON has been previously discussed in relation to existing RMON functionality and is included to focus these RMON activities. It is recognized that other issues may be considered and that certain of the following issues may not be part of the final specification(s):
1. Application Performance Measurement
Monitoring support for the measurement and characterization of network application protocols, striving to measure an application user's experience as closely as possible. The RMON-2 MIB (RFC 2021) contains a protocol directory that will be used to identify applications for monitoring purposes.
While it is important to measure the performance of computing and network resources, these measurements don't give an insight to the actual service delivered to end-users. This end-user experience is best measured by the response-time and availability of application transactions because users interact directly with applications. This working group will create extensions to the RMON-2 MIB that will allow Application Performance Measurements to be retrieved with SNMP, no matter which technology is used to perform the measurements.
The goal of the working group is to provide a common framework and set of MIB objects, within the current RMON framework, for the identification and characterization of application responsiveness and availability, and the reporting of test results produced by such mechanisms. Common metrics and derived metrics will be characterized and reported in a manner consistent with the IP Performance Metrics Framework (RFC 2330).
It is an explicit non-goal of the working group to select one or more mechanisms as the preferred or standard RMON application performance measurement mechanism. However, it is possible that one or more standard mechanisms will be developed in the future, after significant implementation experience has been gained by the working group.
2. Differentiated Services Statistics Collection
Monitoring support for Differentiated Services (DS) statistics collection, for the purpose of DS codepoint usage analysis and possibly other statistics related to DS deployment and performance tuning.
3. Interface TopN Reporting
It is often too slow or difficult to determine the busiest ports in devices such as high port-density switches, using existing RMON mechanisms. New monitoring support is needed for quickly determining the most congested (highest utilized) physical ports and links in an RMON-capable device with multiple interfaces.
4. TR-RMON MIB Advancement
The Token Ring RMON MIB (RFC 1513) is ready for standards track advancement. An interoperability and deployment survey has already been completed, but the MIB must be updated in SMIv2 format before it can be advanced on the standards track.
5. Transport Performance Measurement
There is a need for standardized means to collect and report selectable performance metrics and statistics derived from the monitoring of network packets and transport protocol states. The monitoring covers both passive and active traffic generation sources. Monitoring support for the these measurements can provide a drill-down capability to provide insight into the performance of the lower-level transactions which comprise the overall performance of a network application.
The goal of the working group is to provide a common framework and set of MIB objects, within the current RMON framework, for the identification and characterization of transaction-level performance, and the reporting of test results produced by such mechanisms. Common metrics and derived statistics will be characterized and reported in a manner consistent with the IP Performance Metrics Framework (RFC 2330).
6. SMON MIB Advancement
The SMON MIB (RFC 2613) is ready for standards track advancement. An interoperability and deployment survey will be completed, and submitted to the IESG. It is possible that minor enhancements and corrections to RFC 2613 will be made, based on the survey findings and working group input.
7. RMON-2 MIB Advancement
The RMON-2 MIB (RFC 2021) is ready for standards track advancement. An interoperability and deployment survey will be completed, and submitted to the IESG. It is possible that minor enhancements and corrections to RFC 2021 will be made, based on the survey findings and working group input.
8. RMON PI Reference Advancement
The RMON Protocol Identifiers Reference (RFC 2895) is ready for standards track advancement. An interoperability and deployment survey will be completed, and submitted to the IESG. It is possible that minor enhancements and corrections to RFC 2895 will be made, based on the survey findings and working group input.
9. Synthetic Sources for Performance Monitoring
Mechanisms are needed for the remote control of synthetic packet sources and destinations, for the purpose of enhancing remote performance monitoring capabilities within IP networks and services. These mechanisms must utilize the RMON protocol directory for protocol encapsulation identification. Any interactions with the RMON Framework or dependencies on specific RMON MIB objects (if any) will be specified as well.
10. RMON Framework
Documentation is needed which clarifies the remote network monitoring framework, and describes the inter-relationships and dependencies between the various RMON MIB modules. A conceptual model is needed to help administrators and developers better understand data sources, the protocol directory, and the existing RMON statistical collections. Undocumented 'RMON folklore', as well as the limitations and appropriate application of various implementation techniques will also be addressed.
11. Real-time Application QoS Monitoring MIB
There is a need to extend the RMON framework to monitor end devices such as IP Phones, pagers, Instant Message Clients, Cell Phones, and PDA devices. An end-to-end user experience of the quality of service (QoS) and performance for such an application is a combination of device performance and transport network performance. Monitoring should be performed at the application layer that reflects a specific end user experience on a particular IP end point, reflecting specific transport network performance
There is a need to extend the RMON framework to monitor end devices such as IP Phones, pagers, Instant Message Clients, Cell Phones, and PDA devices. An end-to-end user experience of the quality of service (QoS) and performance for such an application is a combination of device performance and transport network performance. Monitoring should be performed at the application layer that reflects a specific end user experience on a particular IP end point, reflecting specific transport network performance.
This working group will extend the RMON Framework to allow Real-time Application QoS information of these types of end devices to be retrieved with SNMP, independent of the technology used to perform the measurements.
The WG will define a common framework and set of MIB objects, within the current RMON framework, for the identification and characterization of application QoS parameters, and the reporting of the on-going measurement reports produced by these mechanisms. Common metrics and derived metrics will be characterized and reported in a manner consistent with the IP Performance Metrics Framework (RFC 2330).
The WG will also define a set of RAQMON Application level QoS PDUs to have common formats of reporting statistics between a RAQMON Data Source and a RAQMON Report Collector. These Common RAQMON PDUs will be transported over existing protocols, such as RTCP or SNMP.
The measurement methodology is out of the scope of the RAQMON work and will be in conformance with the IPPM WG recommendations, and also may take into account considerations from application-specific (IM and telephony) WGs as needed. This WG will consider the cases for transport of RAQMON PDUs, including how RTCP might be used and still meet security/privacy goals.
Security aspects related to RAQMON reports will be cognizant of privacy and anonymity issues while being responsive to the needs of measurement applications.
| Done | Activation of working group, call for suggested MIB modules. | |
| Done | Reach agreement on the functional scope of the charter, and finalize the document deliverables. | |
| Done | Submit initial Internet-Draft for Differentiated Services Monitoring | |
| Done | Submit initial Internet-Draft for Interface TopN Reporting | |
| Done | Submit initial Internet-Draft for TR-RMON MIB in SMIv2 Format | |
| Done | Begin Working Group Last Call for TR-RMON MIB in SMIv2 Format | |
| Done | Submit initial Internet-Draft for Application Performance Metrics | |
| Done | Begin Working Group Last Call for Differentiated Services Monitoring | |
| Done | Begin Working Group Last Call for Interface TopN Reporting | |
| Done | Submit Final Draft of Differentiated Services Monitoring to IESG for standards track action | |
| Done | Begin Working Group Last Call for Application Performance Metrics | |
| Done | Submit Final Draft of Application Performance Metrics to IESG for standards track action | |
| Done | Submit Final Draft of Interface TopN Reporting to IESG for standards track action | |
| Done | Call for MIB Modules for Synthetic Sources for Performance Monitoring | |
| Done | Call for RMON-2 Implementation reports | |
| Done | Call for RMON-PI Implementation reports | |
| Done | Submit initial Internet-Draft for Synthetic Sources for Performance Monitoring | |
| Done | Submit initial Internet-Draft for the RMON Framework | |
| Done | Submit Final Draft of TR-RMON MIB in SMIv2 Format | |
| Done | Complete RMON-PI Implementation Report | |
| Done | Begin WG Last Call for Transport Performance Measurement | |
| Done | Begin WG Last Call for Synthetic Sources for Performance Monitoring | |
| Done | Submit Final RMON-2 Implementation Report to IESG | |
| Done | Submit Final SMON Implementation Report to IESG | |
| Done | Complete RMON-2 Implementation Report | |
| Done | Submit Final RMON-PI Implementation Report to IESG | |
| Done | Complete SMON Implementation Report | |
| Done | Begin WG Last Call for RMON Framework | |
| Done | Publish initial Internet-Draft for the Extensions to RMON Framework for RAQMON | |
| Done | Publish initial Internet-Draft for the RAQMON PDU Types | |
| Done | Submit Final Draft of Transport Performance Measurement to IESG for standards track action | |
| Done | Submit Final Draft of Synthetic Sources for Performance Monitoring to IESG for standards track action | |
| Done | Publish initial Internet-Draft for the RAQMON MIB | |
| Done | Submit Final Draft of RMON Framework to IESG for standards track action | |
| Done | Begin Working Group Last Call for the Extensions to RMON Framework for RAQMON document | |
| Done | Begin Working Group Last Call for the RAQMON PDU Types document | |
| Done | Begin Working Group Last Call for the RAQMON MIB document | |
| Done | Submit initial draft for RMON Protocol Macros for IPv6 | |
| Dec 03 | Submit the RAQMON PDU Types document to the IESG for publication consideration as a Proposed Standard | |
| Dec 03 | Submit the RAQMON MIB document to the IESG for publication consideration as a Proposed Standard | |
| Dec 03 | Begin WG Last Call for RMON Protocol Macros for IPv6 | |
| Dec 03 | Submit the Extensions to RMON Framework for RAQMON document to the IESG for publication consideration as an Informational RFC | |
| Feb 04 | Submit final draft of RMON Protocol Macros for IPv6 to the IESG |
| RFC | Status | Title |
|---|---|---|
| RFC1271 | PS | Remote Network Monitoring Management Information Base |
| RFC1757 | DS | Remote Network Monitoring Management Information Base |
| RFC2021 | PS | Remote Network Monitoring Management Information Base Version 2 using SMIv2 |
| RFC2074 | PS | Remote Network Monitoring MIB Protocol Identifiers |
| RFC2613 | PS | Remote Network Monitoring MIB Extensions for Switch Networks Version 1.0 |
| RFC2819 | Standard | Remote Network Monitoring Management Information Base |
| RFC2895 | PS | Remote Network Monitoring MIB Protocol Identifier Reference |
| RFC2896 | I | Remote Network Monitoring MIB Protocol Identifier Macros |
| RFC3144 | PS | Remote Monitoring MIB Extensions for Interface Parameters Monitoring |
| RFC3287 | PS | Remote Monitoring MIB Extensions for Differentiated Services |
| RFC3273 | PS | Remote Network Monitoring Management Information Base for High Capacity Networks |
| RFC3395 | PS | Remote Network Monitoring MIB Protocol Identifier Reference Extensions |
| RFC3434 | PS | Remote Monitoring MIB Extensions for High Capacity Alarms |
| RFC3577 | I | Introduction to the Remote Monitoring (RMON) Family of MIB Modules |
OPS Area RMONMIB WG Meeting Minutes IETF #58 November 10, 2003 Minutes by Andy Bierman and Russell Dietz Review Material --------------- (A) draft-ietf-rmonmib-raqmon-framework-03.txt (B) draft-ietf-rmonmib-raqmon-pdu-03.txt (C) draft-ietf-rmonmib-raqmon-mib-02.txt (D) draft-ietf-rmonmib-pi-ipv6-00.txt (E) draft-ietf-rmonmib-apm-mib-12.txt (F) draft-ietf-rmonmib-tpm-mib-12.txt (G) draft-ietf-rmonmib-sspm-mib-10.txt (H) draft-ietf-rmonmib-rmon-oid-assignments-00.txt (I) draft-ietf-rmonmib-rmon2-v2-00.txt Agenda ------ 1) WG Status 2) Protocol Identifiers for IPv6 3) RMON2-MIB (Version 2) 4) Real-time Application Quality of Service Monitoring Minutes ------- 1) Working Group Status The following work items have been completed, but not yet published as RFCs. Some need more work before they can be published. a) Advancement of RFC 2613 (SMON) The WG is currently waiting for IESG action for advancement to Draft Standard. This action is on hold because RFC 2613 has a normative reference to RFC 2021 (RMON-2). It cannot advance until RMON-2 advances to Draft Standard. b) Advancement of RFC 2021 (RMON-2) The following issues were discussed: usrHistoryObjectVariable access control: - there are owner issues for access control (inherited AC and ownership). This RMON object could follow the DISMAN approach (local inherits access rights of the referenced object) The agent needs to check access granted on each get of the referenced object, not just when the pointer object it is set. - Discussion on VACM/Access Control. MUST, SHOULD or MAY will determine issues with current implementations are able to be included. A proposal was made to change the text to 'SHOULD' and add text in the security considerations calling out the issue. - Resolution: - add specified text to the security considerations document trapDestTable: - support for new trapDestTable features was discussed: - IPv6 support - Interaction with SNMPv3 - proposal - deprecate the trapDestTable - add clarifying text to RMON2-MIB - Resolutions - trapDestTable should be deprecated and no new features added to it - VACM is applied after notification destination selection - SNMPv3 MIB modules are used if both trapDestTable and 'snmpv3 notification MIBs' are configured - General consensus is that SNMPv3 takes precedence c) APM-MIB The AD review was completed in December 2002. An update <draft-ietf-rmonmib-apm-mib-12.txt> should be approved by the IESG soon. d) TPM-MIB The AD review was completed in February 2003. Many revisions to fix clarifications have been done since. The current revision is <draft-ietf-rmonmib-tpm-mib-12.txt>. This version will be forwarded to the Area Director as the final version of this document. e) SSPM-MIB The AD review was completed in February 2003. Many revisions to fix clarifications have been done since. The current revision is <draft-ietf-rmonmib-sspm-mib-10.txt>. This version will be forwarded to the Area Director as the final version of this document. f) IANA guidelines for the registry of rmon MIB modules The IESG recently approved this document which clarifies OID assignment procedures for RMON MIB modules. The approved version is called <draft-ietf-rmonmib-rmon-oid-assignments-01.txt>. 3) Protocol Identifier Macros for IPv6 This document in an extension to RFC 2895 to support new encapsulation layers for IPv6. The latest draft (D) was discussed by the group. Resolutions: - Use the term Protocol IDs, not 'MACROs'. - Action to double check the macros, then spin the draft for final consideration and WG Last Call. 4) Real-time Application Quality of Service Monitoring The RAQMON Framework (A), RAQMON PDU (B), and RAQMON MIB (C) documents were discussed together. A presentation on these drafts was given, explaining the changes from the last versions, and open issues with each draft. Refer to the slides for details on this presentation. The following is a summary of the issues that were discussed: General RAQMON comments: - Jitter: Add jitter type to PDU (spin appropriate documents with PDU change) clarification of 'passive observation' jitter and inter-frame jitter - Counts: Add Clarifying Text - RSVP parameter issue: change in object definition RAQMON Framework document: - Remove any coupling RMON framework and RAQMON framework. ACTION: Remove "extend RMON framework" from documents. - Jitter -- There is still an issue with how aggregation is done for one-way-delay. ACTION: Add clarification RAQMON PDU document: - Issues fixed - Document Spin Draft - Other 'fixes' proposed to 'pack' the PDU and compress unused bits in the fields - Should change terminology regarding specific SNMP PDU types (e.g., inform vs. trap) The term 'notification' should be used instead. - Consider configuration MIB for RDS later on, as experimental - Length of the enterprise ID should be the same every where: 32 bits - PDU docs - Not to reserve any bits for version ? Use report type version - 16 bit for it ? - Keep the addressing as is. - Clarify records count: 15 x 28 - get rid of redundant counter repeated with each record. - Check with Dan and other authors to get the final edits -- significant changes requested - SPIN RAQMON MIB Document: - Issues fixed - Document Spin Draft - Inet Address from IPADDR - Change required - Framework normative, MIB and PDU reference Framework -- fix the 'raqmon' date and time; remove this TC; use RFC2579 TC -- must use local time or must use 'source' time; add clarifying text -- RaqmonParticpantdAddr - not INET IP, just |