Last Modified: 2003-05-12
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 |
OPS Area RMONMIB WG Meeting Minutes IETF #57 July 14, 2003 Minutes by Andy Bierman Review Material --------------- (A) draft-ietf-rmonmib-raqmon-framework-02.txt (B) draft-ietf-rmonmib-raqmon-pdu-02.txt (C) draft-ietf-rmonmib-raqmon-mib-01.txt (D) draft-stephan-ipv6-protocol-identifier-00.txt (E) draft-ietf-rmonmib-apm-mib-09.txt (F) draft-ietf-rmonmib-tpm-mib-09.txt (G) draft-ietf-rmonmib-sspm-mib-07.txt Agenda ------ 1) WG Status 2) Fixing the TimeFilter TC and updating RFC 2021 3) Real-time Application Quality of Service Monitoring 4) Protocol Identifiers for IPv6 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 2895 (RMON PI) This RFC was approved as a Draft Standard in June 2003. It is not yet listed on the RFC Editor's pages as a Draft Standard. b) 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. c) APM-MIB The AD review was completed in December 2002. An update <draft-ietf-rmonmib-apm-mib-10.txt> should be published soon. This version should be ready for IETF Last Call. d) TPM-MIB The AD review was completed in February 2003. An update <draft-ietf-rmonmib-tpm-mib-09.txt> was published in June 2003. This draft needs to be checked for any needed corrections. It should be ready for IETF Last Call. e) SSPM-MIB The AD review was completed in February 2003. An update <draft-ietf-rmonmib-sspm-mib-07.txt> was published in June 2003. This draft needs to be checked for any needed corrections. It should be ready for IETF Last Call. f) Introduction to RMON Family of MIBs This RFC was approved as an Informational RFC in June 2003. It should be published soon as RFC 3577. g) Advancement of RFC 2021 (RMON-2) The WG has decided to attempt to advance RFC 2021 to Draft Standard. An update to this RFC is expected soon to make the following changes: The following MIB objects will be deprecated: probeDownloadFile probeDownloadTFTPServer probeDownloadAction probeDownloadStatus serialMode serialProtocol serialTimeout serialModemInitString serialModemHangUpString serialModemConnectResp serialModemNoConnectResp serialDialoutTimeout serialStatus serialConnectDestIpAddress serialConnectType serialConnectDialString serialConnectSwitchConnectSeq serialConnectSwitchDisconnectSeq serialConnectSwitchResetSeq serialConnectOwner serialConnectStatus netConfigIPAddress netConfigSubnetMask netConfigStatus netDefaultGateway tokenRingMLStatsDroppedFrames tokenRingMLStatsCreateTime tokenRingPStatsDroppedFrames tokenRingPStatsCreateTime ringStationControlDroppedFrames ringStationControlCreateTime sourceRoutingStatsDroppedFrames sourceRoutingStatsCreateTime A new MODULE-COMPLIANCE and appropriate GROUP macros will be added which removes the newly deprecated objects. The boilerplate and references will be updated to be aligned with the current template. The nlMatrixTopNControlRateBase and nlMatrixTopNControlRateBase objects will be updated to int grate the changes described in section 3 of the HC-RMON MIB (RFC 3273). The conformance section of the RMON2-MIB module will e updated to indicate that the addition high capacity enumerations are not required for compliance to the RMON2-MIB. 2) Fixing the TimeFilter TC The working group decided that a new MIB object to identify the TimeFilter mode implemented by an agent is not needed. An application uses the exact same algorithm to process TimeFilter index information whether the agent returns all possible instances of the TimeFilter value or if it suppresses redundant instances. Since it is possible that multiple tables using a TimeFilter can be supported by a single agent, a simple scalar TimeFilter mode object is not sufficient anyway. 3) 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. One issue discussed was whether RAQMON overlaps too much with RTCP. It was argued that RAQMON has distinct functionality because we don't want to sniff packets, but rather collect metrics from the endpoint. The packets could be encrypted, preventing statistics collection. Also we want a snapshot of the metrics at the time of failure from the endpoint. The following changes to the RAQMON documents were discussed: - use Enterprise ID and report ID to identify section - enterprise ID should be 32 bits instead of 16 - IP addresses will be binary instead of ASCII - RMON not RAQMON in the name field in the RTCP APP packet - RAQMON RDS MIB is used to define the objects for the notification -- do not have jitter in the mandatory list; look at list and figure out which should be there every time for every application - use of Inform you need to process ACK; you must be congestion-aware or congestion-safe; - perhaps this requirement could be met by sending 1 report every 2 minutes, but this may not be safe because congestion could occur at the receiver aggregation point - change draft to say RDS MUST meet RFC 2914 requirements somehow. - MIB changes: - use InetAddress instead of IpAddress - use MAX-ACCESS read-create instead of read-write in the exception table - use reference clauses instead of cut-and-paste; have normative text in just one place New versions of the the RAQMON documents are expected within five weeks of the IETF meeting. 4) Protocol Identifier Macros for IPv6 Emile Stephan presented some slides outlining the need for an extension to RFC 2895 to support new encapsulation layers. New encapsulations should include: - IPv6 (IPv6, IPv6 in IPv4, IPv4 in IPv6) Refer to the slides for more details on this presentation. The working group decided to work on this update to RFC 2895, if an author could be found (Emile agreed to author this document) and if the additions are limited to a very short list, related only to IPv6 encapsulations. This work will be proposed as an extension the RMON Protocol Identifiers portion of the working group charter. |