idnits 2.17.1 draft-ietf-avt-rtcp-xr-mib-00.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.a on line 18. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 669. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 681. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 40), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 40. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** The document seems to lack an RFC 3978 Section 5.5 (updated by RFC 4748) Disclaimer -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. 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 13 longer pages, the longest (page 1) being 72 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 17 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC3410' is mentioned on line 74, but not defined == Unused Reference: 'RFC3611' is defined on line 689, but no explicit reference was found in the text == Unused Reference: 'RFC2571' is defined on line 693, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 697, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 701, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 704, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 720, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 724, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 728, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 732, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 741, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 745, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 752, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 20 errors (**), 0 flaws (~~), 17 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Audio/Video Working Group Alan Clark 3 Internet-Draft Telchemy 4 Expires: April 10, 2005 Amy Pendleton 5 Nortel Networks 7 Proposed RTP Control Protocol Extended Reports (RTCP XR) 8 VoIP Metrics Management Information Base 9 draft-ietf-avt-rtcp-xr-mib-00.txt 11 Status of this Memo 13 This document is an Internet-Draft and is subject to all provisions 14 of section 3 of RFC 3667. By submitting this Internet-Draft, each 15 author represents that any applicable patent or other IPR claims of 16 which he or she is aware have been or will be disclosed, and any of 17 which he or she become aware will be disclosed, in accordance with 18 RFC 3668. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as 23 Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at http:// 31 www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on April 10, 2005. 38 Copyright Notice 40 Copyright (C) The Internet Society (2004). All Rights Reserved. 42 This document is a product of the Audio-Visual Transport (AVT) 43 working group of the Internet Engineering Task Force. Comments are 44 solicited and should be addressed to the working group's mailing 45 list at avt@ietf.org and/or the authors. 47 Abstract 49 This memo defines a portion of the Management Information Base (MIB) 50 for use with network management protocols in the Internet community. 51 In particular, it defines objects for managing Real-Time Transport 52 Control Protocol Extended Reports (RTCP XR) VoIP Metrics (RFC3611). 54 Table of Contents 56 1. The Network Management Framework ............................. 2 57 2. Overview ..................................................... 3 58 2.1 Components .................................................. 3 59 2.2 Applicability of the MIB to RTP System Implementations ...... 4 60 2.3 The Structure of the RTCP XR MIB ............................ 4 61 2.4 Relationship to the RAQMON Architecture...................... 4 62 3 Definitions ................................................... 4 63 4. Security Considerations ...................................... 14 64 5. Acknowledgements ............................................. 14 65 6. Intellectual Property ........................................ 14 66 7. References ................................................... 15 67 8. Authors' Addresses ........................................... 17 68 9. Full Copyright Statement ..................................... 17 70 1. The Internet-Standard Management Framework 72 For a detailed overview of the documents that describe the current 73 Internet-Standard Management Framework, please refer to section 7 of 74 RFC 3410 [RFC3410]. 76 Managed objects are accessed via a virtual information store, termed 77 the Management Information Base or MIB. MIB objects are generally 78 accessed through the Simple Network Management Protocol (SNMP). 79 Objects in the MIB are defined using the mechanisms defined in the 80 Structure of Management Information (SMI). This memo specifies a MIB 81 module that is compliant to the SMIv2, which is described in STD 58, 82 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 83 [RFC2580]. 85 2. Overview 87 An "RTP System" may be a host end-system that runs an application 88 program that sends or receives RTP data packets, or it may be an 89 intermediate-system that forwards RTP packets. RTP Control Protocol 90 (RTCP) packets are sent by senders and receivers to convey 91 information about RTP packet transmission and reception [RFC3550]. 92 RTP monitors may collect RTCP information on senders and receivers to 93 and from an RTP host or intermediate-system. 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in RFC 2119. 99 2.1 Components 101 The RTCP XR MIB is structured around "Session," "Receiver" and 102 "Sender" conceptual abstractions. 104 2.1.1 An RTP Session is an association of two or more participants 105 communicating with RTP. For each participant, the session is defined 106 by a particular pair of destination transport addresses (one network 107 address plus a port pair for RTP and RTCP). The destination 108 transport addresses may be common for all participants, as in the 109 case of IP multicast, or may be different for each, as in the case of 110 individual unicast addresses plus a common port pair," as defined in 111 section 3 of [RFC3550]. 113 2.1.2 A "Sender" is identified within an RTP session by a 32-bit 114 numeric "Synchronization Source," or "SSRC", value and is "...the 115 source of a stream of RTP packets" as defined in section 3 of 116 [RFC3550]. The sender is also a source of RTCP Sender Report packets 117 as specified in section 6 of [RFC3550]. 119 2.1.3 A "Receiver" of a "stream of RTP packets" can be a unicast or 120 multicast Receiver as described in 2.1.1, above. An RTP Receiver has 121 an SSRC value that is unique to the session. An RTP Receiver is a 122 source of RTCP Receiver Reports as specified in section 6 of 123 [RFC3550]. 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). 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.2.3 Many host systems will want to keep track of streams beyond 145 what they are sending and receiving. In a host monitor system, a 146 host agent would use RTP data from the host to maintain data about 147 streams it is sending and receiving, and RTCP data to collect data 148 about other hosts in the session. 150 2.3 The Structure of the RTCP XR MIB 152 There is one table in the RTCP XR MIB. The rtpXrVoipTable contains 153 objects that describe completed sessions at the host or monitor. 155 rtpXrVoipIndex is a global object that permits a network management 156 application to obtain a unique index for conceptual row creation 157 in the rtpSessionTable. In this way the SNMP Set operation MAY 158 be used to configure a monitor. 160 2.4 Relationship to the RAQMON Architecture 162 3. Definitions 164 RTCPXR-MIB DEFINITIONS ::= BEGIN 165 IMPORTS 166 Counter32, Counter64, Gauge32, mib-2, Integer32, 167 MODULE-IDENTITY, 168 OBJECT-TYPE, Unsigned32 FROM SNMPv2-SMI 169 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF 170 InterfaceIndex FROM IF-MIB 171 ItuPerceivedSeverity FROM ITU-ALARM-TC; 173 rtcpXrMIB MODULE-IDENTITY 174 LAST-UPDATED "200409120000Z" 175 ORGANIZATION 176 "IETF AVT Working Group" 177 DESCRIPTION 178 "The managed objects of RTCP XR systems. 179 Refer to RFC 3611, Real Time Control Protocol Extended 180 Reports (RTCP XR) Section 4.7 VoIP Metrics" 181 REVISION "200409120000Z" 182 DESCRIPTION "Initial version of this MIB. 183 Published as draft-ietf-avt-rtcpxrmib-00.txt." 185 ::= { mib-2 TBD } 187 -- 188 -- OBJECTS 189 -- 190 rtcpXrMIBObjects OBJECT IDENTIFIER ::= { rtcpXrMIB 1 } 191 rtcpXrConformance OBJECT IDENTIFIER ::= { rtcpXrMIB 2 } 192 rtcpXrEvents OBJECT IDENTIFIER ::= { rtcpXrMIB 3 } 194 -- 195 -- RTCP Extended Reports - Voice over IP Metrics 196 -- 197 -- Description 198 -- This MIB provides basic voice quality monitoring capabilities 199 -- for Voice-over-packet systems. The MIB contains 5 tables of 200 -- information:- 201 -- a table with one entry for each voice terminationPoint 202 -- a table that defines the parameters associated with voice 203 -- coders 204 -- a table of call records with call identifying and quality 205 -- information 206 -- a table of extended call records with additional metrics 207 -- a table of Termination Point groups with one entry per 208 -- logical group 210 rtcpXrVoipTable OBJECT-TYPE 211 SYNTAX SEQUENCE OF rtcpXrVoipEntry 212 ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "Table of information about a receiver or receivers of RTCP XR 216 session data. RTP hosts that receive RTCP XR session packets 217 MUST create an entry in this table for that receiver/sender 218 pair. RTP hosts that send RTCP XR session packets MAY create 219 an entry in this table for each receiver to their stream 220 using RTCP XR feedback from the RTP group. " 221 ::= { rtcpXrMIBObjects 1 } 223 rtcpXrVoipEntry OBJECT-TYPE 224 SYNTAX rtcpXrVoipEntry 225 STATUS current 226 DESCRIPTION 227 "An entry in the table of call records. A row in this table 228 is created for each RTP session endpoint participating." 229 INDEX { rtcpXrVoipIndex } 230 ::= { rtcpXrVoipTable 1 } 232 rtcpXrVoipEntry ::= SEQUENCE { 233 rtcpXrVoipIndex INTEGER, 234 rtcpXrVoipCallIdentifier OCTET STRING, 235 rtcpXrVoipSessionIdentifier OCTET STRING, 236 rtcpXrVoipSourceIPaddress OCTET STRING, 237 rtcpXrVoipSourceIdentifier OCTET STRING, 238 rtcpXrVoipDestinationIPaddress OCTET STRING, 239 rtcpXrVoipDestinationIdentifier OCTET STRING, 240 rtcpXrVoipVocoderType OCTET STRING, 241 rtcpXrVoipFrameSize INTEGER, 242 rtcpXrVoipSmapleRate INTEGER, 243 rtcpXrVoipCallDurationMs INTEGER, 244 rtcpXrVoipNetworkLossRate INTEGER, 245 rtcpXrVoipAverageDiscardRate INTEGER, 246 rtcpXrVoipBurstLossDensity INTEGER, 247 rtcpXrVoipBurstLenMs INTEGER, 248 rtcpXrVoipGapLossDensity INTEGER, 249 rtcpXrVoipGapLenMs INTEGER, 250 rtcpXrVoipAverageOneWayDelay INTEGER, 251 rtcpXrVoipEndSystemDelay INTEGER, 252 rtcpXrVoipNoiseLeveldBm INTEGER, 253 rtcpXrVoipSignalLeveldBm INTEGER, 254 rtcpXrVoipLocalRERLdB INTEGER, 255 rtcpXrVoipConversationalR INTEGER, 256 rtcpXrVoipListeningR INTEGER, 257 rtcpXrVoipListeningMOSLQ INTEGER, 258 rtcpXrVoipConversationalMOSCQ INTEGER, 259 rtcpXrVoipPlcType INTEGER, 260 rtcpXrVoipJitterBufferAdaptationMode INTEGER, 261 rtcpXrVoipJitterBufferAdaptationRate INTEGER, 262 rtcpXrVoipJitterBufferAverageDelay INTEGER, 263 rtcpXrVoipJitterBufferMaximumDelay INTEGER, 264 rtcpXrVoipJitterBufferSize INTEGER 265 } 267 rtcpXrVoipIndex OBJECT-TYPE 268 SYNTAX INTEGER (0..65535) 269 STATUS current 270 DESCRIPTION 271 "Index for this call." 272 ::= { rtcpXrVoipEntry 1 } 274 rtcpXrVoipCallIdentifier OBJECT-TYPE 275 SYNTAX OCTET STRING 276 STATUS optional 277 DESCRIPTION 278 "Call identifier for this call." 279 ::= { rtcpXrVoipEntry 2 } 281 rtcpXrVoipSessionIdentifier OBJECT-TYPE 282 SYNTAX OCTET STRING 283 STATUS optional 284 DESCRIPTION 285 "Unique identifier for this session. Where a billing record 286 correlation identifer is not available for a particular call, 287 another identifier such as SSRC can be used." 288 ::= { rtcpXrVoipEntry 3 } 290 rtcpXrVoipSourceIPaddress OBJECT-TYPE 291 SYNTAX OCTET STRING 292 STATUS optional 293 DESCRIPTION 294 "Source IP address for this session." 295 ::= { rtcpXrVoipEntry 4 } 297 rtcpXrVoipSourceIdentifierType OBJECT-TYPE 298 SYNTAX INTEGER { dialedNumber(0), 299 urlId (1) } 300 DESCRIPTION 301 "Defines the type of address in parameter 302 rtcpXrVoipSourceIdentifier" 303 ::= { rtcpXrVoipEntry 5 } 305 rtcpXrVoipSourceIdentifier OBJECT-TYPE 306 SYNTAX OCTET STRING 307 STATUS optional 308 DESCRIPTION 309 "Alternate identifier to the IP address. This can be E.164, 310 DN,or URL." 311 ::= { rtcpXrVoipEntry 6 } 313 rtcpXrVoipDestinationIPaddress OBJECT-TYPE 314 SYNTAX OCTET STRING 315 STATUS current 316 DESCRIPTION 317 "Source IP address for this session." 318 ::= { rtcpXrVoipEntry 7 } 320 rtcpXrVoipDestinationIdentifierType OBJECT-TYPE 321 SYNTAX INTEGER { dialedNumber(0), 322 urlId (1) } 323 DESCRIPTION 324 "Defines the type of address in parameter 325 rtcpXrVoipDestinationIdentifier" 326 ::= { rtcpXrVoipEntry 8 } 328 rtcpXrVoipDestinationIdentifier OBJECT-TYPE 329 SYNTAX OCTET STRING 330 STATUS current 331 DESCRIPTION 332 "Alternate identifier to the IP address. This can be E.164, 333 DN, or URL." 334 ::= { rtcpXrVoipEntry 9 } 336 rtcpXrVoipVocoderType OBJECT-TYPE 337 SYNTAX OCTET STRING 338 STATUS current 339 DESCRIPTION 340 "Vocoder type used on this call." 341 ::= { rtcpXrVoipEntry 10 } 343 rtcpXrVoipFrameSize OBJECT-TYPE 344 SYNTAX INTEGER 345 STATUS current 346 DESCRIPTION 347 "Companion information to vocoder type. This represents the 348 size of the frames within the RTP packets at the time the 349 information is capture." 350 ::= { rtcpXrVoipEntry 11 } 352 rtcpXrVoipSampleRate OBJECT-TYPE 353 SYNTAX OCTET STRING 354 STATUS current 355 DESCRIPTION 356 "Companion information to vocoder type. This represents the 357 rate at which the frames where sampled. 358 ::= { rtcpXrVoipEntry 12 } 360 rtcpXrVoipCallDurationMs OBJECT-TYPE 361 SYNTAX INTEGER 362 STATUS current 363 DESCRIPTION 364 "Duration of call in milliseconds." 365 ::= { rtcpXrVoipEntry 13 } 367 rtcpXrVoipStartTimestamp OBJECT-TYPE 368 SYNTAX INTEGER 369 ACCESS read-only 370 STATUS mandatory 371 DESCRIPTION 372 "The timestamp captured at the start of the session." 373 ::= { rtcpXrVoipEntry 14 } 375 rtcpXrVoipEndTimestamp OBJECT-TYPE 376 SYNTAX INTEGER 377 STATUS current 378 DESCRIPTION 379 "The timestamp captured at the end of the session." 380 ::= { rtcpXrVoipEntry 15 } 382 rtcpXrVoipNetworkLossRate OBJECT-TYPE 383 SYNTAX INTEGER 384 STATUS current 385 DESCRIPTION 386 "Average rate of network packet loss (RFC3611 Section 4.7)." 387 ::= { rtcpXrVoipEntry 16 } 389 rtcpXrVoipAverageDiscardRate OBJECT-TYPE 390 SYNTAX INTEGER 391 STATUS current 392 DESCRIPTION 393 "Average rate of discards due to jitter(RFC3611 Section 4.7)." 394 ::= { rtcpXrVoipEntry 17 } 396 rtcpXrVoipBurstLossDensity OBJECT-TYPE 397 SYNTAX INTEGER 398 STATUS current 399 DESCRIPTION 400 "Density of loss and discarded packets during burst periods. 401 (see RFC3611 Section 4.7)" 402 ::= { rtcpXrVoipEntry 18 } 404 rtcpXrVoipBurstLenMs OBJECT-TYPE 405 SYNTAX INTEGER 406 STATUS current 407 DESCRIPTION 408 "Average length of bursts in milliseconds (RFC3611 409 Section 4.7)." 410 ::= { rtcpXrVoipEntry 19 } 412 rtcpXrVoipGapLossDensity OBJECT-TYPE 413 SYNTAX INTEGER 414 STATUS current 415 DESCRIPTION 416 "Density of loss and discarded packets during gap periods 417 (see RFC3611 Section 4.7)." 418 ::= { rtcpXrVoipEntry 20 } 420 rtcpXrVoipGapLenMs OBJECT-TYPE 421 SYNTAX INTEGER 422 STATUS current 423 DESCRIPTION 424 "Average length of gaps in milliseconds (see RFC3611 425 Section 4.7)." 426 ::= { rtcpXrVoipEntry 21 } 428 rtcpXrVoipAverageOneWayDelay OBJECT-TYPE 429 SYNTAX INTEGER 430 STATUS current 431 DESCRIPTION 432 "Average (symmetric) one way RTCP delay on call. A value of 433 zero may indicate that this value has not yet been determined. 434 (see RFC3611 Section 4.7)." 435 ::= { rtcpXrVoipEntry 22 } 437 rtcpXrVoipEndSystemDelay OBJECT-TYPE 438 SYNTAX INTEGER 439 STATUS current 440 DESCRIPTION 441 "Average end system delay on call. A value of zero may 442 indicate that this value has not yet been determined 443 (see RFC3611 Section 4.7)." 444 ::= { rtcpXrVoipEntry 23 } 446 rtcpXrVoipNoiseLeveldBm OBJECT-TYPE 447 SYNTAX INTEGER 448 STATUS current 449 DESCRIPTION 450 "Measured received silent period noise level in dBm 451 (see RFC3611 Section 4.7)." 452 ::= { rtcpXrVoipEntry 24 } 454 rtcpXrVoipSignalLeveldBm OBJECT-TYPE 455 SYNTAX INTEGER 456 STATUS current 457 DESCRIPTION 458 "Measured received signal level during talkspurts in dBm 459 (see RFC3611 Section 4.7)." 460 ::= { rtcpXrVoipEntry 25 } 462 rtcpXrVoipLocalRERLdB OBJECT-TYPE 463 SYNTAX INTEGER 464 STATUS current 465 DESCRIPTION 466 "Residual Echo Return Loss measured at this endpoint 467 (see RFC3611 Section 4.7)." 468 ::= { rtcpXrVoipEntry 26 } 470 rtcpXrVoipConversationalRCQ OBJECT-TYPE 471 SYNTAX INTEGER 472 STATUS current 473 DESCRIPTION 474 "Conversational quality R factor for this call 475 (see RFC3611 Section 4.7)." 476 ::= { rtcpXrVoipEntry 27 } 478 rtcpXrVoipListeningMOSLQ OBJECT-TYPE 479 SYNTAX INTEGER 480 STATUS current 481 DESCRIPTION 482 "Estimated listening quality MOS for this call 483 (see RFC3611 Section 4.7)." 484 ::= { rtcpXrVoipEntry 28 } 486 rtcpXrVoipConversationalMOSCQ OBJECT-TYPE 487 SYNTAX INTEGER 488 STATUS current 489 DESCRIPTION 490 "Estimated conversational quality MOS for this call 491 (see RFC3611 Section 4.7)." 492 ::= { rtcpXrVoipEntry 29 } 494 rtcpXrVoipPlcType OBJECT-TYPE 495 SYNTAX INTEGER { disabled(1), 496 enhanced(2), 497 standard(3), 498 unspecified (4)} 499 STATUS current 500 DESCRIPTION 501 "Defines type of packet loss concealment used on this call 502 (see RFC3611 Section 4.7)." 503 ::= { rtcpXrVoipEntry 30 } 505 rtcpXrVoipJitterBufferAdaptationMode OBJECT-TYPE 506 SYNTAX INTEGER { reserved (1), 507 nonAdaptive (2), 508 adaptive (3), 509 unknown (4) } 510 STATUS current 511 DESCRIPTION 512 "Defines if jitter buffer is in fixed or adaptive mode 513 (see RFC3611 Section 4.7)." 514 ::= { rtcpXrVoipEntry 31 } 516 rtcpXrVoipJitterBufferAdaptationRate OBJECT-TYPE 517 SYNTAX INTEGER 518 STATUS current 519 DESCRIPTION 520 "Estimated adaptation rate of jitter buffer 521 (see RFC3611 Section 4.7)." 522 ::= { rtcpXrVoipEntry 32 } 524 rtcpXrVoipJitterBufferAverageDelay OBJECT-TYPE 525 SYNTAX INTEGER 526 STATUS current 527 DESCRIPTION 528 "Average size of jitter buffer in mS 529 (see RFC3611 Section 4.7)." 530 ::= { rtcpXrVoipEntry 33 } 532 rtcpXrVoipJitterBufferMaximumDelay OBJECT-TYPE 533 SYNTAX INTEGER 534 STATUS current 535 DESCRIPTION 536 "Maximum delay through jitter buffer at current size in mS 537 (see RFC3611 Section 4.7)." 538 ::= { rtcpXrVoipEntry 34 } 540 rtcpXrVoipJitterBufferSize OBJECT-TYPE 541 SYNTAX INTEGER 542 STATUS current 543 DESCRIPTION 544 "Absolute maximum size jitter buffer can reach in mS 545 (see RFC3611 Section 4.7)." 546 ::= { rtcpXrVoipEntry 35 } 548 -- Notifications 550 rtcpXrVoipNotifications OBJECT IDENTIFIER ::= { rtcpXrEvents 0 } 552 -- 553 -- RTCP XR Threshold Violation Notification 554 -- 555 -- RTCP XR issues event notification when two conditions are met: 556 -- 1) The notification is enabled for a specified endpoint 557 -- 2) The voice quality falls below the specified threshold 558 -- 560 rtcpXrVoipThresholdViolation TRAP-TYPE 561 ENTERPRISE rtcpXrVoipNotifications 562 VARIABLES { rtcpXrVoipAlertSeverity, rtcpXrVoipAlertType, 563 rtcpXrVoipIndex} 564 DESCRIPTION 565 "Notification that voice quality has changed 566 Sent immediately when the condition is detected." 567 ::= 1 569 -- 570 -- Definition of Alert Severity: import from Alarm MIB 571 -- 573 rtcpXrVoipAlertSeverity OBJECT-TYPE 574 SYNTAX ItuPerceivedSeverity 575 STATUS current 576 DESCRIPTION 577 "The severity of the alert as defined in ITU-T X.733." 578 ::= { rtcpXrVoipEntry 36 } 580 -- 581 -- 582 -- The definition of the syntax is as follows: 583 -- 584 -- ItuPerceivedSeverity ::= TEXTUAL-CONVENTION 585 -- STATUS current 586 -- DESCRIPTION 587 -- "ITU perceived severity values" 588 -- REFERENCE 589 -- "ITU Recommendation M.3100, 'Generic Network 590 -- Information Model', 1995 591 -- ITU Recommendation X.733, 'Information Technology 592 -- - Open Systems Interconnection - System Management: 593 -- Alarm Reporting Function', 1992" 594 -- SYNTAX INTEGER 595 -- { 596 -- cleared (1), 597 -- indeterminate (2), 598 -- critical (3), 599 -- major (4), 600 -- minor (5), 601 -- warning (6) 602 -- } 603 -- 604 -- 605 -- In use with these alarms, the cleared value will not be used 606 -- due the size of alarms. 608 rtcpXrVoipAlertType OBJECT-TYPE 609 SYNTAX OCTET STRING 610 ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "Text description of the type of alert. Where possible, 614 this parameter should be populated with the correct 615 rtcpXrVoipEventsEntry" 616 ::= { rtcpXrVoipEntry 37 } 618 4. Security Considerations 620 In most cases, MIBs are not themselves security risks; if SNMP 621 security is operating as intended, the use of a MIB to view 622 information about a system, or to change some parameter at the 623 system, is a tool, not a threat. 625 None of the read-only objects in this MIB reports a password, though 626 some SDES [RFC3550] items such as the CNAME [RFC3550], the canonical 627 name, may be deemed sensitive depending on the security policies of a 628 particular enterprise. If access to these objects is not limited by 629 an appropriate access control policy, these objects can provide an 630 attacker with information about a system's configuration and the 631 services that that system is providing. Some enterprises view their 632 network and system configurations, as well as information about usage 633 and performance, as corporate assets; such enterprises may wish to 634 restrict SNMP access to most of the objects in the MIB. 636 Confidentiality of RTP and RTCP data packets is defined in section 9 637 of the RTP specification [RFC3550]. Encryption may be performed on 638 RTP packets, RTCP packets, or both. Encryption of RTCP packets may 639 pose a problem for third-party monitors though "For RTCP, it is 640 allowed to split a compound RTCP packet into two lower-layer packets, 641 one to be encrypted and one to be sent in the clear. For example, 642 SDES information might be encrypted while reception reports were sent 643 in the clear to accommodate third-party monitors [RFC3550]." 645 SNMPv1 by itself is not a secure environment. Even if the network 646 itself is secure (for example by using IPSec), there is no control as 647 to who on the secure network is allowed to access and GET/SET 648 (read/change/create/delete) the objects in this MIB. It is 649 recommended that the implementers consider the security features as 650 provided by the SNMPv3 framework. Specifically, the use of the 651 User-based Security Model RFC 2574 [RFC2574] and the View-based 652 Access Control Model RFC 2575 [RFC2575] is recommended. It is then a 653 customer/user responsibility to ensure that the SNMP entity giving 654 access to an instance of this MIB, is properly configured to give 655 access to the objects only to those principals (users) that have 656 legitimate rights to indeed GET or SET (change/create/delete) them. 658 5. Acknowledgements 660 6. Intellectual Property 662 The IETF takes no position regarding the validity or scope of any 663 Intellectual Property Rights or other rights that might be claimed to 664 pertain to the implementation or use of the technology described in 665 this document or the extent to which any license under such rights 666 might or might not be available; nor does it represent that it has 667 made any independent effort to identify any such rights. Information 668 on the procedures with respect to rights in RFC documents can be 669 found in BCP 78 and BCP 79. 671 Copies of IPR disclosures made to the IETF Secretariat and any 672 assurances of licenses to be made available, or the result of an 673 attempt made to obtain a general license or permission for the use of 674 such proprietary rights by implementers or users of this 675 specification can be obtained from the IETF on-line IPR repository at 676 http://www.ietf.org/ipr. 677 The IETF invites any interested party to bring to its attention any 678 copyrights, patents or patent applications, or other proprietary 679 rights which may cover technology that may be required to practice 680 this standard. Please address the information to the IETF at 681 ietf-ipr@ietf.org. 683 7. Normative References 685 [RFC3550] Shulzrinne, H., Casner, S., Frederick, R. and V. 686 Jacobson, "RTP: A Transport Protocol for real-time 687 applications," RFC 3550, July 2003. 689 [RFC3611] Friedman, T., Caceres, R., Clark, A., "RTP Control 690 Protocol Reporting Extensions (RTCP XR)," RFC 3611, 691 [October/November] 2003 693 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 694 Architecture for Describing SNMP Management Frameworks", 695 RFC 2571, December 1999. 697 [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification 698 of Management Information for TCP/IP-based Internets", 699 STD 16, RFC 1155, May 1990. 701 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", 702 STD 16, RFC 1212, April 1991. 704 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 705 the SNMP", RFC 1215, April 1991. 707 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 708 Rose, M. and S. Waldbusser, "Structure of Management 709 Information Version 2 (SMIv2)", STD 58, RFC 2578, 710 December 1999. 712 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 713 Rose, M. and S. Waldbusser, "Textual Conventions for 714 SMIv2", STD 58, RFC 2579, December 1999. 716 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 717 Rose, M. and S. Waldbusser, "Conformance Statements for 718 SMIv2", STD 58, RFC 2580, December 1999. 720 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, 721 "Simple Network Management Protocol", STD 15, RFC 1157, 722 May 1990. 724 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 725 "Introduction to Community-based SNMPv2", RFC 1901, 726 April 1996. 728 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 729 "Transport Mappings for Version 2 of the Simple Network 730 Management Protocol (SNMPv2)", RFC 1906, April 1996. 732 [RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen, 733 "Message Processing and Dispatching for the Simple 734 Network Management Protocol (SNMP)", RFC 2572, December 735 1999. 737 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 738 (USM) for version 3 of the Simple Network Management 739 Protocol (SNMPv3)", RFC 2574, December 1999. 741 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 742 "Protocol Operations for Version 2 of the Simple Network 743 Management Protocol (SNMPv2)", RFC 1905, April 1996. 745 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 746 Applications", RFC 2573, December 1999. 748 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 749 Access Control Model (VACM) for the Simple Network 750 Management Protocol (SNMP)", RFC 2575, December 1999. 752 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 753 "Introduction to Version 3 of the Internet-standard 754 Network 755 Management Framework", RFC 2570, December 1999. 757 8. Authors' Addresses 759 Alan Clark 760 Telchemy Incorporated 761 3360 Martins Farm Road, Ste 200 762 Suwanee, Georgia 30024 763 U.S.A. 765 Email: alan@telchemy.com 767 Amy Pendleton 768 Nortel Networks 769 2380 Performance Drive 770 Richardson, Texas 75081 771 U.S.A. 773 Email: aspen@nortelnetworks.com 775 9. Full Copyright Statement 777 Copyright (C) The Internet Society (2004). This document is subject 778 to the rights, licenses and restrictions contained in BCP 78, and 779 except as set forth therein, the authors retain all their rights. 781 This document and translations of it may be copied and furnished to 782 others, and derivative works that comment on or otherwise explain it 783 or assist in its implementation may be prepared, copied, published 784 and distributed, in whole or in part, without restriction of any 785 kind, provided that the above copyright notice and this paragraph are 786 included on all such copies and derivative works. However, this 787 document itself may not be modified in any way, such as by removing 788 the copyright notice or references to the Internet Society or other 789 Internet organizations, except as needed for the purpose of 790 developing Internet standards in which case the procedures for 791 copyrights defined in the Internet Standards process must be 792 followed, or as required to translate it into languages other than 793 English. 795 The limited permissions granted above are perpetual and will not be 796 revoked by the Internet Society or its successors or assigns. 798 This document and the information contained herein is provided on an 799 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 800 REPRESENTS OR IS SPONSORED BY, THE INTERNET SOCIETY AND THE INTERNET 801 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, 802 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 803 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 804 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.