smilint output for ./IANA-PWE3-MIB

Message Severities
Severity	Count
error	2
warning	3

Message Types
Type	Count
bad-identifier-case (error)	1
object-identifier-not-prefix (error)	1
type-unref (warning)	3

Messages:

IANA-PWE3-MIB

   1: -- extracted from draft-ietf-pwe3-pw-mib-12.txt
   2: -- at Mon Sep 24 06:09:07 2007

   3: 
   4:    IANA-PWE3-MIB DEFINITIONS ::= BEGIN
   5: 
   6:    IMPORTS
   7:        MODULE-IDENTITY, transmission
   8:           FROM SNMPv2-SMI -- [RFC2578]
   9: 
  10:        TEXTUAL-CONVENTION
  11:           FROM SNMPv2-TC; -- [RFC2579]
  12: 
  13:    ianaPwe3MIB  MODULE-IDENTITY
  14:        LAST-UPDATED "200702041200Z"  -- 4 February 2006 12:00:00 GMT
  15:        ORGANIZATION "IANA"
  16:        CONTACT-INFO
  17:             "Internet Assigned Numbers Authority
  18:             Internet Corporation for Assigned Names and Numbers
  19:             4676 Admiralty Way, Suite 330
  20:             Marina del Rey, CA 90292-6601
  21: 
  22:             Phone: +1 310 823 9358
  23:             EMail: iana@iana.org"
  24:        DESCRIPTION
  25:            "This MIB module defines the IANAPwTypeTC and
  26:            IANAPwPsnTypeTC textual conventions for use in PWE3
  27:            MIB modules.
  28: 
  29:            Any additions or changes to the contents of this MIB
  30:            module require either publication of an RFC, Designated
  31:            Expert Review as defined in RFC 2434, Guidelines for
  32:            Writing an IANA Considerations Section in RFCs, and should
  33:            be based on the procedures defined in [RFC4446]. The
  34:            Designated Expert will be selected by the IESG Area
  35:            Director(s) of the internet Area.
  36: 
  37:            Copyright (C) The IETF Trust (2007).  The initial
  38:            version of this MIB module was published in RFC yyyy;
  39:            for full legal notices see the RFC itself.  Supplementary
  40:            information may be available at:
  41:            http://www.ietf.org/copyrights/ianamib.html."
  42:       -- RFC Ed.: replace yyyy with actual RFC number & remove this note
  43: 
  44:        REVISION     "200702041200Z"  -- 4 February 2006 12:00:00 GMT
  45:        DESCRIPTION  "Original version, published as part of RFC yyyy."
  46:    -- RFC Editor: please fill the yyyy and remove this note.
  47: 
  48:        ::= { transmission XXXX }

48: error - `XXXX' should start with a lower case letter
48: error - Object identifier element `XXXX' name only allowed as first element

  49:    -- RFC Editor: please fill the XXXX based on the IANA allocation
  50:    -- and remove this note.
  51: 
  52:    IANAPwTypeTC ::= TEXTUAL-CONVENTION

52: warning - warning: current type `IANAPwTypeTC' is not referenced in this module

  53:       STATUS     current
  54:       DESCRIPTION
  55:          "Indicates the PW type (i.e. the carried service). "
  56:     SYNTAX   INTEGER {
  57:        other(0),
  58:        frameRelayDlciMartiniMode(1),
  59:        atmAal5SduVcc(2),
  60:        atmTransparent(3),
  61:        ethernetTagged(4),
  62:        ethernet(5),
  63:        hdlc(6),
  64:        ppp(7),
  65:        cem(8),  -- Historic type
  66:        atmCellNto1Vcc(9),
  67:        atmCellNto1Vpc(10),
  68:        ipLayer2Transport(11),
  69:        atmCell1to1Vcc(12),
  70:        atmCell1to1Vpc(13),
  71:        atmAal5PduVcc(14),
  72:        frameRelayPortMode(15),
  73:        cep(16),
  74:        e1Satop(17),
  75:        t1Satop(18),
  76:        e3Satop(19),
  77:        t3Satop(20),
  78:        basicCesPsn(21),
  79:        basicTdmIp(22),
  80:        tdmCasCesPsn(23),
  81:        tdmCasTdmIp(24),
  82:        frDlci(25),
  83:        wildcard (32767)
  84:         }
  85: 
  86:    IANAPwPsnTypeTC ::= TEXTUAL-CONVENTION

86: warning - warning: current type `IANAPwPsnTypeTC' is not referenced in this module

  87:       STATUS      current
  88:       DESCRIPTION
  89:          "Identifies the PSN type which the PW will use over the
  90:           network."
  91:       SYNTAX   INTEGER {
  92:          mpls        (1),
  93:          l2tp        (2),
  94:          udpOverIp   (3),
  95:          mplsOverIp  (4),
  96:          mplsOverGre (5),
  97:          other       (6)
  98:          }
  99: 
 100:    IANAPwCapabilities ::= TEXTUAL-CONVENTION

100: warning - warning: current type `IANAPwCapabilities' is not referenced in this module

 101:       STATUS      current
 102:       DESCRIPTION
 103:          "This TC describes a collection of cabailities related to
 104:           a specific PW.
 105:           Values may be added in the future based on new capabilities
 106:           introduced in IETF documents.
 107:          "
 108:      SYNTAX   BITS {
 109:        pwStatusIndication (0), -- Applicable only if maintenence
 110:                                -- protocol is in use.
 111:        pwVCCV             (1)
 112:      }
 113: 
 114:    END
 115: 
 116: -- 
 117: --    Copyright (C) The IETF Trust (2007).
 118: -- 
 119: --    This document is subject to the rights, licenses and restrictions
 120: --    contained in BCP 78, and except as set forth therein, the authors
 121: --    retain all their rights.
 122: -- 
 123: --    This document and the information contained herein are provided on an
 124: --    "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
 125: --    OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
 126: --    THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
 127: --    OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 128: --    THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
 129: --    WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 130: -- 
 131: -- 
 132: -- Intellectual Property
 133: -- 
 134: --    The IETF takes no position regarding the validity or scope of any
 135: --    Intellectual Property Rights or other rights that might be claimed to
 136: --    pertain to the implementation or use of the technology described in
 137: --    this document or the extent to which any license under such rights
 138: --    might or might not be available; nor does it represent that it has
 139: --    made any independent effort to identify any such rights.  Information
 140: --    on the procedures with respect to rights in RFC documents can be
 141: --    found in BCP 78 and BCP 79.
 142: -- 
 143: --    Copies of IPR disclosures made to the IETF Secretariat and any
 144: --    assurances of licenses to be made available, or the result of an
 145: --    attempt made to obtain a general license or permission for the use of
 146: --    such proprietary rights by implementers or users of this
 147: --    specification can be obtained from the IETF on-line IPR repository at
 148: --    http://www.ietf.org/ipr.
 149: -- 
 150: --    The IETF invites any interested party to bring to its attention any
 151: --    copyrights, patents or patent applications, or other proprietary
 152: --    rights that may cover technology that may be required to implement
 153: --    this standard.  Please address the information to the IETF at
 154: --    ietf-ipr@ietf.org.
 155: -- 
 156: -- 
 157: -- Acknowledgment
 158: -- 
 159: --    Funding for the RFC Editor function is provided by the IETF
 160: --    Administrative Support Activity (IASA).
 161: