---
oid: "1.3.6.1.2.1.87"
short-description: "rtpMIB MODULE-IDENTITY"
last-modified: "2021-02-10"
parent-oid: "1.3.6.1.2.1"
---

## OID: `1.3.6.1.2.1.87`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) rtpMIB(87)}
```

### Description

```asn1
rtpMIB MODULE-IDENTITY
LAST-UPDATED "200010020000Z" -- 2 October 2000
ORGANIZATION
"IETF AVT Working Group
Email: rem-conf@es.net"
CONTACT-INFO
"Mark Baugher
Postal: Intel Corporation
2111 NE 25th Avenue
Hillsboro, OR 97124
United States
Tel: +1 503 466 8406
Email: mbaugher@passedge.com
Bill Strahm
Postal: Intel Corporation
2111 NE 25th Avenue
Hillsboro, OR 97124
United States
Tel: +1 503 264 4632
Email: bill.strahm@intel.com
Irina Suconick
Postal: Ennovate Networks
60 Codman Hill Rd.,
Boxboro, Ma 01719
Tel: +1 781-505-2155
Email: irina@ennovatenetworks.com"
DESCRIPTION
"The managed objects of RTP systems. The MIB is structured around three types of information.
1. General information about RTP sessions such as the session address.
2. Information about RTP streams being sent to an RTP session by a particular sender.
3. Information about RTP streams received on an RTP session by a particular receiver from a particular sender.
There are two types of RTP Systems, RTP hosts and RTP monitors. As described below, certain objects are unique to a particular type of RTP System. An RTP host may also function as an RTP monitor.
Refer to RFC 1889, RTP: A Transport Protocol for Real-Time Applications, section 3.0, for definitions."
REVISION "200010020000Z" -- 2 October 2000
DESCRIPTION "Initial version of this MIB.
Published as RFC 2959."
```

**Classification:** MIB object for network management; Module in a given formal language

### Supplementary information

Automatically extracted from IETF [RFC 2959](https://www.rfc-editor.org/rfc/rfc2959.html).

### Child OIDs

- `1.3.6.1.2.1.87.1`: `rtpMIBObjects(1)`
- `1.3.6.1.2.1.87.2`: `rtpConformance(2)`

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.