Last Modified: 2003-02-24
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 | |
| APR 03 | Begin Working Group Last Call for the Extensions to RMON Framework for RAQMON document | |
| MAY 03 | Begin Working Group Last Call for the RAQMON PDU Types document | |
| MAY 03 | Begin Working Group Last Call for the RAQMON MIB document | |
| JUL 03 | Submit the Extensions to RMON Framework for RAQMON document to the IESG for publication consideration as an Informational RFC | |
| AUG 03 | Submit the RAQMON PDU Types document to the IESG for publication consideration as a Proposed Standard | |
| AUG 03 | Submit the RAQMON MIB document to the IESG for publication consideration as a Proposed Standard |
| 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 |
OPS Area RMONMIB WG Meeting Minutes IETF #56 March 17, 2003 Minutes by Andy Bierman Review Material --------------- (A) draft-ietf-rmonmib-raqmon-framework-01.txt (B) draft-ietf-rmonmib-raqmon-pdu-01.txt (C) draft-ietf-rmonmib-raqmon-mib-00.txt Agenda ------ 1) WG Status (5 minutes) Status of completed documents 2) Protocol Identifier Macros (10 minutes) Request from IPPM WG to update PI Macros RFC 3) Fixing the TimeFilter TC and updating RFC 2021 (15 minutes) discussion of email proposal (2/3/03) to create new timeFilterMode MIB object 4) Real-time Application Quality of Service Monitoring (90 min) Discussion of the RAQMON Framework (A) Determine if the framework is complete Should the framework provide extensibility and allow for future PDU types and/or delivery mechanisms Discussion of the RAQMON PDU (B) Discuss congestion awareness requirements Determine if the PDU contains all appropriate fields Should there be different high-level conformance level to allow devices to subset the PDU fields in a consistent manner? Discussion of the RAQMON MIB (C) Determine (if possible) if the MIB is complete for: configuration reported attributes collected from RAQMON PDU Minutes ------- 1) Working Group Status a) Advancement of RFC 2074 (RMON PI) The implementation report needs to be reissued as a report for RFC 2895 (RMON PI Reference). The updated RFC contains only the normative portions of RFC 2074, without any semantic changes. After this report is posted on the IETF WEB site, the advancement of RFC 2895 (not 2074) can be considered by the IESG. b) Advancement of RFC 2613 (SMON) The WG is currently waiting for IESG action for advancement to Draft Standard. c) APM-MIB The AD review was completed in December 2002. An update <draft-ietf-rmonmib-apm-mib-08.txt> was published in March 2002. A final WG Last Call was started on April 3, 2003 and will conclude on April 17, 2003. d) TPM-MIB The AD review was completed in February 2003. The WG is waiting for the authors to publish an update. e) SSPM-MIB The AD review was completed in February 2003. The WG is waiting for the authors to publish an update. f) Introduction to RMON Family of MIBs The final WG Last Call was completed in February 2003. The WG is currently waiting for an AD review. 2) Protocol Identifier Macros : Request from IPPM WG to update PI Macros RFC. Emile Stephan presented some slides outlining the need for an update to RFC 2895 to support new encapsulation layers. New encapsulations should include: - IPv6 (IPv6, IPv6 in IPv4, IPv4 in IPv6) - Sub-IP (VLAN and MPLS) Refer to the slides for more details on this presentation. The WG will not be adding a new item to the charter for this work unless and until an Internet Draft is submitted which completely describes the problem and solution proposal. There is currently insufficient interest and resources in the WG to do this work without such a draft. 3a) Fixing the TimeFilter TC A new MIB object, called timeFilterMode was proposed to the WG mailing list on 2/3/03. This object would identify and configure the TimeFilter TC behavior for the entire agent. The definition in RFC 2021 specifies that an agent will iterate through all values of the TimeFilter in an INDEX instance. This causes a lot of redundant information to be returned, and is not compatible with the GetBulk PDU type. A new TimeFilter mode, in which redundant rows are not returned, is supported with this new timeFilterMode object. There is agreement that the semantics embodied in this MIB object should be added to the RMON-2 MIB, but there is not agreement related to some other details. In particular, the object should be read-only, not-read-write. It should also be a bit in the probeCapabilities object, instead of a separate object. A new version of the probeCapabilities object will be proposed to the WG mailing list, which includes the timeFilterMode support. 3b) Updating RFC 2021 (RMON-2) The RMON-2 MIB will be updated to support the TimeFilter mode described in (3a). In addition, the extensions for the HC-RMON MIB will also be integrated. There are a number of objects that must be deprecated in order to advance RMON-2 to Draft Standard. An email to the WG mailing list will be sent identifying these objects. It is likely that RFC 2021 will be cycled at Proposed Standard, because there are many objects that must be deprecated in order for it to be advanced to Draft Standard. 4) Real-time Application Quality of Service Monitoring The RAQMON Framework (A) and RAQMON PDU (B) documents were discussed together. The RAQMON MIB (C) was not discussed at this meeting. It was not updated since the last IETF, like the other two RAQMON documents, because the MIB contents depend on the stability of the framework and PDU documents. Anwar Siddiqui gave a presentation on the Framework and PDU drafts, explaining the changes from the last versions, and open issues with each draft. Refer to the slides for details on this presentation. One high level issue to resolve is the general design of the PDU structure. Should there be two PDU types (Basic and Application) in which the Basic PDU contains a fixed list of metrics, and the Application PDU contains only a vendor-defined list of extensions to the Basic PDU? There was general agreement within the group to simplify this design and have only one PDU type, which is extensible. The next version of the RAQMON documents will contain a solution proposal for this single, extensible PDU design. Another issue facing the RAQMON design is the mechanisms used for congestion avoidance. There is some rate limiting provided by RTCP. In addition, the SNMP transport will be limited to one RAQMON packet per second generated from the RAQMON Data Source. New versions of the the RAQMON documents are expected soon. The authors will address open issues and remove redundant text from each document, so that normative text for a particular RAQMON detail appears in only one document. |