Справочник по сетевым протоколам

RFC1065 - часть 9

data and then interpret its contents.

Further note that by use of the ASN.1 EXTERNAL type, encodings other

than ASN.1 may be used in opaquely-encoded data.

3.3. Encodings

Once an instance of an object type has been identified, its value may

be transmitted by applying the basic encoding rules of ASN.1 to the

syntax for the object type.

Rose & McCloghrie [Page 9]

RFC 1065 SMI August 1988

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:



A textual name, termed the OBJECT DESCRIPTOR, for the object type,

along with its corresponding OBJECT IDENTIFIER.


The abstract syntax for the object type. This must resolve to an

instance of the ASN.1 type ObjectSyntax (defined below).


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.


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


One of mandatory, optional, or obsolete.

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


4.1. Guidelines for Object Names

No object type in the Internet-Standard MIB shall use a sub-

identifier of 0 in its name. This value is reserved for use with

future extensions.

Each OBJECT DESCRIPTOR corresponding to an object type in the

internet-standard MIB shall be a unique, but mnemonic, printable

string. This promotes a common language for humans to use when

discussing the MIB and also facilitates simple table mappings for

user interfaces.

4.2. Object Types and Instances

An object type is a definition of a kind of managed object; it is

Rose & McCloghrie [Page 10]

- Начало -  - Назад -  - Вперед -