NOTE: This charter is a snapshot of the 51st IETF Meeting in London, England. It may now be out-of-date. Last Modified: 31-Jul-01
Andy Bierman <abierman@cisco.com>
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Bert Wijnen <bwijnen@lucent.com>
Steven Waldbusser <waldbusser@nextbeacon.com>
General Discussion:rmonmib@ietf.org
To Subscribe: http://www.ietf.org/mailman/listinfo/rmonmib
Archive: www.ietf.org/mail-archive/working-groups/rmonmib/current/maillist.htm
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.
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 |
Feb 01 |
|
Submit Final Draft of TR-RMON MIB in SMIv2 Format |
Mar 01 |
|
Begin Working Group Last Call for Application Performance Metrics |
Mar 01 |
|
Submit Final Draft of Application Performance Metrics to IESG for standards track action |
Apr 01 |
|
Submit Final Draft of Interface TopN Reporting to IESG for standards track action |
· Remote Network Monitoring Management Information Base for High Capacity Networks
· Remote Monitoring MIB Extensions for Interface Parameters Monitoring
· Remote Monitoring MIB Extensions for Differentiated Services
· Application Performance Measurement MIB
· Application Performance Measurement Framework Transport Performance Metrics MIB
· Remote Monitoring MIB Extensions for Identifying Application Protocol Verbs
· Token Ring Extensions to the Remote Network Monitoring MIB
RFC |
Status |
Title |
RFC2021 |
PS |
Remote Network Monitoring Management Information Base Version 2 using SMIv2 |
RFC2613 |
PS |
Remote Network Monitoring MIB Extensions for Switch Networks Version 1.0 |
RFC2819 |
S |
Remote Network Monitoring Management Information Base |
RFC2895 |
PS |
Remote Network Monitoring MIB Protocol Identifier Reference |
RFC2896 |
Remote Network Monitoring MIB Protocol Identifier Macros |
OPS Area
RMONMIB WG Meeting Minutes
IETF #51
March 8 & 10, 2001
Minutes by Andy Bierman
Review Material
---------------
(A) draft-ietf-rmonmib-apm-mib-04.txt
(B) draft-ietf-rmonmib-appverbs-02.txt
(C) draft-ietf-rmonmib-dsmon-mib-05.txt
(D) draft-ietf-rmonmib-tpm-mib-02.txt
(E) ftp://ftpeng.cisco.com/ftp/rmonmib/rmon-charter-new-jul01.html
(F) draft-bullard-pcap-01.txt
(G) draft-cole-sspm-03.txt
(H) draft-kalbfleisch-sspmmib-02.txt
(I) draft-quittek-pcap-ext-00.txt
Agenda
------
Aug 8) Discussion of current chartered drafts
1) RMON Extensions for Differentiated Services (C)
2) Application Performance Measurement MIB (A)
3) Transport Performance Metrics MIB (D)
4) RMON Extensions for Identifying Application Protocol Verbs (B)
Aug 10) Discussion of charter extension proposal and current unchartered drafts and work items
5) Charter extension proposal (E)
6) SMON MIB Advancement
7) RMON Framework
8) Definition of Managed Objects for Synthetic Sources for Performance Monitoring Algorithms. (G) (H)
9) Remote Packet Capture (F) (I)
10) VoIP Monitoring Issues
Minutes
-------
1) DSMON MIB
There were no new comments on the -05 draft. A 3 week WG Last Call has just been completed, and this draft will be forwarded to the Area Directors with the WG recommendation to the IESG that it be published as a Proposed Standard RFC.
2) APM MIB
The latest version of the APM MIB was presented, and then discussed by the group. The proper behavior of the httpFilterTable objects, and the associated scalar objects (apmHttpIgnoreUnregisteredURLs and apmHttp4xxIsFailure).
Some clarifications were requested by the group:
a) apmAppDirectoryResponsivenessBoundary* objects should be restricted such that each boundary 'N' is <= bucket 'N+1'. The user should easily be able to use less than 7 buckets. The 'RMON single count' principle (e.g., each packet should fall into exactly one bucket) should be preserved.
b) Clarify age-out algorithm for the apmNameTable
c) apmHttp4xxIsFailure description say errors '400 through 409'. Correct text is '400 through 499'.
d) Provide examples of a protocol with multiple responsiveness types. The apmResponsivenessType object shows up in the INDEX of many tables in order to provide multiple entries for each protocol for each responsiveness type.
Refer to the APM slides for more details.
3) TPM MIB
The latest version of the TPM MIB was presented, and then discussed by the group. It was suggested that the metric definitions be moved to their own document, but the group decided that they only apply to TPM, so they should remain in the TPM document. Integration with the IPPM metric definitions was discussed, such as separate registration 'sub-roots' for IPPM and RMON metrics. The TPM statistical functions should use IPPM metric definitions whenever possible, instead of defining new metrics.
This draft should be discussed in detail on the mailing list.
Work on the TPM MIB needs to be completed soon.
Refer to the TPM slides for more details.
4) Protocol Identifiers for Application Verbs
There were no new comments on the -02 draft. A 3 week WG Last Call has just been completed, and this draft will be forwarded to the Area Directors with the WG recommendation to the IESG that it be published as a Proposed Standard RFC.
5) Charter Extension Proposal
The charter extension proposal posted July 1 (E) was discussed by the group. This extension covers the following work items:
a) SMON MIB Advancement
b) RMON-2 MIB Advancement
c) RMON-PI Reference Advancement
d) Synthetic Sources for Performance Monitoring (SSPM)
e) RMON Framework document
Suggestions for more detailed wording for these charter items should be sent to the mailing list.
There was complete consensus that these work items should be added to the charter, and there are at least 2 or more people interested in co-authoring each proposed document.
A comment was made that the milestones for March 2002 should be extended to April 2002. An updated charter proposal will be posted and a URL sent to the mailing list and the A-Ds for approval.
6) SMON MIB Advancement
The WG is collecting implementation reports on RFC 1613.
Anybody who has implemented either agent or manager side SW utilizing part or all of this MIB should send an implementation report to the WG Chair (abierman@cisco.com) and/or the WG mailing list (rmonmib@ietf.org), if you have not done so already.
The group discussed whether this MIB should be extended in any way, and if so, should the extensions be integrated into the SMON-MIB module or be placed in a new module. There is some interest in creating an SMON-EXT-MIB module, and SMON extension proposals should be published as I-Ds or sent to the mailing list for discussion. There is no commitment to create an SMON extension, but there is interest.
There was complete consensus that RFC 2613 should be advanced without changes. An implementation report is almost complete, and will be forwarded to the A-Ds with the recommendation that the MIB be republished as a Draft Standard RFC. The group debated whether a new I-D was needed, and if so, is a WG Last Call needed as well. Only mandatory boilerplate changes are needed, so no WG Last Call will be done. The SMON authors may choose to publish a new I-D (e.g., draft-ietf-rmonmib-smon-v2-00.txt) or may choose to provide diffs the the RFC Editor upon request.
7) RMON Framework
The group discussed whether a new Informational RFC is needed to explain how all the RMON documents relate to one another, and how various RMON features relate to other areas, such as the IPPM metric definitions. RMON Data sources, common control table behavior, and 'RMON folklore' should also be documented.
There was complete consensus to create such a document, and several people are interested in co-authoring it.
8) SSPM MIB
The latest version of the SSPM MIB (H) was presented, and then discussed by the group. The group agreed this draft should be used as the starting point for the WG version. Any WG member who does not wish the current SSPM MIB to be used as the starting point should speak up on the mailing list, or preferably publish an alternate proposal in an Internet Draft, before September 24, 2001.
The WG is urged to discuss the latest version on the mailing list, even before it is converted to a WG draft. Hopefully significant agreement can be reached on the content before the next IETF.
The current draft contains tables for collected data, which is somewhat controversial, since the SPPM MIB is for configuration of devices which participate in synthetic transactions for performance measurement purposes.
The SSPM Framework document (G) was also discussed. It is not clear that a separate SSPM Framework document is needed, as opposed to a more general RMON Framework document. The group decided (see item 5) that the general RMON Framework document should be written instead of an SSPM-specific framework. Details which may be omitted from a generalized framework should be moved to the SSPM MIB.
Refer to the SSPM slides for more details.
9) Remote Packet Capture
The need for new remote packet capture facilities within the RMON Framework was discussed by the group. Several features could be implemented to enhance the packet filter and capture capability of an RMON probe, and the group discussed the costs and benefits of some of these features. Among them:
a) ability to capture packet slices on header boundaries in order to easily support variable length headers and the ability to enforce 'privacy rules', by not allowing capture of any user data
b) ability to 'push' captured packet slices to an application, rather than requiring the application to poll for the slices with SNMP
c) ability to algorithmically select which packet slices will be captured on an interface in a manner that is easier to use than the current 'bit-oriented' RMON-1 filtering
d) precise packet ingress timestamps which meet IPPM requirements for packet timestamping
There was a wide range of opinions on all or part of this work, from strong objection to strong support, and everything in between.
The proposal for this work item and the 2 solution proposals (F and I) will be discussed further on the mailing list. If there is sufficient interest in the problem, then a charter extension proposal will be written, reviewed by the WG, and forwarded to the A-Ds for consideration.
Refer to the PCAP slides for more details.
10) VoIP Monitoring
The Realtime Application Monitoring (RAPMON) Framework was presented, and then discussed by the group. This proposal would allow IP endpoints running realtime services (such as Voice over IP) to transmit performance data to a centralized data collector, which in turn provides aggregated data (via MIB objects) to SNMP applications.
There appeared to be a great deal of interest in this work, and it will be discussed further on the mailing list. If there is sufficient interest in the problem, then a charter extension proposal will be written, reviewed by the WG, and forwarded to the A-Ds for consideration.
Refer to the RAPMON slides for more details.
Agenda
Transport Performance Metrics MIB
Realtime Application Monitoring (Rapmon) Framework
Synthetic Sources for Performance Monitoring