Protocol Action: Remote Network Monitoring MIB Protocol Identifiers to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 31 July 1996 16:45 UTC
Received: from ietf.org by ietf.org id aa11188; 31 Jul 96 12:45 EDT
Received: from localhost by ietf.org id aa11122; 31 Jul 96 12:44 EDT
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: rmonmib@cisco.com
Sender: ietf-announce-request@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Remote Network Monitoring MIB Protocol Identifiers to Proposed Standard
Date: Wed, 31 Jul 1996 12:44:27 -0400
X-Orig-Sender: scoya@ietf.org
Message-ID: <9607311244.aa11122@ietf.org>
The IESG has approved the following two Internet-Drafts: 1. Remote Network Monitoring Management Information Base version 2 <draft-ietf-rmonmib-rmonmib-v2-03.txt> 2. Remote Network Monitoring MIB Protocol Identifiers <draft-ietf-rmonmib-rmonprot-03.txt> as Proposed Standards. These documents are the product of the Remote Network Monitoring Working Group. The IESG contact person is Deirdre Kostick. Technical Summary The Remote Network Monitoring MIB (RMON) as defined in RFC 1757, provides an NMS with mechanisms to monitor and collect large amounts of data about the traffic utilization of particular subnetworks, by promiscuously monitoring the MAC frames transmitted onto those subnetworks. RMON-2 builds upon the RFC 1757 standard, enabling several network management functions, such as fault monitoring, application monitoring, capacity and network planning, and remote polling. The new MIB extends many monitoring capabilities beyond the MAC layer, up through the application layer. Numerous improvements such as probe configuration, better resource management, and faster table uploads, have also been made to increase the robustness and interoperability of RMON implementations. Working Group Summary The process of evaluating and selecting a subset of features for development out of the many different proposals was the most contentious aspect of the WG effort. The following features were the least contentious: * extend the basic RMON-1 functions beyond the MAC layer * use a centralized protocol directory architecture * add user-specified history collection * reduce table retrieval times * increase NMS control of probe resources * add a trap destination table for RMON traps These features were more contentious: * include application-layer matrix-topN-reporting * improve RMON filtering capabilities * include general probe configuration capabilities The MIB and Protocol Identifiers documents reflect the consensus of the Working Group. Protocol Quality The RMON-2 MIB and RMON Protocol Identifiers documents were reviewed for the IETF NM Area by Jeff Johnson, and for the IESG by Deirdre Kostick.