Connected: An Internet Encyclopedia
RFC 1904 - 6.5.2. Mapping of the VARIATION clause

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1904
Up: 6. Mapping of the AGENT-CAPABILITIES macro
Up: 6.5. Mapping of the SUPPORTS clause
Prev: 6.5.1. Mapping of the INCLUDES clause
Next: 6.5.2.1. Mapping of the SYNTAX clause

### 6.5.2. Mapping of the VARIATION clause

The VARIATION clause, which need not be present, is repeatedly used to name each object or notification which the agent implements in some variant or refined fashion with respect to the correspondent invocation of the OBJECT-TYPE or NOTIFICATION-TYPE macro.

Note that the variation concept is meant for generic implementation restrictions, e.g., if the variation for an object depends on the values of other objects, then this should be noted in the appropriate DESCRIPTION clause.

By definition, each object specified in a VARIATION clause follows a SUPPORTS clause which names the information module in which that object is defined. Therefore, the use of an IMPORTS statement, to specify from where such objects are imported, is redundant and is not required in an information module.

6.5.2.1. Mapping of the SYNTAX clause
6.5.2.2. Mapping of the WRITE-SYNTAX clause
6.5.2.3. Mapping of the ACCESS clause
6.5.2.4. Mapping of the CREATION-REQUIRES clause
6.5.2.5. Mapping of the DEFVAL clause
6.5.2.6. Mapping of the DESCRIPTION clause

Next: 6.5.2.1. Mapping of the SYNTAX clause

Connected: An Internet Encyclopedia
RFC 1904 - 6.5.2. Mapping of the VARIATION clause