Internet Draft Anwar Siddiqui Avaya Inc. Dan Romascanu Avaya Inc. Eugene Golovinsky BMC Software Richard Smith Avaya Inc. 22 Oct. 2002 Real-time Application Quality of Service Monitoring (RAQMON) MIB Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." To view the list Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Remote Monitoring MIB [RFC2819]. In particular, it describes managed objects used for realtime application QOS monitoring. Distribution of this memo is unlimited. RMON MIB WG Expires July 2003 [Page 1] INTERNET DRAFT RAQMON MIB January 2003 Table of Contents Status of this Memo 1 Abstract 1 1 Introduction 2 2 The Internet-Standard Management Framework 2 3 RAQMON Framework 3 4 Structure of the RAQMON MIB 4 5 RAQMON MIB Definitions 4 6 Normative References 24 7 Informative References 24 8 Intellectual Property 26 9 Security Considerations 26 10 Author's Address 27 A Full Copyright Statement 28 B Log of Changes 28 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a method of sorting the interfaces of a monitored device according to values of parameters specific to this interface. The original RAQMON draft [SIDDIQUI1] was split into 3 parts to identify the RAQMON Framework, RAQMON QOS PDU and RAQMON MIB. This memo defines the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Remote Monitoring MIB [RFC2819] to accommodate RAQMON solution. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the RMON MIB WG Expires July 2003 [Page 2] INTERNET DRAFT RAQMON MIB January 2003 Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 3. RAQMON Framework As outlined in [SIDDIQUI2] the RAQMON framework is based on three entities: - RAQMON Data Source (RDS) - RAQMON Report Collector (RRC) - RAQMON MIB Structure Figure 1 below shows various interfaces in RAQMON Framework. This draft specifies the Management Information Base (MIB) Modules used by the RAQMON Report Collectors to store data derived from RAQMON PDUs. +----------------------+ +---------------------------+ | IP End Device | | IP End Device >----+ | |+--------------------+| |+--------------------+ | | || APPLICATION || || APPLICATION | | | || -Voice over IP <----(1)----> -Voice over IP >- + | | || -Instant Messaging|| || -Instant Messaging| | 3 | || -Email || || -Email | 2 | | |+--------------------+| |+--------------------+ | | | | | | | | | | | | +------------------+ | | | +----------------------+ | |RAQMON Data Source|<-+ | | | | (RDS) |<---+ | | +------------------+ | +-----------|---------------+ | (4) | +----------------------------+ | | |/ |/ +------------------+ +------------------+ +-------------+ |RAQMON Report | .. |RAQMON Report | | RAQMON | |Collector (RRC) #n| |Collector (RRC) #1|<--5-->| Manager | +------------------+ +------------------+ +-------------+ Figure 1 - RAQMON Framework. (1) Communication Session between IP end devices/apps affected by RMON MIB WG Expires July 2003 [Page 3] INTERNET DRAFT RAQMON MIB January 2003 underlying transport network (2) Context-Sensitive transport network Specific Metrics (3) Device State Specific Metrics (4) RAQMON PDU transmitted over this interface (IP Address, port) (5) RAQMON MIB running between RRCs and a RAQMON Application ('RAQMON manager') 4. Structure of the RAQMON MIB The RAQMON MIB is composed of three MIB groups: The raqmonSession MIB group incorporates the following tables: - raqmonParticpantTable contains information about participants in open and closed (terminated) sessions - raqmonQosTable contains historical information about QoS during sessions - raqmonParticpantAddrTable maps particpant addresses into the index of the raqmonParticpantTable The raqmonException MIB group includes a table of filters that trigger notifications for sessions with poor QoS. The raqmonConfig MIB group includes object that define the configuration of the RAQMON collector. All objects in the MIB MUST be implemented by the RAQMON collectors, with the exception of the raqmonPDUBasicPDU object and raqmonSNMPTransportNotification which MUST be implemented by a RAQMON device. This is reflected in the conformance clauses. 5. RAQMON MIB Definitions -- -- The original version of this MIB was created by Richard Smith from -- Avaya Labs Australia RAQMON-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF mib-2, enterprises, IpAddress, Integer32, Unsigned32, Gauge32, Counter32, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE FROM SNMPv2-SMI RowStatus, TEXTUAL-CONVENTION, TruthValue FROM SNMPv2-TC RMON MIB WG Expires July 2003 [Page 4] INTERNET DRAFT RAQMON MIB January 2003 Utf8String FROM SYSAPPL-MIB Dscp FROM DIFFSERV-DSCP-TC; raqmon MODULE-IDENTITY LAST-UPDATED "200301130000Z" -- January 13, 2003 ORGANIZATION "IETF RMON MIB Working Group" CONTACT-INFO "Dan Romascanu Postal: Avaya Israel Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel Tel: +972 3 6458414 Email: dromasca@avaya.com " DESCRIPTION "Real-Time Application QoS Monitoring MIB" REVISION "200301130000Z" -- January 13, 2003 DESCRIPTION "The original version of this MIB, published as RFCXXXX" ::= { rmon 6889 } -- need to assign a branch under RMON -- -- Type definitions -- Duration ::= Unsigned32 -- -- Textual conventions -- RaqmonDateAndTime ::= TEXTUAL-CONVENTION DISPLAY-HINT "2d-1d-1d,1d:1d:1d" STATUS current DESCRIPTION "A date-time specification in Coordinated Universal Time (UTC). This definition is used rather than DateAndTime from SNMPv2-TC or ExtUTCTime from SMIv2 since a fixed length field in UTC was preferred RMON MIB WG Expires July 2003 [Page 5] INTERNET DRAFT RAQMON MIB January 2003 for use as an INDEX. field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..59 For example, Tuesday May 26, 1992 at 1:30:15 UTC would be displayed as: 1992-5-26,13:30:15." SYNTAX OCTET STRING (SIZE (7)) -- -- Node definitions -- raqmonEvents OBJECT IDENTIFIER ::= { raqmon 0 } raqmonSessionAlarm NOTIFICATION-TYPE OBJECTS { raqmonParticipantAddr, raqmonParticipantName, raqmonParticipantPeerAddr, raqmonQosRTT, raqmonQosJitter, raqmonQosLostPackets, raqmonQosRcvdPackets } STATUS current DESCRIPTION "A notification generated by an entry in the raqmonSessionExceptionTable." ::= { raqmonEvents 1 } raqmonSNMPTransportNotofication NOTIFICATION-TYPE OBJECTS { raqmonPDUBasicPDU } STATUS current DESCRIPTION "A Notification generated by a RAQMON device to a collector, if an SNMP agent is implemented in the RAQMON device. Note that similar format PDUs MAY Be generated by RAQMON devices without a full SNMP agent being REQUIRED." ::= { raqmonEvents 2 } RMON MIB WG Expires July 2003 [Page 6] INTERNET DRAFT RAQMON MIB January 2003 raqmonMIBObjects OBJECT IDENTIFIER ::= { raqmon 1 } raqmonSession OBJECT IDENTIFIER ::= { raqmonMIBObjects 1 } raqmonParticipantTable OBJECT-TYPE SYNTAX SEQUENCE OF RaqmonParticipantEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of information about participants in sessions. Contains both active and closed (terminated) sessions. " ::= { raqmonSession 1 } raqmonParticipantEntry OBJECT-TYPE SYNTAX RaqmonParticipantEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry contains information from a single session participant. Rows are removed for inactive sessions when implementation specific age or space limits are reached. " INDEX { raqmonParticipantStartDate, raqmonParticipantIndex } ::= { raqmonParticipantTable 1 } RaqmonParticipantEntry ::= SEQUENCE { raqmonParticipantStartDate RaqmonDateAndTime, raqmonParticipantIndex Integer32, raqmonParticipantAddr IpAddress, raqmonParticipantSendPort INTEGER, raqmonParticipantRecvPort Integer32, raqmonParticipantSetupDelay Unsigned32, raqmonParticipantName Utf8String, raqmonParticipantTool Utf8String, raqmonParticipantQosCount Unsigned32, RMON MIB WG Expires July 2003 [Page 7] INTERNET DRAFT RAQMON MIB January 2003 raqmonParticipantEndDate RaqmonDateAndTime, raqmonParticipantRcvdPT INTEGER, raqmonParticipantSentPT INTEGER, raqmonParticipantActive TruthValue, raqmonParticipantPeerIndex OCTET STRING, raqmonParticipantPeerAddr IpAddress, raqmonParticipantSrcLayer2 INTEGER, raqmonParticipantDestLayer2 INTEGER, raqmonParticipantSrcLayer3 Dscp, raqmonParticipantDestLayer3 Dscp, raqmonParticipantCPUMean INTEGER, raqmonParticipantCPUMin INTEGER, raqmonParticipantCPUMax INTEGER, raqmonParticipantMemoryMean INTEGER, raqmonParticipantMemoryMin INTEGER, raqmonParticipantMemoryMax INTEGER, raqmonParticipantRTTMean Gauge32, raqmonParticipantRTTMin Gauge32, raqmonParticipantRTTMax Gauge32, raqmonParticipantJitterMean Gauge32, raqmonParticipantJitterMin Gauge32, raqmonParticipantJitterMax Gauge32, raqmonParticipantPackets Counter32, raqmonParticipantLostPackets Counter32 RMON MIB WG Expires July 2003 [Page 8] INTERNET DRAFT RAQMON MIB January 2003 } raqmonParticipantStartDate OBJECT-TYPE SYNTAX RaqmonDateAndTime MAX-ACCESS not-accessible STATUS current DESCRIPTION "The date and time of this entry. It will be the date and time of the first report received." ::= { raqmonParticipantEntry 1 } raqmonParticipantIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index of the conceptual row which is for SNMP purposes only and has no relation to any protocol value. There is no requirement that these rows are created or maintained sequentially. The index will be unique for a particular date and time." ::= { raqmonParticipantEntry 2 } raqmonParticipantAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "IP Address of the participant for this session." ::= { raqmonParticipantEntry 3 } raqmonParticipantSendPort OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "Port from which session data is sent." ::= { raqmonParticipantEntry 4 } raqmonParticipantRecvPort OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Port on which session data is received." RMON MIB WG Expires July 2003 [Page 9] INTERNET DRAFT RAQMON MIB January 2003 ::= { raqmonParticipantEntry 5 } raqmonParticipantSetupDelay OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session setup time in milliseconds." ::= { raqmonParticipantEntry 6 } raqmonParticipantName OBJECT-TYPE SYNTAX Utf8String MAX-ACCESS read-only STATUS current DESCRIPTION "The data source name for the participant." ::= { raqmonParticipantEntry 7 } raqmonParticipantTool OBJECT-TYPE SYNTAX Utf8String MAX-ACCESS read-only STATUS current DESCRIPTION "A string giving the name and possibly version of the application generating the stream, e.g., videotool 1.2. This information may be useful for debugging purposes and is similar to the Mailer or Mail- System-Version SMTP headers. The tool value is expected to remain constant for the duration of the session." ::= { raqmonParticipantEntry 8 } raqmonParticipantQosCount OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of entries in the QOS history table for this participant and session." ::= { raqmonParticipantEntry 9 } raqmonParticipantEndDate OBJECT-TYPE SYNTAX RaqmonDateAndTime MAX-ACCESS read-only STATUS current RMON MIB WG Expires July 2003 [Page 10] INTERNET DRAFT RAQMON MIB January 2003 DESCRIPTION "The date and time of the last report received." ::= { raqmonParticipantEntry 10 } raqmonParticipantRcvdPT OBJECT-TYPE SYNTAX INTEGER (0..127) MAX-ACCESS read-only STATUS current DESCRIPTION "Payload type of received packets." ::= { raqmonParticipantEntry 11 } raqmonParticipantSentPT OBJECT-TYPE SYNTAX INTEGER (0..127) MAX-ACCESS read-only STATUS current DESCRIPTION "Payload type of sent packets." ::= { raqmonParticipantEntry 12 } raqmonParticipantActive OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Value 'true' ndicates that the session for this participant is active (open). Value 'false' indicates that the session is closed (terminated). " ::= { raqmonParticipantEntry 13 } raqmonParticipantPeerIndex OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0 | 11)) MAX-ACCESS read-only STATUS current DESCRIPTION "The index of the corresponding entry in this table for the other peer participant. If there is no such entry then the value will be a zero length string. Otherwise it will be a string of length 11 consisting of the raqmonParticipantStartDate octet string appended with an octet string of length 4 containing raqmonParticipantIndex (most significant octet first). Note, the entry may no longer exist even if the index is not zero length since the entry may have RMON MIB WG Expires July 2003 [Page 11] INTERNET DRAFT RAQMON MIB January 2003 been deleted due to implementation defined limits being exceeded. " ::= { raqmonParticipantEntry 14 } raqmonParticipantPeerAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "IP address of peer endpoint." ::= { raqmonParticipantEntry 15 } raqmonParticipantSrcLayer2 OBJECT-TYPE SYNTAX INTEGER (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "Source Layer 2 priority" ::= { raqmonParticipantEntry 16 } raqmonParticipantDestLayer2 OBJECT-TYPE SYNTAX INTEGER (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "Destination Layer 2 priority." ::= { raqmonParticipantEntry 17 } raqmonParticipantSrcLayer3 OBJECT-TYPE SYNTAX Dscp MAX-ACCESS read-only STATUS current DESCRIPTION "Source Layer 3 DSCP value" ::= { raqmonParticipantEntry 18 } raqmonParticipantDestLayer3 OBJECT-TYPE SYNTAX Dscp MAX-ACCESS read-only STATUS current DESCRIPTION "Destination Layer 3 DSCP value" ::= { raqmonParticipantEntry 19 } raqmonParticipantCPUMean OBJECT-TYPE SYNTAX INTEGER (0..100) MAX-ACCESS read-only RMON MIB WG Expires July 2003 [Page 12] INTERNET DRAFT RAQMON MIB January 2003 STATUS current DESCRIPTION "Mean CPU utilization as a percentage." ::= { raqmonParticipantEntry 20 } raqmonParticipantCPUMin OBJECT-TYPE SYNTAX INTEGER (0..100) MAX-ACCESS read-only STATUS current DESCRIPTION "Minimum CPU utilization as a percentage." ::= { raqmonParticipantEntry 21 } raqmonParticipantCPUMax OBJECT-TYPE SYNTAX INTEGER (0..100) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum CPU utilization as a percentage." ::= { raqmonParticipantEntry 22 } raqmonParticipantMemoryMean OBJECT-TYPE SYNTAX INTEGER (0..100) MAX-ACCESS read-only STATUS current DESCRIPTION "Mean memory utilization as a percentage." ::= { raqmonParticipantEntry 23 } raqmonParticipantMemoryMin OBJECT-TYPE SYNTAX INTEGER (0..100) MAX-ACCESS read-only STATUS current DESCRIPTION "Minimum memory utilization as a percentage." ::= { raqmonParticipantEntry 24 } raqmonParticipantMemoryMax OBJECT-TYPE SYNTAX INTEGER (0..100) MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum memory utilization as a percentage." ::= { raqmonParticipantEntry 25 } raqmonParticipantRTTMean OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only RMON MIB WG Expires July 2003 [Page 13] INTERNET DRAFT RAQMON MIB January 2003 STATUS current DESCRIPTION "Mean round trip time (RTT) over the entire session." ::= { raqmonParticipantEntry 26 } raqmonParticipantRTTMin OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Minimum round trip time (RTT) over the entire session." ::= { raqmonParticipantEntry 27 } raqmonParticipantRTTMax OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Maximum round trip time (RTT) over the entire session." ::= { raqmonParticipantEntry 28 } raqmonParticipantJitterMean OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Mean jitter over the entire session." ::= { raqmonParticipantEntry 29 } raqmonParticipantJitterMin OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Minimum jitter over the entire session." ::= { raqmonParticipantEntry 30 } raqmonParticipantJitterMax OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Maximim jitter over the entire session." ::= { raqmonParticipantEntry 31 } raqmonParticipantPackets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only RMON MIB WG Expires July 2003 [Page 14] INTERNET DRAFT RAQMON MIB January 2003 STATUS current DESCRIPTION "Count of packets received for the entire session." ::= { raqmonParticipantEntry 32 } raqmonParticipantLostPackets OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of packets lost by this receiver for the entire session." ::= { raqmonParticipantEntry 33 } raqmonQosTable OBJECT-TYPE SYNTAX SEQUENCE OF RaqmonQosEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Table of historical information about quality of service data during sessions. " ::= { raqmonSession 2 } raqmonQosEntry OBJECT-TYPE SYNTAX RaqmonQosEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry contains information from a single RAQMON packet. Rows are removed for inactive sessions when implementation specific time or space limits are reached. " INDEX { raqmonParticipantStartDate, raqmonParticipantIndex, raqmonQosTime } ::= { raqmonQosTable 1 } RaqmonQosEntry ::= SEQUENCE { raqmonQosTime Duration, raqmonQosRTT Gauge32, raqmonQosJitter RMON MIB WG Expires July 2003 [Page 15] INTERNET DRAFT RAQMON MIB January 2003 Gauge32, raqmonQosRcvdPackets Integer32, raqmonQosRcvdOctets Integer32, raqmonQosSentPackets Integer32, raqmonQosSentOctets Integer32, raqmonQosLostPackets Integer32, raqmonQosRsvpStatus INTEGER } raqmonQosTime OBJECT-TYPE SYNTAX Duration MAX-ACCESS read-only STATUS current DESCRIPTION "Time of this entry measured from the start of the corresponding participant session." ::= { raqmonQosEntry 1 } raqmonQosRTT OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The round trip time. Will contain the previous value if there was no report for this time (or 2^32 - 1 if value never reported). " ::= { raqmonQosEntry 2 } raqmonQosJitter OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "An estimate of delay variation as observed by this receiver. Will contain the previous value if there was no report for this time (or 2^32 - 1 if value never reported). " ::= { raqmonQosEntry 3 } RMON MIB WG Expires July 2003 [Page 16] INTERNET DRAFT RAQMON MIB January 2003 raqmonQosRcvdPackets OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of packets received by this receiver since the last entry containing a value for this field. This is not a cumulative value since the start of the session. Set to -1 if value not reported for this time. " ::= { raqmonQosEntry 4 } raqmonQosRcvdOctets OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of octets received by this receiver since the last entry containing a value for this field. This is not a cumulative value since the start of the session. Set to -1 if value not reported for this time. " ::= { raqmonQosEntry 5 } raqmonQosSentPackets OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of packets sent since the last entry containing a value for this field. This is not a cumulative value since the start of the session. Set to -1 if value not reported for this time. " ::= { raqmonQosEntry 6 } raqmonQosSentOctets OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of octets sent since the last entry containing a value for this field. This is not a cumulative value since the start of the session. RMON MIB WG Expires July 2003 [Page 17] INTERNET DRAFT RAQMON MIB January 2003 Set to -1 if value not reported for this time. " ::= { raqmonQosEntry 7 } raqmonQosLostPackets OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of packets lost as observed by this receiver since the last entry containing a value for this field. Set to -1 if value not reported for this time." ::= { raqmonQosEntry 8 } raqmonQosRsvpStatus OBJECT-TYPE SYNTAX INTEGER { unknown(-1), notInUse(0), disabled(1), reservationPending(2), reservationFailed(3), reservationSuccess(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The RSVP status. Will contain the previous value if there was no report for this time (or if no value was ever reported)." ::= { raqmonQosEntry 9 } raqmonParticipantAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF RaqmonParticipantAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Maps raqmonParticipantAddr to the index of the raqmonParticipantTable. This table allows management applications to find entries sorted by raqmonParticipantAddr rather than raqmonParticipantStartDate." ::= { raqmonSession 3 } raqmonParticipantAddrEntry OBJECT-TYPE SYNTAX RaqmonParticipantAddrEntry MAX-ACCESS not-accessible RMON MIB WG Expires July 2003 [Page 18] INTERNET DRAFT RAQMON MIB January 2003 STATUS current DESCRIPTION "Each entry corresponds to exactly one entry in the raqmonParticipantEntry - the entry containing the index pair rraqmonParticipantStartDate, raqmonParticipantIndex." INDEX { raqmonParticipantAddr, raqmonParticipantStartDate, raqmonParticipantIndex } ::= { raqmonParticipantAddrTable 1 } RaqmonParticipantAddrEntry ::= SEQUENCE { raqmonParticipantAddrEndDate RaqmonDateAndTime } raqmonParticipantAddrEndDate OBJECT-TYPE SYNTAX RaqmonDateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of raqmonParticipantEndDate for the corresponding raqmonParticipantEntry." ::= { raqmonParticipantAddrEntry 1 } raqmonException OBJECT IDENTIFIER ::= { raqmonMIBObjects 2 } raqmonSessionExceptionTable OBJECT-TYPE SYNTAX SEQUENCE OF RaqmonSessionExceptionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table creates filters so that a management station can get immediate notification of a session that has had poor quality of service." ::= { raqmonException 2 } raqmonSessionExceptionEntry OBJECT-TYPE SYNTAX RaqmonSessionExceptionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the raqmonSessionExceptionTable." INDEX { raqmonSessionExceptionIndex } RMON MIB WG Expires July 2003 [Page 19] INTERNET DRAFT RAQMON MIB January 2003 ::= { raqmonSessionExceptionTable 1 } RaqmonSessionExceptionEntry ::= SEQUENCE { raqmonSessionExceptionIndex INTEGER, raqmonSessionExceptionJitterThreshold Unsigned32, raqmonSessionExceptionRttThreshold Unsigned32, raqmonSessionExceptionLostPacketsThreshold Integer32, raqmonSessionExceptionRowStatus RowStatus } raqmonSessionExceptionIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index that uniquely identifies an entry in the raqmonSessionExceptionTable." ::= { raqmonSessionExceptionEntry 2 } raqmonSessionExceptionJitterThreshold OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "Threshold for jitter in units of milliseconds. The value during a session must be greater than or equal to this value for an exception to be created." ::= { raqmonSessionExceptionEntry 3 } raqmonSessionExceptionRttThreshold OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "Threshold for round trip time in units of milliseconds. The value during a session must be greater than or equal to this value for an exception to be created." ::= { raqmonSessionExceptionEntry 4 } raqmonSessionExceptionLostPacketsThreshold OBJECT-TYPE SYNTAX Integer32 (0..1000) MAX-ACCESS read-write RMON MIB WG Expires July 2003 [Page 20] INTERNET DRAFT RAQMON MIB January 2003 STATUS current DESCRIPTION "Threshold for lost packets in units of tenth of a percent. The value during a session must be greater than or equal to this value for an exception to be created." ::= { raqmonSessionExceptionEntry 5 } raqmonSessionExceptionRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Value of 'active' when exceptions are being monitored by the system. A newly-created conceptual row must have the all read-create objects initialized before becoming 'active'. A conceptual row that is in the 'notReady' or 'notInService' state MAY be removed after 5 minutes." ::= { raqmonSessionExceptionEntry 7 } raqmonConfig OBJECT IDENTIFIER ::= { raqmonMIBObjects 3 } raqmonConfigPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-write STATUS current DESCRIPTION "The UDP port to listen on for RAQMON reports." ::= { raqmonConfig 1 } raqmonConfigPDUTransport OBJECT-TYPE SYNTAX BITS { other(0), rtcp(1), snmp(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The PDU transport used by this collector. If rtcp(1) is set, the collector supports RTCP transport If snmp(2) is set, the collector supports SNMP transport." RMON MIB WG Expires July 2003 [Page 21] INTERNET DRAFT RAQMON MIB January 2003 ::= { raqmonConfig 2 } -- editor note: does this need to be read-write? Can a collector support -- multiple transports simultaneously? raqmonConfigRaqmonPDUs OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Count of RAQMON PDUs received by the Collector." ::= { raqmonConfig 3 } -- RAQMON PDU Definition raqmonPDU OBJECT IDENTIFIER ::= { raqmonMIBObjects 4 } raqmonPDUBasicPDU OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "A binary representationof the Basic RAQMON PDU," REFERENCE "[SIDDIQUI2]" ::= { raqmonPDU 1 } raqmonConformance OBJECT IDENTIFIER ::= { raqmon 2 } raqmonGroups OBJECT IDENTIFIER ::= { raqmonConformance 1 } raqmonCollectorGroup OBJECT-GROUP OBJECTS { raqmonParticipantStartDate, raqmonParticipantIndex, raqmonParticipantAddr, raqmonParticipantSendPort, raqmonParticipantRecvPort, raqmonParticipantSetupDelay, raqmonParticipantName, raqmonParticipantTool, raqmonParticipantQosCount, raqmonParticipantEndDate, raqmonParticipantRcvdPT, raqmonParticipantSentPT, raqmonParticipantActive, raqmonParticipantPeerIndex, raqmonParticipantPeerAddr, raqmonParticipantSrcLayer2, RMON MIB WG Expires July 2003 [Page 22] INTERNET DRAFT RAQMON MIB January 2003 raqmonParticipantDestLayer2, raqmonParticipantSrcLayer3, raqmonParticipantDestLayer3, raqmonParticipantCPUMean, raqmonParticipantCPUMin, raqmonParticipantCPUMax, raqmonParticipantMemoryMean, raqmonParticipantMemoryMin, raqmonParticipantMemoryMax, raqmonParticipantRTTMean, raqmonParticipantRTTMin, raqmonParticipantRTTMax, raqmonParticipantJitterMean, raqmonParticipantJitterMin, raqmonParticipantJitterMax, raqmonParticipantPackets, raqmonParticipantLostPackets, raqmonQosTime,raqmonQosRTT, raqmonQosJitter, raqmonQosRcvdPackets, raqmonQosRcvdOctets, raqmonQosSentPackets, raqmonQosSentOctets, raqmonQosLostPackets, raqmonQosRsvpStatus, raqmonParticipantAddrEndDate, raqmonConfigPort, raqmonSessionExceptionIndex, raqmonSessionExceptionJitterThreshold, raqmonSessionExceptionRttThreshold, raqmonSessionExceptionLostPacketsThreshold, raqmonSessionExceptionRowStatus, raqmonConfigPDUTransport, raqmonConfigRaqmonPDUs } STATUS current DESCRIPTION "Objects used in RAQMON by a Collector" ::= { raqmonGroups 1 } raqmonCollectorNotifications NOTIFICATION-GROUP NOTIFICATIONS { raqmonSessionAlarm } STATUS current DESCRIPTION "Description." ::= { raqmonGroups 2 } raqmonDeviceGroup OBJECT-GROUP OBJECTS { RMON MIB WG Expires July 2003 [Page 23] INTERNET DRAFT RAQMON MIB January 2003 raqmonPDUBasicPDU } STATUS current DESCRIPTION "Objects by a device to generate Notifications, for RAQMON SNMP Transport." ::= { raqmonGroups 3 } raqmonDeviceNotifications NOTIFICATION-GROUP NOTIFICATIONS { raqmonSNMPTransportNotofication } STATUS current DESCRIPTION "Description." ::= { raqmonGroups 4 } END 6. Normative References [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2819] Waldbusser, S., "Remote Network Monitoring Management Information Base", STD 59, RFC 2819, May 2000 7. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. RMON MIB WG Expires July 2003 [Page 24] INTERNET DRAFT RAQMON MIB January 2003 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [SIDDIQUI1] A. Siddiqui, D.Romascanu, E. Golovinsky, and R. Smith, RMON MIB WG Expires July 2003 [Page 25] INTERNET DRAFT RAQMON MIB January 2003 "Real-time Application Quality of Service Monitoring (RAQMON) MIB", Internet-Draft, draft-siddiqui-rmonmib-raqmon-mib-01.txt, February 2002 [SIDDIQUI2] A. Siddiqui, D.Romascanu, E. Golovinsky, and R. Smith, "Framework for Real-time Application Quality of Service Monitoring (RAQMON)", Internet-Draft, draft-siddiqui-raqmon- framework-00.txt, October 2002 [SIDDIQUI3] A. Siddiqui, D.Romascanu, E. Golovinsky, and R. Smith, "Protocol Data Units for Real-time Application Quality of Service Monitoring (RAQMON)", Internet-Draft, draft-siddiqui-raqmon-pdu- 00.txt, October 2002 8. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 9. Security Considerations There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. There are a number of managed objects in this MIB that may contain RMON MIB WG Expires July 2003 [Page 26] INTERNET DRAFT RAQMON MIB January 2003 sensitive information. These are: raqmonParticipantAddr It is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is RECOMMENDED that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model [RFC2274] and the View-based Access Control Model [RFC2275] is RECOMMENDED. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 10. Authors' Addresses Anwar A. Siddiqui Avaya Labs 307 Middletown Lincroft Road Lincroft, New Jersey 07738 USA Tel: +1 732 852-3200 Fax: +1 732 817-5922 E-mail: anwars@avaya.com Dan Romascanu Avaya Inc. Atidim Technology Park, Bldg. #3 Tel Aviv, 61131 Israel Tel: +972-3-645-8414 Email: dromasca@avaya.com RMON MIB WG Expires July 2003 [Page 27] INTERNET DRAFT RAQMON MIB January 2003 Richard Smith Avaya Inc. 123 Epping Rd North Ryde NSW 2113 Australia Tel: +61 2 9886 8987 Email: rsmith9@avaya.com Eugene Golovinsky BMC Software 2101 CityWest Blvd. Houston, Texas 77042 USA Tel: +1 713 918-1816 Email: eugene_golovinsky@bmc.com A. Full Copyright Statement This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. B. Log of Changes (This section will be removed prior to publication as RFC) B1. Changes in draft-siddiqui-rmonmib-raqmon-mib-02.txt RMON MIB WG Expires July 2003 [Page 28] INTERNET DRAFT RAQMON MIB January 2003 - changed OID of raqmonSessionAlarm - clarifications in DESCRIPTION clauses - changed raqmonParticpantActive SYNTAX to TruthValue - change range of raqmonParticipantSrcLayer2 and raqmonParticipantDestLayer2 to (0..7) - changed raqmonParticipantSrcLayer3 and raqmonParticipantDestLayer3 to Dscp - changed counters SYNTAX to Counter32 - added raqmonConfigPDUTransport and raqmonConfigRaqmonPDUs - added raqmonPDUBasicPDU and raqmonSNMPTransportNotofication - changed raqmonConformace to reflect the different conformace requirements for collectors and RAQMON devices B2. Changes in draft-ietf-rmon-raqmon-mib-00.txt - changed MAX-ACCESS clause of read-write objects in raqmonParticpantTable to read-only - changed syntax of raqmonConfigPDUTransport to BITS - changed document boulerplate - divided references in normative and informative RMON MIB WG Expires July 2003 [Page 29]