idnits 2.17.1 draft-ietf-avt-rtcp-xr-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2360. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2269. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2276. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2282. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 36 longer pages, the longest (page 12) being 61 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2005) is 6760 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Audio/Video Working Group Alan Clark 2 Internet-Draft Telchemy 3 Expires: April 22, 2006 Amy Pendleton 4 Nortel 5 October 2005 7 RTP Control Protocol Extended Reports (RTCP XR) 8 VoIP Metrics Management Information Base 9 draft-ietf-avt-rtcp-xr-mib-03.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on April 22, 2006. 36 This document is a product of the Audio-Visual Transport (AVT) 37 working group of the Internet Engineering Task Force. Comments are 38 solicited and should be addressed to the working group's mailing 39 list at avt@ietf.org and/or the authors. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it defines objects for managing Real-Time Transport 46 Control Protocol Extended Reports (RTCP XR) VoIP Metrics (RFC3611). 48 Table of Contents 50 1. The Network Management Framework ............................. 2 51 2. Overview ..................................................... 3 52 2.1 Components .................................................. 3 53 2.2 Applicability of the MIB to RTP System Implementations ...... 3 54 2.3 Relationship to the RTP MIB....................................3 55 2.4 Relationship to the RAQMON Architecture...................... 3 56 2.5 The Structure of the RTCP XR MIB ............................ 4 57 2.6 Application to multi-party and multicast calls .............. 4 58 3 Definitions ................................................... 5 59 4. Security Considerations ...................................... 42 60 5. IANA Considerations .......................................... 42 61 5. Acknowledgements ............................................. 42 62 6. Intellectual Property ........................................ 43 63 7. Normative References ......................................... 43 64 9. Informative References ....................................... 43 65 8. Authors' Addresses ........................................... 44 66 9. Full Copyright Statement ..................................... 44 68 1. The Internet-Standard Management Framework 70 For a detailed overview of the documents that describe the current 71 Internet-Standard Management Framework, please refer to section 7 of 72 RFC 3410 [RFC3410]. 74 Managed objects are accessed via a virtual information store, termed 75 the Management Information Base or MIB. MIB objects are generally 76 accessed through the Simple Network Management Protocol (SNMP). 77 Objects in the MIB are defined using the mechanisms defined in the 78 Structure of Management Information (SMI). This memo specifies a MIB 79 module that is compliant to the SMIv2, which is described in STD 58, 80 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 81 [RFC2580]. 83 2. Overview 85 An "RTP System" may be a host end-system that runs an application 86 program that sends or receives RTP data packets, or it may be an 87 intermediate-system that forwards RTP packets. RTP Control Protocol 88 (RTCP) packets are sent by senders and receivers to convey 89 information about RTP packet transmission and reception [RFC3550]. 90 RTCP Extended Report (XR) [RFC3611] packets are sent by receivers 91 to convey additional information about certain types of RTP packet 92 reception. 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 96 document are to be interpreted as described in RFC 2119. 98 2.1 Components 100 The RTCP XR MIB is structured around "Session", "Source", 101 "Destination" and "Receiver" conceptual abstractions. 103 2.1.1 An RTP Session is an association of two or more participants 104 communicating with RTP. For each participant, the session is defined 105 by a particular pair of destination transport addresses (one network 106 address plus a port pair for RTP and RTCP). The destination 107 transport addresses may be common for all participants, as in the 108 case of IP multicast, or may be different for each, as in the case of 109 individual unicast addresses plus a common port pair," as defined in 110 section 3 of [RFC3550]. 112 2.1.2 A "Sender" is identified within an RTP session by a 32-bit 113 numeric "Synchronization Source," or "SSRC", value and is "...the 114 source of a stream of RTP packets" as defined in section 3 of 115 [RFC3550]. The sender is also a source of RTCP Sender Report packets 116 as specified in section 6 of [RFC3550]. 118 2.1.3 A "Receiver" of a "stream of RTP packets" can be a unicast or 119 multicast Receiver as described in 2.1.1, above. An RTP Receiver has 120 an SSRC value that is unique to the session. An RTP Receiver is a 121 source of RTCP Receiver Reports as specified in section 6 of 122 [RFC3550] and RTCP XR VoIP Metrics Reports as specified in section 123 4.7 of [RFC3611]. 125 2.2 Applicability of the MIB to RTP System Implementations 127 The RTCP XR MIB may be used in RTP Host Systems (end systems), see 128 section 3 of [RFC3550], that are supporting Voice over IP (VoIP host 129 systems) or in intermediate systems. 131 2.2.1 VoIP host Systems are end-systems that may use the RTCP XR MIB 132 to collect RTP Voice over IP session data that the host is sending or 133 receiving; these data may be used by a network manager to detect and 134 diagnose faults that occur over the lifetime of a VoIP session as in 135 a "help-desk" scenario. 137 2.2.2 Monitors of RTP Voice over IP sessions may be third-party or 138 may be located in the RTP host. Monitors may use the RTCP XR MIB to 139 collect Voice over IP session statistical data; these data may be 140 used by a network manager for planning and other network-management 141 purposes. A Monitor may use the RTCP XR MIB to collect data to 142 permit a network manager to diagnose faults in VoIP sessions. 144 2.3 Relationship to the RTP MIB 146 The RTP MIB defines a session table, sender and receiver tables and 147 inverse tables to support fast location of session information. 149 The RTP MIB Version 2 [draft TBD] has a session table that is 150 identical to the session table in the RTCP XR MIB. This is intended 151 to allow implementations that support both the RTP MIB V2 and the 152 RTCP XR MIB to use a common session table. 154 2.4 Relationship to the RAQMON Architecture 156 The Real-time Application QoS monitoring (RAQMON) Framework [xxx] 157 defines an architecture that extends the Remote Monitoring (RMON) 158 family of applications for monitoring of application QoS in real 159 time, and an extensible data model with objects carried between 160 RAQMON data sources and RAQMON collectors. The RAQMON work is 161 more generic, and complementary in concept to RTCP-XR, covering a 162 wider range of applications running concurrently, while RTCP-XR 163 focuses on in-depth QoS monitoring of media traffic in VoIP. 165 The Real-time Application QoS Monitoring (RAQMON) MIB is defined 166 by [xxx] and runs on RAQMON collectors. A performance monitoring 167 application may query (i) RAQMON collectors for RAQMON MIB 168 information about the QoS parameters of multiple concurrent 169 applications (ii) end-points and gateways for in-depth RTCP-XR 170 information about the media QoS of VoIP or (iii) both. 172 2.5 The Structure of the RTCP XR MIB 174 There are four tables in the RTCP XR MIB 176 The rtcpXrSessionIDtable contains identifying information about each 177 session and about the source and destination. 179 The rtcpXrBasicParametersTable contains basic packet loss, discard 180 and delay related parameters about a session. 182 The rtcpXrVoiceQualityMetricSTable contains information about the 183 call quality of a session 185 The rtcpXrHistoryTable contains aggregate information about a group 186 of sessions. 188 2.6 Application to multi-party and multicast calls 190 The RTCP XR MIB may be applied to multi-party calls. The Session 191 table is defined in terms of uni-directional RTP streams from a 192 source to a destination. 194 For a multi-party IP-IP conference call in which parties are 195 directly interconnected in a mesh network, a row should be created 196 in the session table for each such interconnection. 198 For a multi-party call in which parties are interconnected via 199 a bridge function and RTP streams are literally or logically 200 terminated at the bridge, a row should be created in the session 201 table for the RTP sessions established to and from each endpoint 202 and the bridge. 204 For a multicast call in which RTP sessions are terminated in 205 logical IP addresses from they are redistributed, a row in the 206 session table should be created for the source to multicast 207 address RTP session. 209 RTCPXR-MIB DEFINITIONS ::= BEGIN 210 IMPORTS 211 mib-2, MODULE-IDENTITY, NOTIFICATION-TYPE, 212 OBJECT-TYPE, Unsigned32, Integer32, 213 Gauge32, Counter32 FROM SNMPv2-SMI 214 OBJECT-GROUP, MODULE-COMPLIANCE, 215 NOTIFICATION-GROUP FROM SNMPv2-CONF 216 TEXTUAL-CONVENTION, RowPointer, DateAndTime 217 FROM SNMPv2-TC 218 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 219 InetAddressType, InetAddress, 220 InetPortNumber FROM INET-ADDRESS-MIB 221 ItuPerceivedSeverity FROM ITU-ALARM-TC-MIB; 223 rtcpXrMIB MODULE-IDENTITY 224 LAST-UPDATED "200510230000Z" 225 ORGANIZATION 226 "IETF AVT Working Group" 227 CONTACT-INFO 228 "IETF AVT Working Group 229 Chairs: Colin Perkins, Magnus Westerlund 230 Working Group Email: avt@ietf.org 232 Editors: Alan Clark 233 Telchemy 234 Email: alan@telchemy.com 236 Amy Pendleton 237 Nortel 238 Email: aspen@nortel.com" 239 DESCRIPTION 240 "RTCP Extended Reports MIB 241 Copyright (c) The Internet Society (2005) 242 This version of the MIB module is part of 243 RFC nnnn and is based on RFC3611." 245 REVISION "200510230000Z" 246 DESCRIPTION 247 "Initial version, published as RFC nnnn" 249 -- RFC Ed: replace nnnn (2 occurrences) with the actual RFC number and 250 -- remove this notice 252 ::= { mib-2 mmm } 254 -- IANA: need assignment of a mib-2 OID for this MIB 255 -- RFC Ed: replace mmm with IANA assigned number and remove this note 257 -- 258 -- RTCP Extended Reports - Voice over IP Metrics 259 -- 260 -- Description 261 -- This MIB module provides basic voice quality monitoring 262 -- capabilities for Voice-over-packet systems. The MIB contains 263 -- 4 tables of information:- 264 -- a table of call records with session identifying information 265 -- a table of basic parameters for each session 266 -- a table of call quality metrics for each session 267 -- a table of aggregate statistics for groups of calls 269 -- 270 -- TEXTUAL CONVENTIONS 271 -- 273 LeveldB ::= TEXTUAL-CONVENTION 274 DISPLAY-HINT "d" 275 STATUS current 276 DESCRIPTION 277 "Represents a signal level in decibels (dB)." 278 SYNTAX Integer32 (-120..120|127) 280 Rfactor ::= TEXTUAL-CONVENTION 281 DISPLAY-HINT "d" 282 STATUS current 283 DESCRIPTION 284 "Call or transmission quality expressed as an 285 R factor in the range 0 to 120. A value of 286 127 shall be interpreted as NULL or unsupported." 287 REFERENCE 288 "ITU-T G.107" 289 SYNTAX Unsigned32 (0..120|127) 291 ScaledMOSscore ::= TEXTUAL-CONVENTION 292 DISPLAY-HINT "d" 293 STATUS current 294 DESCRIPTION 295 "Call or transmission quality expressed as a 296 MOS score scaled by 10. MOS is typically represented 297 as a 1.0 to 5.0 score with a single decimal place and 298 hence in this representation as 10 to 50. A value of 299 127 shall be interpreted as NULL or unsupported." 300 REFERENCE 301 "ITU-T P.800" 302 SYNTAX Integer32 (10..50|127) 304 Percentage ::= TEXTUAL-CONVENTION 305 DISPLAY-HINT "d" 306 STATUS current 307 DESCRIPTION 308 "Percentage expressed as a rounded integer." 309 SYNTAX Unsigned32 (0..100) 311 -- 312 -- OBJECTS 313 -- 315 rtcpXrEvents OBJECT IDENTIFIER ::= { rtcpXrMIB 0 } 316 rtcpXrMIBObjects OBJECT IDENTIFIER ::= { rtcpXrMIB 1 } 317 rtcpXrConformance OBJECT IDENTIFIER ::= { rtcpXrMIB 2 } 319 -- 320 -- Table of Session Identifying information 321 -- 323 rtcpXrSessionIDTable OBJECT-TYPE 324 SYNTAX SEQUENCE OF RtcpXrSessionIDEntry 325 MAX-ACCESS not-accessible 326 STATUS current 327 DESCRIPTION 328 "Table of information about RTP Sessions for which RTCP XR 329 parameters and metrics are available. " 330 ::= { rtcpXrMIBObjects 1 } 332 rtcpXrSessionIDEntry OBJECT-TYPE 333 SYNTAX RtcpXrSessionIDEntry 334 MAX-ACCESS not-accessible 335 STATUS current 336 DESCRIPTION 337 "An entry in the table of call records. A row in this table 338 is created for each RTP session endpoint participating." 339 INDEX { rtcpXrSessionIDCallState, rtcpXrSessionIDIndex } 340 ::= { rtcpXrSessionIDTable 1 } 342 RtcpXrSessionIDEntry ::= SEQUENCE { 343 rtcpXrSessionIDCallState INTEGER, 344 rtcpXrSessionIDIndex Unsigned32, 345 rtcpXrSessionIDSessionIdentifier OCTET STRING, 346 rtcpXrSessionIDStartTime DateAndTime, 347 rtcpXrSessionIDStopTime DateAndTime, 348 rtcpXrSessionIDSourceIPtype InetAddressType, 349 rtcpXrSessionIDSourceIPaddress InetAddress, 350 rtcpXrSessionIDSourceRTPport InetPortNumber, 351 rtcpXrSessionIDSourceRTCPport InetPortNumber, 352 rtcpXrSessionIDDestIPtype InetAddressType, 353 rtcpXrSessionIDDestIPaddress InetAddress, 354 rtcpXrSessionIDDestRTPport InetPortNumber, 355 rtcpXrSessionIDDestRTCPport InetPortNumber, 356 rtcpXrSessionIDSrceIdenType INTEGER, 357 rtcpXrSessionIDSrceIdentifier OCTET STRING, 358 rtcpXrSessionIDDestIdenType INTEGER, 359 rtcpXrSessionIDDestIdentifier OCTET STRING, 360 rtcpXrSessionIDMeasurePt INTEGER, 361 rtcpXrSessionIDMeasurePtID OCTET STRING, 362 rtcpXrSessionIDReverseSession RowPointer, 363 rtcpXrSessionIDAltMeasurePt RowPointer 364 } 366 rtcpXrSessionIDCallState OBJECT-TYPE 367 SYNTAX INTEGER { active(1), 368 completed(2) 369 } 371 MAX-ACCESS not-accessible 372 STATUS current 373 DESCRIPTION 374 "Index for this session within the Session ID 375 table. The value of this parameter shall be 2 if the 376 session is complete or inactive and 1 if the session 377 is still active." 378 ::= { rtcpXrSessionIDEntry 1 } 380 rtcpXrSessionIDIndex OBJECT-TYPE 381 SYNTAX Unsigned32 (0..4294967295) 382 MAX-ACCESS not-accessible 383 STATUS current 384 DESCRIPTION 385 "Index for this session within the Session ID table." 386 ::= { rtcpXrSessionIDEntry 2 } 388 rtcpXrSessionIDSessionIdentifier OBJECT-TYPE 389 SYNTAX OCTET STRING (SIZE(0..128)) 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "Unique identifier for this session. A billing record 394 correlation identifier should be used if available, 395 otherwise an identifier such as SSRC can be used." 396 ::= { rtcpXrSessionIDEntry 3 } 398 rtcpXrSessionIDStartTime OBJECT-TYPE 399 SYNTAX DateAndTime 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "Call start time for this call. If the start time is not 404 known then this represents the earliest known time associated 405 with the call." 406 ::= { rtcpXrSessionIDEntry 4 } 408 rtcpXrSessionIDStopTime OBJECT-TYPE 409 SYNTAX DateAndTime 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "Call stop time for this call. If the call is still active 414 then this shall have the value 0. If the call is complete 415 but the time is unknown then this shall have the value of the 416 latest time associated with the call." 417 ::= { rtcpXrSessionIDEntry 5 } 419 rtcpXrSessionIDSourceIPtype OBJECT-TYPE 420 SYNTAX InetAddressType 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "IP address type for the originating IP endpoint for this 425 RTP stream." 426 ::= { rtcpXrSessionIDEntry 6 } 428 rtcpXrSessionIDSourceIPaddress OBJECT-TYPE 429 SYNTAX InetAddress 430 MAX-ACCESS read-only 431 STATUS current 432 DESCRIPTION 433 "IP address for the originating IP endpoint for this 434 RTP stream." 435 ::= { rtcpXrSessionIDEntry 7 } 437 rtcpXrSessionIDSourceRTPport OBJECT-TYPE 438 SYNTAX InetPortNumber 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "Source UDP port for RTP. A value of 0 indicates 443 an unknown port number." 444 ::= { rtcpXrSessionIDEntry 8 } 446 rtcpXrSessionIDSourceRTCPport OBJECT-TYPE 447 SYNTAX InetPortNumber 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "Source UDP port for RTCP. A value of 0 indicates 452 an unknown port number." 453 ::= { rtcpXrSessionIDEntry 9 } 455 rtcpXrSessionIDDestIPtype OBJECT-TYPE 456 SYNTAX InetAddressType 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "Destination IP address type for this session." 461 ::= { rtcpXrSessionIDEntry 10 } 463 rtcpXrSessionIDDestIPaddress OBJECT-TYPE 464 SYNTAX InetAddress 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "Destination IP address for this session." 469 ::= { rtcpXrSessionIDEntry 11 } 471 rtcpXrSessionIDDestRTPport OBJECT-TYPE 472 SYNTAX InetPortNumber 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "Destination UDP port for RTP. A value of 0 indicates 477 an unknown port number." 478 ::= { rtcpXrSessionIDEntry 12 } 480 rtcpXrSessionIDDestRTCPport OBJECT-TYPE 481 SYNTAX InetPortNumber 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "Destination UDP port for RTCP.A value of 0 indicates 486 an unknown port number." 487 ::= { rtcpXrSessionIDEntry 13 } 489 rtcpXrSessionIDSrceIdenType OBJECT-TYPE 490 SYNTAX INTEGER {dialedNumber (1), 491 urlID (2), 492 other (3) } 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "Defines the type of address in parameter 497 rtcpXrSessionIDSourceIdentifier" 498 ::= { rtcpXrSessionIDEntry 14 } 500 rtcpXrSessionIDSrceIdentifier OBJECT-TYPE 501 SYNTAX OCTET STRING (SIZE(0..128)) 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "Alternate identifier to the IP address. This can be E.164, 506 DN, or URL." 507 ::= { rtcpXrSessionIDEntry 15 } 509 rtcpXrSessionIDDestIdenType OBJECT-TYPE 510 SYNTAX INTEGER {dialedNumber (1), 511 urlID (2), 512 other (3) } 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION 516 "Defines the type of address in parameter 517 rtcpXrSessionIDDestIdentifier." 518 ::= { rtcpXrSessionIDEntry 16 } 520 rtcpXrSessionIDDestIdentifier OBJECT-TYPE 521 SYNTAX OCTET STRING (SIZE(0..128)) 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "Alternate identifier to the IP address. This can be E.164, 526 DN, or URL." 527 ::= { rtcpXrSessionIDEntry 17 } 529 rtcpXrSessionIDMeasurePt OBJECT-TYPE 530 SYNTAX INTEGER { localEndpoint (1), 531 remoteEndpoint (2), 532 midStream (3) 533 } 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION 538 "Place that these metrics were measured - this endpoint, 539 remote endpoint (i.e. reported through XR), or midstream. 540 If this MIB is supported in a midstream device (e.g. probe) 541 then data from the IP endpoint reported to this device 542 using RFC3611 would be described as 'remoteEndpoint' and 543 data measured locally would be described as 'midStream'. 544 If this MIB is supported in an IP endpoint then the metrics 545 obtained from measurement of the incoming stream would be 546 'localEndpoint' and those reported via RFC3611 from the 547 remote end would be 'remoteEndpoint'. 548 This MIB could therefore report both remote and local 549 data if located in an IP endpoint or both remote and 550 midstream data if located in a probe, router or other 551 mid-network device." 552 ::= { rtcpXrSessionIDEntry 18 } 554 rtcpXrSessionIDMeasurePtID OBJECT-TYPE 555 SYNTAX OCTET STRING (SIZE(0..128)) 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION 559 "Information describing the identity of the endpoint that 560 measured the data in this row. If the data was measured 561 locally then this would be the identity of this system, 562 if measured remotely and reported via RFC3611 then this 563 would be the identity of the remote measurement point, 564 if known. Expressed as IP address in 1.1.1.1 notation 565 or as a descriptive name." 566 ::= { rtcpXrSessionIDEntry 19 } 568 rtcpXrSessionIDReverseSession OBJECT-TYPE 569 SYNTAX RowPointer 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "A pointer to the corresponding entry in this table for 574 the reverse direction of transmission. For example, if 575 this row contained locally measured metrics for the A->B 576 direction of transmission then the reverse session would 577 be the row containing locally measured metrics for the 578 B->A direction of transmission." 579 ::= { rtcpXrSessionIDEntry 20 } 581 rtcpXrSessionIDAltMeasurePt OBJECT-TYPE 582 SYNTAX RowPointer 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "A pointer to the corresponding entry in this table for 587 alternate measurement point data. For example, if this 588 MIB was located in a midstream devices and this row 589 contained metrics measured midstream then the alternate 590 measurement point would refer to the metrics reported 591 by the remote endpoint, and vice versa." 592 ::= { rtcpXrSessionIDEntry 21 } 594 -- 595 -- Table of basic call parameters 596 -- 598 rtcpXrBaseParamTable OBJECT-TYPE 599 SYNTAX SEQUENCE OF RtcpXrBaseParamEntry 600 MAX-ACCESS not-accessible 601 STATUS current 602 DESCRIPTION 603 "Table of basic parameters related to RTP sessions in 604 the Session table. " 605 ::= { rtcpXrMIBObjects 2 } 607 rtcpXrBaseParamEntry OBJECT-TYPE 608 SYNTAX RtcpXrBaseParamEntry 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "An entry in the table of basic parameters. A row in this table 613 is created for each RTP session endpoint participating." 614 INDEX { rtcpXrSessionIDCallState, rtcpXrSessionIDIndex } 615 ::= { rtcpXrBaseParamTable 1 } 617 RtcpXrBaseParamEntry ::= SEQUENCE { 618 rtcpXrBaseParamCodecType OCTET STRING, 619 rtcpXrBaseParamCodecBitRate Unsigned32, 620 rtcpXrBaseParamFrameDuration Unsigned32, 621 rtcpXrBaseParamFramesPerPacket Unsigned32, 622 rtcpXrBaseParamSampleRate Unsigned32, 623 rtcpXrBaseParamDurationMs Counter32, 624 rtcpXrBaseParamNetworkLossRate Percentage, 625 rtcpXrBaseParamAvgDiscardRate Percentage, 626 rtcpXrBaseParamBurstLossDensity Percentage, 627 rtcpXrBaseParamBurstLenMs Gauge32, 628 rtcpXrBaseParamGapLossDensity Percentage, 629 rtcpXrBaseParamGapLenMs Gauge32, 630 rtcpXrBaseParamAvgOWDelay Gauge32, 631 rtcpXrBaseParamAvgEndSysDelay Gauge32, 632 rtcpXrBaseParamNoiseLeveldBm LeveldB, 633 rtcpXrBaseParamSignalLeveldBm LeveldB, 634 rtcpXrBaseParamLocalRERLdB LeveldB, 635 rtcpXrBaseParamRemoteRERLdB LeveldB, 636 rtcpXrBaseParamPlcType INTEGER, 637 rtcpXrBaseParamJBuffAdaptMode INTEGER, 638 rtcpXrBaseParamJBuffAdaptRate Unsigned32, 639 rtcpXrBaseParamJBuffAverageDelay Gauge32, 640 rtcpXrBaseParamJBuffMaximumDelay Gauge32, 641 rtcpXrBaseParamJBuffAbsMaxDelay Gauge32, 642 rtcpXrBaseParamJitterLevel Gauge32 643 } 644 rtcpXrBaseParamCodecType OBJECT-TYPE 645 SYNTAX OCTET STRING (SIZE(0..32)) 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "Codec type used on this call. The format used shall be 650 ITU-T G.7xx, GSM FR, GSM EFR, GSM HR, AMR, AMR WB, iLBC 651 or similar. For example 'ITU G.729A'. It is recommended 652 that Codecs are described in consistently with SDP." 653 ::= { rtcpXrBaseParamEntry 1 } 655 rtcpXrBaseParamCodecBitRate OBJECT-TYPE 656 SYNTAX Unsigned32 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "Codec rate in use at the time this data was captured 661 expressed in bits per second. For example G.711 would 662 have the rate 64000 and G.729 would have the rate 8000." 663 ::= { rtcpXrBaseParamEntry 2 } 665 rtcpXrBaseParamFrameDuration OBJECT-TYPE 666 SYNTAX Unsigned32 (0..16384) 667 UNITS "sample clock ticks" 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "Companion information to Codec type. This represents the 672 duration of the time interval represented by a frame, which 673 is generally equivalent to the nominal spacing of frames. 674 This is expressed in sample clock ticks as defined under 675 rtxpXrSampleRate. 676 This parameter may be equated to the SDP ptime parameter 677 which is expressed in milliseconds (however which cannot 678 represent certain Codec types, e.g. those with 2.5mS 679 frames)." 680 ::= { rtcpXrBaseParamEntry 3 } 682 rtcpXrBaseParamFramesPerPacket OBJECT-TYPE 683 SYNTAX Unsigned32 (0..65535) 684 UNITS "frames per packet" 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "Number of Codec frames contained in a single IP packet in 689 this RTP stream at the time of sampling. The duration of 690 speech per IP packet is the product of Frame Duration and 691 Frames Per Packet. This may vary during a call." 692 ::= {rtcpXrBaseParamEntry 4 } 694 rtcpXrBaseParamSampleRate OBJECT-TYPE 695 SYNTAX Unsigned32 (0..16777215) 696 UNITS "samples per second" 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "Companion information to Codec type. This represents the 701 rate at which media was sampled (e.g. 8000 for narrowband 702 voice, 16000 for wideband voice)." 703 ::= { rtcpXrBaseParamEntry 5 } 705 rtcpXrBaseParamDurationMs OBJECT-TYPE 706 SYNTAX Counter32 707 UNITS "milliseconds" 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "Current duration of call in milliseconds if still active, 712 duration of call in milliseconds if complete." 713 ::= { rtcpXrBaseParamEntry 6 } 715 rtcpXrBaseParamNetworkLossRate OBJECT-TYPE 716 SYNTAX Percentage 717 UNITS "percent" 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "Average rate of network packet loss." 722 REFERENCE 723 "See RFC3611 Section 4.7." 724 ::= { rtcpXrBaseParamEntry 7 } 726 rtcpXrBaseParamAvgDiscardRate OBJECT-TYPE 727 SYNTAX Percentage 728 UNITS "percent" 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "Average rate of discards due to jitter." 733 REFERENCE 734 "See RFC3611 Section 4.7." 735 ::= { rtcpXrBaseParamEntry 8 } 737 rtcpXrBaseParamBurstLossDensity OBJECT-TYPE 738 SYNTAX Percentage 739 UNITS "percent" 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "Density of loss and discarded packets during burst periods." 744 REFERENCE 745 "See RFC3611 Section 4.7." 746 ::= { rtcpXrBaseParamEntry 9 } 748 rtcpXrBaseParamBurstLenMs OBJECT-TYPE 749 SYNTAX Gauge32 750 UNITS "milliseconds" 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "Average length of bursts in milliseconds." 755 REFERENCE 756 "See RFC3611 Section 4.7." 757 ::= { rtcpXrBaseParamEntry 10 } 759 rtcpXrBaseParamGapLossDensity OBJECT-TYPE 760 SYNTAX Percentage 761 UNITS "percent" 762 MAX-ACCESS read-only 763 STATUS current 764 DESCRIPTION 765 "Density of loss and discarded packets during gap periods." 766 REFERENCE 767 "See RFC3611 Section 4.7." 768 ::= { rtcpXrBaseParamEntry 11 } 770 rtcpXrBaseParamGapLenMs OBJECT-TYPE 771 SYNTAX Gauge32 772 UNITS "milliseconds" 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "Average length of gaps in milliseconds." 777 REFERENCE 778 "See RFC3611 Section 4.7." 779 ::= { rtcpXrBaseParamEntry 12 } 781 rtcpXrBaseParamAvgOWDelay OBJECT-TYPE 782 SYNTAX Gauge32 783 UNITS "milliseconds" 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "Average (symmetric) one way RTCP delay on call. A value of 788 zero indicates that this value has not yet been determined." 789 REFERENCE 790 "See RFC3611 Section 4.7." 791 ::= { rtcpXrBaseParamEntry 13 } 793 rtcpXrBaseParamAvgEndSysDelay OBJECT-TYPE 794 SYNTAX Gauge32 795 UNITS "milliseconds" 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "Average end system delay on call. A value of zero may 800 indicate that this value has not yet been determined." 801 REFERENCE 802 "See RFC3611 Section 4.7." 803 ::= { rtcpXrBaseParamEntry 14 } 805 rtcpXrBaseParamNoiseLeveldBm OBJECT-TYPE 806 SYNTAX LeveldB 807 UNITS "dBm0" 808 MAX-ACCESS read-only 809 STATUS current 810 DESCRIPTION 811 "Measured received silent period noise level in dBm. 812 A value of 127 indicates that this parameter is not 813 available. 814 In midpoint applications this parameter may not be 815 available. If this is a midstream device and call 816 quality metrics were calculated using the value of 817 this parameter reported from the endpoint in an 818 RTCP XR payload then the value used in this 819 calculation MAY be reported." 820 REFERENCE 821 "See RFC3611 Section 4.7." 822 ::= { rtcpXrBaseParamEntry 15 } 824 rtcpXrBaseParamSignalLeveldBm OBJECT-TYPE 825 SYNTAX LeveldB 826 UNITS "dBm0" 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "Measured received signal level during talkspurts in dBm. 831 A value of 127 indicates that this parameter is not 832 available. 833 In midpoint applications this parameter may not be 834 available. If this is a midstream device and call 835 quality metrics were calculated using the value of 836 this parameter reported from the endpoint in an 837 RTCP XR payload then the value used in this 838 calculation MAY be reported." 839 REFERENCE 840 "See RFC3611 Section 4.7." 841 ::= { rtcpXrBaseParamEntry 16 } 843 rtcpXrBaseParamLocalRERLdB OBJECT-TYPE 844 SYNTAX LeveldB 845 UNITS "dBm" 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "Residual Echo Return Loss measured at this endpoint, 850 or at the terminating endpoint of this RTP session. 851 This relates to the echo level from the network beyond 852 the terminating endpoint and may be interpreted as either 853 line echo in the case of a gateway or acoustic echo in the 854 case of a handset. 855 Note that this echo affects conversational quality as 856 perceived by the user at the originating end of this 857 RTP session. 858 A value of 127 indicates that this parameter is not 859 available. 860 In midpoint applications this parameter may not be 861 available. If this is a midstream device and call 862 quality metrics were calculated using the value of 863 this parameter reported from the endpoint in an 864 RTCP XR payload then the value used in this 865 calculation MAY be reported." 866 REFERENCE 867 "See RFC3611 Section 4.7." 868 ::= { rtcpXrBaseParamEntry 17 } 870 rtcpXrBaseParamRemoteRERLdB OBJECT-TYPE 871 SYNTAX LeveldB 872 UNITS "dBm" 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "Residual Echo Return Loss measured at originating endpoint 877 of this RTP session (i.e. the remote endpoint if this MIB 878 is implemented in an endpoint). 879 Note that this affects the conversational quality 880 metrics reported by the terminating (this) endpoint, hence 881 is useful in understanding what has affected the reported 882 call quality metrics 883 A value of 127 indicates that this parameter is not 884 available. 885 In midpoint applications this parameter may not be 886 available. If this is a midstream device and call 887 quality metrics were calculated using the value of 888 this parameter reported from the endpoint in an 889 RTCP XR payload then the value used in this 890 calculation MAY be reported." 891 REFERENCE 892 "See RFC3611 Section 4.7." 893 ::= { rtcpXrBaseParamEntry 18 } 895 rtcpXrBaseParamPlcType OBJECT-TYPE 896 SYNTAX INTEGER { disabled(1), 897 enhanced(2), 898 standard(3), 899 unspecified (4)} 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "Defines type of packet loss concealment used on this call." 904 REFERENCE 905 "See RFC3611 Section 4.7." 906 ::= { rtcpXrBaseParamEntry 19 } 908 rtcpXrBaseParamJBuffAdaptMode OBJECT-TYPE 909 SYNTAX INTEGER { reserved (1), 910 nonAdaptive (2), 911 adaptive (3), 912 unknown (4) } 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "Defines if jitter buffer is in fixed or adaptive mode." 918 REFERENCE 919 "See RFC3611 Section 4.7." 920 ::= { rtcpXrBaseParamEntry 20 } 922 rtcpXrBaseParamJBuffAdaptRate OBJECT-TYPE 923 SYNTAX Unsigned32 (0..15) 924 MAX-ACCESS read-only 925 STATUS current 926 DESCRIPTION 927 "Estimated adaptation rate of jitter buffer." 928 REFERENCE 929 "See RFC3611 Section 4.7." 930 ::= { rtcpXrBaseParamEntry 21 } 932 rtcpXrBaseParamJBuffAverageDelay OBJECT-TYPE 933 SYNTAX Gauge32 934 UNITS "milliseconds" 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "Average size of jitter buffer in mS." 939 REFERENCE 940 "See RFC3611 Section 4.7." 941 ::= { rtcpXrBaseParamEntry 22 } 943 rtcpXrBaseParamJBuffMaximumDelay OBJECT-TYPE 944 SYNTAX Gauge32 945 UNITS "milliseconds" 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION 949 "Maximum delay through jitter buffer at current size in mS." 950 REFERENCE 951 "See RFC3611 Section 4.7." 952 ::= { rtcpXrBaseParamEntry 23 } 954 rtcpXrBaseParamJBuffAbsMaxDelay OBJECT-TYPE 955 SYNTAX Gauge32 956 UNITS "milliseconds" 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "Absolute maximum size jitter buffer can reach in mS." 961 REFERENCE 962 "See RFC3611 Section 4.7." 963 ::= { rtcpXrBaseParamEntry 24 } 965 rtcpXrBaseParamJitterLevel OBJECT-TYPE 966 SYNTAX Gauge32 967 UNITS "milliseconds" 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "Average jitter level measured according to RFC3550 and 972 represented in terms of milliseconds." 973 REFERENCE 974 "See RFC3550 Section 6.4." 975 ::= { rtcpXrBaseParamEntry 25 } 977 -- 978 -- Table of Call Quality Metrics 979 -- 981 rtcpXrCallQualityTable OBJECT-TYPE 982 SYNTAX SEQUENCE OF RtcpXrCallQualityEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "Table of voice quality metrics. A row is created 987 in this table for each row in the Session table." 988 ::= { rtcpXrMIBObjects 3 } 990 rtcpXrCallQualityEntry OBJECT-TYPE 991 SYNTAX RtcpXrCallQualityEntry 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "An entry in the table of voice quality metrics. A row in 996 this table is created for each row in the Session 997 table." 998 INDEX { rtcpXrSessionIDCallState, rtcpXrSessionIDIndex } 999 ::= { rtcpXrCallQualityTable 1 } 1001 RtcpXrCallQualityEntry ::= SEQUENCE { 1002 rtcpXrCallQualityRCQ Rfactor, 1003 rtcpXrCallQualityRLQ Rfactor, 1004 rtcpXrCallQualityExternalRCQ Rfactor, 1005 rtcpXrCallQualityMOSCQ ScaledMOSscore, 1006 rtcpXrCallQualityMOSLQ ScaledMOSscore, 1007 rtcpXrCallQualityRLQestAlgorithm OCTET STRING, 1008 rtcpXrCallQualityRCQestAlgorithm OCTET STRING, 1009 rtcpXrCallQualityMOSLQEstAlgorithm OCTET STRING, 1010 rtcpXrCallQualityMOSCQEstAlgorithm OCTET STRING 1011 } 1013 rtcpXrCallQualityRCQ OBJECT-TYPE 1014 SYNTAX Rfactor 1015 UNITS "R factor" 1016 MAX-ACCESS read-only 1017 STATUS current 1018 DESCRIPTION 1019 "Conversational quality R factor for this call. This value 1020 SHOULD be calculated using ITU G.107 (The E Model) or 1021 extended versions thereof." 1022 REFERENCE 1023 "See RFC3611 Section 4.7." 1024 ::= { rtcpXrCallQualityEntry 1 } 1026 rtcpXrCallQualityRLQ OBJECT-TYPE 1027 SYNTAX Rfactor 1028 UNITS "R factor" 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION 1032 "Listening quality R factor for this call. This value 1033 SHOULD be calculated using ITU G.107 (The E Model) or 1034 extended versions thereof." 1035 ::= { rtcpXrCallQualityEntry 2 } 1037 rtcpXrCallQualityExternalRCQ OBJECT-TYPE 1038 SYNTAX Rfactor 1039 UNITS "R factor" 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "External R factor for this call. This value 1044 SHOULD be calculated using ITU G.107 (The E Model) or 1045 extended versions thereof. 1046 The External R factor relates to the quality of an 1047 incoming voice from another network segment. For example 1048 if a conference bridge terminates and re-creates voice 1049 streams then an R factor would be calculated at the bridge 1050 for the endpoint A to bridge segment and relayed to the 1051 subsequent bridge to endpoint B as an External R factor. 1052 This allows endpoint B to estimate the end-to-end call 1053 quality." 1054 ::= { rtcpXrCallQualityEntry 3 } 1056 rtcpXrCallQualityMOSCQ OBJECT-TYPE 1057 SYNTAX ScaledMOSscore 1058 UNITS "MOS x 10" 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "Estimated conversational quality MOS for this call 1063 expressed in MOS x 10 (e.g. 41 = MOS of 4.1). This value 1064 MAY be calculated by converting the R-CQ value to a MOS." 1065 REFERENCE 1066 "See RFC3611 Section 4.7." 1067 ::= { rtcpXrCallQualityEntry 4 } 1069 rtcpXrCallQualityMOSLQ OBJECT-TYPE 1070 SYNTAX ScaledMOSscore 1071 UNITS "MOS x 10" 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "Estimated listening quality MOS for this call 1076 expressed in MOS x 10 (e.g. 41 = MOS of 4.1). This value 1077 MAY be calculated by converting the R-CQ value to a MOS." 1078 REFERENCE 1079 "See RFC3611 Section 4.7." 1080 ::= { rtcpXrCallQualityEntry 5 } 1082 rtcpXrCallQualityRLQestAlgorithm OBJECT-TYPE 1083 SYNTAX OCTET STRING (SIZE(0..128)) 1084 MAX-ACCESS read-only 1085 STATUS current 1086 DESCRIPTION 1087 "Call quality algorithm used to determine R-LQ factors. 1088 For example, 'ITU-T G.107' for the ITU G.107 1089 E model or 'ETSI TS101329-5E' for ETSI 1090 TS 101 329-5 Annex E." 1091 ::= { rtcpXrCallQualityEntry 6 } 1093 rtcpXrCallQualityRCQestAlgorithm OBJECT-TYPE 1094 SYNTAX OCTET STRING (SIZE(0..128)) 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "Call quality algorithm used to determine R-CQ factors. 1099 For example, 'ITU-T G.107' for the ITU G.107 1100 E model or 'ETSI TS101329-5E' for ETSI 1101 TS 101 329-5 Annex E." 1102 ::= { rtcpXrCallQualityEntry 7 } 1104 rtcpXrCallQualityMOSLQEstAlgorithm OBJECT-TYPE 1105 SYNTAX OCTET STRING (SIZE(0..128)) 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "Call quality algorithm used to determine MOS-LQ scores. 1110 If any localized parameter scaling is used 1111 (for example Japan's TTC MOS scaling) then this 1112 MUST also be reported." 1113 ::= { rtcpXrCallQualityEntry 8 } 1115 rtcpXrCallQualityMOSCQEstAlgorithm OBJECT-TYPE 1116 SYNTAX OCTET STRING (SIZE(0..128)) 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "Call quality algorithm used to determine MOS-CQ scores. 1121 If any localized parameter scaling is used 1122 (for example Japan's TTC MOS scaling) then this 1123 MUST also be reported." 1124 ::= { rtcpXrCallQualityEntry 9 } 1126 -- 1127 -- History Table 1128 -- 1129 -- 1131 rtcpXrHistoryTable OBJECT-TYPE 1132 SYNTAX SEQUENCE OF RtcpXrHistoryEntry 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "Table of aggregate measurement data for groups 1137 of RTP sessions. A group may be a flow or any 1138 other logical association of streams." 1139 ::= { rtcpXrMIBObjects 4 } 1141 rtcpXrHistoryEntry OBJECT-TYPE 1142 SYNTAX RtcpXrHistoryEntry 1143 MAX-ACCESS not-accessible 1144 STATUS current 1145 DESCRIPTION 1146 "An entry in the table of call history records." 1147 INDEX { rtcpXrHistoryIndex } 1148 ::= { rtcpXrHistoryTable 1 } 1150 RtcpXrHistoryEntry ::= SEQUENCE { 1151 rtcpXrHistoryIndex Unsigned32, 1152 rtcpXrHistoryGroupName OCTET STRING, 1153 rtcpXrHistoryStartTime DateAndTime, 1154 rtcpXrHistoryStopTime DateAndTime, 1155 rtcpXrHistoryNumOfSessions Counter32, 1156 rtcpXrHistoryMinDurationMs Gauge32, 1157 rtcpXrHistoryMaxDurationMs Gauge32, 1158 rtcpXrHistoryAvgDurationMs Gauge32, 1159 rtcpXrHistoryMaxNetworkLossRate Percentage, 1160 rtcpXrHistoryAvgNetworkLossRate Percentage, 1161 rtcpXrHistoryMaxDiscardRate Percentage, 1162 rtcpXrHistoryAvgDiscardRate Percentage, 1163 rtcpXrHistoryMaxBurstLossDensity Percentage, 1164 rtcpXrHistoryAvgBurstLossDensity Percentage, 1165 rtcpXrHistoryMinBurstLenMs Gauge32, 1166 rtcpXrHistoryMaxBurstLenMs Gauge32, 1167 rtcpXrHistoryAvgBurstLenMs Gauge32, 1168 rtcpXrHistoryMaxGapLossDensity Percentage, 1169 rtcpXrHistoryAvgGapLossDensity Percentage, 1170 rtcpXrHistoryMinGapLenMs Gauge32, 1171 rtcpXrHistoryMaxGapLenMs Gauge32, 1172 rtcpXrHistoryAvgGapLenMs Gauge32, 1173 rtcpXrHistoryMinOneWayDelay Gauge32, 1174 rtcpXrHistoryMaxOneWayDelay Gauge32, 1175 rtcpXrHistoryAvgOneWayDelay Gauge32, 1176 rtcpXrHistoryOneWayDelayCount Counter32, 1177 rtcpXrHistoryMinEndSystemDelay Gauge32, 1178 rtcpXrHistoryMaxEndSystemDelay Gauge32, 1179 rtcpXrHistoryAvgEndSystemDelay Gauge32, 1180 rtcpXrHistoryEndSystemDelayCount Counter32, 1181 rtcpXrHistoryMinJitterLevel Gauge32, 1182 rtcpXrHistoryMaxJitterLevel Gauge32, 1183 rtcpXrHistoryAvgJitterLevel Gauge32, 1184 rtcpXrHistoryMinNoiseLeveldBm LeveldB, 1185 rtcpXrHistoryMaxNoiseLeveldBm LeveldB, 1186 rtcpXrHistoryAvgNoiseLeveldBm LeveldB, 1187 rtcpXrHistoryNoiseLevelCount Counter32, 1188 rtcpXrHistoryMinSignalLeveldBm LeveldB, 1189 rtcpXrHistoryMaxSignalLeveldBm LeveldB, 1190 rtcpXrHistoryAvgSignalLeveldBm LeveldB, 1191 rtcpXrHistorySignalLevelCount Counter32, 1192 rtcpXrHistoryMinLocalRERLdB LeveldB, 1193 rtcpXrHistoryMaxLocalRERLdB LeveldB, 1194 rtcpXrHistoryAvgLocalRERLdB LeveldB, 1195 rtcpXrHistoryLocalRERLCount Counter32, 1196 rtcpXrHistoryMinRemoteRERLdB LeveldB, 1197 rtcpXrHistoryMaxRemoteRERLdB LeveldB, 1198 rtcpXrHistoryAvgRemoteRERLdB LeveldB, 1199 rtcpXrHistoryRemoteRERLCount Counter32, 1200 rtcpXrHistoryMinRCQ Rfactor, 1201 rtcpXrHistoryMaxRCQ Rfactor, 1202 rtcpXrHistoryAvgRCQ Rfactor, 1203 rtcpXrHistoryRCQCount Counter32, 1204 rtcpXrHistoryMinRLQ Rfactor, 1205 rtcpXrHistoryMaxRLQ Rfactor, 1206 rtcpXrHistoryAvgRLQ Rfactor, 1207 rtcpXrHistoryRLQCount Counter32, 1208 rtcpXrHistoryMinMOSCQ ScaledMOSscore, 1209 rtcpXrHistoryMaxMOSCQ ScaledMOSscore, 1210 rtcpXrHistoryAvgMOSCQ ScaledMOSscore, 1211 rtcpXrHistoryMOSCQCount Counter32, 1212 rtcpXrHistoryMinMOSLQ ScaledMOSscore, 1213 rtcpXrHistoryMaxMOSLQ ScaledMOSscore, 1214 rtcpXrHistoryAvgMOSLQ ScaledMOSscore, 1215 rtcpXrHistoryMOSLQCount Counter32, 1216 rtcpXrHistoryCQAlgorithm OCTET STRING, 1217 rtcpXrHistoryReset INTEGER 1218 } 1220 rtcpXrHistoryIndex OBJECT-TYPE 1221 SYNTAX Unsigned32 (0..4294967295) 1222 MAX-ACCESS not-accessible 1223 STATUS current 1224 DESCRIPTION 1225 "Index for this set of aggregate data." 1226 ::= { rtcpXrHistoryEntry 1 } 1228 rtcpXrHistoryGroupName OBJECT-TYPE 1229 SYNTAX OCTET STRING (SIZE(0..128)) 1230 MAX-ACCESS read-write 1231 STATUS current 1232 DESCRIPTION 1233 "Name of this set of aggregate data. Examples may include 1234 a flow, an interface or some other logical grouping of 1235 RTP sessions." 1236 ::= { rtcpXrHistoryEntry 2 } 1238 rtcpXrHistoryStartTime OBJECT-TYPE 1239 SYNTAX DateAndTime 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "Time at which this history was reset or started." 1244 ::= {rtcpXrHistoryEntry 3 } 1246 rtcpXrHistoryStopTime OBJECT-TYPE 1247 SYNTAX DateAndTime 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "Time at which this history was stopped." 1252 ::= {rtcpXrHistoryEntry 4 } 1254 rtcpXrHistoryNumOfSessions OBJECT-TYPE 1255 SYNTAX Counter32 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "Number of calls included in this history." 1260 ::= {rtcpXrHistoryEntry 5 } 1262 rtcpXrHistoryMinDurationMs OBJECT-TYPE 1263 SYNTAX Gauge32 1264 UNITS "milliseconds" 1265 MAX-ACCESS read-only 1266 STATUS current 1267 DESCRIPTION 1268 "Minimum duration of calls." 1269 ::= {rtcpXrHistoryEntry 6 } 1271 rtcpXrHistoryMaxDurationMs OBJECT-TYPE 1272 SYNTAX Gauge32 1273 UNITS "milliseconds" 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "Maximum duration of calls." 1278 ::= {rtcpXrHistoryEntry 7 } 1280 rtcpXrHistoryAvgDurationMs OBJECT-TYPE 1281 SYNTAX Gauge32 1282 UNITS "milliseconds" 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "Average duration of calls within this history." 1287 ::= {rtcpXrHistoryEntry 8 } 1289 rtcpXrHistoryMaxNetworkLossRate OBJECT-TYPE 1290 SYNTAX Percentage 1291 UNITS "percent" 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "Maximum loss rate occurring on any call in this history." 1296 ::= {rtcpXrHistoryEntry 9 } 1298 rtcpXrHistoryAvgNetworkLossRate OBJECT-TYPE 1299 SYNTAX Percentage 1300 UNITS "percent" 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "Mean for all calls in this history of the individual 1305 per call packet loss rate." 1306 ::= {rtcpXrHistoryEntry 10 } 1308 rtcpXrHistoryMaxDiscardRate OBJECT-TYPE 1309 SYNTAX Percentage 1310 UNITS "percent" 1311 MAX-ACCESS read-only 1312 STATUS current 1313 DESCRIPTION 1314 "Maximum discard rate occurring on any call in this history." 1315 ::= {rtcpXrHistoryEntry 11 } 1317 rtcpXrHistoryAvgDiscardRate OBJECT-TYPE 1318 SYNTAX Percentage 1319 UNITS "percent" 1320 MAX-ACCESS read-only 1321 STATUS current 1322 DESCRIPTION 1323 "Mean for all calls in this history of the individual 1324 per call packet discard rate." 1325 ::= {rtcpXrHistoryEntry 12 } 1327 rtcpXrHistoryMaxBurstLossDensity OBJECT-TYPE 1328 SYNTAX Percentage 1329 UNITS "percent" 1330 MAX-ACCESS read-only 1331 STATUS current 1332 DESCRIPTION 1333 "Maximum of the per-call average burst densities for any 1334 call in this history. A value of 0 shall be reported if 1335 no bursts were reported." 1336 ::= {rtcpXrHistoryEntry 13 } 1338 rtcpXrHistoryAvgBurstLossDensity OBJECT-TYPE 1339 SYNTAX Percentage 1340 UNITS "percent" 1341 MAX-ACCESS read-only 1342 STATUS current 1343 DESCRIPTION 1344 "Mean for all calls in this history of the individual 1345 per call burst density. A value of 0 shall be reported if 1346 no bursts were reported." 1347 ::= {rtcpXrHistoryEntry 14 } 1349 rtcpXrHistoryMinBurstLenMs OBJECT-TYPE 1350 SYNTAX Gauge32 1351 UNITS "milliseconds" 1352 MAX-ACCESS read-only 1353 STATUS current 1354 DESCRIPTION 1355 "Minimum of the per-call burst length for all calls in this 1356 history for which a burst length was reported. A value of 1357 0 shall be reported if no bursts were present." 1358 ::= {rtcpXrHistoryEntry 15 } 1360 rtcpXrHistoryMaxBurstLenMs OBJECT-TYPE 1361 SYNTAX Gauge32 1362 UNITS "milliseconds" 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "Maximum of the per-call burst length for all calls in this 1367 history for which a burst length was reported. A value of 1368 0 shall be reported if no bursts were present." 1369 ::= {rtcpXrHistoryEntry 16 } 1371 rtcpXrHistoryAvgBurstLenMs OBJECT-TYPE 1372 SYNTAX Gauge32 1373 UNITS "milliseconds" 1374 MAX-ACCESS read-only 1375 STATUS current 1376 DESCRIPTION 1377 "Mean of the per-call burst length for all calls in this 1378 history for which a burst length was reported. A value of 1379 0 shall be reported if no bursts were present." 1380 ::= {rtcpXrHistoryEntry 17 } 1382 rtcpXrHistoryMaxGapLossDensity OBJECT-TYPE 1383 SYNTAX Percentage 1384 UNITS "percent" 1385 MAX-ACCESS read-only 1386 STATUS current 1387 DESCRIPTION 1388 "Maximum of the per-call gap density for all calls in this 1389 history for which a gap density was reported. A value of 1390 0 shall be reported if no gaps were present." 1391 ::= {rtcpXrHistoryEntry 18 } 1393 rtcpXrHistoryAvgGapLossDensity OBJECT-TYPE 1394 SYNTAX Percentage 1395 UNITS "percent" 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "Mean of the per-call gap density for all calls in this 1400 history for which a gap density was reported. A value of 1401 0 shall be reported if no gaps were present." 1402 ::= {rtcpXrHistoryEntry 19 } 1404 rtcpXrHistoryMinGapLenMs OBJECT-TYPE 1405 SYNTAX Gauge32 1406 UNITS "milliseconds" 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "Minimum of the per-call gap length for all calls in this 1411 history for which a gap length was reported. A value of 1412 0 shall be reported if no gaps were present." 1413 ::= {rtcpXrHistoryEntry 20 } 1415 rtcpXrHistoryMaxGapLenMs OBJECT-TYPE 1416 SYNTAX Gauge32 1417 UNITS "milliseconds" 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "Maximum of the per-call gap length for all calls in this 1422 history for which a gap length was reported. A value of 1423 0 shall be reported if no gaps were present." 1424 ::= {rtcpXrHistoryEntry 21 } 1426 rtcpXrHistoryAvgGapLenMs OBJECT-TYPE 1427 SYNTAX Gauge32 1428 UNITS "milliseconds" 1429 MAX-ACCESS read-only 1430 STATUS current 1431 DESCRIPTION 1432 "Mean of the per-call gap length for all calls in this 1433 history for which a gap length was reported. A value of 1434 0 shall be reported if no gaps were present." 1435 ::= {rtcpXrHistoryEntry 22 } 1437 rtcpXrHistoryMinOneWayDelay OBJECT-TYPE 1438 SYNTAX Gauge32 1439 UNITS "milliseconds" 1440 MAX-ACCESS read-only 1441 STATUS current 1442 DESCRIPTION 1443 "Minimum of the per-call OW Delays for all calls in this 1444 history for which a Delay was reported. A value of 1445 0 shall be reported if no Delay values were reported." 1446 ::= {rtcpXrHistoryEntry 23 } 1448 rtcpXrHistoryMaxOneWayDelay OBJECT-TYPE 1449 SYNTAX Gauge32 1450 UNITS "milliseconds" 1451 MAX-ACCESS read-only 1452 STATUS current 1453 DESCRIPTION 1454 "Maximum of the per-call OW Delays for all calls in this 1455 history for which a Delay was reported. A value of 1456 0 shall be reported if no Delay values were reported." 1457 ::= {rtcpXrHistoryEntry 24 } 1459 rtcpXrHistoryAvgOneWayDelay OBJECT-TYPE 1460 SYNTAX Gauge32 1461 UNITS "milliseconds" 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "Mean of the per-call OW Delays for all calls in this 1466 history for which a Delay was reported. A value of 1467 0 shall be reported if no Delay values were reported." 1468 ::= {rtcpXrHistoryEntry 25 } 1470 rtcpXrHistoryOneWayDelayCount OBJECT-TYPE 1471 SYNTAX Counter32 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "Number of sessions included in the One Way Delay 1476 history values (as Delay may not be available on 1477 all calls." 1478 ::= {rtcpXrHistoryEntry 26 } 1480 rtcpXrHistoryMinEndSystemDelay OBJECT-TYPE 1481 SYNTAX Gauge32 1482 UNITS "milliseconds" 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "Minimum of the per-call ES Delays for all calls in this 1487 history for which an ES Delay was reported." 1488 ::= {rtcpXrHistoryEntry 27 } 1490 rtcpXrHistoryMaxEndSystemDelay OBJECT-TYPE 1491 SYNTAX Gauge32 1492 UNITS "milliseconds" 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "Maximum of the per-call ES Delays for all calls in this 1497 history for which an ES Delay was reported." 1498 ::= {rtcpXrHistoryEntry 28 } 1500 rtcpXrHistoryAvgEndSystemDelay OBJECT-TYPE 1501 SYNTAX Gauge32 1502 UNITS "milliseconds" 1503 MAX-ACCESS read-only 1504 STATUS current 1505 DESCRIPTION 1506 "Mean of the per-call ES Delays for all calls in this 1507 history for which an ES Delay was reported." 1508 ::= {rtcpXrHistoryEntry 29 } 1510 rtcpXrHistoryEndSystemDelayCount OBJECT-TYPE 1511 SYNTAX Counter32 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "Number of sessions included in the End System 1516 Delay history values (as End System Delay 1517 may not be available on all calls." 1518 ::= {rtcpXrHistoryEntry 30 } 1520 rtcpXrHistoryMinJitterLevel OBJECT-TYPE 1521 SYNTAX Gauge32 1522 UNITS "milliseconds" 1523 MAX-ACCESS read-only 1524 STATUS current 1525 DESCRIPTION 1526 "Minimum of the per-call jitter for all calls in this 1527 history for which a jitter value was reported." 1528 ::= {rtcpXrHistoryEntry 31 } 1530 rtcpXrHistoryMaxJitterLevel OBJECT-TYPE 1531 SYNTAX Gauge32 1532 UNITS "milliseconds" 1533 MAX-ACCESS read-only 1534 STATUS current 1535 DESCRIPTION 1536 "Maximum of the per-call jitter for all calls in this 1537 history for which a jitter value was reported." 1538 ::= {rtcpXrHistoryEntry 32 } 1540 rtcpXrHistoryAvgJitterLevel OBJECT-TYPE 1541 SYNTAX Gauge32 1542 UNITS "milliseconds" 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "Mean of the per-call jitter for all calls in this 1547 history for which a jitter value was reported." 1548 ::= {rtcpXrHistoryEntry 33 } 1550 rtcpXrHistoryMinNoiseLeveldBm OBJECT-TYPE 1551 SYNTAX LeveldB 1552 UNITS "dBm0" 1553 MAX-ACCESS read-only 1554 STATUS current 1555 DESCRIPTION 1556 "Minimum of the per-call Noise Level for all calls in this 1557 history for which a Noise Level value was reported." 1558 ::= {rtcpXrHistoryEntry 34 } 1560 rtcpXrHistoryMaxNoiseLeveldBm OBJECT-TYPE 1561 SYNTAX LeveldB 1562 UNITS "dBm0" 1563 MAX-ACCESS read-only 1564 STATUS current 1565 DESCRIPTION 1566 "Maximum of the per-call Noise Level for all calls in this 1567 history for which a Noise Level value was reported." 1568 ::= {rtcpXrHistoryEntry 35 } 1570 rtcpXrHistoryAvgNoiseLeveldBm OBJECT-TYPE 1571 SYNTAX LeveldB 1572 UNITS "dBm0" 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "Mean of the per-call Noise Level for all calls in this 1577 history for which a Noise Level value was reported." 1578 ::= {rtcpXrHistoryEntry 36 } 1580 rtcpXrHistoryNoiseLevelCount OBJECT-TYPE 1581 SYNTAX Counter32 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "Number of sessions included in the Noise Level 1586 history values (as Noise Level is an optional 1587 parameter and may not be present on all calls." 1588 ::= {rtcpXrHistoryEntry 37 } 1590 rtcpXrHistoryMinSignalLeveldBm OBJECT-TYPE 1591 SYNTAX LeveldB 1592 UNITS "dBm0" 1593 MAX-ACCESS read-only 1594 STATUS current 1595 DESCRIPTION 1596 "Minimum of the per-call Signal Level for all calls in this 1597 history for which a Signal Level value was reported." 1598 ::= {rtcpXrHistoryEntry 38 } 1600 rtcpXrHistoryMaxSignalLeveldBm OBJECT-TYPE 1601 SYNTAX LeveldB 1602 UNITS "dBm0" 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "Maximum of the per-call Signal Level for all calls in this 1607 history for which a Signal Level value was reported." 1608 ::= {rtcpXrHistoryEntry 39 } 1610 rtcpXrHistoryAvgSignalLeveldBm OBJECT-TYPE 1611 SYNTAX LeveldB 1612 UNITS "dBm0" 1613 MAX-ACCESS read-only 1614 STATUS current 1615 DESCRIPTION 1616 "Mean of the per-call Signal Level for all calls in this 1617 history for which a Signal Level value was reported." 1618 ::= {rtcpXrHistoryEntry 40 } 1620 rtcpXrHistorySignalLevelCount OBJECT-TYPE 1621 SYNTAX Counter32 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "Number of sessions included in the Signal Level 1626 history values (as Signal Level is an optional 1627 parameter and may not be present on all calls." 1628 ::= {rtcpXrHistoryEntry 41 } 1630 rtcpXrHistoryMinLocalRERLdB OBJECT-TYPE 1631 SYNTAX LeveldB 1632 UNITS "dBm" 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "Minimum of the per-call local RERL for all calls in this 1637 history for which a local RERL value was reported." 1638 ::= {rtcpXrHistoryEntry 42 } 1640 rtcpXrHistoryMaxLocalRERLdB OBJECT-TYPE 1641 SYNTAX LeveldB 1642 UNITS "dBm" 1643 MAX-ACCESS read-only 1644 STATUS current 1645 DESCRIPTION 1646 "Maximum of the per-call local RERL for all calls in this 1647 history for which a local RERL value was reported." 1648 ::= {rtcpXrHistoryEntry 43 } 1650 rtcpXrHistoryAvgLocalRERLdB OBJECT-TYPE 1651 SYNTAX LeveldB 1652 UNITS "dBm" 1653 MAX-ACCESS read-only 1654 STATUS current 1655 DESCRIPTION 1656 "Mean of the per-call local RERL for all calls in this 1657 history for which a local RERL value was reported." 1658 ::= {rtcpXrHistoryEntry 44 } 1660 rtcpXrHistoryLocalRERLCount OBJECT-TYPE 1661 SYNTAX Counter32 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION 1665 "Number of sessions included in the Local RERL 1666 history values (as Local RERL is an optional 1667 parameter and may not be present on all calls." 1668 ::= {rtcpXrHistoryEntry 45 } 1670 rtcpXrHistoryMinRemoteRERLdB OBJECT-TYPE 1671 SYNTAX LeveldB 1672 UNITS "dBm" 1673 MAX-ACCESS read-only 1674 STATUS current 1675 DESCRIPTION 1676 "Minimum of the per-call remote RERL for all calls in this 1677 history for which a remote RERL value was reported." 1678 ::= {rtcpXrHistoryEntry 46 } 1680 rtcpXrHistoryMaxRemoteRERLdB OBJECT-TYPE 1681 SYNTAX LeveldB 1682 UNITS "dBm" 1683 MAX-ACCESS read-only 1684 STATUS current 1685 DESCRIPTION 1686 "Maximum of the per-call remote RERL for all calls in this 1687 history for which a remote RERL value was reported." 1688 ::= {rtcpXrHistoryEntry 47 } 1690 rtcpXrHistoryAvgRemoteRERLdB OBJECT-TYPE 1691 SYNTAX LeveldB 1692 UNITS "dBm" 1693 MAX-ACCESS read-only 1694 STATUS current 1695 DESCRIPTION 1696 "Mean of the per-call remote RERL for all calls in this 1697 history for which a remote RERL value was reported." 1698 ::= {rtcpXrHistoryEntry 48 } 1700 rtcpXrHistoryRemoteRERLCount OBJECT-TYPE 1701 SYNTAX Counter32 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "Number of sessions included in the Remote RERL 1706 history values (as Remote RERL is an optional 1707 parameter and may not be present on all calls." 1708 ::= {rtcpXrHistoryEntry 49 } 1710 rtcpXrHistoryMinRCQ OBJECT-TYPE 1711 SYNTAX Rfactor 1712 UNITS "R factor" 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "Minimum of the per-call R-CQ for all calls in this 1717 history for which an R-CQ value was reported." 1718 ::= {rtcpXrHistoryEntry 50 } 1720 rtcpXrHistoryMaxRCQ OBJECT-TYPE 1721 SYNTAX Rfactor 1722 UNITS "R factor" 1723 MAX-ACCESS read-only 1724 STATUS current 1725 DESCRIPTION 1726 "Maximum of the per-call R-CQ for all calls in this 1727 history for which an R-CQ value was reported." 1728 ::= {rtcpXrHistoryEntry 51 } 1730 rtcpXrHistoryAvgRCQ OBJECT-TYPE 1731 SYNTAX Rfactor 1732 UNITS "R factor" 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "Mean of the per-call R-CQ for all calls in this 1737 history for which an R-CQ value was reported." 1738 ::= {rtcpXrHistoryEntry 52 } 1740 rtcpXrHistoryRCQCount OBJECT-TYPE 1741 SYNTAX Counter32 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "Number of sessions included in the R CQ 1746 history values (as R CQ is an optional 1747 parameter and may not be present on all calls." 1748 ::= {rtcpXrHistoryEntry 53 } 1750 rtcpXrHistoryMinRLQ OBJECT-TYPE 1751 SYNTAX Rfactor 1752 UNITS "R factor" 1753 MAX-ACCESS read-only 1754 STATUS current 1755 DESCRIPTION 1756 "Minimum of the per-call R-LQ for all calls in this 1757 history for which an R-LQ value was reported." 1758 ::= {rtcpXrHistoryEntry 54 } 1760 rtcpXrHistoryMaxRLQ OBJECT-TYPE 1761 SYNTAX Rfactor 1762 UNITS "R factor" 1763 MAX-ACCESS read-only 1764 STATUS current 1765 DESCRIPTION 1766 "Maximum of the per-call R-LQ for all calls in this 1767 history for which an R-LQ value was reported." 1768 ::= {rtcpXrHistoryEntry 55 } 1770 rtcpXrHistoryAvgRLQ OBJECT-TYPE 1771 SYNTAX Rfactor 1772 UNITS "R factor" 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION 1776 "Mean of the per-call R-LQ for all calls in this 1777 history for which an R-LQ value was reported." 1778 ::= {rtcpXrHistoryEntry 56 } 1780 rtcpXrHistoryRLQCount OBJECT-TYPE 1781 SYNTAX Counter32 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "Number of sessions included in the R LQ 1786 history values (as R LQ is an optional 1787 parameter and may not be present on all calls." 1788 ::= {rtcpXrHistoryEntry 57 } 1790 rtcpXrHistoryMinMOSCQ OBJECT-TYPE 1791 SYNTAX ScaledMOSscore 1792 UNITS "MOS x 10" 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "Minimum of the per-call MOS-CQ for all calls in this 1797 history for which a MOS-CQ value was reported." 1798 ::= {rtcpXrHistoryEntry 58 } 1800 rtcpXrHistoryMaxMOSCQ OBJECT-TYPE 1801 SYNTAX ScaledMOSscore 1802 UNITS "MOS x 10" 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION 1806 "Maximum of the per-call MOS-CQ for all calls in this 1807 history for which a MOS-CQ value was reported." 1808 ::= {rtcpXrHistoryEntry 59 } 1810 rtcpXrHistoryAvgMOSCQ OBJECT-TYPE 1811 SYNTAX ScaledMOSscore 1812 UNITS "MOS x 10" 1813 MAX-ACCESS read-only 1814 STATUS current 1815 DESCRIPTION 1816 "Mean of the per-call MOS-CQ for all calls in this 1817 history for which a MOS-CQ value was reported." 1818 ::= {rtcpXrHistoryEntry 60 } 1820 rtcpXrHistoryMOSCQCount OBJECT-TYPE 1821 SYNTAX Counter32 1822 MAX-ACCESS read-only 1823 STATUS current 1824 DESCRIPTION 1825 "Number of sessions included in the MOS CQ 1826 history values (as MOS CQ is an optional 1827 parameter and may not be present on all calls." 1828 ::= {rtcpXrHistoryEntry 61 } 1830 rtcpXrHistoryMinMOSLQ OBJECT-TYPE 1831 SYNTAX ScaledMOSscore 1832 UNITS "MOS x 10" 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "Minimum of the per-call MOS-LQ for all calls in this 1837 history for which a MOS-LQ value was reported." 1838 ::= {rtcpXrHistoryEntry 62 } 1840 rtcpXrHistoryMaxMOSLQ OBJECT-TYPE 1841 SYNTAX ScaledMOSscore 1842 UNITS "MOS x 10" 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "Maximum of the per-call MOS-LQ for all calls in this 1847 history for which a MOS-LQ value was reported." 1848 ::= {rtcpXrHistoryEntry 63 } 1850 rtcpXrHistoryAvgMOSLQ OBJECT-TYPE 1851 SYNTAX ScaledMOSscore 1852 UNITS "MOS x 10" 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "Mean of the per-call MOS-LQ for all calls in this 1857 history for which a MOS-LQ value was reported." 1858 ::= {rtcpXrHistoryEntry 64 } 1860 rtcpXrHistoryMOSLQCount OBJECT-TYPE 1861 SYNTAX Counter32 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "Number of sessions included in the MOS LQ 1866 history values (as MOS LQ is an optional 1867 parameter and may not be present on all calls." 1868 ::= {rtcpXrHistoryEntry 65 } 1870 rtcpXrHistoryCQAlgorithm OBJECT-TYPE 1871 SYNTAX OCTET STRING (SIZE(0..32)) 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "Call quality algorithm used - if consistent 1876 for all calls in this history." 1877 ::= {rtcpXrHistoryEntry 66 } 1879 rtcpXrHistoryReset OBJECT-TYPE 1880 SYNTAX INTEGER { running (1), 1881 stop (2), 1882 reset (3) 1883 } 1884 MAX-ACCESS read-write 1885 STATUS current 1886 DESCRIPTION 1887 "Status of this row in the history table. 1888 Writing a value of 2 to this object MUST cause 1889 history updates to be stopped for this row. Writing 1890 a value of 3 to this object MUST cause the history 1891 row to be reset. 1892 Reads MUST return a value of 1 if the row is still 1893 being updated or 2 if the row update has stopped." 1894 ::= {rtcpXrHistoryEntry 67 } 1896 -- 1897 -- Notifications 1898 -- 1900 rtcpXrVoipThresholdViolation NOTIFICATION-TYPE 1901 OBJECTS { rtcpXrVoipAlertSeverity, rtcpXrVoipAlertType, 1902 rtcpXrVoipAlertInfoType, rtcpXrVoipAlertPointer } 1903 STATUS current 1904 DESCRIPTION 1905 "Notification that voice quality has changed 1906 Sent immediately when the condition is detected." 1907 ::= { rtcpXrEvents 1} 1909 rtcpXrEventParam OBJECT IDENTIFIER ::= { rtcpXrEvents 2 } 1911 rtcpXrVoipAlertType OBJECT-TYPE 1912 SYNTAX SnmpAdminString 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "Text description of the type of alert. Where possible, 1917 this parameter should be populated with the correct 1918 rtcpXrVoipEntry or rtcpXrVoipHistory description." 1919 ::= { rtcpXrEventParam 1 } 1921 rtcpXrVoipAlertInfoType OBJECT-TYPE 1922 SYNTAX INTEGER { adminStringOnly (1), 1923 sessionPointer (2), 1924 historyPointer (3) 1925 } 1926 MAX-ACCESS read-only 1927 STATUS current 1928 DESCRIPTION 1929 "Indicates the type of information returned in the 1930 rtcpXrVoipAlertInfo parameter." 1931 ::= { rtcpXrEventParam 2 } 1933 rtcpXrVoipAlertPointer OBJECT-TYPE 1934 SYNTAX RowPointer 1935 MAX-ACCESS read-only 1936 STATUS current 1937 DESCRIPTION 1938 "Pointer to the table of call session information to 1939 identify the specific call that triggered the alert." 1940 ::= { rtcpXrEventParam 3 } 1942 rtcpXrVoipAlertSeverity OBJECT-TYPE 1943 SYNTAX ItuPerceivedSeverity 1944 MAX-ACCESS read-only 1945 STATUS current 1946 DESCRIPTION 1947 "The severity of the alert as defined in ITU-T X.733 and 1948 RFC3877." 1950 REFERENCE 1951 "See Alarm MIB - RFC3877." 1952 ::= { rtcpXrEventParam 4 } 1954 -- 1955 -- MODULE GROUPS 1956 -- 1957 -- There are four types of RTCP XR VoIP Metrics System. 1958 -- 1959 -- RTCP XR VOIP Metrics Systems MUST implement one of the four 1960 -- identified types of system and SHOULD NOT implement the 1961 -- rtcpXrMinimalCompliance system, which is included only 1962 -- for reasons of compatibility with RFC3611's minimal 1963 -- requirements. 1964 -- 1966 rtcpXrCompliances OBJECT IDENTIFIER ::= { rtcpXrConformance 1 } 1967 rtcpXrGroups OBJECT IDENTIFIER ::= { rtcpXrConformance 2 } 1969 rtcpXrFullMetricsCompliance MODULE-COMPLIANCE 1970 STATUS current 1971 DESCRIPTION 1972 "Describes the requirements for conformance to the 1973 rtcpXr MIB for VoIP devices that support basic 1974 reporting." 1975 MODULE -- this module 1976 MANDATORY-GROUPS { rtcpXrSessionIDGroup, 1977 rtcpXrBaseParamGroup, 1978 rtcpXrCallQualityGroup 1979 } 1980 ::= { rtcpXrCompliances 1 } 1982 rtcpXrMetricsAlertsCompliance MODULE-COMPLIANCE 1983 STATUS current 1984 DESCRIPTION 1985 "Describes the requirements for conformance to the 1986 rtcpXr MIB for VoIP devices that support reporting 1987 and alerts." 1988 MODULE -- this module 1989 MANDATORY-GROUPS { rtcpXrSessionIDGroup, 1990 rtcpXrBaseParamGroup, 1991 rtcpXrCallQualityGroup, 1992 rtcpXrNotificationParmsGroup, 1993 rtcpXrNotificationsGroup 1994 } 1995 ::= { rtcpXrCompliances 2 } 1997 rtcpXrMetricsHistoryCompliance MODULE-COMPLIANCE 1998 STATUS current 1999 DESCRIPTION 2000 "Describes the requirements for conformance to the 2001 rtcpXr MIB for VoIP devices that support reporting, 2002 call history and alerts." 2003 MODULE -- this module 2004 MANDATORY-GROUPS { rtcpXrSessionIDGroup, 2005 rtcpXrBaseParamGroup, 2006 rtcpXrCallQualityGroup, 2007 rtcpXrMIBHistoryGroup, 2008 rtcpXrNotificationParmsGroup, 2009 rtcpXrNotificationsGroup } 2010 ::= { rtcpXrCompliances 3 } 2012 rtcpXrHistoryCompliance MODULE-COMPLIANCE 2013 STATUS current 2014 DESCRIPTION 2015 "Describes the requirements for conformance to the 2016 rtcpXr MIB for VoIP devices that support only 2017 call history." 2018 MODULE -- this module 2019 MANDATORY-GROUPS { rtcpXrMIBHistoryGroup 2020 } 2021 ::= { rtcpXrCompliances 4 } 2023 rtcpXrMinimalCompliance MODULE-COMPLIANCE 2024 STATUS current 2025 DESCRIPTION 2026 "Describes the minimal requirements for conformance to 2027 the rtcpXr MIB - NOT RECOMMENDED." 2028 MODULE -- this module 2029 MANDATORY-GROUPS { rtcpXrSessionIDGroup, 2030 rtcpXrBaseParamGroup 2031 } 2032 ::= { rtcpXrCompliances 5 } 2034 rtcpXrSessionIDGroup OBJECT-GROUP 2035 OBJECTS { 2036 rtcpXrSessionIDSessionIdentifier, 2037 rtcpXrSessionIDStartTime, 2038 rtcpXrSessionIDStopTime, 2039 rtcpXrSessionIDSourceIPtype, 2040 rtcpXrSessionIDSourceIPaddress, 2041 rtcpXrSessionIDSourceRTPport, 2042 rtcpXrSessionIDSourceRTCPport, 2043 rtcpXrSessionIDDestIPtype, 2044 rtcpXrSessionIDDestIPaddress, 2045 rtcpXrSessionIDDestRTPport, 2046 rtcpXrSessionIDDestRTCPport, 2047 rtcpXrSessionIDDestIdentifier, 2048 rtcpXrSessionIDDestIdenType, 2049 rtcpXrSessionIDSrceIdentifier, 2050 rtcpXrSessionIDSrceIdenType, 2051 rtcpXrSessionIDMeasurePt, 2052 rtcpXrSessionIDMeasurePtID, 2053 rtcpXrSessionIDReverseSession, 2054 rtcpXrSessionIDAltMeasurePt 2055 } 2057 STATUS current 2058 DESCRIPTION 2059 "Session ID objects used in rtcpXr VoIP Metrics MIB" 2060 ::= { rtcpXrGroups 1 } 2062 rtcpXrBaseParamGroup OBJECT-GROUP 2063 OBJECTS { 2064 rtcpXrBaseParamCodecType, 2065 rtcpXrBaseParamCodecBitRate, 2066 rtcpXrBaseParamFrameDuration, 2067 rtcpXrBaseParamFramesPerPacket, 2068 rtcpXrBaseParamSampleRate, 2069 rtcpXrBaseParamDurationMs, 2070 rtcpXrBaseParamNetworkLossRate, 2071 rtcpXrBaseParamAvgDiscardRate, 2072 rtcpXrBaseParamBurstLossDensity, 2073 rtcpXrBaseParamBurstLenMs, 2074 rtcpXrBaseParamGapLossDensity, 2075 rtcpXrBaseParamGapLenMs, 2076 rtcpXrBaseParamAvgOWDelay, 2077 rtcpXrBaseParamAvgEndSysDelay, 2078 rtcpXrBaseParamNoiseLeveldBm, 2079 rtcpXrBaseParamSignalLeveldBm, 2080 rtcpXrBaseParamLocalRERLdB, 2081 rtcpXrBaseParamRemoteRERLdB, 2082 rtcpXrBaseParamPlcType, 2083 rtcpXrBaseParamJBuffAdaptMode, 2084 rtcpXrBaseParamJBuffAdaptRate, 2085 rtcpXrBaseParamJBuffAverageDelay, 2086 rtcpXrBaseParamJBuffMaximumDelay, 2087 rtcpXrBaseParamJBuffAbsMaxDelay, 2088 rtcpXrBaseParamJitterLevel 2089 } 2090 STATUS current 2091 DESCRIPTION 2092 "Objects used in rtcpXr VoIP Metrics MIB" 2093 ::= { rtcpXrGroups 2 } 2095 rtcpXrCallQualityGroup OBJECT-GROUP 2096 OBJECTS { 2097 rtcpXrCallQualityRCQ, 2098 rtcpXrCallQualityRLQ, 2099 rtcpXrCallQualityExternalRCQ, 2100 rtcpXrCallQualityMOSCQ, 2101 rtcpXrCallQualityMOSLQ, 2102 rtcpXrCallQualityRLQestAlgorithm, 2103 rtcpXrCallQualityRCQestAlgorithm, 2104 rtcpXrCallQualityMOSLQEstAlgorithm, 2105 rtcpXrCallQualityMOSCQEstAlgorithm 2106 } 2107 STATUS current 2108 DESCRIPTION 2109 "Call quality objects used in rtcpXr VoIP Metrics MIB" 2110 ::= { rtcpXrGroups 3 } 2112 rtcpXrMIBHistoryGroup OBJECT-GROUP 2113 OBJECTS { 2114 rtcpXrHistoryGroupName, 2115 rtcpXrHistoryStartTime, 2116 rtcpXrHistoryStopTime, 2117 rtcpXrHistoryNumOfSessions, 2118 rtcpXrHistoryMinDurationMs, 2119 rtcpXrHistoryMaxDurationMs, 2120 rtcpXrHistoryAvgDurationMs, 2121 rtcpXrHistoryMaxNetworkLossRate, 2122 rtcpXrHistoryAvgNetworkLossRate, 2123 rtcpXrHistoryMaxDiscardRate, 2124 rtcpXrHistoryAvgDiscardRate, 2125 rtcpXrHistoryMaxBurstLossDensity, 2126 rtcpXrHistoryAvgBurstLossDensity, 2127 rtcpXrHistoryMinBurstLenMs, 2128 rtcpXrHistoryMaxBurstLenMs, 2129 rtcpXrHistoryAvgBurstLenMs, 2130 rtcpXrHistoryMaxGapLossDensity, 2131 rtcpXrHistoryAvgGapLossDensity, 2132 rtcpXrHistoryMinGapLenMs, 2133 rtcpXrHistoryMaxGapLenMs, 2134 rtcpXrHistoryAvgGapLenMs, 2135 rtcpXrHistoryMinOneWayDelay, 2136 rtcpXrHistoryMaxOneWayDelay, 2137 rtcpXrHistoryAvgOneWayDelay, 2138 rtcpXrHistoryOneWayDelayCount, 2139 rtcpXrHistoryMinEndSystemDelay, 2140 rtcpXrHistoryMaxEndSystemDelay, 2141 rtcpXrHistoryAvgEndSystemDelay, 2142 rtcpXrHistoryEndSystemDelayCount, 2143 rtcpXrHistoryAvgJitterLevel, 2144 rtcpXrHistoryMinJitterLevel, 2145 rtcpXrHistoryMaxJitterLevel, 2146 rtcpXrHistoryMinNoiseLeveldBm, 2147 rtcpXrHistoryMaxNoiseLeveldBm, 2148 rtcpXrHistoryAvgNoiseLeveldBm, 2149 rtcpXrHistoryNoiseLevelCount, 2150 rtcpXrHistoryMinSignalLeveldBm, 2151 rtcpXrHistoryMaxSignalLeveldBm, 2152 rtcpXrHistoryAvgSignalLeveldBm, 2153 rtcpXrHistorySignalLevelCount, 2154 rtcpXrHistoryMinLocalRERLdB, 2155 rtcpXrHistoryMaxLocalRERLdB, 2156 rtcpXrHistoryAvgLocalRERLdB, 2157 rtcpXrHistoryLocalRERLCount, 2158 rtcpXrHistoryMinRemoteRERLdB, 2159 rtcpXrHistoryMaxRemoteRERLdB, 2160 rtcpXrHistoryAvgRemoteRERLdB, 2161 rtcpXrHistoryRemoteRERLCount, 2162 rtcpXrHistoryMinRCQ, 2163 rtcpXrHistoryMaxRCQ, 2164 rtcpXrHistoryAvgRCQ, 2165 rtcpXrHistoryRCQCount, 2166 rtcpXrHistoryMinRLQ, 2167 rtcpXrHistoryMaxRLQ, 2168 rtcpXrHistoryAvgRLQ, 2169 rtcpXrHistoryRLQCount, 2170 rtcpXrHistoryMinMOSCQ, 2171 rtcpXrHistoryMaxMOSCQ, 2172 rtcpXrHistoryAvgMOSCQ, 2173 rtcpXrHistoryMOSCQCount, 2174 rtcpXrHistoryMinMOSLQ, 2175 rtcpXrHistoryMaxMOSLQ, 2176 rtcpXrHistoryAvgMOSLQ, 2177 rtcpXrHistoryMOSLQCount, 2178 rtcpXrHistoryCQAlgorithm, 2179 rtcpXrHistoryReset 2180 } 2181 STATUS current 2182 DESCRIPTION 2183 "Objects used in rtcpXr VoIP History MIB" 2184 ::= { rtcpXrGroups 4 } 2186 rtcpXrNotificationParmsGroup OBJECT-GROUP 2187 OBJECTS { 2188 rtcpXrVoipAlertSeverity, 2189 rtcpXrVoipAlertType, 2190 rtcpXrVoipAlertInfoType, 2191 rtcpXrVoipAlertPointer 2192 } 2193 STATUS current 2194 DESCRIPTION 2195 "Notification parameters emitted by a rtcpXr endpoint." 2196 ::= { rtcpXrGroups 5 } 2198 rtcpXrNotificationsGroup NOTIFICATION-GROUP 2199 NOTIFICATIONS { 2200 rtcpXrVoipThresholdViolation 2201 } 2202 STATUS current 2203 DESCRIPTION 2204 "Notifications emitted by a rtcpXr endpoint." 2205 ::= { rtcpXrGroups 6 } 2207 END 2209 4. Security Considerations 2211 Certain MIB objects contain endpoint identifying information: 2213 rtcpXrSessionIDSourceIPaddress 2214 rtcpXrSessionIDDestIPaddress 2215 rtcpXrSessionIDSrceIdentifier 2216 rtcpXrSessionIDDestIdentifier 2218 Unauthorized exposure of these objects may lead to disclosure of the 2219 addresses of the participants in applications, or information about 2220 the traffic patents of the applications, which may be considered 2221 sensitive in certain environments. 2223 Access to rtcpXrHistoryReset can result in resetting the table of 2224 aggregate call quality information, which results in the loss of 2225 useful management data. 2227 It is thus important to control even GET and/or NOTIFY access to 2228 these objects and possibly to even encrypt their values when sending 2229 them over the network via SNMP. 2231 SNMP versions prior to SNMPv3 did not include adequate security. 2232 Even if the network itself is secure (for example by using IPSec), 2233 even then, there is no control as to who on the secure network is 2234 allowed to access and GET/SET (read/change/create/delete) the objects 2235 in this MIB module. 2237 It is RECOMMENDED that implementers consider the security features as 2238 provided by the SNMPv3 framework (see [RFC3410], section 8), 2239 including full support for the SNMPv3 cryptographic mechanisms (for 2240 authentication and privacy). 2242 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2243 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2244 enable cryptographic security. It is then a customer/operator 2245 responsibility to ensure that the SNMP entity giving access to an 2246 instance of this MIB module is properly configured to give access to 2247 the objects only to those principals (users) that have legitimate 2248 rights to indeed GET or SET (change/create/delete) them. 2250 5. IANA Considerations 2252 An OID within the mib-2 tree is requested, following which this note 2253 may be deleted. 2255 6. Acknowledgements 2257 The authors would like to acknowledge the input and advice provided 2258 by Dan Romascanu, Rajesh Kumar. Kim Curran and Shane Holthaus. 2260 7. Intellectual Property 2262 The IETF takes no position regarding the validity or scope of any 2263 Intellectual Property Rights or other rights that might be claimed to 2264 pertain to the implementation or use of the technology described in 2265 this document or the extent to which any license under such rights 2266 might or might not be available; nor does it represent that it has 2267 made any independent effort to identify any such rights. Information 2268 on the procedures with respect to rights in RFC documents can be 2269 found in BCP 78 and BCP 79. 2271 Copies of IPR disclosures made to the IETF Secretariat and any 2272 assurances of licenses to be made available, or the result of an 2273 attempt made to obtain a general license or permission for the use of 2274 such proprietary rights by implementers or users of this 2275 specification can be obtained from the IETF on-line IPR repository at 2276 http://www.ietf.org/ipr. 2278 The IETF invites any interested party to bring to its attention any 2279 copyrights, patents or patent applications, or other proprietary 2280 rights that may cover technology that may be required to implement 2281 this standard. Please address the information to the IETF at 2282 ietf-ipr@ietf.org. 2284 8. Normative References 2286 [RFC3550] Shulzrinne, H., Casner, S., Frederick, R. and V. 2287 Jacobson, "RTP: A Transport Protocol for real-time 2288 applications," RFC 3550, July 2003. 2290 [RFC3611] Friedman, T., Caceres, R., Clark, A., "RTP Control 2291 Protocol Reporting Extensions (RTCP XR)," RFC 3611, 2292 [October/November] 2003 2294 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2295 Rose, M. and S. Waldbusser, "Structure of Management 2296 Information Version 2 (SMIv2)", STD 58, RFC 2578, 2297 December 1999. 2299 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2300 Rose, M. and S. Waldbusser, "Textual Conventions for 2301 SMIv2", STD 58, RFC 2579, December 1999. 2303 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2304 Rose, M. and S. Waldbusser, "Conformance Statements for 2305 SMIv2", STD 58, RFC 2580, December 1999. 2307 9. Informative References 2309 [RFC3410] Case, J., Mundy, R., Partain, D. and Stewart, B., 2310 "Introduction and Applicability Statements for Internet 2311 Standard Management Framework", RFC 3410, December 2002 2313 8. Authors' Addresses 2315 Alan Clark 2316 Telchemy Incorporated 2317 3360 Martins Farm Road, Ste 200 2318 Suwanee, Georgia 30024 2319 U.S.A. 2321 Email: alan@telchemy.com 2323 Amy Pendleton 2324 Nortel 2325 2380 Performance Drive 2326 Richardson, Texas 75081 2327 U.S.A. 2329 Email: aspen@nortel.com 2331 9. Full Copyright Statement 2333 Copyright (C) The Internet Society (2005). This document is subject 2334 to the rights, licenses and restrictions contained in BCP 78, and 2335 except as set forth therein, the authors retain all their rights. 2337 This document and translations of it may be copied and furnished to 2338 others, and derivative works that comment on or otherwise explain it 2339 or assist in its implementation may be prepared, copied, published 2340 and distributed, in whole or in part, without restriction of any 2341 kind, provided that the above copyright notice and this paragraph are 2342 included on all such copies and derivative works. However, this 2343 document itself may not be modified in any way, such as by removing 2344 the copyright notice or references to the Internet Society or other 2345 Internet organizations, except as needed for the purpose of 2346 developing Internet standards in which case the procedures for 2347 copyrights defined in the Internet Standards process must be 2348 followed, or as required to translate it into languages other than 2349 English. 2351 The limited permissions granted above are perpetual and will not be 2352 revoked by the Internet Society or its successors or assigns. 2354 This document and the information contained herein are provided on 2355 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 2356 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 2357 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 2358 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2359 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2360 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.