Connected: An Internet Encyclopedia
7.3. Mapping of the MAX-ACCESS clause
Up:
Connected: An Internet Encyclopedia
Up:
Requests For Comments
Up:
RFC 1902
Up:
7. Mapping of the OBJECT-TYPE macro
Prev: 7.2. Mapping of the UNITS clause
Next: 7.4. Mapping of the STATUS clause
7.3. Mapping of the MAX-ACCESS clause
7.3. Mapping of the MAX-ACCESS clause
The MAX-ACCESS clause, which must be present, defines whether it
makes "protocol sense" to read, write and/or create an instance of
the object, or to include its value in a notification. This is the
maximal level of access for the object. (This maximal level of
access is independent of any administrative authorization policy.)
The value "read-write" indicates that read and write access make
"protocol sense", but create does not. The value "read-create"
indicates that read, write and create access make "protocol sense".
The value "not-accessible" indicates an auxiliary object (see Section
7.7). The value "accessible-for-notify" indicates an object which is
accessible only via a notification (e.g., snmpTrapOID [5]).
These values are ordered, from least to greatest: "not-accessible",
"accessible-for-notify", "read-only", "read-write", "read-create".
If any columnar object in a conceptual row has "read-create" as its
maximal level of access, then no other columnar object of the same
conceptual row may have a maximal access of "read-write". (Note that
"read-create" is a superset of "read-write".)
Next: 7.4. Mapping of the STATUS clause
Connected: An Internet Encyclopedia
7.3. Mapping of the MAX-ACCESS clause