Connected: An Internet Encyclopedia
5.1.1. Mapping to the SYNTAX clause
Up:
Connected: An Internet Encyclopedia
Up:
Requests For Comments
Up:
RFC 1212
Up:
5. Appendix: DE-osifying MIBs
Up:
5.1. Managed Object Mapping
Prev: 5.1. Managed Object Mapping
Next: 5.1.2. Mapping to the ACCESS clause
5.1.1. Mapping to the SYNTAX clause
5.1.1. Mapping to the SYNTAX clause
When mapping to the SYNTAX clause of the OBJECT-type macro:
- An object with BOOLEAN syntax becomes an INTEGER taking
either of values true(1) or false(2).
- An object with ENUMERATED syntax becomes an INTEGER,
taking any of the values given.
- An object with BIT STRING syntax containing no more than
32 bits becomes an INTEGER defined as a sum; otherwise if
more than 32 bits are present, the object becomes an
OCTET STRING, with the bits numbered from left-to-right,
in which the least significant bits of the last octet may
be "reserved for future use".
- An object with a character string syntax becomes either
an OCTET STRING or a DisplayString, depending on the
repertoire of the character string.
- An non-tabular object with a complex syntax, such as REAL
or EXTERNAL, must be decomposed, usually into an OCTET
STRING (if sensible). As a rule, any object with a
complicated syntax should be avoided.
- Tabular objects must be decomposed into rows of columnar
objects.
Next: 5.1.2. Mapping to the ACCESS clause
Connected: An Internet Encyclopedia
5.1.1. Mapping to the SYNTAX clause