Connected: An Internet Encyclopedia
RFC 1904 - 5.6. Usage Example

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1904
Up: 5. Mapping of the MODULE-COMPLIANCE macro
Prev: 5.5. Mapping of the MODULE-COMPLIANCE value
Next: 6. Mapping of the AGENT-CAPABILITIES macro

### 5.6. Usage Example

The compliance statement contained in the (hypothetical) XYZv2-MIB might be:

    xyzMIBCompliance MODULE-COMPLIANCE
        STATUS  current
        DESCRIPTION
                "The compliance statement for XYZv2 entities which implement
                the XYZv2 MIB."
        MODULE  -- compliance to the containing MIB module
            MANDATORY-GROUPS { xyzSystemGroup,
                               xyzStatsGroup, xyzTrapGroup,
                               xyzSetGroup,
                               xyzBasicNotificationsGroup }

            GROUP   xyzV1Group
            DESCRIPTION
                "The xyzV1 group is mandatory only for those
                 XYZv2 entities which also implement XYZv1."
    ::= { xyzMIBCompliances 1 }

According to this invocation, to claim alignment with the compliance statement named

         { xyzMIBCompliances 1 }

a system must implement the XYZv2-MIB's xyzSystemGroup, xyzStatsGroup, xyzTrapGroup, and xyzSetGroup object conformance groups, as well as the xyzBasicNotificationsGroup notifications group. Furthermore, if the XYZv2 entity also implements XYZv1, then it must also support the XYZv1Group group, if compliance is to be claimed.

Next: 6. Mapping of the AGENT-CAPABILITIES macro

Connected: An Internet Encyclopedia
RFC 1904 - 5.6. Usage Example