Connected: An Internet Encyclopedia
RFC 1902 - 7.10. Mapping of the OBJECT-TYPE value

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1902
Up: 7. Mapping of the OBJECT-TYPE macro
Prev: 7.9. Mapping of the DEFVAL clause
Next: 7.11. Usage Example

### 7.10. Mapping of the OBJECT-TYPE value

The value of an invocation of the OBJECT-TYPE macro is the name of the object, which is an OBJECT IDENTIFIER, an administratively assigned name.

When an OBJECT IDENTIFIER is assigned to an object:

1. If the object corresponds to a conceptual table, then only a single assignment, that for a conceptual row, is present immediately beneath that object. The administratively assigned name for the conceptual row object is derived by appending a sub-identifier of "1" to the administratively assigned name for the conceptual table.

2. If the object corresponds to a conceptual row, then at least one assignment, one for each column in the conceptual row, is present beneath that object. The administratively assigned name for each column is derived by appending a unique, positive sub-identifier to the administratively assigned name for the conceptual row.

3. Otherwise, no other OBJECT IDENTIFIERs which are subordinate to the object may be assigned.

Note that the final sub-identifier of any administratively assigned name for an object shall be positive. A zero-valued final sub- identifier is reserved for future use.

Further note that although conceptual tables and rows are given administratively assigned names, these conceptual objects may not be manipulated in aggregate form by the management protocol.

Next: 7.11. Usage Example

Connected: An Internet Encyclopedia
RFC 1902 - 7.10. Mapping of the OBJECT-TYPE value