smilint output for ./POLICY-DEVICE-AUX-MIB


Message Severities
SeverityCount
minor error3
warning1
Message Types
TypeCount
revision-missing (minor error)1
textual-convention-nested (minor error)2
type-unref (warning)1

Messages:

POLICY-DEVICE-AUX-MIB

   1: -- extracted from draft-kzm-rap-pol-aux-mib-01.txt
   2: -- at Thu Jul 20 07:08:05 2000
  16: 
  17: policyDeviceAuxMib MODULE-IDENTITY
  18:         LAST-UPDATED    "200007121800Z" -- 12 July 2000
  19:         ORGANIZATION    "IETF RAP WG"
  20:         CONTACT-INFO
  21:                  "Kwok Ho Chan
  22:                   Nortel Networks, Inc.
  23:                   600 Technology Park Drive
  24:                   Billerica, MA 01821 USA
  25:                   Phone: +1 978 288 8175
  26:                   Email: khchan@nortelnetworks.com
  27: 
  28:                   John Seligson
  29:                   Nortel Networks, Inc.
  30:                   4401 Great America Parkway
  31:                   Santa Clara, CA USA 95054
  32:                   Phone: +1 408 495-2992
  33:                   Email: jseligso@nortelnetworks.com
  34: 
  35:                   Keith McCloghrie
  36:                   Cisco Systems, Inc.
  37:                   170 West Tasman Drive,
  38:                   San Jose, CA 95134-1706 USA
  39:                   Phone: +1 408 526 5260
  40:                   Email: kzm@cisco.com"
  41:         DESCRIPTION
  42:             "This module defines an infrastructure used
  43:             for support of policy-based provisioning of
  44:             a network device."
  45:         ::= { experimental 999 }
  45: minor error - revision for last update is missing

...
  52: 
  53: Role ::= TEXTUAL-CONVENTION
  53: warning - warning: current type `Role' is not referenced in this module
  53: minor error -
textual convention `Role' can not be derived from the textual convention `SnmpAdminString'
  54:     STATUS       current
  55:     DESCRIPTION
  56:         "A role represents a functionality characteristic or
  57:         capability of a resource to which policies are applied.
  58:         Examples of roles include Backbone interface, Frame Relay
  59:         interface, BGP-capable router, web server, firewall, etc.
  60: 
  61:         Valid characters are a-z, A-Z, 0-9, period, hyphen and
  62:         underscore.  A role must not start with an underscore."
  63:     REFERENCE
  64:         "Policy Core Information Model,
  65:         draft-ietf-policy-core-info-model-06.txt"
  66:     SYNTAX SnmpAdminString  (SIZE (1..31))
  67: 
  68: RoleCombination ::= TEXTUAL-CONVENTION
  68: minor error - textual convention `RoleCombination' can not be derived from the textual convention `SnmpAdminString'
  69:     STATUS       current
  70:     DESCRIPTION
  71:         "A Display string consisting of a set of roles concatenated
  72:         with a '+' character where the roles are in lexicographic
  73:         order from minimum to maximum.
  74: 
  75:         For example, a+b and b+a are NOT different role-combinations;
  76:         rather, they are different formating of the same (one) role-
  77:         combination.
  78: 
  79:         Notice the roles within a role-combination are in lexicographic
  80:         order from minimum to maximum, hence, we declare:
  81:           a+b is the valid formating of the role-combination,
  82:           b+a is an invalid formating of the role-combination.
  83: 
  84:         Notice the need of zero-length role-combination as the role-
  85:         combination of interfaces to which no roles have been assigned.
  86:         This role-combination is also known as the null role-combination.
  87:         (Note the deliberate use of lower case leters to avoid confusion
  88:         with the ASCII NULL character which has a value of zero but length
  89:         of one.)"
  90:     SYNTAX SnmpAdminString  (SIZE (0..255))
  91: 
  92: -- The Policy Interface Table supports
  93: -- associating an interface with a specific role combination.
  94: 
  95: -- This table satisfy the need to monitor the configuration of
  96: -- roles on a per interface basis, and is no less scalable as
  97: -- other required per interface parameters.
  98: -- This does not preclude roles being associated with some less
  99: -- granular entities, and should be addressed when such need arise.