Connected: An Internet Encyclopedia
RFC 1155 - 4. Managed Objects

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1155
Prev: 3.3. Encodings
Next: 4.1. Guidelines for Object Names

### 4. Managed Objects

Although it is not the purpose of this memo to define objects in the MIB, this memo specifies a format to be used by other memos which define these objects.

An object type definition consists of five fields:

OBJECT:

  A textual name, termed the OBJECT DESCRIPTOR, for the object type, along with its corresponding OBJECT IDENTIFIER.

Syntax:

  The abstract syntax for the object type. This must resolve to an instance of the ASN.1 type ObjectSyntax (defined below).

Definition:

  A textual description of the semantics of the object type. Implementations should ensure that their instance of the object fulfills this definition since this MIB is intended for use in multi-vendor environments. As such it is vital that objects have consistent meaning across all machines.

Access:

  One of read-only, read-write, write-only, or not-accessible.

Status:

  One of mandatory, optional, or obsolete.

Future memos may also specify other fields for the objects which they define.

4.1. Guidelines for Object Names
4.2. Object Types and Instances
4.3. Macros for Managed Objects

Next: 4.1. Guidelines for Object Names

Connected: An Internet Encyclopedia
RFC 1155 - 4. Managed Objects