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


RFC1065 - часть 7

In addition, it is strongly recommended

that the enterprise will also register its networking subsystems

under this subtree, in order to provide an unambiguous identification

mechanism for use in management protocols. For example, if the

"Flintstones, Inc." enterprise produced networking subsystems, then

they could request a node under the enterprises subtree from the

Assigned Numbers authority. Such a node might be numbered:

The "Flintstones, Inc." enterprise might then register their "Fred

Router" under the name of:

3.2. Syntax

Syntax is used to define the structure corresponding to object types.

ASN.1 constructs are used to define this structure, although the full

generality of ASN.1 is not permitted.

The ASN.1 type ObjectSyntax defines the different syntaxes which may

be used in defining an object type.

3.2.1. Primitive Types

Only the ASN.1 primitive types INTEGER, OCTET STRING, OBJECT

IDENTIFIER, and NULL are permitted. These are sometimes referred to

as non-aggregate types. Guidelines for Enumerated INTEGERs

If an enumerated INTEGER is listed as an object type, then a named-

number having the value 0 shall not be present in the list of

Rose & McCloghrie [Page 7]

RFC 1065 SMI August 1988

enumerations. Use of this value is prohibited.

3.2.2. Constructor Types

The ASN.1 constructor type SEQUENCE is permitted, providing that it

is used to generate either lists or tables.

For lists, the syntax takes the form:

SEQUENCE { , ..., }

where each resolves to one of the ASN.1 primitive types listed

above. Further, these ASN.1 types are always present (the DEFAULT

and OPTIONAL clauses do not appear in the SEQUENCE definition).

For tables, the syntax takes the form:


where resolves to a list constructor.

Lists and tables are sometimes referred to as aggregate types.

3.2.3. Defined Types

In addition, new application-wide types may be defined, so long as

Содержание  Назад  Вперед