---
oid: "1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
short-description: "recValue OBJECT-TYPE"
last-modified: "2025-07-23"
parent-oid: "1.3.6.1.4.1.1206.4.1.1.7.9.11.1"
---

## OID: `1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 1206 transportation(4) protocols(1) layers(1) application(7) recMech(9) recEntriesTable(11) recEntry(1) recValue(3)}
```

### Description

```asn1
recValue OBJECT-TYPE
SYNTAX Opaque
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>The value of this object is set to the BER
encoding of the value referenced by the recConfigRecordOID
of the associated recordingConfigID when the entry was collected.
Its length is variable. The value shall not contain any padding
characters either before or after the values.
NOTE: Opaque objects are doubly wrapped. For SNMP
operations, which use BER, this would be {type, length,
{type, length, value}}. For example, a zero-length octet
string, would be encoded in BER as 0x44 02 04 00. For STMP
or SFMP operations, which use OER, this would be {length,
{type, length, value}}. For example, the same example would
be encoded in OER as 0x02 04 00.
<Object Identifier> 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3"
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### 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.