smilint output for ./DISMAN-EXPRESSION-MIB


Message Severities
SeverityCount
minor error1
warning1
Message Types
TypeCount
index-element-no-size (minor error)1
index-exceeds-too-large (warning)1

Messages:

DISMAN-EXPRESSION-MIB

   1: -- extracted from draft-ietf-disman-express-mib-v2-02.txt
   2: -- at Tue Jun 17 06:13:37 2003
 941: 
 942: expValueEntry OBJECT-TYPE
 942: warning - warning: index of row `expValueEntry' can exceed OID size limit by 79 subidentifier(s)
 943:      SYNTAX      ExpValueEntry
 944:      MAX-ACCESS  not-accessible
 945:      STATUS      current
 946:      DESCRIPTION
 947:       "A single value from an evaluated expression.  For a given
 948:       instance, only one 'Val' object in the conceptual row will be
 949:       instantiated, that is, the one with the appropriate type for
 950:       the value.  For values that contain no objects of
 951:       expObjectSampleType 'deltaValue' or 'changedValue', reading a
 952:       value from the table causes the evaluation of the expression
 953:       for that value.  For those that contain a 'deltaValue' or
 954:       'changedValue' the value read is as of the last sampling
 955:       interval.
 956: 
 957:       If in the attempt to evaluate the expression one or more
 958:       of the necessary objects is not available, the corresponding
 959:       entry in this table is effectively not instantiated.
 960: 
 961:       To maintain security of MIB information, when creating a new
 962:       row in this table, the managed system must record the security
 963:       credentials of the requester.  These security credentials are
 964:       the parameters necessary as inputs to isAccessAllowed from
 965:       [RFC2571]. When obtaining the objects that make up the
 966:       expression, the system must (conceptually) use isAccessAllowed to
 967:       ensure that it does not violate security.
 968: 
 969:       The evaluation of that expression takes place under the
 970:       security credentials of the creator of its expExpressionEntry.
 971: 
 972:       To maintain security of MIB information, expression evaluation must
 973:       take place using security credentials for the implied Gets of the
 974:       objects in the expression as inputs (conceptually) to
 975:       isAccessAllowed from the Architecture for Describing SNMP
 976:       Management Frameworks.  These are the security credentials of the
 977:       creator of the corresponding expExpressionEntry."
 978:      INDEX       { expExpressionOwner, expExpressionName,
 979:                    IMPLIED expValueInstance }
 980:      ::= { expValueTable 1 }
 981: 
 982: ExpValueEntry ::= SEQUENCE {
 983:      expValueInstance          OBJECT IDENTIFIER,
 984:      expValueCounter32Val      Counter32,
 985:      expValueUnsigned32Val     Unsigned32,
 986:      expValueTimeTicksVal      TimeTicks,
 987:      expValueInteger32Val      Integer32,
 988:      expValueIpAddressVal      IpAddress,
 989:      expValueOctetStringVal    OCTET STRING,
 990:      expValueOidVal            OBJECT IDENTIFIER,
 991:      expValueCounter64Val      Counter64
 992: }
 993: 
 994: expValueInstance OBJECT-TYPE
 994: minor error - index element `expValueInstance' of row `expValueEntry' should but cannot have a size restriction
 995:      SYNTAX      OBJECT IDENTIFIER
 996:      MAX-ACCESS  not-accessible
 997:      STATUS      current
 998:      DESCRIPTION
 999:       "The final instance portion of a value's OID according to
1000:       the wildcarding in instances of expObjectID for the
1001:       expression.  The prefix of this OID fragment is 0.0,
1002:       leading to the following behavior.
1003: 
1004:       If there is no wildcarding, the value is 0.0.0.  In other
1005:       words, there is one value which standing alone would have
1006:       been a scalar with a 0 at the end of its OID.
1007: 
1008:       If there is wildcarding, the value is 0.0 followed by
1009:       a value that the wildcard can take, thus defining one value
1010:       instance for each real, possible value of the wildcard.
1011:       So, for example, if the wildcard worked out to be an ifIndex,
1012:       there is an expValueInstance for each applicable ifIndex."
1013:      ::= { expValueEntry 1 }