draft-ietf-avt-rtcp-xr-mib-03.txt   draft-ietf-avt-rtcp-xr-mib-04.txt 
Audio/Video Working Group Alan Clark Audio/Video Working Group Alan Clark
Internet-Draft Telchemy Internet-Draft Telchemy
Expires: April 22, 2006 Amy Pendleton Expires: August 31, 2006 Amy Pendleton
Nortel Nortel
October 2005 March 2006
RTP Control Protocol Extended Reports (RTCP XR) RTP Control Protocol Extended Reports (RTCP XR)
VoIP Metrics Management Information Base VoIP Metrics Management Information Base
draft-ietf-avt-rtcp-xr-mib-03.txt draft-ietf-avt-rtcp-xr-mib-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 22, 2006. This Internet-Draft will expire on August 31, 2006.
This document is a product of the Audio-Visual Transport (AVT) This document is a product of the Audio-Visual Transport (AVT)
working group of the Internet Engineering Task Force. Comments are working group of the Internet Engineering Task Force. Comments are
solicited and should be addressed to the working group's mailing solicited and should be addressed to the working group's mailing
list at avt@ietf.org and/or the authors. list at avt@ietf.org and/or the authors.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
skipping to change at page 2, line 16 skipping to change at page 2, line 16
1. The Network Management Framework ............................. 2 1. The Network Management Framework ............................. 2
2. Overview ..................................................... 3 2. Overview ..................................................... 3
2.1 Components .................................................. 3 2.1 Components .................................................. 3
2.2 Applicability of the MIB to RTP System Implementations ...... 3 2.2 Applicability of the MIB to RTP System Implementations ...... 3
2.3 Relationship to the RTP MIB....................................3 2.3 Relationship to the RTP MIB....................................3
2.4 Relationship to the RAQMON Architecture...................... 3 2.4 Relationship to the RAQMON Architecture...................... 3
2.5 The Structure of the RTCP XR MIB ............................ 4 2.5 The Structure of the RTCP XR MIB ............................ 4
2.6 Application to multi-party and multicast calls .............. 4 2.6 Application to multi-party and multicast calls .............. 4
3 Definitions ................................................... 5 3 Definitions ................................................... 5
4. Security Considerations ...................................... 42 4. Security Considerations ...................................... 38
5. IANA Considerations .......................................... 42 5. IANA Considerations .......................................... 38
5. Acknowledgements ............................................. 42 5. Acknowledgements ............................................. 38
6. Intellectual Property ........................................ 43 6. Intellectual Property ........................................ 39
7. Normative References ......................................... 43 7. Normative References ......................................... 39
9. Informative References ....................................... 43 9. Informative References ....................................... 39
8. Authors' Addresses ........................................... 44 8. Authors' Addresses ........................................... 40
9. Full Copyright Statement ..................................... 44 9. Full Copyright Statement ..................................... 40
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 46 skipping to change at page 3, line 46
diagnose faults that occur over the lifetime of a VoIP session as in diagnose faults that occur over the lifetime of a VoIP session as in
a "help-desk" scenario. a "help-desk" scenario.
2.2.2 Monitors of RTP Voice over IP sessions may be third-party or 2.2.2 Monitors of RTP Voice over IP sessions may be third-party or
may be located in the RTP host. Monitors may use the RTCP XR MIB to may be located in the RTP host. Monitors may use the RTCP XR MIB to
collect Voice over IP session statistical data; these data may be collect Voice over IP session statistical data; these data may be
used by a network manager for planning and other network-management used by a network manager for planning and other network-management
purposes. A Monitor may use the RTCP XR MIB to collect data to purposes. A Monitor may use the RTCP XR MIB to collect data to
permit a network manager to diagnose faults in VoIP sessions. permit a network manager to diagnose faults in VoIP sessions.
2.3 Relationship to the RTP MIB 2.3 Relationship to the RTP MIB V2
The RTP MIB defines a session table, sender and receiver tables and
inverse tables to support fast location of session information.
The RTP MIB Version 2 [draft TBD] has a session table that is The RTP MIB V2 [draft-ietf-avt-mib-rtp-bis-00.txt] defines a table
identical to the session table in the RTCP XR MIB. This is intended of session identifying information. The tables in the RTCP XR MIB
to allow implementations that support both the RTP MIB V2 and the augment the session data from the RTP MIB V2, providing detailed
RTCP XR MIB to use a common session table. performance information for RTP sessions transporting Voice over
IP. The RTP MIB V2 session table MUST be implemented if the RTCP
XR MIB Basic Parameter and Call Quality tables are implemented.
The history table in this MIB contains aggregate information and
does not have any relationship to the RTP MIB V2 session table.
In implementations that use only the RTCP XR history table to
report aggregate data, the RTP MIB V2 session table MUST NOT be
implemented.
2.4 Relationship to the RAQMON Architecture 2.4 Relationship to the RAQMON Architecture
The Real-time Application QoS monitoring (RAQMON) Framework [xxx] The Real-time Application QoS monitoring (RAQMON) Framework [RAQMON]
defines an architecture that extends the Remote Monitoring (RMON) defines an architecture that extends the Remote Monitoring (RMON)
family of applications for monitoring of application QoS in real family of applications for monitoring of application QoS in real
time, and an extensible data model with objects carried between time, and an extensible data model with objects carried between
RAQMON data sources and RAQMON collectors. The RAQMON work is RAQMON data sources and RAQMON collectors. The RAQMON work is
more generic, and complementary in concept to RTCP-XR, covering a more generic, and complementary in concept to RTCP-XR, covering a
wider range of applications running concurrently, while RTCP-XR wider range of applications running concurrently, while RTCP-XR
focuses on in-depth QoS monitoring of media traffic in VoIP. focuses on in-depth QoS monitoring of media traffic in VoIP.
The Real-time Application QoS Monitoring (RAQMON) MIB is defined The Real-time Application QoS Monitoring (RAQMON) MIB is defined
by [xxx] and runs on RAQMON collectors. A performance monitoring by [xxx] and runs on RAQMON collectors. A performance monitoring
application may query (i) RAQMON collectors for RAQMON MIB application may query (i) RAQMON collectors for RAQMON MIB
information about the QoS parameters of multiple concurrent information about the QoS parameters of multiple concurrent
applications (ii) end-points and gateways for in-depth RTCP-XR applications (ii) end-points and gateways for in-depth RTCP-XR
information about the media QoS of VoIP or (iii) both. information about the media QoS of VoIP or (iii) both.
2.5 The Structure of the RTCP XR MIB 2.5 The Structure of the RTCP XR MIB
There are four tables in the RTCP XR MIB There are three tables in the RTCP XR MIB
The rtcpXrSessionIDtable contains identifying information about each
session and about the source and destination.
The rtcpXrBasicParametersTable contains basic packet loss, discard The rtcpXrBasicParametersTable contains basic packet loss, discard
and delay related parameters about a session. and delay related parameters about a session.
The rtcpXrVoiceQualityMetricSTable contains information about the The rtcpXrVoiceQualityMetricsTable contains information about the
call quality of a session call quality of a session
The rtcpXrHistoryTable contains aggregate information about a group The rtcpXrHistoryTable contains aggregate information about a group
of sessions. of sessions.
2.6 Application to multi-party and multicast calls 2.6 Application to multi-party and multicast calls
The RTCP XR MIB may be applied to multi-party calls. The Session The RTCP XR MIB may be applied to multi-party calls. The RTP MIB
table is defined in terms of uni-directional RTP streams from a Session table is defined in terms of uni-directional RTP streams
source to a destination. from a source to a destination.
For a multi-party IP-IP conference call in which parties are For a multi-party IP-IP conference call in which parties are
directly interconnected in a mesh network, a row should be created directly interconnected in a mesh network, a row should be created
in the session table for each such interconnection. in the session table for each such interconnection.
For a multi-party call in which parties are interconnected via For a multi-party call in which parties are interconnected via
a bridge function and RTP streams are literally or logically a bridge function and RTP streams are literally or logically
terminated at the bridge, a row should be created in the session terminated at the bridge, a row should be created in the session
table for the RTP sessions established to and from each endpoint table for the RTP sessions established to and from each endpoint
and the bridge. and the bridge.
skipping to change at page 5, line 15 skipping to change at page 4, line 67
RTCPXR-MIB DEFINITIONS ::= BEGIN RTCPXR-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
mib-2, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2, MODULE-IDENTITY, NOTIFICATION-TYPE,
OBJECT-TYPE, Unsigned32, Integer32, OBJECT-TYPE, Unsigned32, Integer32,
Gauge32, Counter32 FROM SNMPv2-SMI Gauge32, Counter32 FROM SNMPv2-SMI
OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
TEXTUAL-CONVENTION, RowPointer, DateAndTime TEXTUAL-CONVENTION, RowPointer, DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress, ItuPerceivedSeverity FROM ITU-ALARM-TC-MIB
InetPortNumber FROM INET-ADDRESS-MIB rtpSessionIndex, rtpSessionCallStatus
ItuPerceivedSeverity FROM ITU-ALARM-TC-MIB; FROM RTP-MIBV2;
rtcpXrMIB MODULE-IDENTITY rtcpXrMIB MODULE-IDENTITY
LAST-UPDATED "200510230000Z" LAST-UPDATED "200603040000Z"
ORGANIZATION ORGANIZATION
"IETF AVT Working Group" "IETF AVT Working Group"
CONTACT-INFO CONTACT-INFO
"IETF AVT Working Group "IETF AVT Working Group
Chairs: Colin Perkins, Magnus Westerlund Chairs: Colin Perkins, Magnus Westerlund
Working Group Email: avt@ietf.org Working Group Email: avt@ietf.org
Editors: Alan Clark Editors: Alan Clark
Telchemy Telchemy
Email: alan@telchemy.com Email: alan@telchemy.com
Amy Pendleton Amy Pendleton
Nortel Nortel
Email: aspen@nortel.com" Email: aspen@nortel.com"
DESCRIPTION DESCRIPTION
"RTCP Extended Reports MIB "RTCP Extended Reports MIB
Copyright (c) The Internet Society (2005) Copyright (c) The Internet Society (2005)
This version of the MIB module is part of This version of the MIB module is part of
RFC nnnn and is based on RFC3611." RFC nnnn and is based on RFC3611."
REVISION "200510230000Z" REVISION "200603040000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC nnnn" "Published as draft-ietf-avt-rtcp-xr-mib-04.txt"
-- RFC Ed: replace above draft with RFC number and remove this note
::= { mib-2 mmm } ::= { mib-2 nnn }
-- IANA: need assignment of a mib-2 OID for this MIB -- IANA: need assignment of a mib-2 OID for this MIB
-- RFC Ed: replace mmm with assigned OID number and remove this note
-- --
-- RTCP Extended Reports - Voice over IP Metrics -- RTCP Extended Reports - Voice over IP Metrics
-- --
-- Description -- Description
-- This MIB module provides basic voice quality monitoring -- This MIB module provides basic voice quality monitoring
-- capabilities for Voice-over-packet systems. The MIB contains -- capabilities for Voice-over-packet systems. The MIB contains
-- 3 tables of information that augment the data available in
-- the RTP MIB V2.
-- a table of basic parameters for each Stream
-- a table of call quality metrics for each Stream
-- a table of aggregate statistics for groups of calls -- a table of aggregate statistics for groups of calls
-- the indexes to these tables are imported from the RTP MIB V2
-- and hence this MIB MUST be used in conjunction with at least
-- the RTP session table from that MIB
-- TEXTUAL CONVENTIONS -- TEXTUAL CONVENTIONS
LeveldB ::= TEXTUAL-CONVENTION LeveldB ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents a signal level in decibels (dB)." "Represents a signal level in decibels (dB)."
SYNTAX Integer32 (-120..120|127) SYNTAX Integer32 (-120..120|127)
Rfactor ::= TEXTUAL-CONVENTION Rfactor ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
skipping to change at page 7, line 4 skipping to change at page 4, line 164
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Percentage expressed as a rounded integer." "Percentage expressed as a rounded integer."
SYNTAX Unsigned32 (0..100) SYNTAX Unsigned32 (0..100)
-- --
-- OBJECTS -- OBJECTS
-- --
rtcpXrEvents OBJECT IDENTIFIER ::= { rtcpXrMIB 0 } rtcpXrEvents OBJECT IDENTIFIER ::= { rtcpXrMIB 0 }
rtcpXrMIBObjects OBJECT IDENTIFIER ::= { rtcpXrMIB 1 } rtcpXrMIBObjects OBJECT IDENTIFIER ::= { rtcpXrMIB 1 }
rtcpXrConformance OBJECT IDENTIFIER ::= { rtcpXrMIB 2 } rtcpXrConformance OBJECT IDENTIFIER ::= { rtcpXrMIB 2 }
-- --
-- Table of basic RTP stream parameters
rtcpXrSessionIDTable OBJECT-TYPE
SYNTAX SEQUENCE OF RtcpXrSessionIDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of information about RTP Sessions for which RTCP XR
parameters and metrics are available. "
::= { rtcpXrMIBObjects 1 }
rtcpXrSessionIDEntry OBJECT-TYPE
SYNTAX RtcpXrSessionIDEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table of call records. A row in this table
is created for each RTP session endpoint participating."
INDEX { rtcpXrSessionIDCallState, rtcpXrSessionIDIndex }
::= { rtcpXrSessionIDTable 1 }
RtcpXrSessionIDEntry ::= SEQUENCE {
rtcpXrSessionIDCallState INTEGER,
rtcpXrSessionIDIndex Unsigned32,
rtcpXrSessionIDSessionIdentifier OCTET STRING,
rtcpXrSessionIDStartTime DateAndTime,
rtcpXrSessionIDStopTime DateAndTime,
rtcpXrSessionIDSourceIPtype InetAddressType,
rtcpXrSessionIDSourceIPaddress InetAddress,
rtcpXrSessionIDSourceRTPport InetPortNumber,
rtcpXrSessionIDSourceRTCPport InetPortNumber,
rtcpXrSessionIDDestIPtype InetAddressType,
rtcpXrSessionIDDestIPaddress InetAddress,
rtcpXrSessionIDDestRTPport InetPortNumber,
rtcpXrSessionIDDestRTCPport InetPortNumber,
rtcpXrSessionIDSrceIdenType INTEGER,
rtcpXrSessionIDSrceIdentifier OCTET STRING,
rtcpXrSessionIDDestIdenType INTEGER,
rtcpXrSessionIDDestIdentifier OCTET STRING,
rtcpXrSessionIDMeasurePt INTEGER,
rtcpXrSessionIDMeasurePtID OCTET STRING,
rtcpXrSessionIDReverseSession RowPointer,
rtcpXrSessionIDAltMeasurePt RowPointer
}
rtcpXrSessionIDCallState OBJECT-TYPE
SYNTAX INTEGER { active(1),
completed(2)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index for this session within the Session ID
table. The value of this parameter shall be 2 if the
session is complete or inactive and 1 if the session
is still active."
::= { rtcpXrSessionIDEntry 1 }
rtcpXrSessionIDIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index for this session within the Session ID table."
::= { rtcpXrSessionIDEntry 2 }
rtcpXrSessionIDSessionIdentifier OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Unique identifier for this session. A billing record
correlation identifier should be used if available,
otherwise an identifier such as SSRC can be used."
::= { rtcpXrSessionIDEntry 3 }
rtcpXrSessionIDStartTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Call start time for this call. If the start time is not
known then this represents the earliest known time associated
with the call."
::= { rtcpXrSessionIDEntry 4 }
rtcpXrSessionIDStopTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Call stop time for this call. If the call is still active
then this shall have the value 0. If the call is complete
but the time is unknown then this shall have the value of the
latest time associated with the call."
::= { rtcpXrSessionIDEntry 5 }
rtcpXrSessionIDSourceIPtype OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"IP address type for the originating IP endpoint for this
RTP stream."
::= { rtcpXrSessionIDEntry 6 }
rtcpXrSessionIDSourceIPaddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"IP address for the originating IP endpoint for this
RTP stream."
::= { rtcpXrSessionIDEntry 7 }
rtcpXrSessionIDSourceRTPport OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Source UDP port for RTP. A value of 0 indicates
an unknown port number."
::= { rtcpXrSessionIDEntry 8 }
rtcpXrSessionIDSourceRTCPport OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Source UDP port for RTCP. A value of 0 indicates
an unknown port number."
::= { rtcpXrSessionIDEntry 9 }
rtcpXrSessionIDDestIPtype OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Destination IP address type for this session."
::= { rtcpXrSessionIDEntry 10 }
rtcpXrSessionIDDestIPaddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Destination IP address for this session."
::= { rtcpXrSessionIDEntry 11 }
rtcpXrSessionIDDestRTPport OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Destination UDP port for RTP. A value of 0 indicates
an unknown port number."
::= { rtcpXrSessionIDEntry 12 }
rtcpXrSessionIDDestRTCPport OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Destination UDP port for RTCP.A value of 0 indicates
an unknown port number."
::= { rtcpXrSessionIDEntry 13 }
rtcpXrSessionIDSrceIdenType OBJECT-TYPE
SYNTAX INTEGER {dialedNumber (1),
urlID (2),
other (3) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the type of address in parameter
rtcpXrSessionIDSourceIdentifier"
::= { rtcpXrSessionIDEntry 14 }
rtcpXrSessionIDSrceIdentifier OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Alternate identifier to the IP address. This can be E.164,
DN, or URL."
::= { rtcpXrSessionIDEntry 15 }
rtcpXrSessionIDDestIdenType OBJECT-TYPE
SYNTAX INTEGER {dialedNumber (1),
urlID (2),
other (3) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the type of address in parameter
rtcpXrSessionIDDestIdentifier."
::= { rtcpXrSessionIDEntry 16 }
rtcpXrSessionIDDestIdentifier OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Alternate identifier to the IP address. This can be E.164,
DN, or URL."
::= { rtcpXrSessionIDEntry 17 }
rtcpXrSessionIDMeasurePt OBJECT-TYPE
SYNTAX INTEGER { localEndpoint (1),
remoteEndpoint (2),
midStream (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Place that these metrics were measured - this endpoint,
remote endpoint (i.e. reported through XR), or midstream.
If this MIB is supported in a midstream device (e.g. probe)
then data from the IP endpoint reported to this device
using RFC3611 would be described as 'remoteEndpoint' and
data measured locally would be described as 'midStream'.
If this MIB is supported in an IP endpoint then the metrics
obtained from measurement of the incoming stream would be
'localEndpoint' and those reported via RFC3611 from the
remote end would be 'remoteEndpoint'.
This MIB could therefore report both remote and local
data if located in an IP endpoint or both remote and
midstream data if located in a probe, router or other
mid-network device."
::= { rtcpXrSessionIDEntry 18 }
rtcpXrSessionIDMeasurePtID OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..128))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Information describing the identity of the endpoint that
measured the data in this row. If the data was measured
locally then this would be the identity of this system,
if measured remotely and reported via RFC3611 then this
would be the identity of the remote measurement point,
if known. Expressed as IP address in 1.1.1.1 notation
or as a descriptive name."
::= { rtcpXrSessionIDEntry 19 }
rtcpXrSessionIDReverseSession OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding entry in this table for
the reverse direction of transmission. For example, if
this row contained locally measured metrics for the A->B
direction of transmission then the reverse session would
be the row containing locally measured metrics for the
B->A direction of transmission."
::= { rtcpXrSessionIDEntry 20 }
rtcpXrSessionIDAltMeasurePt OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A pointer to the corresponding entry in this table for
alternate measurement point data. For example, if this
MIB was located in a midstream devices and this row
contained metrics measured midstream then the alternate
measurement point would refer to the metrics reported
by the remote endpoint, and vice versa."
::= { rtcpXrSessionIDEntry 21 }
-- --
rtcpXrBaseParamTable OBJECT-TYPE rtcpXrBaseParamTable OBJECT-TYPE
SYNTAX SEQUENCE OF RtcpXrBaseParamEntry SYNTAX SEQUENCE OF RtcpXrBaseParamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of basic parameters related to RTP sessions in "Table of basic parameters related to RTP sessions in
the Session table. " the Session table. "
::= { rtcpXrMIBObjects 2 } ::= { rtcpXrMIBObjects 2 }
rtcpXrBaseParamEntry OBJECT-TYPE rtcpXrBaseParamEntry OBJECT-TYPE
SYNTAX RtcpXrBaseParamEntry SYNTAX RtcpXrBaseParamEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table of basic parameters. A row in this table "An entry in the table of basic parameters. A row in this table
is created for each RTP session endpoint participating." is created for each RTP session endpoint participating."
INDEX { rtcpXrSessionIDCallState, rtcpXrSessionIDIndex } INDEX { rtpSessionCallStatus, rtpSessionIndex }
::= { rtcpXrBaseParamTable 1 } ::= { rtcpXrBaseParamTable 1 }
RtcpXrBaseParamEntry ::= SEQUENCE { RtcpXrBaseParamEntry ::= SEQUENCE {
rtcpXrBaseParamCodecType OCTET STRING, rtcpXrBaseParamCodecType OCTET STRING,
rtcpXrBaseParamCodecBitRate Unsigned32, rtcpXrBaseParamCodecBitRate Unsigned32,
rtcpXrBaseParamFrameDuration Unsigned32, rtcpXrBaseParamFrameDuration Unsigned32,
rtcpXrBaseParamFramesPerPacket Unsigned32, rtcpXrBaseParamFramesPerPacket Unsigned32,
rtcpXrBaseParamSampleRate Unsigned32, rtcpXrBaseParamSampleRate Unsigned32,
rtcpXrBaseParamDurationMs Counter32, rtcpXrBaseParamDurationMs Counter32,
rtcpXrBaseParamNetworkLossRate Percentage, rtcpXrBaseParamNetworkLossRate Percentage,
skipping to change at page 19, line 34 skipping to change at page 4, line 573
::= { rtcpXrMIBObjects 3 } ::= { rtcpXrMIBObjects 3 }
rtcpXrCallQualityEntry OBJECT-TYPE rtcpXrCallQualityEntry OBJECT-TYPE
SYNTAX RtcpXrCallQualityEntry SYNTAX RtcpXrCallQualityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the table of voice quality metrics. A row in "An entry in the table of voice quality metrics. A row in
this table is created for each row in the Session this table is created for each row in the Session
table." table."
INDEX { rtcpXrSessionIDCallState, rtcpXrSessionIDIndex } INDEX { rtpSessionCallStatus, rtpSessionIndex }
::= { rtcpXrCallQualityTable 1 } ::= { rtcpXrCallQualityTable 1 }
RtcpXrCallQualityEntry ::= SEQUENCE { RtcpXrCallQualityEntry ::= SEQUENCE {
rtcpXrCallQualityRCQ Rfactor, rtcpXrCallQualityRCQ Rfactor,
rtcpXrCallQualityRLQ Rfactor, rtcpXrCallQualityRLQ Rfactor,
rtcpXrCallQualityExternalRCQ Rfactor, rtcpXrCallQualityExternalRCQ Rfactor,
rtcpXrCallQualityMOSCQ ScaledMOSscore, rtcpXrCallQualityMOSCQ ScaledMOSscore,
rtcpXrCallQualityMOSLQ ScaledMOSscore, rtcpXrCallQualityMOSLQ ScaledMOSscore,
rtcpXrCallQualityRLQestAlgorithm OCTET STRING, rtcpXrCallQualityRLQestAlgorithm OCTET STRING,
rtcpXrCallQualityRCQestAlgorithm OCTET STRING, rtcpXrCallQualityRCQestAlgorithm OCTET STRING,
skipping to change at page 37, line 30 skipping to change at page 34, line 5
rtcpXrCompliances OBJECT IDENTIFIER ::= { rtcpXrConformance 1 } rtcpXrCompliances OBJECT IDENTIFIER ::= { rtcpXrConformance 1 }
rtcpXrGroups OBJECT IDENTIFIER ::= { rtcpXrConformance 2 } rtcpXrGroups OBJECT IDENTIFIER ::= { rtcpXrConformance 2 }
rtcpXrFullMetricsCompliance MODULE-COMPLIANCE rtcpXrFullMetricsCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
rtcpXr MIB for VoIP devices that support basic rtcpXr MIB for VoIP devices that support basic
reporting." reporting."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { rtcpXrSessionIDGroup, MANDATORY-GROUPS {
rtcpXrBaseParamGroup, rtcpXrBaseParamGroup,
rtcpXrCallQualityGroup rtcpXrCallQualityGroup
} }
::= { rtcpXrCompliances 1 } ::= { rtcpXrCompliances 1 }
rtcpXrMetricsAlertsCompliance MODULE-COMPLIANCE rtcpXrMetricsAlertsCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
rtcpXr MIB for VoIP devices that support reporting rtcpXr MIB for VoIP devices that support reporting
and alerts." and alerts."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { rtcpXrSessionIDGroup, MANDATORY-GROUPS {
rtcpXrBaseParamGroup, rtcpXrBaseParamGroup,
rtcpXrCallQualityGroup, rtcpXrCallQualityGroup,
rtcpXrNotificationParmsGroup, rtcpXrNotificationParmsGroup,
rtcpXrNotificationsGroup rtcpXrNotificationsGroup
} }
::= { rtcpXrCompliances 2 } ::= { rtcpXrCompliances 2 }
rtcpXrMetricsHistoryCompliance MODULE-COMPLIANCE rtcpXrMetricsHistoryCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the requirements for conformance to the "Describes the requirements for conformance to the
rtcpXr MIB for VoIP devices that support reporting, rtcpXr MIB for VoIP devices that support reporting,
call history and alerts." call history and alerts."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { rtcpXrSessionIDGroup, MANDATORY-GROUPS {
rtcpXrBaseParamGroup, rtcpXrBaseParamGroup,
rtcpXrCallQualityGroup, rtcpXrCallQualityGroup,
rtcpXrMIBHistoryGroup, rtcpXrMIBHistoryGroup,
rtcpXrNotificationParmsGroup, rtcpXrNotificationParmsGroup,
rtcpXrNotificationsGroup } rtcpXrNotificationsGroup }
::= { rtcpXrCompliances 3 } ::= { rtcpXrCompliances 3 }
rtcpXrHistoryCompliance MODULE-COMPLIANCE rtcpXrHistoryCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 38, line 31 skipping to change at page 35, line 4
MANDATORY-GROUPS { rtcpXrMIBHistoryGroup MANDATORY-GROUPS { rtcpXrMIBHistoryGroup
} }
::= { rtcpXrCompliances 4 } ::= { rtcpXrCompliances 4 }
rtcpXrMinimalCompliance MODULE-COMPLIANCE rtcpXrMinimalCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Describes the minimal requirements for conformance to "Describes the minimal requirements for conformance to
the rtcpXr MIB - NOT RECOMMENDED." the rtcpXr MIB - NOT RECOMMENDED."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { rtcpXrSessionIDGroup, MANDATORY-GROUPS {
rtcpXrBaseParamGroup rtcpXrBaseParamGroup
} }
::= { rtcpXrCompliances 5 } ::= { rtcpXrCompliances 5 }
rtcpXrSessionIDGroup OBJECT-GROUP
OBJECTS {
rtcpXrSessionIDSessionIdentifier,
rtcpXrSessionIDStartTime,
rtcpXrSessionIDStopTime,
rtcpXrSessionIDSourceIPtype,
rtcpXrSessionIDSourceIPaddress,
rtcpXrSessionIDSourceRTPport,
rtcpXrSessionIDSourceRTCPport,
rtcpXrSessionIDDestIPtype,
rtcpXrSessionIDDestIPaddress,
rtcpXrSessionIDDestRTPport,
rtcpXrSessionIDDestRTCPport,
rtcpXrSessionIDDestIdentifier,
rtcpXrSessionIDDestIdenType,
rtcpXrSessionIDSrceIdentifier,
rtcpXrSessionIDSrceIdenType,
rtcpXrSessionIDMeasurePt,
rtcpXrSessionIDMeasurePtID,
rtcpXrSessionIDReverseSession,
rtcpXrSessionIDAltMeasurePt
}
STATUS current
DESCRIPTION
"Session ID objects used in rtcpXr VoIP Metrics MIB"
::= { rtcpXrGroups 1 }
rtcpXrBaseParamGroup OBJECT-GROUP rtcpXrBaseParamGroup OBJECT-GROUP
OBJECTS { OBJECTS {
rtcpXrBaseParamCodecType, rtcpXrBaseParamCodecType,
rtcpXrBaseParamCodecBitRate, rtcpXrBaseParamCodecBitRate,
rtcpXrBaseParamFrameDuration, rtcpXrBaseParamFrameDuration,
rtcpXrBaseParamFramesPerPacket, rtcpXrBaseParamFramesPerPacket,
rtcpXrBaseParamSampleRate, rtcpXrBaseParamSampleRate,
rtcpXrBaseParamDurationMs, rtcpXrBaseParamDurationMs,
rtcpXrBaseParamNetworkLossRate, rtcpXrBaseParamNetworkLossRate,
rtcpXrBaseParamAvgDiscardRate, rtcpXrBaseParamAvgDiscardRate,
skipping to change at page 39, line 40 skipping to change at page 35, line 40
rtcpXrBaseParamJBuffAdaptMode, rtcpXrBaseParamJBuffAdaptMode,
rtcpXrBaseParamJBuffAdaptRate, rtcpXrBaseParamJBuffAdaptRate,
rtcpXrBaseParamJBuffAverageDelay, rtcpXrBaseParamJBuffAverageDelay,
rtcpXrBaseParamJBuffMaximumDelay, rtcpXrBaseParamJBuffMaximumDelay,
rtcpXrBaseParamJBuffAbsMaxDelay, rtcpXrBaseParamJBuffAbsMaxDelay,
rtcpXrBaseParamJitterLevel rtcpXrBaseParamJitterLevel
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used in rtcpXr VoIP Metrics MIB" "Objects used in rtcpXr VoIP Metrics MIB"
::= { rtcpXrGroups 2 } ::= { rtcpXrGroups 1 }
rtcpXrCallQualityGroup OBJECT-GROUP rtcpXrCallQualityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
rtcpXrCallQualityRCQ, rtcpXrCallQualityRCQ,
rtcpXrCallQualityRLQ, rtcpXrCallQualityRLQ,
rtcpXrCallQualityExternalRCQ, rtcpXrCallQualityExternalRCQ,
rtcpXrCallQualityMOSCQ, rtcpXrCallQualityMOSCQ,
rtcpXrCallQualityMOSLQ, rtcpXrCallQualityMOSLQ,
rtcpXrCallQualityRLQestAlgorithm, rtcpXrCallQualityRLQestAlgorithm,
rtcpXrCallQualityRCQestAlgorithm, rtcpXrCallQualityRCQestAlgorithm,
rtcpXrCallQualityMOSLQEstAlgorithm, rtcpXrCallQualityMOSLQEstAlgorithm,
rtcpXrCallQualityMOSCQEstAlgorithm rtcpXrCallQualityMOSCQEstAlgorithm
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Call quality objects used in rtcpXr VoIP Metrics MIB" "Call quality objects used in rtcpXr VoIP Metrics MIB"
::= { rtcpXrGroups 3 } ::= { rtcpXrGroups 2 }
rtcpXrMIBHistoryGroup OBJECT-GROUP rtcpXrMIBHistoryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
rtcpXrHistoryGroupName, rtcpXrHistoryGroupName,
rtcpXrHistoryStartTime, rtcpXrHistoryStartTime,
rtcpXrHistoryStopTime, rtcpXrHistoryStopTime,
rtcpXrHistoryNumOfSessions, rtcpXrHistoryNumOfSessions,
rtcpXrHistoryMinDurationMs, rtcpXrHistoryMinDurationMs,
rtcpXrHistoryMaxDurationMs, rtcpXrHistoryMaxDurationMs,
rtcpXrHistoryAvgDurationMs, rtcpXrHistoryAvgDurationMs,
rtcpXrHistoryMaxNetworkLossRate, rtcpXrHistoryMaxNetworkLossRate,
skipping to change at page 41, line 22 skipping to change at page 37, line 22
rtcpXrHistoryMinMOSLQ, rtcpXrHistoryMinMOSLQ,
rtcpXrHistoryMaxMOSLQ, rtcpXrHistoryMaxMOSLQ,
rtcpXrHistoryAvgMOSLQ, rtcpXrHistoryAvgMOSLQ,
rtcpXrHistoryMOSLQCount, rtcpXrHistoryMOSLQCount,
rtcpXrHistoryCQAlgorithm, rtcpXrHistoryCQAlgorithm,
rtcpXrHistoryReset rtcpXrHistoryReset
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects used in rtcpXr VoIP History MIB" "Objects used in rtcpXr VoIP History MIB"
::= { rtcpXrGroups 4 } ::= { rtcpXrGroups 3 }
rtcpXrNotificationParmsGroup OBJECT-GROUP rtcpXrNotificationParmsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
rtcpXrVoipAlertSeverity, rtcpXrVoipAlertSeverity,
rtcpXrVoipAlertType, rtcpXrVoipAlertType,
rtcpXrVoipAlertInfoType, rtcpXrVoipAlertInfoType,
rtcpXrVoipAlertPointer rtcpXrVoipAlertPointer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification parameters emitted by a rtcpXr endpoint." "Notification parameters emitted by a rtcpXr endpoint."
::= { rtcpXrGroups 5 } ::= { rtcpXrGroups 4 }
rtcpXrNotificationsGroup NOTIFICATION-GROUP rtcpXrNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
rtcpXrVoipThresholdViolation rtcpXrVoipThresholdViolation
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifications emitted by a rtcpXr endpoint." "Notifications emitted by a rtcpXr endpoint."
::= { rtcpXrGroups 6 } ::= { rtcpXrGroups 5 }
END END
4. Security Considerations 4. Security Considerations
Certain MIB objects contain endpoint identifying information:
rtcpXrSessionIDSourceIPaddress
rtcpXrSessionIDDestIPaddress
rtcpXrSessionIDSrceIdentifier
rtcpXrSessionIDDestIdentifier
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.
Access to rtcpXrHistoryReset can result in resetting the table of Access to rtcpXrHistoryReset can result in resetting the table of
aggregate call quality information, which results in the loss of aggregate call quality information, which results in the loss of
useful management data. useful management data.
It is thus important to control even GET and/or NOTIFY access to It is thus important to control even GET and/or NOTIFY access to
these objects and possibly to even encrypt their values when sending these objects and possibly to even encrypt their values when sending
them over the network via SNMP. them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
skipping to change at page 42, line 54 skipping to change at page 38, line 42
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
5. IANA Considerations 5. IANA Considerations
An OID within the mib-2 tree is requested, following which this note An OID within the mib-2 tree is requested, following which this note
may be deleted. may be deleted.
6. Acknowledgements 6. Acknowledgements
The authors would like to acknowledge the input and advice provided The authors would like to acknowledge the input and advice provided
by Dan Romascanu, Rajesh Kumar. Kim Curran and Shane Holthaus. by Dan Romascanu, Rajesh Kumar Kim Curran, Shane Holthaus and Brian
Park.
7. Intellectual Property 7. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 44, line 5 skipping to change at page 39, line 58
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, December 1999. SMIv2", STD 58, RFC 2580, December 1999.
9. Informative References 9. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and Stewart, B., [RFC3410] Case, J., Mundy, R., Partain, D. and Stewart, B.,
"Introduction and Applicability Statements for Internet "Introduction and Applicability Statements for Internet
Standard Management Framework", RFC 3410, December 2002 Standard Management Framework", RFC 3410, December 2002
[RAQMON] Siddiqui, A., Romascanu, D.,
draft-ietf-rmonmib-framework-16.txt
8. Authors' Addresses 8. Authors' Addresses
Alan Clark Alan Clark
Telchemy Incorporated Telchemy Incorporated
3360 Martins Farm Road, Ste 200 3360 Martins Farm Road, Ste 200
Suwanee, Georgia 30024 Suwanee, Georgia 30024
U.S.A. U.S.A.
Email: alan@telchemy.com Email: alan@telchemy.com
Amy Pendleton Amy Pendleton
Nortel Nortel
2380 Performance Drive 2380 Performance Drive
Richardson, Texas 75081 Richardson, Texas 75081
U.S.A. U.S.A.
Email: aspen@nortel.com Email: aspen@nortel.com
9. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 39 change blocks. 
360 lines changed or deleted 64 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/