idnits 2.17.1 draft-ietf-avt-mib-rtp-bis-01.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 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1523. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1534. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1541. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1547. ** 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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. 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.) -- The document date (June 2006) is 6524 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) == Missing Reference: 'RFC2574' is mentioned on line 1425, but not defined ** Obsolete undefined reference: RFC 2574 (Obsoleted by RFC 3414) == Missing Reference: 'RFC2575' is mentioned on line 1426, but not defined ** Obsolete undefined reference: RFC 2575 (Obsoleted by RFC 3415) == Unused Reference: 'RFC3611' is defined on line 1470, but no explicit reference was found in the text Summary: 5 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force A. Clark 2 Internet-Draft Telchemy Incorporated 3 Expires: 22 December 2006 A. Pendleton 4 Nortel 5 June 2006 7 Real-time Transport Protocol (RTP) MIB Version 2 8 draft-ietf-avt-mib-rtp-bis-01 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as 20 Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on 22 December 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 This memo defines a portion of the Management Information Base (MIB) 42 for use with network management protocols in the Internet community. 43 In particular, it defines objects for managing Real-Time Transport 44 Protocol (RTP) systems (RFC3550) and is a proposed replacement for 45 RFC 2959 - the RTP MIB. 47 Table of Contents 48 1. The Network Management Framework ............................. 2 49 2. Overview ..................................................... 2 50 2.1 Components .................................................. 2 51 2.2 Applicability of the MIB to RTP System Implementations ...... 3 52 2.3 The Structure of the RTP MIB ................................ 4 53 3 Definitions ................................................... 4 54 4. Security Considerations ...................................... 27 55 5. IANA Considerations .......................................... 28 56 6. Acknowledgements ............................................. 28 57 7. Intellectual Property ........................................ 28 58 8. References ................................................... 28 59 9. Informative References ....................................... 29 60 10. Authors' Addresses .......................................... 29 61 Full Copyright Statement ........................................ 29 63 1. The Internet-Standard Management Framework 65 For a detailed overview of the documents that describe the current 66 Internet-Standard Management Framework, please refer to section 7 of 67 RFC 3410 [RFC3410]. 69 Managed objects are accessed via a virtual information store, termed 70 the Management Information Base or MIB. MIB objects are generally 71 accessed through the Simple Network Management Protocol (SNMP). 72 Objects in the MIB are defined using the mechanisms defined in the 73 Structure of Management Information (SMI). This memo specifies a MIB 74 module that is compliant to the SMIv2, which is described in STD 58, 75 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 76 [RFC2580]. 78 2. Overview 79 An "RTP System" may be a host end-system that runs an application 80 program that sends or receives RTP data packets, or it may be an 81 intermediate-system that forwards RTP packets. RTP Control Protocol 82 (RTCP) packets are sent by senders and receivers to convey 83 information about RTP packet transmission and reception [RFC3550]. 84 RTP monitors may collect RTCP information on senders and receivers to 85 and from an RTP host or intermediate-system. 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in RFC 2119. 91 2.1 Components 92 The RTP MIB is structured around "Session," "Receiver" and "Sender" 93 conceptual abstractions. 95 2.1.1 An "RTP Session" is the "...association of participants 96 communicating with RTP. For each participant, the session is defined 97 by a particular pair of destination transport addresses (one network 98 address plus a port pair for RTP and RTCP). The destination 99 transport addresses may be common for all participants, as in the 100 case of IP multicast, or may be different for each, as in the case of 101 individual unicast addresses plus a common port pair," as defined in 102 section 3 of [RFC3550]. 104 2.1.2 A "Sender" is identified within an RTP session by a 32-bit 105 numeric "Synchronization Source," or "SSRC", value and is "...the 106 source of a stream of RTP packets" as defined in section 3 of 107 [RFC3550]. The sender is also a source of RTCP Sender Report packets 108 as specified in section 6 of [RFC3550]. 110 2.1.3 A "Receiver" of a "stream of RTP packets" can be a unicast or 111 multicast Receiver as described in 2.1.1, above. An RTP Receiver has 112 an SSRC value that is unique to the session. An RTP Receiver is a 113 source of RTCP Receiver Reports as specified in section 6 of 114 [RFC3550]. 116 2.2 Applicability of the MIB to RTP System Implementations 117 The RTP MIB may be used in two types of RTP implementations, RTP Host 118 Systems (end systems) and RTP Monitors, see section 3 of [RFC3550]. 119 Use of the RTP MIB for RTP Translators and Mixers, as defined in 120 section 7 of [RFC3550], is for further study. 122 2.2.1 RTP host Systems are end-systems that may use the RTP MIB to 123 collect RTP session and stream data that the host is sending or 124 receiving; these data may be used by a network manager to detect and 125 diagnose faults that occur over the lifetime of an RTP session as in 126 a "help-desk" scenario. 128 2.2.2 RTP Monitors of multicast RTP sessions may be third-party or 129 may be located in the RTP host. RTP Monitors may use the RTP MIB to 130 collect RTP session and stream statistical data; these data may be 131 used by a network manager for capacity planning and other network- 132 management purposes. An RTP Monitor may use the RTP MIB to collect 133 data to permit a network manager to detect and diagnose faults in RTP 134 sessions or to permit a network manger to configure its operation. 136 2.2.3 Many host systems will want to keep track of streams beyond 137 what they are sending and receiving. In a host monitor system, a 138 host agent would use RTP data from the host to maintain data about 139 streams it is sending and receiving, and RTCP data to collect data 140 about other hosts in the session. For example, an agent for an RTP 141 host that is sending a stream would use data from its RTP system to 142 maintain the rtpSenderTable, but it may want to maintain a 143 rtpRcvrTable for endpoints that are receiving its stream. To do this 144 the RTP agent will collect RTCP data from the receivers of its stream 145 to build the rtpRcvrTable. A host monitor system MUST set the 146 rtpSessionMonitor object to 'true(1)', but it does not have to accept 147 management operations that create and destroy rows in its 148 rtpSessionTable. 150 2.2.4 The RTCP XR MIB provides extended data related to the 151 performance of Voice over IP streams. The RTP-MIBV2 and RTCP XR 152 MIBs have been designed to be used together to support the management 153 of Voice over IP systems. 155 2.3 The Structure of the RTP MIB 157 There are six tables in the RTP MIB. The rtpSessionTable contains 158 objects that describe active sessions at the host, or monitor. The 159 rtpSenderTable contains information about senders to the RTP session. 160 The rtpRcvrTable contains information about receivers of RTP session 161 data. The rtpSessionInverseTable, rtpSenderInverseTable, and 162 rtpRcvrInverseTable contain information to efficiently find indexes 163 into the rtpSessionTable, rtpSenderTable, and rtpRcvrTable, 164 respectively. 166 The reverse lookup tables (rtpSessionInverseTable, 167 rtpSenderInverseTable, and rtpRcvrInverseTable) are optional tables 168 to help management applications efficiently access conceptual rows in 169 other tables. Implementors of this MIB SHOULD implement these tables 170 for multicast RTP sessions when table indexes (rtpSessionIndex of 171 rtpSessionTable, rtpSenderSSRC of rtpSenderTable, and the SSRC pair 172 in the rtpRcvrTable) are not available from other MIBs. Otherwise, 173 the management application may be forced to perform expensive tree 174 walks through large numbers of sessions, senders, or receivers. 176 For any particular RTP session, the rtpSessionMonitor object 177 indicates whether remote senders or receivers to the RTP session are 178 to be monitored. If rtpSessionMonitor is true(1) then senders and 179 receivers to the session MUST be monitored with entries in the 180 rtpSenderTable and rtpRcvrTable. RTP sessions are monitored by the 181 RTP agent that updates rtpSenderTable and rtpRcvrTable objects with 182 information from RTCP reports from remote senders or remote receivers 183 respectively. 185 rtpSessionNewIndex is a global object that permits a network- 186 management application to obtain a unique index for conceptual row 187 creation in the rtpSessionTable. In this way the SNMP Set operation 188 MAY be used to configure a monitor. 190 3. Definitions 192 RTP-MIB DEFINITIONS ::= BEGIN 193 IMPORTS 194 Counter32, Counter64, Gauge32, mib-2, Integer32, 195 MODULE-IDENTITY, 196 OBJECT-TYPE, Unsigned32 FROM SNMPv2-SMI 197 InetAddressType, InetAddress, 198 InetPortNumber FROM INET-ADDRESS-MIB 199 RowStatus, TestAndIncr, 200 TruthValue, DateAndTime FROM SNMPv2-TC 201 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF 202 Utf8String FROM SYSAPPL-MIB 203 InterfaceIndex FROM IF-MIB; 205 rtpMIBV2 MODULE-IDENTITY 206 LAST-UPDATED "200602260000Z" -- 26 February 2006 207 ORGANIZATION 208 "IETF AVT Working Group 209 Email: avt@ietf.org" 210 CONTACT-INFO 211 "Alan Clark 212 Telchemy 213 3360 Martins Farm Rd 214 Suwanee, GA 20024 215 United States 216 Email: alan@telchemy.com 218 Amy Pendleton 219 Nortel 220 2380 Performance Drive 221 Richardson, TX 75081 222 Email: aspen@nortel.com" 224 DESCRIPTION 225 "The managed objects of RTP systems. The MIB is 226 structured around three types of information. 227 1. General information about RTP sessions such 228 as the session address. 229 2. Information about RTP streams being sent to 230 an RTP session by a particular sender. 231 3. Information about RTP streams received on an 232 RTP session by a particular receiver from a 233 particular sender. 234 There are two types of RTP Systems, RTP hosts and 235 RTP monitors. As described below, certain objects 236 are unique to a particular type of RTP System. An 237 RTP host may also function as an RTP monitor. 238 Refer to RFC 3550, 'RTP: A Transport Protocol for 239 Real-Time Applications,' section 3.0, for definitions." 240 REVISION "200602260000Z" -- 26 February 2006 241 DESCRIPTION "Version 2 of this MIB. 242 Published as draft-ietf-avt-mib-rtp-bis-01" 243 ::= { mib-2 nnn } 245 -- OBJECTS 246 -- 248 rtpMIBV2Objects OBJECT IDENTIFIER ::= { rtpMIBV2 1 } 249 rtpConformance OBJECT IDENTIFIER ::= { rtpMIBV2 2 } 251 -- SESSION NEW INDEX 252 -- 254 rtpSessionNewIndex OBJECT-TYPE 255 SYNTAX TestAndIncr 256 MAX-ACCESS read-write 257 STATUS current 258 DESCRIPTION 259 "This object is used to assign values to rtpSessionIndex 260 as described in 'Textual Conventions for SMIv2'. For an RTP 261 system that supports the creation of rows, the network manager 262 would read the object, and then write the value back in 263 the Set that creates a new instance of rtpSessionEntry. If 264 the Set fails with the code 'inconsistentValue,' then the 265 process must be repeated; If the Set succeeds, then the object 266 is incremented, and the new instance is created according to 267 the manager's directions. However, if the RTP agent is not 268 acting as a monitor, only the RTP agent may create conceptual 269 rows in the RTP session table." 270 ::= { rtpMIBV2Objects 1 } 272 -- SESSION INVERSE TABLE 273 -- 274 rtpSessionInverseTable OBJECT-TYPE 275 SYNTAX SEQUENCE OF RtpSessionInverseEntry 276 MAX-ACCESS not-accessible 277 STATUS current 278 DESCRIPTION 279 "Maps source and destination address to or more rtpSessionIndex 280 values describing rows in the rtpSessionTable. This allows 281 rows to be retrieved in the rtpSessionTable corresponding to a 282 given session without having to walk the entire (potentially 283 large) table." 284 ::= { rtpMIBV2Objects 2 } 286 rtpSessionInverseEntry OBJECT-TYPE 287 SYNTAX RtpSessionInverseEntry 288 MAX-ACCESS not-accessible 289 STATUS current 290 DESCRIPTION 291 "Each entry corresponds to exactly one entry in the 292 rtpSessionTable." 293 INDEX { rtpSessionSourceIPaddress, rtpSessionSourceRTPport, 294 rtpSessionDestIPaddress, rtpSessionDestRTPport, 295 rtpSessionCallState, rtpSessionIndex } 296 ::= { rtpSessionInverseTable 1 } 298 RtpSessionInverseEntry ::= SEQUENCE { 299 rtpSessionInverseStartTime DateAndTime 300 } 302 rtpSessionInverseStartTime OBJECT-TYPE 303 SYNTAX DateAndTime 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "The local time at which this row was 308 created." 309 ::= { rtpSessionInverseEntry 1 } 311 -- SESSION TABLE 312 -- 313 rtpSessionTable OBJECT-TYPE 314 SYNTAX SEQUENCE OF RtpSessionEntry 315 MAX-ACCESS not-accessible 316 STATUS current 317 DESCRIPTION 318 "There's one entry in rtpSessionTable for each RTP session 319 on which packets are being sent, received, and/or 320 monitored." 321 ::= { rtpMIBV2Objects 3 } 323 rtpSessionEntry OBJECT-TYPE 324 SYNTAX RtpSessionEntry 325 MAX-ACCESS not-accessible 326 STATUS current 327 DESCRIPTION 328 "Data in rtpSessionTable uniquely identify an RTP session. A 329 host RTP agent MUST create a read-only row for each session to 330 which packets are being sent or received. Rows MUST be created 331 by the RTP Agent at the start of a session when one or more 332 senders or receivers are observed. An RTP 333 session SHOULD be monitored to create management information on 334 all RTP streams being sent or received when the 335 rtpSessionMonitor has the TruthValue of 'true(1)'. An RTP 336 monitor SHOULD permit row creation with the side effect of 337 causing the RTP System to join the multicast session for the 338 purposes of gathering management information (additional 339 conceptual rows are created in the rtpRcvrTable and 340 rtpSenderTable). Thus, rtpSessionTable rows SHOULD be created 341 for RTP session monitoring purposes. Rows created by a 342 management application SHOULD be deleted via SNMP operations by 343 management applications. Rows created by management operations 344 are deleted by management operations by setting 345 rtpSessionRowStatus to 'destroy(6)'." 346 INDEX { rtpSessionCallState, rtpSessionIndex } 347 ::= { rtpSessionTable 1 } 349 RtpSessionEntry ::= SEQUENCE { 350 rtpSessionCallState INTEGER, 351 rtpSessionIndex Integer32, 352 rtpSessionSessionIdentifier OCTET STRING, 353 rtpSessionStartTime DateAndTime, 354 rtpSessionStopTime DateAndTime, 355 rtpSessionSourceIPtype InetAddressType, 356 rtpSessionSourceIPaddress InetAddress, 357 rtpSessionSourceRTPport InetPortNumber, 358 rtpSessionSourceRTCPport InetPortNumber, 359 rtpSessionDestIPtype InetAddressType, 360 rtpSessionDestIPaddress InetAddress, 361 rtpSessionDestRTPport InetPortNumber, 362 rtpSessionDestRTCPport InetPortNumber, 363 rtpSessionSrceIdenType INTEGER, 364 rtpSessionSrceIdentifier OCTET STRING, 365 rtpSessionDestIdenType INTEGER, 366 rtpSessionDestIdentifier OCTET STRING, 367 rtpSessionIfIndex InterfaceIndex, 368 rtpSessionMonitor TruthValue, 369 rtpSessionSenderJoins Counter32, 370 rtpSessionReceiverJoins Counter32, 371 rtpSessionByes Counter32, 372 rtpSessionRowStatus RowStatus, 373 rtpSessionMaxNumEntries Integer32 374 } 376 rtpSessionCallState OBJECT-TYPE 377 SYNTAX INTEGER { active(1), 378 completed(2) 379 } 380 MAX-ACCESS not-accessible 381 STATUS current 382 DESCRIPTION 383 "Index for this session within the Session ID 384 table. The value of this parameter shall be 2 if the 385 session is complete or inactive and 1 if the session 386 is still active." 387 ::= { rtpSessionEntry 1 } 389 rtpSessionIndex OBJECT-TYPE 390 SYNTAX Integer32 (1..2147483647) 391 MAX-ACCESS not-accessible 392 STATUS current 393 DESCRIPTION 394 "The index of the conceptual row which is for SNMP purposes 395 only and has no relation to any protocol value. There is 396 no requirement that these rows are created or maintained 397 sequentially." 398 ::= { rtpSessionEntry 2 } 400 rtpSessionSessionIdentifier OBJECT-TYPE 401 SYNTAX OCTET STRING (SIZE(0..128)) 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "Unique identifier for this session. A billing record 406 correlation identifier should be used if available, 407 otherwise an identifier such as SSRC can be used." 408 ::= { rtpSessionEntry 3 } 410 rtpSessionStartTime OBJECT-TYPE 411 SYNTAX DateAndTime 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "Call start time for this call. If the start time is not 416 known then this represents the earliest known time associated 417 with the call." 418 ::= { rtpSessionEntry 4 } 420 rtpSessionStopTime OBJECT-TYPE 421 SYNTAX DateAndTime 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "Call stop time for this call. If the call is still active 426 then this shall have the value 0. If the call is complete 427 but the time is unknown then this shall have the value of the 428 latest time associated with the call." 429 ::= { rtpSessionEntry 5 } 431 rtpSessionSourceIPtype OBJECT-TYPE 432 SYNTAX InetAddressType 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "IP address type for the originating IP endpoint for this 437 RTP stream." 438 ::= { rtpSessionEntry 6 } 440 rtpSessionSourceIPaddress OBJECT-TYPE 441 SYNTAX InetAddress 442 MAX-ACCESS read-only 443 STATUS current 444 DESCRIPTION 445 "IP address for the originating IP endpoint for this 446 RTP stream." 447 ::= { rtpSessionEntry 7 } 449 rtpSessionSourceRTPport OBJECT-TYPE 450 SYNTAX InetPortNumber 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "Source UDP port for RTP. A value of 0 indicates 455 an unknown port number." 456 ::= { rtpSessionEntry 8 } 458 rtpSessionSourceRTCPport OBJECT-TYPE 459 SYNTAX InetPortNumber 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION 463 "Source UDP port for RTCP. A value of 0 indicates 464 an unknown port number." 465 ::= { rtpSessionEntry 9 } 467 rtpSessionDestIPtype OBJECT-TYPE 468 SYNTAX InetAddressType 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "Destination IP address type for this session." 473 ::= { rtpSessionEntry 10 } 475 rtpSessionDestIPaddress OBJECT-TYPE 476 SYNTAX InetAddress 477 MAX-ACCESS read-only 478 STATUS current 479 DESCRIPTION 480 "Destination IP address for this session." 481 ::= { rtpSessionEntry 11 } 483 rtpSessionDestRTPport OBJECT-TYPE 484 SYNTAX InetPortNumber 485 MAX-ACCESS read-only 486 STATUS current 487 DESCRIPTION 488 "Destination UDP port for RTP. A value of 0 indicates 489 an unknown port number." 490 ::= { rtpSessionEntry 12 } 492 rtpSessionDestRTCPport OBJECT-TYPE 493 SYNTAX InetPortNumber 494 MAX-ACCESS read-only 495 STATUS current 496 DESCRIPTION 497 "Destination UDP port for RTCP.A value of 0 indicates 498 an unknown port number." 499 ::= { rtpSessionEntry 13 } 501 rtpSessionSrceIdenType OBJECT-TYPE 502 SYNTAX INTEGER {dialedNumber (1), 503 urlID (2), 504 other (3) } 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "Defines the type of address in parameter 509 rtpSessionSourceIdentifier" 510 ::= { rtpSessionEntry 14 } 512 rtpSessionSrceIdentifier OBJECT-TYPE 513 SYNTAX OCTET STRING (SIZE(0..128)) 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "Alternate identifier to the IP address. This can be E.164, 518 DN, or URL." 519 ::= { rtpSessionEntry 15 } 521 rtpSessionDestIdenType OBJECT-TYPE 522 SYNTAX INTEGER {dialedNumber (1), 523 urlID (2), 524 other (3) } 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "Defines the type of address in parameter 529 rtpSessionDestIdentifier." 530 ::= { rtpSessionEntry 16 } 532 rtpSessionDestIdentifier OBJECT-TYPE 533 SYNTAX OCTET STRING (SIZE(0..128)) 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "Alternate identifier to the IP address. This can be E.164, 538 DN, or URL." 539 ::= { rtpSessionEntry 17 } 541 rtpSessionIfIndex OBJECT-TYPE 542 SYNTAX InterfaceIndex 543 MAX-ACCESS read-create 544 STATUS current 545 DESCRIPTION 546 "The ifIndex value is set to the corresponding value 547 from IF-MIB (See RFC 2233, 'The Interfaces Group MIB using 548 SMIv2'). This is the interface that the RTP stream is being sent 549 to or received from, or in the case of an RTP Monitor the 550 interface that RTCP packets will be received on. Cannot be 551 changed if rtpSessionRowStatus is 'active'." 552 ::= { rtpSessionEntry 18 } 554 rtpSessionMonitor OBJECT-TYPE 555 SYNTAX TruthValue 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION 559 "Boolean, Set to 'true(1)' if remote senders or receivers in 560 addition to the local RTP System are to be monitored using RTCP. 561 RTP Monitors MUST initialize to 'true(1)' and RTP Hosts SHOULD 562 initialize this 'false(2)'. Note that because 'host monitor' 563 systems are receiving RTCP from their remote participants they 564 MUST set this value to 'true(1)'." 565 ::= { rtpSessionEntry 19 } 567 rtpSessionSenderJoins OBJECT-TYPE 568 SYNTAX Counter32 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The number of senders that have been observed to have 573 joined the session since this conceptual row was created 574 (rtpSessionStartTime). A sender 'joins' an RTP 575 session by sending to it. Senders that leave and then 576 re-join following an RTCP BYE (see RFC 3550, 'RTP: A 577 Transport Protocol for Real-Time Applications,' sec. 6.6) 578 or session timeout may be counted twice. Every time a new 579 RTP sender is detected either using RTP or RTCP, this counter 580 is incremented." 581 ::= { rtpSessionEntry 20 } 583 rtpSessionReceiverJoins OBJECT-TYPE 584 SYNTAX Counter32 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "The number of receivers that have been been observed to 589 have joined this session since this conceptual row was 590 created (rtpSessionStartTime). A receiver 'joins' an RTP 591 session by sending RTCP Receiver Reports to the session. 592 Receivers that leave and then re-join following an RTCP BYE 593 (see RFC 3550, 'RTP: A Transport Protocol for Real-Time 594 Applications,' sec. 6.6) or session timeout may be counted 595 twice." 596 ::= { rtpSessionEntry 21 } 598 rtpSessionByes OBJECT-TYPE 599 SYNTAX Counter32 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "A count of RTCP BYE (see RFC 3550, 'RTP: A Transport 604 Protocol for Real-Time Applications,' sec. 6.6) messages 605 received by this entity." 606 ::= { rtpSessionEntry 22 } 608 rtpSessionRowStatus OBJECT-TYPE 609 SYNTAX RowStatus 610 MAX-ACCESS read-create 611 STATUS current 612 DESCRIPTION 613 "Value of 'active' when RTP or RTCP messages are being 614 sent or received by an RTP System. A newly-created 615 conceptual row must have the all read-create objects 616 initialized before becoming 'active'. 617 A conceptual row that is in the 'notReady' or 'notInService' 618 state MAY be removed after 5 minutes." 619 ::= { rtpSessionEntry 23 } 621 rtpSessionMaxNumEntries OBJECT-TYPE 622 SYNTAX Integer32 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The maximum number of entries that can be supported 627 in this table." 628 ::= { rtpSessionEntry 24 } 630 -- SENDER INVERSE TABLE 631 -- 632 rtpSenderInverseTable OBJECT-TYPE 633 SYNTAX SEQUENCE OF RtpSenderInverseEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "Maps rtpSenderIPAddress, rtpSessionIndex, to the rtpSenderSSRC 638 index of the rtpSenderTable. This table allows management 639 applications to find entries sorted by Sender IP address rather 640 than sorted by rtpSessionIndex. Given the rtpSessionDomain and 641 rtpSenderAddr, a set of rtpSessionIndex and rtpSenderSSRC values 642 can be returned from a tree walk. When rtpSessionIndex is 643 specified in the SNMP Get-Next operations, one or more 644 rtpSenderSSRC values may be returned." 645 ::= { rtpMIBV2Objects 4 } 647 rtpSenderInverseEntry OBJECT-TYPE 648 SYNTAX RtpSenderInverseEntry 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "Each entry corresponds to exactly one entry in the 653 rtpSenderTable - the entry containing the index pair, 654 rtpSessionIndex, rtpSenderSSRC." 655 INDEX { rtpSenderIPaddress, rtpSenderRTPport, rtpSessionCallState, 656 rtpSessionIndex, rtpSenderSSRC } 657 ::= { rtpSenderInverseTable 1 } 659 RtpSenderInverseEntry ::= SEQUENCE { 660 rtpSenderInverseStartTime DateAndTime 661 } 663 rtpSenderInverseStartTime OBJECT-TYPE 664 SYNTAX DateAndTime 665 MAX-ACCESS read-only 666 STATUS current 667 DESCRIPTION 668 "The time at which this row was 669 created." 670 ::= { rtpSenderInverseEntry 1 } 672 -- SENDERS TABLE 673 -- 674 rtpSenderTable OBJECT-TYPE 675 SYNTAX SEQUENCE OF RtpSenderEntry 676 MAX-ACCESS not-accessible 677 STATUS current 678 DESCRIPTION 679 "Table of information about a sender or senders to an RTP 680 Session. RTP sending hosts MUST have an entry in this table 681 for each stream being sent. RTP receiving hosts MAY have an 682 entry in this table for each sending stream being received by 683 this host. RTP monitors MUST create an entry for each observed 684 sender to a multicast RTP Session as a side-effect when a 685 conceptual row in the rtpSessionTable is made 'active' by a 686 manager." 687 ::= { rtpMIBV2Objects 5 } 689 rtpSenderEntry OBJECT-TYPE 690 SYNTAX RtpSenderEntry 691 MAX-ACCESS not-accessible 692 STATUS current 693 DESCRIPTION 694 "Each entry contains information from a single RTP Sender 695 Synchronization Source (SSRC, see RFC 3550 'RTP: A Transport 696 Protocol for Real-Time Applications' sec.6). The session is 697 identified to the the SNMP entity by rtpSessionIndex. 698 Rows are removed by the RTP agent when a BYE is received 699 from the sender or when the sender times out (see RFC 700 3550, Sec. 6.2.1) or when the rtpSessionEntry is deleted." 701 INDEX { rtpSessionCallState, rtpSessionIndex, rtpSenderSSRC } 702 ::= { rtpSenderTable 1 } 704 RtpSenderEntry ::= SEQUENCE { 705 rtpSenderSSRC Unsigned32, 706 rtpSenderCNAME Utf8String, 707 rtpSenderIPtype InetAddressType, 708 rtpSenderIPaddress InetAddress, 709 rtpSenderRTPport InetPortNumber, 710 rtpSenderRTCPport InetPortNumber, 711 rtpSenderPackets Counter64, 712 rtpSenderOctets Counter64, 713 rtpSenderTool Utf8String, 714 rtpSenderSRs Counter32, 715 rtpSenderSRTime DateAndTime, 716 rtpSenderPT Integer32, 717 rtpSenderStartTime DateAndTime 718 } 720 rtpSenderSSRC OBJECT-TYPE 721 SYNTAX Unsigned32 722 MAX-ACCESS not-accessible 723 STATUS current 724 DESCRIPTION 725 "The RTP SSRC, or synchronization source identifier of the 726 sender. The RTP session address plus an SSRC uniquely 727 identify a sender to an RTP session (see RFC 3550, 'RTP: A 728 Transport Protocol for Real-Time Applications' sec.3)." 729 ::= { rtpSenderEntry 1 } 731 rtpSenderCNAME OBJECT-TYPE 732 SYNTAX Utf8String 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The RTP canonical name of the sender." 737 ::= { rtpSenderEntry 2 } 739 rtpSenderIPtype OBJECT-TYPE 740 SYNTAX InetAddressType 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "IP address type for the originating IP endpoint for this 745 RTP stream." 746 ::= { rtpSenderEntry 3 } 748 rtpSenderIPaddress OBJECT-TYPE 749 SYNTAX InetAddress 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "IP address for the originating IP endpoint for this 754 RTP stream." 755 ::= { rtpSenderEntry 4 } 757 rtpSenderRTPport OBJECT-TYPE 758 SYNTAX InetPortNumber 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "Source UDP port for RTP. A value of 0 indicates 763 an unknown port number." 764 ::= { rtpSenderEntry 5 } 766 rtpSenderRTCPport OBJECT-TYPE 767 SYNTAX InetPortNumber 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "Source UDP port for RTCP. A value of 0 indicates 772 an unknown port number." 773 ::= { rtpSenderEntry 6 } 775 rtpSenderPackets OBJECT-TYPE 776 SYNTAX Counter64 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "Count of RTP packets sent by this sender, or observed by 782 an RTP monitor, since rtpSenderStartTime." 783 ::= { rtpSenderEntry 7 } 785 rtpSenderOctets OBJECT-TYPE 786 SYNTAX Counter64 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "Count of non-header RTP octets sent by this sender, or observed 791 by an RTP monitor, since rtpSenderStartTime." 792 ::= { rtpSenderEntry 8 } 794 rtpSenderTool OBJECT-TYPE 795 SYNTAX Utf8String (SIZE(0..127)) 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "Name of the application program source of the stream." 800 ::= { rtpSenderEntry 9 } 802 rtpSenderSRs OBJECT-TYPE 803 SYNTAX Counter32 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "A count of the number of RTCP Sender Reports that have 808 been sent from this sender, or observed if the RTP entity 809 is a monitor, since rtpSenderStartTime." 810 ::= { rtpSenderEntry 10 } 812 rtpSenderSRTime OBJECT-TYPE 813 SYNTAX DateAndTime 814 MAX-ACCESS read-only 815 STATUS current 816 DESCRIPTION 817 "rtpSenderSRTime is the time at which 818 the last SR was received from this sender, in the case of a 819 monitor or receiving host. Or sent by this sender, in the 820 case of a sending host." 821 ::= { rtpSenderEntry 11 } 823 rtpSenderPT OBJECT-TYPE 824 SYNTAX Integer32(0..127) 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "Payload type from the RTP header of the most recently received 829 RTP Packet (see RFC 3550, 'RTP: A Transport Protocol for 831 Real-Time Applications' sec. 5)." 832 ::= { rtpSenderEntry 12 } 834 rtpSenderStartTime OBJECT-TYPE 835 SYNTAX DateAndTime 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The time at which this row was 840 created." 841 ::= { rtpSenderEntry 13 } 843 -- 844 -- RECEIVER INVERSE TABLE 845 -- 846 rtpRcvrInverseTable OBJECT-TYPE 847 SYNTAX SEQUENCE OF RtpRcvrInverseEntry 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "Maps rtpRcvrIPaddress and rtpSessionIndex to the rtpRcvrSRCSSRC 852 and rtpRcvrSSRC indexes of the rtpRcvrTable. This table allows 853 management applications to find entries by rtpRcvrIPaddress 854 rather than by rtpSessionIndex. Given rtpSessionDomain and 855 rtpRcvrIPaddress, a set of rtpSessionIndex, rtpRcvrSRCSSRC, and 856 rtpRcvrSSRC values can be returned from a tree walk. When 857 rtpSessionIndex is specified in SNMP Get-Next operations, one or 858 more rtpRcvrSRCSSRC and rtpRcvrSSRC pairs may be returned." 859 ::= { rtpMIBV2Objects 6 } 861 rtpRcvrInverseEntry OBJECT-TYPE 862 SYNTAX RtpRcvrInverseEntry 863 MAX-ACCESS not-accessible 864 STATUS current 865 DESCRIPTION 866 "Each entry corresponds to exactly one entry in the 867 rtpRcvrTable - the entry containing the index pair, 868 rtpSessionIndex, rtpRcvrSSRC." 869 INDEX { rtpRcvrIPaddress, rtpRcvrRTPport, rtpSessionCallState, 870 rtpSessionIndex, rtpRcvrSRCSSRC, rtpRcvrSSRC } 871 ::= { rtpRcvrInverseTable 1 } 873 RtpRcvrInverseEntry ::= SEQUENCE { 874 rtpRcvrInverseStartTime DateAndTime 875 } 877 rtpRcvrInverseStartTime OBJECT-TYPE 878 SYNTAX DateAndTime 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The time at which this row was 884 created." 885 ::= { rtpRcvrInverseEntry 1 } 887 -- 888 -- RECEIVERS TABLE 889 -- 890 rtpRcvrTable OBJECT-TYPE 891 SYNTAX SEQUENCE OF RtpRcvrEntry 892 MAX-ACCESS not-accessible 893 STATUS current 894 DESCRIPTION 895 "Table of information about a receiver or receivers of RTP 896 session data. RTP hosts that receive RTP session packets 897 MUST create an entry in this table for that receiver/sender 898 pair. RTP hosts that send RTP session packets MAY create 899 an entry in this table for each receiver to their stream 900 using RTCP feedback from the RTP group. RTP monitors 901 create an entry for each observed RTP session receiver as 902 a side effect when a conceptual row in the rtpSessionTable 903 is made 'active' by a manager." 904 ::= { rtpMIBV2Objects 7 } 906 rtpRcvrEntry OBJECT-TYPE 907 SYNTAX RtpRcvrEntry 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "Each entry contains information from a single RTP 912 Synchronization Source that is receiving packets from the 913 sender identified by rtpRcvrSRCSSRC (SSRC, see RFC 3550, 914 'RTP: A Transport Protocol for Real-Time Applications' 915 sec.6). The session is identified to the the RTP Agent entity 916 by rtpSessionIndex. Rows are removed by the RTP agent when 917 a BYE is received from the sender or when the sender times 918 out (see RFC 3550) or when the rtpSessionEntry is deleted." 919 INDEX { rtpSessionCallState, rtpSessionIndex, rtpRcvrSRCSSRC, 920 rtpRcvrSSRC } 921 ::= { rtpRcvrTable 1 } 923 RtpRcvrEntry ::= SEQUENCE { 924 rtpRcvrSRCSSRC Unsigned32, 925 rtpRcvrSSRC Unsigned32, 926 rtpRcvrCNAME Utf8String, 927 rtpRcvrIPtype InetAddressType, 928 rtpRcvrIPaddress InetAddress, 929 rtpRcvrRTPport InetPortNumber, 930 rtpRcvrRTCPport InetPortNumber, 931 rtpRcvrRTT Gauge32, 932 rtpRcvrLostPackets Counter64, 933 rtpRcvrJitter Gauge32, 934 rtpRcvrTool Utf8String, 935 rtpRcvrRRs Counter32, 936 rtpRcvrRRTime DateAndTime, 937 rtpRcvrPT Integer32, 938 rtpRcvrPackets Counter64, 939 rtpRcvrOctets Counter64, 940 rtpRcvrStartTime DateAndTime 941 } 943 rtpRcvrSRCSSRC OBJECT-TYPE 944 SYNTAX Unsigned32 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "The RTP SSRC, or synchronization source identifier of the 949 sender. The RTP session address plus an SSRC uniquely 950 identify a sender or receiver of an RTP stream (see RFC 951 3550, 'RTP: A Transport Protocol for Real-Time 952 Applications' sec.3)." 953 ::= { rtpRcvrEntry 1 } 955 rtpRcvrSSRC OBJECT-TYPE 956 SYNTAX Unsigned32 957 MAX-ACCESS not-accessible 958 STATUS current 959 DESCRIPTION 960 "The RTP SSRC, or synchronization source identifier of the 961 receiver. The RTP session address plus an SSRC uniquely 962 identify a receiver of an RTP stream (see RFC 3550, 'RTP: 963 A Transport Protocol for Real-Time Applications' sec.3)." 964 ::= { rtpRcvrEntry 2 } 966 rtpRcvrCNAME OBJECT-TYPE 967 SYNTAX Utf8String 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The RTP canonical name of the receiver." 972 ::= { rtpRcvrEntry 3 } 974 rtpRcvrIPtype OBJECT-TYPE 975 SYNTAX InetAddressType 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "Destination IP address type for this session." 980 ::= { rtpRcvrEntry 4 } 982 rtpRcvrIPaddress OBJECT-TYPE 983 SYNTAX InetAddress 984 MAX-ACCESS read-only 985 STATUS current 986 DESCRIPTION 987 "Destination IP address for this session." 988 ::= { rtpRcvrEntry 5 } 990 rtpRcvrRTPport OBJECT-TYPE 991 SYNTAX InetPortNumber 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "Destination UDP port for RTP. A value of 0 indicates 996 an unknown port number." 997 ::= { rtpRcvrEntry 6 } 999 rtpRcvrRTCPport OBJECT-TYPE 1000 SYNTAX InetPortNumber 1001 MAX-ACCESS read-only 1002 STATUS current 1003 DESCRIPTION 1004 "Destination UDP port for RTCP.A value of 0 indicates 1005 an unknown port number." 1006 ::= { rtpRcvrEntry 7 } 1008 rtpRcvrRTT OBJECT-TYPE 1009 SYNTAX Gauge32 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "The round trip time measurement taken by the source of the 1014 RTP stream based on the algorithm described on sec. 6 of 1015 RFC 3550, 'RTP: A Transport Protocol for Real-Time 1016 Applications.' This algorithm can produce meaningful 1017 results when the RTP agent has the same clock as the stream 1018 sender (when the RTP monitor is also the sending host for the 1019 particular receiver). Otherwise, the entity should return 1020 'noSuchInstance' in response to queries against rtpRcvrRTT." 1021 ::= { rtpRcvrEntry 8 } 1023 rtpRcvrLostPackets OBJECT-TYPE 1024 SYNTAX Counter64 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "A count of RTP packets lost as observed by this receiver 1029 since rtpRcvrStartTime." 1030 ::= { rtpRcvrEntry 9 } 1032 rtpRcvrJitter OBJECT-TYPE 1033 SYNTAX Gauge32 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "An estimate of delay variation as observed by this 1038 receiver. (see RFC 3550, 'RTP: A Transport Protocol 1039 for Real-Time Applications' sec.6.3.1 and A.8)." 1040 ::= { rtpRcvrEntry 10 } 1042 rtpRcvrTool OBJECT-TYPE 1043 SYNTAX Utf8String (SIZE(0..127)) 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "Name of the application program source of the stream." 1048 ::= { rtpRcvrEntry 11 } 1050 rtpRcvrRRs OBJECT-TYPE 1051 SYNTAX Counter32 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "A count of the number of RTCP Receiver Reports that have 1056 been sent from this receiver, or observed if the RTP entity 1057 is a monitor, since rtpRcvrStartTime." 1058 ::= { rtpRcvrEntry 12 } 1060 rtpRcvrRRTime OBJECT-TYPE 1061 SYNTAX DateAndTime 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "rtpRcvrRRTime is the time at which the last RTCP Receiver Report 1066 was received from this receiver, in the case of a monitor or RR 1067 receiver (the RTP Sender). It is the time at which the last 1068 RR was sent by this receiver in the case of an RTP receiver 1069 sending the RR." 1070 ::= { rtpRcvrEntry 13 } 1072 rtpRcvrPT OBJECT-TYPE 1073 SYNTAX Integer32(0..127) 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "Static or dynamic payload type from the RTP header (see 1078 RFC 3550, 'RTP: A Transport Protocol for Real-Time 1079 Applications' sec. 5)." 1080 ::= { rtpRcvrEntry 14 } 1082 rtpRcvrPackets OBJECT-TYPE 1083 SYNTAX Counter64 1084 MAX-ACCESS read-only 1085 STATUS current 1086 DESCRIPTION 1087 "Count of RTP packets received by this RTP host receiver 1088 since rtpRcvrStartTime." 1089 ::= { rtpRcvrEntry 15 } 1091 rtpRcvrOctets OBJECT-TYPE 1092 SYNTAX Counter64 1093 MAX-ACCESS read-only 1094 STATUS current 1095 DESCRIPTION 1096 "Count of non-header RTP octets received by this receiving RTP 1097 host since rtpRcvrStartTime." 1098 ::= { rtpRcvrEntry 16 } 1100 rtpRcvrStartTime OBJECT-TYPE 1101 SYNTAX DateAndTime 1102 MAX-ACCESS read-only 1103 STATUS current 1104 DESCRIPTION 1105 "The time at which this row was created." 1106 ::= { rtpRcvrEntry 17 } 1108 -- MODULE GROUPS 1109 -- 1110 -- There are two types of RTP Systems, RTP hosts and RTP Monitors. 1111 -- Thus there are three kinds of objects: 1) Objects common to both 1112 -- kinds of systems, 2) Objects unique to RTP Hosts and 3) Objects 1113 -- unique to RTP Monitors. There is a fourth group, 4) Objects that 1114 -- SHOULD be implemented by Multicast hosts and RTP Monitors 1116 rtpGroups OBJECT IDENTIFIER ::= { rtpConformance 1 } 1117 rtpSystemGroup OBJECT-GROUP 1118 OBJECTS { 1119 rtpSessionSessionIdentifier, 1120 rtpSessionStartTime, 1121 rtpSessionStopTime, 1122 rtpSessionDestIPtype, 1123 rtpSessionDestIPaddress, 1124 rtpSessionDestRTPport, 1125 rtpSessionDestRTCPport, 1126 rtpSessionSrceIdenType, 1127 rtpSessionSrceIdentifier, 1128 rtpSessionDestIdenType, 1129 rtpSessionDestIdentifier, 1130 rtpSessionIfIndex, 1131 rtpSessionSenderJoins, 1132 rtpSessionReceiverJoins, 1133 rtpSessionByes, 1134 rtpSessionMonitor, 1135 rtpSessionMaxNumEntries, 1136 rtpSenderCNAME, 1137 rtpSenderIPtype, 1138 rtpSenderIPaddress, 1139 rtpSenderRTPport, 1140 rtpSenderRTCPport, 1141 rtpSenderPackets, 1142 rtpSenderOctets, 1143 rtpSenderTool, 1144 rtpSenderSRs, 1145 rtpSenderSRTime, 1146 rtpSenderStartTime, 1147 rtpRcvrCNAME, 1148 rtpRcvrIPtype, 1149 rtpRcvrIPaddress, 1150 rtpRcvrRTPport, 1151 rtpRcvrRTCPport, 1152 rtpRcvrLostPackets, 1153 rtpRcvrJitter, 1154 rtpRcvrTool, 1155 rtpRcvrRRs, 1156 rtpRcvrRRTime, 1157 rtpRcvrStartTime 1158 } 1159 STATUS current 1160 DESCRIPTION 1161 "Objects available to all RTP Systems." 1162 ::= { rtpGroups 1 } 1164 rtpHostGroup OBJECT-GROUP 1165 OBJECTS { 1166 rtpSessionSourceIPtype, 1167 rtpSessionSourceIPaddress, 1168 rtpSessionSourceRTPport, 1169 rtpSessionSourceRTCPport, 1170 rtpSenderPT, 1171 rtpRcvrPT, 1172 rtpRcvrRTT, 1173 rtpRcvrOctets, 1174 rtpRcvrPackets 1175 } 1176 STATUS current 1177 DESCRIPTION 1178 "Objects that are available to RTP Host systems, but may not 1179 be available to RTP Monitor systems." 1180 ::= { rtpGroups 2 } 1182 rtpMonitorGroup OBJECT-GROUP 1183 OBJECTS { 1184 rtpSessionNewIndex, 1185 rtpSessionRowStatus 1186 } 1187 STATUS current 1188 DESCRIPTION 1189 "Objects used to create rows in the RTP Session Table. These 1190 objects are not needed if the system does not create rows." 1191 ::= { rtpGroups 3 } 1193 rtpInverseGroup OBJECT-GROUP 1194 OBJECTS { 1195 rtpSessionInverseStartTime, 1196 rtpSenderInverseStartTime, 1197 rtpRcvrInverseStartTime 1198 } 1199 STATUS current 1200 DESCRIPTION 1201 "Objects used in the Inverse Lookup Tables." 1202 ::= { rtpGroups 4 } 1204 -- Compliance 1205 -- 1206 rtpCompliances OBJECT IDENTIFIER ::= { rtpConformance 2 } 1208 rtpHostCompliance MODULE-COMPLIANCE 1209 STATUS current 1210 DESCRIPTION 1211 "Host implementations MUST comply." 1212 MODULE RTP-MIB 1213 MANDATORY-GROUPS { 1214 rtpSystemGroup, 1215 rtpHostGroup 1216 } 1217 GROUP rtpMonitorGroup 1218 DESCRIPTION 1219 "Host systems my optionally support row creation and deletion. 1220 This would allow an RTP Host system to act as an RTP Monitor." 1221 GROUP rtpInverseGroup 1222 DESCRIPTION 1223 "Multicast RTP Systems SHOULD implement the optional 1224 tables." 1225 OBJECT rtpSessionNewIndex 1226 MIN-ACCESS not-accessible 1227 DESCRIPTION 1228 "RTP system implementations support of 1229 row creation and deletion is OPTIONAL so 1230 implementation of this object is OPTIONAL." 1231 OBJECT rtpSessionDestIPtype 1232 MIN-ACCESS read-only 1233 DESCRIPTION 1234 "Row creation and deletion is OPTIONAL so 1235 read-create access to this object is OPTIONAL." 1236 OBJECT rtpSessionDestIPaddress 1237 MIN-ACCESS read-only 1238 DESCRIPTION 1239 "Row creation and deletion is OPTIONAL so 1240 read-create access to this object is OPTIONAL." 1241 OBJECT rtpSessionDestRTPport 1242 MIN-ACCESS read-only 1243 DESCRIPTION 1244 "Row creation and deletion is OPTIONAL so 1245 read-create access to this object is OPTIONAL." 1246 OBJECT rtpSessionDestRTCPport 1247 MIN-ACCESS read-only 1248 DESCRIPTION 1249 "Row creation and deletion is OPTIONAL so 1250 read-create access to this object is OPTIONAL." 1251 OBJECT rtpSessionIfIndex 1252 MIN-ACCESS read-only 1253 DESCRIPTION 1254 "Row creation and deletion is OPTIONAL so 1255 read-create access to this object is OPTIONAL." 1256 OBJECT rtpSessionRowStatus 1257 MIN-ACCESS not-accessible 1258 DESCRIPTION 1259 "Row creation and deletion is OPTIONAL so 1260 read-create access to this object is OPTIONAL." 1262 OBJECT rtpSessionInverseStartTime 1263 MIN-ACCESS not-accessible 1264 DESCRIPTION 1265 "Multicast RTP Systems SHOULD implement the optional 1266 tables." 1268 OBJECT rtpSenderInverseStartTime 1269 MIN-ACCESS not-accessible 1270 DESCRIPTION 1271 "Multicast RTP Systems SHOULD implement the optional 1272 tables." 1273 OBJECT rtpRcvrInverseStartTime 1274 MIN-ACCESS not-accessible 1275 DESCRIPTION 1276 "Multicast RTP Systems SHOULD implement the optional 1277 tables." 1278 ::= { rtpCompliances 1 } 1280 rtpMonitorCompliance MODULE-COMPLIANCE 1281 STATUS current 1282 DESCRIPTION 1283 "Monitor implementations must comply. RTP Monitors are not 1284 required to support creation or deletion." 1285 MODULE RTP-MIB 1286 MANDATORY-GROUPS { 1287 rtpSystemGroup, 1288 rtpMonitorGroup 1289 } 1290 GROUP rtpHostGroup 1291 DESCRIPTION 1292 "Monitor implementations may not have access to values in the 1293 rtpHostGroup." 1294 GROUP rtpInverseGroup 1295 DESCRIPTION 1296 "Multicast RTP Systems SHOULD implement the optional 1297 tables." 1298 OBJECT rtpSessionSourceIPtype 1299 MIN-ACCESS not-accessible 1300 DESCRIPTION 1301 "RTP monitor sourcing of RTP or RTCP data packets 1302 is OPTIONAL and implementation of this object is 1303 OPTIONAL." 1304 OBJECT rtpSessionSourceIPaddress 1305 MIN-ACCESS not-accessible 1306 DESCRIPTION 1307 "RTP monitor sourcing of RTP or RTCP data packets 1308 is OPTIONAL and implementation of this object is 1309 OPTIONAL." 1311 OBJECT rtpSessionSourceRTPport 1312 MIN-ACCESS not-accessible 1313 DESCRIPTION 1314 "RTP monitor sourcing of RTP or RTCP data packets 1315 is OPTIONAL and implementation of this object is 1316 OPTIONAL." 1318 OBJECT rtpSessionSourceRTCPport 1319 MIN-ACCESS not-accessible 1320 DESCRIPTION 1321 "RTP monitor sourcing of RTP or RTCP data packets 1322 is OPTIONAL and implementation of this object is 1323 OPTIONAL." 1324 OBJECT rtpRcvrPT 1325 MIN-ACCESS not-accessible 1326 DESCRIPTION 1327 "RTP monitor systems may not support 1328 retrieval of the RTP Payload Type from the RTP 1329 header (and may receive RTCP messages only). When 1330 queried for the payload type information" 1331 OBJECT rtpSenderPT 1332 MIN-ACCESS not-accessible 1333 DESCRIPTION 1334 "RTP monitor systems may not support 1335 retrieval of the RTP Payload Type from the RTP 1336 header (and may receive RTCP messages only). When 1337 queried for the payload type information." 1338 OBJECT rtpRcvrOctets 1339 MIN-ACCESS not-accessible 1340 DESCRIPTION 1341 "RTP monitor systems may receive only the RTCP messages 1342 and not the RTP messages that contain the octet count 1343 of the RTP message. Thus implementation of this 1344 object is OPTIONAL" 1345 OBJECT rtpRcvrPackets 1346 MIN-ACCESS not-accessible 1347 DESCRIPTION 1348 "RTP monitor systems may receive only the RTCP messages 1349 and not the RTP messages that contain the octet count 1350 of the RTP message. Thus implementation of this 1351 object is OPTIONAL." 1352 OBJECT rtpSessionIfIndex 1353 MIN-ACCESS read-only 1354 DESCRIPTION 1355 "Row creation and deletion is OPTIONAL so 1356 read-create access to this object is OPTIONAL." 1357 OBJECT rtpSessionInverseStartTime 1358 MIN-ACCESS not-accessible 1359 DESCRIPTION 1360 "Multicast RTP Systems SHOULD implement the optional 1361 tables." 1363 OBJECT rtpSenderInverseStartTime 1364 MIN-ACCESS not-accessible 1365 DESCRIPTION 1366 "Multicast RTP Systems SHOULD implement the optional 1367 tables." 1368 OBJECT rtpRcvrInverseStartTime 1369 MIN-ACCESS not-accessible 1370 DESCRIPTION 1371 "Multicast RTP Systems SHOULD implement the optional 1372 tables." 1373 ::= { rtpCompliances 2 } 1374 END 1375 4. Security Considerations 1377 In most cases, MIBs are not themselves security risks; if SNMP 1378 security is operating as intended, the use of a MIB to view 1379 information about a system, or to change some parameter at the 1380 system, is a tool, not a threat. However, there are a number of 1381 management objects defined in this MIB that have a MAX-ACCESS clause 1382 of read-write and/or read-create. Such objects may be considered 1383 sensitive or vulnerable in some network environments. The support 1384 for SET operations in a non-secure environment without proper 1385 protection can have a negative effect on network operations. 1387 None of the read-only objects in this MIB reports a password, though 1388 some SDES [RFC3550] items such as the CNAME [RFC3550], the canonical 1389 name, may be deemed sensitive depending on the security policies of a 1390 particular enterprise. If access to these objects is not limited by 1391 an appropriate access control policy, these objects can provide an 1392 attacker with information about a system's configuration and the 1393 services that that system is providing. Some enterprises view their 1394 network and system configurations, as well as information about usage 1395 and performance, as corporate assets; such enterprises may wish to 1396 restrict SNMP access to most of the objects in the MIB. This MIB 1397 supports read-write operations against rtpSessionNewIndex which has 1398 the side effect of creating an entry in the rtpSessionTable when it 1399 is written to. Five objects in rtpSessionEntry have read-create 1400 access: rtpSessionDomain, rtpSessionRemAddr, rtpSessionIfIndex, 1401 rtpSessionRowStatus, and rtpSessionIfAddr identify an RTP session to 1402 be monitored on a particular interface. The values of these objects 1403 are not to be changed once created, and initialization of these 1404 objects affects only the monitoring of an RTP session and not the 1405 operation of an RTP session on any host end-system. Since write 1406 operations to rtpSessionNewIndex and the five objects in 1407 rtpSessionEntry affect the operation of the monitor, write access to 1408 these objects should be subject to access control. 1410 Confidentiality of RTP and RTCP data packets is defined in section 9 1411 of the RTP specification [RFC3550]. Encryption may be performed on 1412 RTP packets, RTCP packets, or both. Encryption of RTCP packets may 1413 pose a problem for third-party monitors though "For RTCP, it is 1414 allowed to split a compound RTCP packet into two lower-layer packets, 1415 one to be encrypted and one to be sent in the clear. For example, 1416 SDES information might be encrypted while reception reports were sent 1417 in the clear to accommodate third-party monitors [RFC3550]." 1419 SNMPv1 by itself is not a secure environment. Even if the network 1420 itself is secure (for example by using IPSec), there is no control as 1421 to who on the secure network is allowed to access and GET/SET 1422 (read/change/create/delete) the objects in this MIB. It is 1423 recommended that the implementers consider the security features as 1424 provided by the SNMPv3 framework. Specifically, the use of the 1425 User-based Security Model RFC 2574 [RFC2574] and the View-based 1426 Access Control Model RFC 2575 [RFC2575] is recommended. It is then a 1427 customer/user responsibility to ensure that the SNMP entity giving 1428 access to an instance of this MIB, is properly configured to give 1429 access to the objects only to those principals (users) that have 1430 legitimate rights to indeed GET or SET (change/create/delete) them. 1432 5. IANA Considerations 1433 TBD 1435 6. Acknowledgements 1437 The authors wish to thank Brian Park for his contributions in 1438 reviewing this MIB. 1440 7. Intellectual Property 1442 The IETF takes no position regarding the validity or scope of any 1443 Intellectual Property Rights or other rights that might be claimed to 1444 pertain to the implementation or use of the technology described in 1445 this document or the extent to which any license under such rights 1446 might or might not be available; nor does it represent that it has 1447 made any independent effort to identify any such rights. Information 1448 on the procedures with respect to rights in RFC documents can be 1449 found in BCP 78 and BCP 79. 1451 Copies of IPR disclosures made to the IETF Secretariat and any 1452 assurances of licenses to be made available, or the result of an 1453 attempt made to obtain a general license or permission for the use of 1454 such proprietary rights by implementers or users of this 1455 specification can be obtained from the IETF on-line IPR repository at 1456 http://www.ietf.org/ipr. 1458 The IETF invites any interested party to bring to its attention any 1459 copyrights, patents or patent applications, or other proprietary 1460 rights that may cover technology that may be required to implement 1461 this standard. Please address the information to the IETF at 1462 ietf-ipr@ietf.org. 1464 8. References 1466 [RFC3550] Shulzrinne, H., Casner, S., Frederick, R. and V. 1467 Jacobson, "RTP: A Transport Protocol for real-time 1468 applications," RFC 3550, July 2003. 1470 [RFC3611] Friedman, T., Caceres, R., Clark, A., "RTP Control 1471 Protocol Reporting Extensions (RTCP XR)," RFC 3611, 1472 [October/November] 2003 1474 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1475 Rose, M. and S. Waldbusser, "Structure of Management 1476 Information Version 2 (SMIv2)", STD 58, RFC 2578, 1477 December 1999. 1479 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1480 Rose, M. and S. Waldbusser, "Textual Conventions for 1481 SMIv2", STD 58, RFC 2579, December 1999. 1483 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1484 Rose, M. and S. Waldbusser, "Conformance Statements for 1485 SMIv2", STD 58, RFC 2580, December 1999. 1487 9. Informative References 1489 [RFC3410] Case, J., Mundy, R., Partain, D. and Stewart, B., 1490 "Introduction and Applicability Statements for Internet 1491 Standard Management Framework", RFC 3410, December 2002 1493 10. Authors' Addresses 1495 Alan Clark 1496 Telchemy Incorporated 1497 2905 Premiere Parkway, Suite 280 1498 Duluth, Georgia 30097 1499 U.S.A. 1500 Email: alan@telchemy.com 1502 Amy Pendleton 1503 Nortel 1504 2380 Performance Drive 1505 Richardson, Texas 75081 1506 U.S.A. 1507 Email: aspen@nortel.com 1509 Full Copyright Statement 1511 Copyright (C) The Internet Society (2006). 1513 This document is subject to the rights, licenses and restrictions 1514 contained in BCP 78, and except as set forth therein, the authors 1515 retain all their rights. 1517 This document and the information contained herein are provided on an 1518 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1519 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1520 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1521 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1522 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1523 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1525 Intellectual Property 1527 The IETF takes no position regarding the validity or scope of any 1528 Intellectual Property Rights or other rights that might be claimed to 1529 pertain to the implementation or use of the technology described in 1530 this document or the extent to which any license under such rights 1531 might or might not be available; nor does it represent that it has 1532 made any independent effort to identify any such rights. Information 1533 on the procedures with respect to rights in RFC documents can be 1534 found in BCP 78 and BCP 79. 1536 Copies of IPR disclosures made to the IETF Secretariat and any 1537 assurances of licenses to be made available, or the result of an 1538 attempt made to obtain a general license or permission for the use of 1539 such proprietary rights by implementers or users of this 1540 specification can be obtained from the IETF on-line IPR repository at 1541 http://www.ietf.org/ipr. 1543 The IETF invites any interested party to bring to its attention any 1544 copyrights, patents or patent applications, or other proprietary 1545 rights that may cover technology that may be required to implement 1546 this standard. Please address the information to the IETF at ietf- 1547 ipr@ietf.org. 1549 Acknowledgement 1551 Funding for the RFC Editor function is currently provided by the 1552 Internet Society.