---
oid: "1.3.6.1.2.1.10.166.21.1.2.1.3"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsOamIdStdMIB(21) mplsOamIdObjects(1) mplsOamIdMegTable(2) mplsOamIdMegEntry(1) mplsOamIdMegOperatorType(3)}"
description: "mplsOamIdMegOperatorType OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2020-01-27"
---

## OID : `1.3.6.1.2.1.10.166.21.1.2.1.3`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) mplsStdMIB(166) mplsOamIdStdMIB(21) mplsOamIdObjects(1) mplsOamIdMegTable(2) mplsOamIdMegEntry(1) mplsOamIdMegOperatorType(3)}
```

### Description

```asn1
mplsOamIdMegOperatorType OBJECT-TYPE
SYNTAX INTEGER {
ipCompatible (1),
iccBased (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the operator type for the MEG. Conceptual rows
having 'iccBased' as the operator type MUST have valid
values for the objects mplsOamIdMegIdIcc and
mplsOamIdMegIdUmc when the row status is active."
REFERENCE
"1. RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers,
September 2011.
2. RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 3.1."
DEFVAL { ipCompatible }
```

**Classification**: MIB object for network management

### Supplementary information

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

### Child OIDs

No child OID

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