Connected: An Internet Encyclopedia
RFC 1902 - 7.1.9. Opaque

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1902
Up: 7. Mapping of the OBJECT-TYPE macro
Up: 7.1. Mapping of the SYNTAX clause
Prev: 7.1.8. TimeTicks
Next: 7.1.10. Counter64

### 7.1.9. Opaque

The Opaque type is provided solely for backward-compatibility, and shall not be used for newly-defined object types.

The Opaque type supports the capability to pass arbitrary ASN.1 syntax. A value is encoded using the ASN.1 Basic Encoding Rules [4] into a string of octets. This, in turn, is encoded as an OCTET STRING, in effect "double-wrapping" the original ASN.1 value.

Note that a conforming implementation need only be able to accept and recognize opaquely-encoded data. It need not be able to unwrap the data and then interpret its contents.

A requirement on "standard" MIB modules is that no object may have a SYNTAX clause value of Opaque.

Next: 7.1.10. Counter64

Connected: An Internet Encyclopedia
RFC 1902 - 7.1.9. Opaque