One document matched: draft-ietf-rmonmib-raqmon-mib-04.txt
Differences from draft-ietf-rmonmib-raqmon-mib-03.txt
Internet Draft Anwar Siddiqui
Avaya Inc.
Dan Romascanu
Avaya
Eugene Golovinsky
BMC Software
13 June 2004
Real-time Application Quality of Service
Monitoring (RAQMON) MIB
<draft-ietf-rmonmib-raqmon-mib-04.txt>
Status of this Memo
By submitting this Internet-Draft, we certify that any applicable
patent or other IPR claims of which we are aware have been disclosed,
and any of which we become aware will be disclosed, in accordance
with RFC 3668.
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 (2004). 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 - RFC
2819. In particular, it describes managed objects used for real-time
application Quality of Service (QoS) monitoring.
RMON MIB WG Expires December 2004 [Page 1]
INTERNET DRAFT RAQMON MIB June 2004
Distribution of this memo is unlimited.
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 3
5 RAQMON MIB Definitions 3
6 Security Considerations 28
7 Acknowledgements 29
Normative References 29
Informative References 30
Author's Address 30
Full Copyright Statement 30
Intellectual Property 31
Log of Changes 31
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 extends [RFC2819] with managed objects used for
real-time application QOS monitoring.
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
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].
RMON MIB WG Expires December 2004 [Page 2]
INTERNET DRAFT RAQMON MIB June 2004
3. RAQMON Framework
As outlined in [RAQMON-FRAMEWORK], the RAQMON framework is based on
three entities:
- RAQMON Data Source (RDS)
- RAQMON Report Collector (RRC)
- RAQMON MIB Structure
The RAQMON MIB describes information passed between RRCs and a RAQMON
Application ("RAQMON manager").
4. Structure of the RAQMON MIB
The RAQMON MIB module is composed of three MIB groups: raqmonSession,
raqmonException, and raqmonConfig.
The raqmonSession MIB group incorporates the following tables:
- the raqmonParticpantTable contains information about
participants in open and closed (terminated) sessions
- the raqmonQosTable contains historical information about QoS
during sessions
- the raqmonParticpantAddrTable maps particpant addresses into the
indexes 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 Report Collector.
This MIB module would normally be implemented by RAQMON Report
Collectors.
A separate MIB module is defined by [RAQMON-PDU] for mapping the
RAQMON PDUs onto an SNMP transport. The MIB module defined in
[RAQMON-PDU] is normally implemented by RAQMON Data Sources (RDS).
5. RAQMON MIB Definitions
RAQMON-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-GROUP, NOTIFICATION-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
RMON MIB WG Expires December 2004 [Page 3]
INTERNET DRAFT RAQMON MIB June 2004
Integer32, Unsigned32,
Gauge32, Counter32, OBJECT-TYPE,
MODULE-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI
InetAddressType, InetAddress
FROM INET-ADDRESS-MIB
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB
rmon
FROM RMON-MIB
RowStatus, TruthValue, DateAndTime, RowPointer
FROM SNMPv2-TC
Dscp
FROM DIFFSERV-DSCP-TC;
raqmon MODULE-IDENTITY
LAST-UPDATED "200406130000Z" -- June 13, 2004
ORGANIZATION
"IETF RMON MIB Working Group"
CONTACT-INFO
"WG Charter:
http://www.ietf.org/html.charters/rmonmib-charter.html
Mailing lists:
General Discussion: rmonmib@ietf.org
To Subscribe: rmonmib-requests@ietf.org
In Body: subscribe your_email_address
Chair: Andy Bierman
Cisco Inc.
Email: abierman@cisco.com
Editor: Dan Romascanu
Avaya
Email: dromasca@avaya.com"
DESCRIPTION
"Real-Time Application QoS Monitoring MIB.
Copyright (c) The Internet Society (2004).
This version of this MIB module is part of
RFC yyyy; See the RFC itself for full legal notices."
-- RFC Ed.: replace yyyy with the actual RFC
-- number & remove this notice.
REVISION "200406130000Z"
DESCRIPTION
"Initial version, published as RFC yyyy."
RMON MIB WG Expires December 2004 [Page 4]
INTERNET DRAFT RAQMON MIB June 2004
-- RFC-Editor assigns yyyy
::= { rmon 31 }
--
-- 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 }
raqmonMIBObjects OBJECT IDENTIFIER ::= { raqmon 1 }
raqmonSession OBJECT IDENTIFIER ::= { raqmonMIBObjects 1 }
raqmonParticipantTable OBJECT-TYPE
SYNTAX SEQUENCE OF RaqmonParticipantEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains information about participants in
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 }
RMON MIB WG Expires December 2004 [Page 5]
INTERNET DRAFT RAQMON MIB June 2004
RaqmonParticipantEntry ::=
SEQUENCE {
raqmonParticipantStartDate DateAndTime,
raqmonParticipantIndex Unsigned32,
raqmonParticipantReportCaps BITS,
raqmonParticipantAddrType InetAddressType,
raqmonParticipantAddr InetAddress,
raqmonParticipantSendPort Unsigned32,
raqmonParticipantRecvPort Unsigned32,
raqmonParticipantSetupDelay Unsigned32,
raqmonParticipantName SnmpAdminString,
raqmonParticipantTool SnmpAdminString,
raqmonParticipantQosCount Gauge32,
raqmonParticipantEndDate DateAndTime,
raqmonParticipantRcvdPT Unsigned32,
raqmonParticipantSentPT Unsigned32,
raqmonParticipantActive TruthValue,
raqmonParticipantPeer RowPointer,
raqmonParticipantPeerAddrType InetAddressType,
raqmonParticipantPeerAddr InetAddress,
raqmonParticipantSrcLayer2 Unsigned32,
raqmonParticipantDestLayer2 Unsigned32,
raqmonParticipantSrcLayer3 Dscp,
raqmonParticipantDestLayer3 Dscp,
raqmonParticipantCpuMean Unsigned32,
raqmonParticipantCpuMin Unsigned32,
raqmonParticipantCpuMax Unsigned32,
raqmonParticipantMemoryMean Unsigned32,
raqmonParticipantMemoryMin Unsigned32,
raqmonParticipantMemoryMax Unsigned32,
raqmonParticipantRttMean Gauge32,
raqmonParticipantRttMin Gauge32,
raqmonParticipantRttMax Gauge32,
raqmonParticipantJitterType INTEGER,
raqmonParticipantJitterMean Gauge32,
raqmonParticipantJitterMin Gauge32,
raqmonParticipantJitterMax Gauge32,
raqmonParticipantOwdMean Gauge32,
raqmonParticipantOwdMin Gauge32,
raqmonParticipantOwdMax Gauge32,
raqmonParticipantPackets Counter32,
raqmonParticipantLostPackets Counter32,
raqmonParticipantSrcPayloadType Unsigned32,
raqmonParticipantDestPayloadType Unsigned32
}
raqmonParticipantStartDate OBJECT-TYPE
SYNTAX DateAndTime
RMON MIB WG Expires December 2004 [Page 6]
INTERNET DRAFT RAQMON MIB June 2004
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 Unsigned32
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 be created or
maintained sequentially. The index will be unique for a
particular date and time."
::= { raqmonParticipantEntry 2 }
raqmonParticipantReportCaps OBJECT-TYPE
SYNTAX BITS {
raqmonPartReportDsrcName(0),
raqmonPartReportRecvName(1),
raqmonPartReportDsrcPort(2),
raqmonPartReportRecvPort(3),
raqmonPartReportSetupTime(4),
raqmonPartReportSetupDelay(5),
raqmonPartReportSessionDuration(6),
raqmonPartReportSetupStatus(7),
raqmonPartReportRtt(8),
raqmonPartReportOwd(9),
raqmonPartReportJitter(10),
raqmonPartReportRcvdPackets(11),
raqmonPartReportRcvdOctets(12),
raqmonPartReportSentPackets(13),
raqmonPartReportSentOctets(14),
raqmonPartReportCumPacketsLoss(15),
raqmonPartReportFractionPacketsLoss(16),
raqmonPartReportSrcPayloadType(17),
raqmonPartReportDestpayloadType(18),
raqmonPartReportSrcLayer2Priority(19),
raqmonPartReportSrcTosDscp(20),
raqmonPartReportDestLayer2Priority(21),
raqmonPartReportDestTosDscp(22),
raqmonPartReportCPU(23),
raqmonPartReportMemory(24),
RMON MIB WG Expires December 2004 [Page 7]
INTERNET DRAFT RAQMON MIB June 2004
raqmonPartReportAppName(25)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Report capabilities of the participant, as
perceived by the Collector.
If the participant can report the Data Source Name
as defined in [RAQMON-FRAMEWORK], Section 5.3,
then the raqmonPartReportDsrcName bit will be set.
If the participant can report the Receiver Name
as defined in [RAQMON-FRAMEWORK], Section 5.4,
then the raqmonPartReportRecvName bit will be set.
If the participant can report the Data Source Port
as defined in [RAQMON-FRAMEWORK], Section 5.5,
then the raqmonPartReportDsrcPort bit will be set.
If the participant can report the Receiver Port
as defined in [RAQMON-FRAMEWORK], Section 5.6,
then the raqmonPartReportRecvPort bit will be set.
If the participant can report the Session Setup Time
as defined in [RAQMON-FRAMEWORK], Section 5.7,
then the raqmonPartReportSetupTime bit will be set.
If the participant can report the Session Setup Delay
as defined in [RAQMON-FRAMEWORK], Section 5.8,
then the raqmonPartReportSetupDelay bit will be set.
If the participant can report the Session Duration
as defined in [RAQMON-FRAMEWORK], Section 5.9,
then the raqmonPartReportSessionDuration bit will be set.
If the participant can report the Setup Status
as defined in [RAQMON-FRAMEWORK], Section 5.10,
then the raqmonPartReportSetupStatus bit will be set.
If the participant can report the Round-Trip
End-to-end Delay
as defined in [RAQMON-FRAMEWORK], Section 5.11,
then the raqmonPartReportRtt bit will be set.
If the participant can report the One-way
End-to-end Delay
as defined in [RAQMON-FRAMEWORK], Section 5.12,
RMON MIB WG Expires December 2004 [Page 8]
INTERNET DRAFT RAQMON MIB June 2004
then the raqmonPartReportDsrcOwd bit will be set.
If the participant can report the Jitter
as defined in [RAQMON-FRAMEWORK], Section 5.13,
then the raqmonPartReportJitter bit will be set.
If the participant can report the number of application
packets received
as defined in [RAQMON-FRAMEWORK], Section 5.14,
then the raqmonPartReportRcvdPackets bit will be set.
If the participant can report the number of application
octets received
as defined in [RAQMON-FRAMEWORK], Section 5.15,
then the raqmonPartReportRcvdOctets bit will be set.
If the participant can report the number of application
packets sent
as defined in [RAQMON-FRAMEWORK], Section 5.16,
then the raqmonPartReportSentPackets bit will be set.
If the participant can report the number of application
octets sent
as defined in [RAQMON-FRAMEWORK], Section 5.17,
then the raqmonPartReportSentOctets bit will be set.
If the participant can report the number of
cumulative packets lost
as defined in [RAQMON-FRAMEWORK], Section 5.18,
then the raqmonPartReportCumPacketsLoss bit will be set.
If the participant can report the fraction of packets loss
as defined in [RAQMON-FRAMEWORK], Section 5.19,
then the raqmonPartReportFractionPacketsLoss bit will be set.
If the participant can report the Source Payload Type
as defined in [RAQMON-FRAMEWORK], Section 5.20,
then the raqmonPartReportSrcPayloadType bit will be set.
If the participant can report the Destination Payload Type
as defined in [RAQMON-FRAMEWORK], Section 5.21,
then the raqmonPartReportDestPayloadType bit will be set.
If the participant can report the Source layer 2 Priority
as defined in [RAQMON-FRAMEWORK], Section 5.22,
then the raqmonPartReportSrcLayer2Priority bit will be set.
If the participant can report the Source DSCP/ToS value
RMON MIB WG Expires December 2004 [Page 9]
INTERNET DRAFT RAQMON MIB June 2004
as defined in [RAQMON-FRAMEWORK], Section 5.23,
then the raqmonPartReportSrcToSDscp bit will be set.
If the participant can report the Destination layer 2 Priority
as defined in [RAQMON-FRAMEWORK], Section 5.24,
then the raqmonPartReportDestLayer2Priority bit will be set.
If the participant can report the Destination DSCP/ToS value
as defined in [RAQMON-FRAMEWORK], Section 5.25,
then the raqmonPartReportDestToSDscp bit will be set.
If the participant can report the CPU utilization
as defined in [RAQMON-FRAMEWORK], Section 5.26,
then the raqmonPartReportCPU bit will be set.
If the participant can report the memory utilization
as defined in [RAQMON-FRAMEWORK], Section 5.27,
then the raqmonPartReportMemory bit will be set.
If the participant can report the Application Name
as defined in [RAQMON-FRAMEWORK], Section 5.28,
then the raqmonPartReportAppName bit will be set."
::= { raqmonParticipantEntry 3 }
raqmonParticipantAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the Internet address of the participant for
this session."
::= { raqmonParticipantEntry 4 }
raqmonParticipantAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Internet Address of the participant for this session."
::= { raqmonParticipantEntry 5 }
raqmonParticipantSendPort OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Port from which session data is sent."
RMON MIB WG Expires December 2004 [Page 10]
INTERNET DRAFT RAQMON MIB June 2004
REFERENCE
"Section 5.5 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 6 }
raqmonParticipantRecvPort OBJECT-TYPE
SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Port on which session data is received."
REFERENCE
"Section 5.6 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 7 }
raqmonParticipantSetupDelay OBJECT-TYPE
SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Session setup time."
REFERENCE
"Section 5.8 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 8 }
raqmonParticipantName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The data source name for the participant."
::= { raqmonParticipantEntry 9 }
raqmonParticipantTool OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A string giving the name and possibly the 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 10 }
RMON MIB WG Expires December 2004 [Page 11]
INTERNET DRAFT RAQMON MIB June 2004
raqmonParticipantQosCount OBJECT-TYPE
SYNTAX Gauge32
UNITS "entries"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current number of entries in the QOS history table
for this participant and session."
::= { raqmonParticipantEntry 11 }
raqmonParticipantEndDate OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The date and time of the most recent report received."
::= { raqmonParticipantEntry 12 }
raqmonParticipantRcvdPT OBJECT-TYPE
SYNTAX Unsigned32 (0..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Payload type of the received packets."
REFERENCE
"RFC 1890, Section 5.21 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 13 }
raqmonParticipantSentPT OBJECT-TYPE
SYNTAX Unsigned32 (0..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Payload type of sent packets."
REFERENCE
"RFC 1890, Section 5.20 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 14 }
raqmonParticipantActive OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Value 'true' indicates that the session
for this participant is active (open).
Value 'false' indicates that the session
is closed (terminated)."
::= { raqmonParticipantEntry 15 }
RMON MIB WG Expires December 2004 [Page 12]
INTERNET DRAFT RAQMON MIB June 2004
raqmonParticipantPeer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The pointer to the corresponding entry in this table for
the other peer participant. If there is no such entry in
the particpant table of the collector represented by this
SNMP agent, then the value will be { 0 0 }.
"
::= { raqmonParticipantEntry 16 }
raqmonParticipantPeerAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the Internet address of the peer participant
for this session."
::= { raqmonParticipantEntry 17 }
raqmonParticipantPeerAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Internet Address of the peer participant for this
session."
::= { raqmonParticipantEntry 18 }
raqmonParticipantSrcLayer2 OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Source Layer 2 priority."
REFERENCE
"Section 5.22 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 19 }
raqmonParticipantDestLayer2 OBJECT-TYPE
SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Destination Layer 2 priority."
REFERENCE
"Section 5.24 of the [RAQMON-FRAMEWORK]"
RMON MIB WG Expires December 2004 [Page 13]
INTERNET DRAFT RAQMON MIB June 2004
::= { raqmonParticipantEntry 20 }
raqmonParticipantSrcLayer3 OBJECT-TYPE
SYNTAX Dscp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Source Layer 3 DSCP value"
REFERENCE
"Section 5.23 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 21 }
raqmonParticipantDestLayer3 OBJECT-TYPE
SYNTAX Dscp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Destination Layer 3 DSCP value"
REFERENCE
"Section 5.25 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 22 }
raqmonParticipantCpuMean OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
UNITS "percents"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Mean CPU utilization."
REFERENCE
"Section 5.26 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 23 }
raqmonParticipantCpuMin OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
UNITS "percents"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Minimum CPU utilization."
REFERENCE
"Section 5.26 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 24 }
raqmonParticipantCpuMax OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
UNITS "percents"
MAX-ACCESS read-only
RMON MIB WG Expires December 2004 [Page 14]
INTERNET DRAFT RAQMON MIB June 2004
STATUS current
DESCRIPTION
"Maximum CPU utilization."
REFERENCE
"Section 5.26 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 25 }
raqmonParticipantMemoryMean OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
UNITS "percents"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Mean memory utilization."
REFERENCE
"Section 5.27 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 26 }
raqmonParticipantMemoryMin OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
UNITS "percents"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Minimum memory utilization."
REFERENCE
"Section 5.27 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 27 }
raqmonParticipantMemoryMax OBJECT-TYPE
SYNTAX Unsigned32 (0..100)
UNITS "percents"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Maximum memory utilization."
REFERENCE
"Section 5.27 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 28 }
raqmonParticipantRttMean OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Mean round trip time (RTT) over the entire session."
REFERENCE
RMON MIB WG Expires December 2004 [Page 15]
INTERNET DRAFT RAQMON MIB June 2004
"Section 5.11 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 29 }
raqmonParticipantRttMin OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Minimum round trip time (RTT) over the entire session."
REFERENCE
"Section 5.11 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 30 }
raqmonParticipantRttMax OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Maximum round trip time (RTT) over the entire session."
REFERENCE
"Section 5.11 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 31 }
raqmonParticipantJitterType OBJECT-TYPE
SYNTAX INTEGER
{
interArrival(1),
absolute(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Jitter type used in reporting jitter values."
REFERENCE
"Section 5.13 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 32 }
raqmonParticipantJitterMean OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Mean jitter over the entire session."
REFERENCE
"Section 5.13 of the [RAQMON-FRAMEWORK]"
RMON MIB WG Expires December 2004 [Page 16]
INTERNET DRAFT RAQMON MIB June 2004
::= { raqmonParticipantEntry 33 }
raqmonParticipantJitterMin OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Minimum jitter over the entire session."
REFERENCE
"Section 5.13 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 34 }
raqmonParticipantJitterMax OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Maximim jitter over the entire session."
REFERENCE
"Section 5.13 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 35 }
raqmonParticipantOwdMean OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Mean one way delay (OWD) over the entire session."
REFERENCE
"Section 5.12 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 36 }
raqmonParticipantOwdMin OBJECT-TYPE
SYNTAX Gauge32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Minimum one way delay (OWD) over the entire session."
REFERENCE
"Section 5.12 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 37 }
raqmonParticipantOwdMax OBJECT-TYPE
SYNTAX Gauge32
RMON MIB WG Expires December 2004 [Page 17]
INTERNET DRAFT RAQMON MIB June 2004
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Maximum one way delay (OWD) over the entire session."
REFERENCE
"Section 5.12 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 38 }
raqmonParticipantPackets OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of packets received for the entire session."
REFERENCE
"Section 5.14 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 39 }
raqmonParticipantLostPackets OBJECT-TYPE
SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of packets lost by this receiver for the entire
session."
REFERENCE
"Section 5.18 of the [RAQMON-FRAMEWORK]"
::= { raqmonParticipantEntry 40 }
raqmonParticipantSrcPayloadType OBJECT-TYPE
SYNTAX Unsigned32 (0..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The payload type of the packet sent by this RD."
REFERENCE
"RFC 1890, Section 5.20 of the [RAQMON-FRAMEWORK] "
::= { raqmonParticipantEntry 41 }
raqmonParticipantDestPayloadType OBJECT-TYPE
SYNTAX Unsigned32 (0..127)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The payload type of the packet received by this RD."
RMON MIB WG Expires December 2004 [Page 18]
INTERNET DRAFT RAQMON MIB June 2004
REFERENCE
"RFC 1890, Section 5.21 of the [RAQMON-FRAMEWORK] "
::= { raqmonParticipantEntry 42 }
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 Unsigned32,
raqmonQosRtt Integer32,
raqmonQosJitter Integer32,
raqmonQosRcvdPackets Integer32,
raqmonQosRcvdOctets Integer32,
raqmonQosSentPackets Integer32,
raqmonQosSentOctets Integer32,
raqmonQosLostPackets Integer32,
raqmonQosSessionStatus SnmpAdminString
}
raqmonQosTime OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Time of this entry measured from the start of the
corresponding participant session.
RMON MIB WG Expires December 2004 [Page 19]
INTERNET DRAFT RAQMON MIB June 2004
"
::= { raqmonQosEntry 1 }
raqmonQosRtt OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
UNITS "milliseconds"
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 -1 if the value has never
been reported.
"
REFERENCE
"Section 5.10 of the [RAQMON-FRAMEWORK]"
::= { raqmonQosEntry 2 }
raqmonQosJitter OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
UNITS "milliseconds"
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 -1 if the value
has never been reported.
"
REFERENCE
"Section 5.13 of the [RAQMON-FRAMEWORK]"
::= { raqmonQosEntry 3 }
raqmonQosRcvdPackets OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of packets received by this receiver since the
previous entry. Will contain the previous value if there
was no report for this time, or -1 if the value
has never been reported.
"
REFERENCE
"Section 5.14 of the [RAQMON-FRAMEWORK]"
::= { raqmonQosEntry 4 }
RMON MIB WG Expires December 2004 [Page 20]
INTERNET DRAFT RAQMON MIB June 2004
raqmonQosRcvdOctets OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of octets received by this receiver since the
previous report. Will contain the previous value if
there was no report for this time, or -1 if the value
has never been reported.
"
REFERENCE
"Section 5.16 of the [RAQMON-FRAMEWORK]"
::= { raqmonQosEntry 5 }
raqmonQosSentPackets OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
UNITS "packets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of packets sent since the previous report.
Will contain the previous value if there
was no report for this time, or -1 if the value
has never been reported.
"
REFERENCE
"Section 5.15 of the [RAQMON-FRAMEWORK]"
::= { raqmonQosEntry 6 }
raqmonQosSentOctets OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
UNITS "octets"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Count of octets sent since the previous report.
Will contain the previous value if there
was no report for this time, or -1 if the value
has never been reported.
"
REFERENCE
"Section 5.17 of the [RAQMON-FRAMEWORK]"
::= { raqmonQosEntry 7 }
raqmonQosLostPackets OBJECT-TYPE
SYNTAX Integer32 (-1 | 0..2147483647)
UNITS "packets"
RMON MIB WG Expires December 2004 [Page 21]
INTERNET DRAFT RAQMON MIB June 2004
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of packets lost as observed by this receiver
since the Will contain the previous value if there
was no report for this time, or -1 if the value
has never been reported.
"
REFERENCE
"Section 5.18 of the [RAQMON-FRAMEWORK]"
::= { raqmonQosEntry 8 }
raqmonQosSessionStatus OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The session status. Will contain the previous value
if there was no report for this time or the null string
if no value was ever reported)."
REFERENCE
"Section 5.10 of the [RAQMON-FRAMEWORK]"
::= { 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
STATUS current
DESCRIPTION
"Each entry corresponds to exactly one entry in the
raqmonParticipantEntry - the entry containing the
index pair rraqmonParticipantStartDate,
raqmonParticipantIndex.
Note that there is no concern about the indexation of this
RMON MIB WG Expires December 2004 [Page 22]
INTERNET DRAFT RAQMON MIB June 2004
table exceeding the limits defined by RFC 2578 Section 3.5.
According to [RAQMON-FRAMEWORK], Section 5.1, only IPv4 and
IPv6 addresses can be reported as participant addresses."
INDEX { raqmonParticipantAddr,
raqmonParticipantStartDate,
raqmonParticipantIndex }
::= { raqmonParticipantAddrTable 1 }
RaqmonParticipantAddrEntry ::=
SEQUENCE { raqmonParticipantAddrEndDate DateAndTime }
raqmonParticipantAddrEndDate OBJECT-TYPE
SYNTAX DateAndTime
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 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 }
::= { raqmonSessionExceptionTable 1 }
RaqmonSessionExceptionEntry ::=
SEQUENCE {
raqmonSessionExceptionIndex Unsigned32,
raqmonSessionExceptionJitterThreshold Unsigned32,
raqmonSessionExceptionRttThreshold Unsigned32,
raqmonSessionExceptionLostPacketsThreshold Unsigned32,
RMON MIB WG Expires December 2004 [Page 23]
INTERNET DRAFT RAQMON MIB June 2004
raqmonSessionExceptionRowStatus RowStatus
}
raqmonSessionExceptionIndex OBJECT-TYPE
SYNTAX Unsigned32 (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
UNITS "milliseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Threshold for jitter.
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
UNITS "milliseconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Threshold for round trip time.
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 Unsigned32 (0..1000)
UNITS "tenth of a percent"
MAX-ACCESS read-create
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
RMON MIB WG Expires December 2004 [Page 24]
INTERNET DRAFT RAQMON MIB June 2004
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object has a 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,
running on other transport protocols than SNMP.
If the RAQMON PDU transport protocol is SNMP,
a write operation on this object has no effect, as
the standard port 162 is always used"
::= { raqmonConfig 1 }
raqmonConfigPduTransport OBJECT-TYPE
SYNTAX BITS
{
other(0),
snmp(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The PDU transport(s) used by this collector.
If other(0) is set, the collector supports a
transport other than SNMP.
If snmp(1) is set, the collector supports SNMP as a
transport protocol."
::= { raqmonConfig 2 }
raqmonConfigRaqmonPdus OBJECT-TYPE
SYNTAX Counter32
UNITS "PDUs"
MAX-ACCESS read-only
RMON MIB WG Expires December 2004 [Page 25]
INTERNET DRAFT RAQMON MIB June 2004
STATUS current
DESCRIPTION
"Count of RAQMON PDUs received by the Collector."
::= { raqmonConfig 3 }
raqmonConformance OBJECT IDENTIFIER ::= { raqmon 2 }
raqmonCompliances OBJECT IDENTIFIER ::= { raqmonConformance 1 }
raqmonGroups OBJECT IDENTIFIER ::= { raqmonConformance 2 }
raqmonCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the
RAQMON MIB."
MODULE -- this module
MANDATORY-GROUPS { raqmonCollectorGroup,
raqmonCollectorNotificationsGroup
}
::= { raqmonCompliances 1 }
raqmonCollectorGroup OBJECT-GROUP
OBJECTS {
raqmonParticipantReportCaps,
raqmonParticipantAddrType,
raqmonParticipantAddr,
raqmonParticipantSendPort,
raqmonParticipantRecvPort,
raqmonParticipantSetupDelay,
raqmonParticipantName,
raqmonParticipantTool,
raqmonParticipantQosCount,
raqmonParticipantEndDate,
raqmonParticipantRcvdPT,
raqmonParticipantSentPT,
raqmonParticipantActive,
raqmonParticipantPeer,
raqmonParticipantPeerAddrType,
raqmonParticipantPeerAddr,
raqmonParticipantSrcLayer2,
raqmonParticipantDestLayer2,
raqmonParticipantSrcLayer3,
raqmonParticipantDestLayer3,
raqmonParticipantCpuMean,
raqmonParticipantCpuMin,
RMON MIB WG Expires December 2004 [Page 26]
INTERNET DRAFT RAQMON MIB June 2004
raqmonParticipantCpuMax,
raqmonParticipantMemoryMean,
raqmonParticipantMemoryMin,
raqmonParticipantMemoryMax,
raqmonParticipantRttMean,
raqmonParticipantRttMin,
raqmonParticipantRttMax,
raqmonParticipantJitterType,
raqmonParticipantJitterMean,
raqmonParticipantJitterMin,
raqmonParticipantJitterMax,
raqmonParticipantOwdMean,
raqmonParticipantOwdMin,
raqmonParticipantOwdMax,
raqmonParticipantPackets,
raqmonParticipantLostPackets,
raqmonParticipantSrcPayloadType,
raqmonParticipantDestPayloadType,
raqmonQosRtt,
raqmonQosJitter,
raqmonQosRcvdPackets,
raqmonQosRcvdOctets,
raqmonQosSentPackets,
raqmonQosSentOctets,
raqmonQosLostPackets,
raqmonQosSessionStatus,
raqmonParticipantAddrEndDate,
raqmonConfigPort,
raqmonSessionExceptionJitterThreshold,
raqmonSessionExceptionRttThreshold,
raqmonSessionExceptionLostPacketsThreshold,
raqmonSessionExceptionRowStatus,
raqmonConfigPduTransport,
raqmonConfigRaqmonPdus }
STATUS current
DESCRIPTION
"Objects used in RAQMON by a Collector"
::= { raqmonGroups 1 }
raqmonCollectorNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { raqmonSessionAlarm }
STATUS current
DESCRIPTION
"Notifications emitted by a RAQMON collector."
::= { raqmonGroups 2 }
END
RMON MIB WG Expires December 2004 [Page 27]
INTERNET DRAFT RAQMON MIB June 2004
6. Security Considerations
There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write. 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.
Setting the following object to incorrect values can result in
collectors either flooding the management applications with
unnecessary notifications, or not sending notifications when the
QoS in the network may be degraded.
raqmonSessionExceptionJitterThreshold
raqmonSessionExceptionRttThreshold
raqmonSessionExceptionLostPacketsThreshold
Setting the raqmonConfigPort object to incorrect values can result in the
collector not being able to receive RAQMON PDUs from the data sources.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. These are:
raqmonParticipantTable
raqmonQoSTable
raqmonParticpantAddrTable
Unauthorized exposure of these objects may lead to disclosure of the
addresses of the participants in applications, or information about
the traffic patents of the applications, which may be considered
sensitive in certain environments.
It is thus important to control even GET and/or NOTIFY access to
these objects and possibly to even encrypt their values when sending
them over the network via SNMP.
The structure of the RAQMON tables limits what can be usefully done
for access control configuration using VACM. For example, it would not
be possible with these structures to provide a group, with access to
performance data to a specific group of devices, since the index values
for raqmonParticpantEntry cannot be known in advance. Likewise,
raqmonSessionExceptionEntries apply to all entries in the
raqmonQoSTable.
SNMP versions prior to SNMPv3 did not include adequate security.
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
RMON MIB WG Expires December 2004 [Page 28]
INTERNET DRAFT RAQMON MIB June 2004
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module 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.
7. Acknowledgements
Richard Smith created the first proprietary version of this MIB.
The authors would also like to thank to all the participants in the
Remote Monitoring MIB Working Group, and especially to Andy Bierman,
Steven Waldbusser, Alan Clark, Itai Zilbershtein, and Robert Cole for
interesting discussions, ideas, comments and direct contributions
to this work.
The authors would also like to thank Randy Presuhn for the precious
technical comments, as well as for the laborious activity of reviewing
the syntax and spelling of the document.
Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
RMON MIB WG Expires December 2004 [Page 29]
INTERNET DRAFT RAQMON MIB June 2004
[RFC2819] Waldbusser, S., "Remote Network Monitoring Management
Information Base", STD 59, RFC 2819, May 2000.
[RAQMON-FRAMEWORK] A. Siddiqui, D.Romascanu, E. Golovinsky, and R.
Smith, "Framework for Real-time Application Quality of
Service Monitoring (RAQMON)", Internet-Draft,
draft-ietf-rmonmib-raqmon-framework-06.txt, June 2004.
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.
[RAQMON-PDU] A. Siddiqui, D.Romascanu, E. Golovinsky, and R. Smith,
"Protocol Data Units for Real-time Application Quality of
Service Monitoring (RAQMON)", Internet-Draft,
draft-ietf-rmonmib-raqmon-pdu-06.txt, June 2004.
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
Atidim Technology Park, Bldg. #3
Tel Aviv, 61131
Israel
Tel: +972 3-645-8414
Email: dromasca@avaya.com
Eugene Golovinsky
BMC Software
2101 CityWest Blvd.
Houston, Texas 77042
USA
Tel: +1 713 918-1816
Email: eugene_golovinsky@bmc.com
Full Copyright Statement
RMON MIB WG Expires December 2004 [Page 30]
INTERNET DRAFT RAQMON MIB June 2004
Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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."
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.
Log of Changes
(This section will be removed prior to publication as RFC)
Changes in draft-siddiqui-rmonmib-raqmon-mib-02.txt
- changed OID of raqmonSessionAlarm
- clarifications in DESCRIPTION clauses
- changed raqmonParticpantActive SYNTAX to TruthValue
- change range of raqmonParticipantSrcLayer2 and
raqmonParticipantDestLayer2 to (0..7)
RMON MIB WG Expires December 2004 [Page 31]
INTERNET DRAFT RAQMON MIB June 2004
- changed raqmonParticipantSrcLayer3 and raqmonParticipantDestLayer3
to Dscp
- changed counters SYNTAX to Counter32
- added raqmonConfigPDUTransport and raqmonConfigRaqmonPDUs
- added raqmonPDUBasicPDU and raqmonSNMPTransportNotofication
- changed raqmonConformance to reflect the different conformance
requirements for collectors and RAQMON devices
Changes in draft-ietf-rmonmib-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 boilerplate
- divided references in normative and informative
Changes in draft-ietf-rmonmib-raqmon-mib-01.txt
- took out RAQMON PDU definition, now part of [RAQMON-PDU}
- added one way delay objects
- modified SYNTAX of INTEGER objects, in accordance with MIB
guidelines
- re-wrote Security Considerations Section
Changes in draft-ietf-rmonmib-raqmon-mib-02.txt
- introduced REFERENCE clauses, synchronized with RAQMON Framework
- eliminated duplicate text and diagrams relative to the other RAQMON
documents
- fixed MAX-ACCESS of objects in raqmonSessionExceptionTable to read-
create
Changes in draft-ietf-rmonmib-raqmon-mib-03.txt
- introduced raqmonParticpantJitterType object
- changed raqmonQoSRsvpStatus to raqmonQoSSessionStatus
- IMPORT DateAndTime from SMIv2-TC
- Fixed MIB root, in the RMON registry
- re-edited copyright note, according to MIB review document
- various spelling edits
Changes in draft-ietf-rmonmib-raqmon-mib-04.txt
- numerous spelling and syntax edits
- use InetAddress and InetAddressType for objects describing IP
addresses
- use SnmpAddressString instead of Utf8String
- eliminate constraints, and use Unsigned32 as SYNTAX for
RMON MIB WG Expires December 2004 [Page 32]
INTERNET DRAFT RAQMON MIB June 2004
raqmonParticpantIndex
- add missing values, and detail each of the BITS functionality in
raqmonParticpantReportCaps
- rename some objects for better clarity
- add UNITS clause wherever applicable
- change SYNTAX of raqmonParticpantQosCount to Gauge32
- change SYNTAX of raqmonParticpantPeerIndex to RowPointer, and
rename
- change SYNTAX and range of objects in raqmonQoSTable
- clarify several DESCRIPTION clauses, including the ones of
raqmonQoSSessionStatus and raqmonConfigPort
- clarify indexation of raqmonParticipantAddressTable, to avoid
concerns about exceeding OID length limit
- explain VACM limitations with the RAQMON table in the security
considerations section
- modified the copyright and intellectual property notices in
accordance to RFC 3667 and RFC 3668.
RMON MIB WG Expires December 2004 [Page 33]
| PAFTECH AB 2003-2026 | 2026-04-24 04:46:55 |