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