Connected: An Internet Encyclopedia
RFC 1155 - 3.1. Names

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1155
Up: 3. Structure and Identification of Management Information
Prev: 3. Structure and Identification of Management Information
Next: 3.1.1. Directory

### 3.1. Names

Names are used to identify managed objects. This memo specifies names which are hierarchical in nature. The OBJECT IDENTIFIER concept is used to model this notion. An OBJECT IDENTIFIER can be used for purposes other than naming managed object types; for example, each international standard has an OBJECT IDENTIFIER assigned to it for the purposes of identification. In short, OBJECT IDENTIFIERs are a means for identifying some object, regardless of the semantics associated with the object (e.g., a network object, a standards document, etc.)

An OBJECT IDENTIFIER is a sequence of integers which traverse a global tree. The tree consists of a root connected to a number of labeled nodes via edges. Each node may, in turn, have children of its own which are labeled. In this case, we may term the node a subtree. This process may continue to an arbitrary level of depth. Central to the notion of the OBJECT IDENTIFIER is the understanding that administrative control of the meanings assigned to the nodes may be delegated as one traverses the tree. A label is a pairing of a brief textual description and an integer.

The root node itself is unlabeled, but has at least three children directly under it: one node is administered by the International Organization for Standardization, with label iso(1); another is administrated by the International Telegraph and Telephone Consultative Committee, with label ccitt(0); and the third is jointly administered by the ISO and the CCITT, joint-iso-ccitt(2).

Under the iso(1) node, the ISO has designated one subtree for use by other (inter)national organizations, org(3). Of the children nodes present, two have been assigned to the U.S. National Institutes of Standards and Technology. One of these subtrees has been transferred by the NIST to the U.S. Department of Defense, dod(6).

As of this writing, the DoD has not indicated how it will manage its subtree of OBJECT IDENTIFIERs. This memo assumes that DoD will allocate a node to the Internet community, to be administered by the Internet Activities Board (IAB) as follows:

          internet    OBJECT IDENTIFIER ::= { iso org(3) dod(6) 1 }

That is, the Internet subtree of OBJECT IDENTIFIERs starts with the prefix:

          1.3.6.1.

This memo, as a standard approved by the IAB, now specifies the policy under which this subtree of OBJECT IDENTIFIERs is administered. Initially, four nodes are present:

          directory     OBJECT IDENTIFIER ::= { internet 1 }
          mgmt          OBJECT IDENTIFIER ::= { internet 2 }
          experimental  OBJECT IDENTIFIER ::= { internet 3 }
          private       OBJECT IDENTIFIER ::= { internet 4 }

3.1.1. Directory
3.1.2. Mgmt
3.1.3. Experimental
3.1.4. Private

Next: 3.1.1. Directory

Connected: An Internet Encyclopedia
RFC 1155 - 3.1. Names