smilint output for ./URI-MIB

Message Severities
SeverityCount
error2
warning3
Message Types
TypeCount
bad-identifier-case (error)1
object-identifier-not-prefix (error)1
type-unref (warning)3

Messages:

URI-MIB

   1: -- extracted from draft-mcwalter-uri-mib-02.txt
   2: -- at Thu Feb  8 06:08:15 2007
   3: 
   4: URI-MIB DEFINITIONS ::= BEGIN
   5: 
   6: IMPORTS
   7:     MODULE-IDENTITY, mib-2             FROM SNMPv2-SMI      -- [RFC2578]
   8:     TEXTUAL-CONVENTION                 FROM SNMPv2-TC;      -- [RFC2579]
   9: 
  10: uriMIB MODULE-IDENTITY
  11:     LAST-UPDATED "200702050000Z" -- 5 February 2007
  12:     ORGANIZATION "IETF Operations and Management (OPS) Area"
  13:     CONTACT-INFO "EMail: ops-area@ietf.org
  14:                   Home page: http://www.ops.ietf.org/"
  15:     DESCRIPTION
  16:             "This MIB module defines textual conventions for
  17:             representing URIs, as defined by RFC 3986 STD 66.
  18: 
  19:             Copyright (C) The IETF Trust (2007).  This version of this
  20:             MIB module is part of RFC yyyy; see the RFC itself for full
  21:             legal notices."
  22:     REVISION     "200702050000Z" -- 5 February 2007
  23:     DESCRIPTION
  24:            "Initial revision, published as RFC yyyy."
  25: 
  26: -- RFC Ed.: replace yyyy with actual RFC number & remove this note
  27:     ::= { mib-2 XXX }
  27: error - `XXX' should start with a lower case letter
  27: error - Object identifier element `XXX' name only allowed as first element 
  28: -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
  29: 
  30: Uri ::= TEXTUAL-CONVENTION
  30: warning - warning: current type `Uri' is not referenced in this module 
  31:    DISPLAY-HINT "255a"
  32:    STATUS      current
  33:    DESCRIPTION
  34:             "A Uniform Resource Identifier (URI) as defined by STD 66.
  35: 
  36:             This URI MUST be a normalized as defined in section 6 of
  37:             RFC 3986 STD 66.  STD 66 defines that some parts of a URI
  38:             are case-insensitive, but objects using this textual
  39:             convention MUST use normalized URIs.  The purpose of this
  40:             restriction is to help provide unique URIs for use as MIB
  41:             table indexes.  Note that normalization of URIs does not
  42:             by itself provide uniqueness: Two textually distinct
  43:             normalized URIs may be equivalent."
  44:    REFERENCE "RFC 3986 STD 66 and RFC 3305"
  45:    SYNTAX      OCTET STRING
  46: 
  47: Uri255 ::= TEXTUAL-CONVENTION
  47: warning - warning: current type `Uri255' is not referenced in this module 
  48:    DISPLAY-HINT "255a"
  49:    STATUS      current
  50:    DESCRIPTION
  51:             "A Uniform Resource Identifier (URI) as defined by STD 66.
  52: 
  53:             This URI MUST be a normalized as defined in section 6 of
  54:             RFC 3986 STD 66.  STD 66 defines that some parts of a URI
  55:             are case-insensitive, but objects using this textual
  56:             convention MUST use normalized URIs.  The purpose of this
  57:             restriction is to help provide unique URIs for use as MIB
  58:             table indexes.  Note that normalization of URIs does not
  59:             by itself provide uniqueness: Two textually distinct
  60:             normalized URIs may be equivalent.
  61: 
  62:             STD 66 URIs are of unlimited length.  Objects using this
  63:             textual convention impose an arbitrary length limit on the
  64:             URIs that they can represent.  If no length restriction is
  65:             required, then objects SHOULD use the 'Uri' textual
  66:             convention instead."
  67:    REFERENCE "RFC 3986 STD 66 and RFC 3305"
  68:    SYNTAX      OCTET STRING (SIZE (0..255))
  69: 
  70: Uri1024 ::= TEXTUAL-CONVENTION
  70: warning - warning: current type `Uri1024' is not referenced in this module 
  71:    DISPLAY-HINT "1024a"
  72:    STATUS      current
  73:    DESCRIPTION
  74:             "A Uniform Resource Identifier (URI) as defined by STD 66.
  75: 
  76:             This URI MUST be a normalized as defined in section 6 of
  77:             RFC 3986 STD 66.  STD 66 defines that some parts of a URI
  78:             are case-insensitive, but objects using this textual
  79:             convention MUST use normalized URIs.  The purpose of this
  80:             restriction is to help provide unique URIs for use as MIB
  81:             table indexes.  Note that normalization of URIs does not
  82:             by itself provide uniqueness: Two textually distinct
  83:             normalized URIs may be equivalent.
  84: 
  85:             STD 66 URIs are of unlimited length.  Objects using this
  86:             textual convention impose an arbitrary length limit on the
  87:             URIs that they can represent.  If no length restriction is
  88:             required, then objects SHOULD use the 'Uri' textual
  89:             convention instead."
  90:    REFERENCE "RFC 3986 STD 66 and RFC 3305"
  91:    SYNTAX      OCTET STRING (SIZE (0..1024))
  92: 
  93: END
  94: 
  95: -- 
  96: --    Copyright (C) The IETF Trust (2007).  This document is subject to the
  97: --    rights, licenses and restrictions contained in BCP 78, and except as
  98: --    set forth therein, the authors retain all their rights.
  99: -- 
 100: -- 
 101: -- Acknowledgment
 102: -- 
 103: --    Funding for the RFC Editor function is currently provided by the
 104: --    Internet Society.
 105: