Reference record for OID 1.3.6.1.2.1.87.2.2.2

parent

1.3.6.1.2.1.87.2.2 (rtpCompliances)

node code

2

node name

rtpMonitorCompliance

dot oid

1.3.6.1.2.1.87.2.2.2

type

MODULE-COMPLIANCE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) rtpMIB(87) rtpConformance(2) rtpCompliances(2) rtpMonitorCompliance(2)}

{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) rtpMIB(87) rtpConformance(2) rtpCompliances(2) rtpMonitorCompliance(2)}

{iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) rtpMIB(87) rtpConformance(2) rtpCompliances(2) rtpMonitorCompliance(2)}

{iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) rtpMIB(87) rtpConformance(2) rtpCompliances(2) rtpMonitorCompliance(2)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) rtpMIB(87) rtpConformance(2) rtpCompliances(2) rtpMonitorCompliance(2)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) rtpMIB(87) rtpConformance(2) rtpCompliances(2) rtpMonitorCompliance(2)}

iri oid

/iso/identified-organization/dod/internet/mgmt/mib-2/rtpMIB/rtpConformance/rtpCompliances/rtpMonitorCompliance

/iso/identified-organization/dod/internet/mgmt/mib/rtpMIB/rtpConformance/rtpCompliances/rtpMonitorCompliance

/iso/org/dod/internet/mgmt/mib-2/rtpMIB/rtpConformance/rtpCompliances/rtpMonitorCompliance

/iso/org/dod/internet/mgmt/mib/rtpMIB/rtpConformance/rtpCompliances/rtpMonitorCompliance

/iso/iso-identified-organization/dod/internet/mgmt/mib-2/rtpMIB/rtpConformance/rtpCompliances/rtpMonitorCompliance

/iso/iso-identified-organization/dod/internet/mgmt/mib/rtpMIB/rtpConformance/rtpCompliances/rtpMonitorCompliance

iri by oid_info

/ISO/Identified-Organization/6/1/2/1/87/2/2/2

Description by oid_info

rtpMonitorCompliance MODULE-COMPLIANCE STATUS current
DESCRIPTION
"Monitor implementations must comply. RTP Monitors are not
required to support creation or deletion."
MODULE RTP-MIB
MANDATORY-GROUPS {
rtpSystemGroup,
rtpMonitorGroup
}
GROUP rtpHostGroup
DESCRIPTION
"Monitor implementations may not have access to values in the
rtpHostGroup."
GROUP rtpInverseGroup
DESCRIPTION
"Multicast RTP Systems SHOULD implement the optional
tables."
OBJECT rtpSessionLocAddr
MIN-ACCESS not-accessible
DESCRIPTION
"RTP monitor sourcing of RTP or RTCP data packets
is OPTIONAL and implementation of this object is
OPTIONAL."
OBJECT rtpRcvrPT
MIN-ACCESS not-accessible
DESCRIPTION
"RTP monitor systems may not support
retrieval of the RTP Payload Type from the RTP
header (and may receive RTCP messages only). When
queried for the payload type information"
OBJECT rtpSenderPT
MIN-ACCESS not-accessible
DESCRIPTION
"RTP monitor systems may not support
retrieval of the RTP Payload Type from the RTP
header (and may receive RTCP messages only). When
queried for the payload type information."
OBJECT rtpRcvrOctets
MIN-ACCESS not-accessible
DESCRIPTION
"RTP monitor systems may receive only the RTCP messages
and not the RTP messages that contain the octet count
of the RTP message. Thus implementation of this
object is OPTIONAL"
OBJECT rtpRcvrPackets
MIN-ACCESS not-accessible
DESCRIPTION
"RTP monitor systems may receive only the RTCP messages
and not the RTP messages that contain the octet count
of the RTP message. Thus implementation of this
object is OPTIONAL."
OBJECT rtpSessionIfIndex
MIN-ACCESS read-only
DESCRIPTION
"Row creation and deletion is OPTIONAL so
read-create access to this object is OPTIONAL."
OBJECT rtpSessionInverseStartTime
MIN-ACCESS not-accessible
DESCRIPTION
"Multicast RTP Systems SHOULD implement the optional
tables."
OBJECT rtpSenderInverseStartTime
MIN-ACCESS not-accessible
DESCRIPTION
"Multicast RTP Systems SHOULD implement the optional
tables."
OBJECT rtpRcvrInverseStartTime
MIN-ACCESS not-accessible
DESCRIPTION
"Multicast RTP Systems SHOULD implement the optional
tables."
View at oid-info.com

Description by mibdepot

Monitor implementations must comply. RTP Monitors are not
required to support creation or deletion.

Parsed from file rfc2959-Real-Time-Transport-Protocol-RTP.mib.txt
Company: None
Module: RTP-MIB

Description by circitor

Monitor implementations must comply. RTP Monitors are not
required to support creation or deletion.

Parsed from file RTP-MIB.mib
Module: RTP-MIB

Information by oid_info

Automatically extracted from RFC2959

Information by mibdepot

rtpMonitorCompliance MODULE-COMPLIANCE
    STATUS          current
    DESCRIPTION
          "Monitor implementations must comply.  RTP Monitors are not
          required to support creation or deletion."
    MODULE           RTP-MIB
    MANDATORY-GROUPS     {
                         rtpSystemGroup,
                         rtpMonitorGroup
                         }
    GROUP                rtpHostGroup
    DESCRIPTION
        "Monitor implementations may not have access to values in the
         rtpHostGroup."
    GROUP                rtpInverseGroup
    DESCRIPTION
        "Multicast RTP Systems SHOULD implement the optional
         tables."
        OBJECT  rtpSessionLocAddr
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor sourcing of RTP or RTCP data packets
                is OPTIONAL and implementation of this object is
                OPTIONAL."
        OBJECT  rtpRcvrPT
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may not support
                retrieval of the RTP Payload Type from the RTP
                header (and may receive RTCP messages only).  When
                queried for the payload type information"
        OBJECT  rtpSenderPT
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may not support
                retrieval of the RTP Payload Type from the RTP
                header (and may receive RTCP messages only).  When
                queried for the payload type information."
        OBJECT  rtpRcvrOctets
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may receive only the RTCP messages
                and not the RTP messages that contain the octet count
                of the RTP message.  Thus implementation of this
                object is OPTIONAL"
        OBJECT  rtpRcvrPackets
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may receive only the RTCP messages
                and not the RTP messages that contain the octet count
                of the RTP message.  Thus implementation of this
                object is OPTIONAL."
        OBJECT  rtpSessionIfIndex
            MIN-ACCESS read-only
              DESCRIPTION
               "Row creation and deletion is OPTIONAL so
                read-create access to this object is OPTIONAL."
        OBJECT  rtpSessionInverseStartTime
            MIN-ACCESS not-accessible
              DESCRIPTION
               "Multicast RTP Systems SHOULD implement the optional
                tables."
        OBJECT  rtpSenderInverseStartTime
            MIN-ACCESS not-accessible
              DESCRIPTION
               "Multicast RTP Systems SHOULD implement the optional
                tables."
        OBJECT  rtpRcvrInverseStartTime
            MIN-ACCESS not-accessible
              DESCRIPTION
               "Multicast RTP Systems SHOULD implement the optional
                tables."
    ::= { rtpCompliances 2 }

Information by circitor

rtpMonitorCompliance MODULE-COMPLIANCE
    STATUS          current
    DESCRIPTION
          "Monitor implementations must comply.  RTP Monitors are not
          required to support creation or deletion."
    MODULE           RTP-MIB
    MANDATORY-GROUPS     {
                         rtpSystemGroup,
                         rtpMonitorGroup
                         }
    GROUP                rtpHostGroup
    DESCRIPTION
        "Monitor implementations may not have access to values in the
         rtpHostGroup."
    GROUP                rtpInverseGroup
    DESCRIPTION
        "Multicast RTP Systems SHOULD implement the optional
         tables."
        OBJECT  rtpSessionLocAddr
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor sourcing of RTP or RTCP data packets
                is OPTIONAL and implementation of this object is
                OPTIONAL."
        OBJECT  rtpRcvrPT
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may not support
                retrieval of the RTP Payload Type from the RTP
                header (and may receive RTCP messages only).  When
                queried for the payload type information"
        OBJECT  rtpSenderPT
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may not support
                retrieval of the RTP Payload Type from the RTP
                header (and may receive RTCP messages only).  When
                queried for the payload type information."
        OBJECT  rtpRcvrOctets
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may receive only the RTCP messages
                and not the RTP messages that contain the octet count
                of the RTP message.  Thus implementation of this
                object is OPTIONAL"
        OBJECT  rtpRcvrPackets
            MIN-ACCESS not-accessible
              DESCRIPTION
               "RTP monitor systems may receive only the RTCP messages
                and not the RTP messages that contain the octet count
                of the RTP message.  Thus implementation of this
                object is OPTIONAL."
        OBJECT  rtpSessionIfIndex
            MIN-ACCESS read-only
              DESCRIPTION
               "Row creation and deletion is OPTIONAL so
                read-create access to this object is OPTIONAL."
        OBJECT  rtpSessionInverseStartTime
            MIN-ACCESS not-accessible
              DESCRIPTION
               "Multicast RTP Systems SHOULD implement the optional
                tables."
        OBJECT  rtpSenderInverseStartTime
            MIN-ACCESS not-accessible
              DESCRIPTION
               "Multicast RTP Systems SHOULD implement the optional
                tables."
        OBJECT  rtpRcvrInverseStartTime
            MIN-ACCESS not-accessible
              DESCRIPTION
               "Multicast RTP Systems SHOULD implement the optional
                tables."
    ::= { rtpCompliances 2 }

First Registration Authority (recovered by parent 1.3.6)

Defense Communication Agency

Current Registration Authority (recovered by parent 1.3.6.1.2)

Internet Assigned Numbers Authority

Brothers (1)