smilint output for ./EXAMPLE-MIB

Messages:

EXAMPLE-MIB

   1: -- extracted from rfc3737.txt
   2: -- at Tue Apr  6 06:17:52 2004

   3: 
   4:       EXAMPLE-MIB DEFINITIONS ::= BEGIN
   5: 
   6:       IMPORTS
   7:         rmon          FROM RMON-MIB
   8: 
   9:         .. other imports ..

  10: 
  11:       exampleMIB  MODULE-IDENTITY
  12: 
  13:         ... other normal MODULE-IDENTITY stuff ...
  14: 
  15:       ::= { rmon nnn }  -- IANA: please assign nnn
  16:                         -- RFC-Editor: replace nnn with IANA-assigned
  17:                         --             number and remove this note
  18: 
  19:    IANA will assign the number as part of the RFC publication process.
  20: 
  21: -- NOTE: this END was not present in rfc3737.txt,
  22: -- but this does appear to be the end of the MIB.
  23: -- (the next line is '4.  Security Considerations')
  24: 
  25: END
  26: 
  27: -- 
  28: --    Copyright (C) The Internet Society (2004).  This document is subject
  29: --    to the rights, licenses and restrictions contained in BCP 78 and
  30: --    except as set forth therein, the authors retain all their rights.
  31: -- 
  32: --    This document and the information contained herein are provided on an
  33: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
  34: --    REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
  35: --    INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
  36: --    IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
  37: --    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
  38: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
  39: -- 
  40: -- Intellectual Property
  41: -- 
  42: --    The IETF takes no position regarding the validity or scope of any
  43: --    Intellectual Property Rights or other rights that might be claimed
  44: --    to pertain to the implementation or use of the technology
  45: --    described in this document or the extent to which any license
  46: --    under such rights might or might not be available; nor does it
  47: --    represent that it has made any independent effort to identify any
  48: --    such rights.  Information on the procedures with respect to
  49: --    rights in RFC documents can be found in BCP 78 and BCP 79.
  50: -- 
  51: --    Copies of IPR disclosures made to the IETF Secretariat and any
  52: --    assurances of licenses to be made available, or the result of an
  53: --    attempt made to obtain a general license or permission for the use
  54: --    of such proprietary rights by implementers or users of this
  55: --    specification can be obtained from the IETF on-line IPR repository
  56: --    at http://www.ietf.org/ipr.
  57: -- 
  58: --    The IETF invites any interested party to bring to its attention
  59: --    any copyrights, patents or patent applications, or other
  60: --    proprietary rights that may cover technology that may be required
  61: --    to implement this standard.  Please address the information to the
  62: --    IETF at ietf-ipr@ietf.org.
  63: -- 
  64: