smilint output for ./L3VPN-TC-MIB-DRAFT-01


Message Severities
SeverityCount
error2
warning2
Message Types
TypeCount
bad-identifier-case (error)1
module-name-suffix (warning)1
object-identifier-not-prefix (error)1
type-unref (warning)1

Messages:

L3VPN-TC-MIB-DRAFT-01

   1: -- extracted from draft-ietf-l3vpn-tc-mib-01.txt
   2: -- at Thu Feb  5 06:16:36 2004
   3: 
   4: L3VPN-TC-MIB-DRAFT-01 DEFINITIONS ::= BEGIN
   5: 
   6: IMPORTS
   7:    MODULE-IDENTITY, experimental
   8:       FROM SNMPv2-SMI
   9: 
  10:     TEXTUAL-CONVENTION  
  11:       FROM SNMPv2-TC;
  12: 
  13: l3vpnTcMIB MODULE-IDENTITY
  14:    LAST-UPDATED "200402031200Z"  -- 03 February 2004 12:00:00 GMT
  15:    ORGANIZATION "Layer 3 Virtual Private Networks
  16:                  (l3vpn) Working Group."
  17:    CONTACT-INFO
  18:           "   Benson Schliesser
  19:               bensons@savvis.net
  20: 
  21:               Thomas D. Nadeau
  22:               tnadeau@cisco.com
  23: 
  24:               Comments and discussion to l3vpn@ietf.org"
  25: 
  26:    DESCRIPTION
  27:         "This MIB contains TCs for L3VPN."
  28: 
  29:   -- Revision history.
  30:    REVISION "200402031200Z"  -- 03 February 2004 12:00:00 GMT
  31:    DESCRIPTION
  32:       "Updated from PPVPN to L3VPN, and to reflect new MIB
  33:        naming convention."
  34: 
  35:    REVISION "200211031200Z"  -- 03 November 2002 12:00:00 GMT
  36:    DESCRIPTION
  37:       "Refreshed for IETF web page."
  38: 
  39:    REVISION "200202281200Z"  -- 28 February 2002 12:00:00 GMT
  40:    DESCRIPTION
  41:       "Initial draft version."
  42: 
  43:    ::= { experimental XXX } -- to be assigned by IANA
  43: error - `XXX' should start with a lower case letter
  43: error - Object identifier element `XXX' name only allowed as first element
  44: 
  45: -- definition of textual conventions
  46: 
  47: VPNId ::= TEXTUAL-CONVENTION
  47: warning - warning: current type `VPNId' is not referenced in this module
  48:     STATUS current
  49:     DESCRIPTION
  50:         "The purpose of a VPN-ID is to identify a VPN.
  51:          The global VPN Identifier format is:
  52:          3 octet VPN Authority, Organizationally Unique Identifier
  53:          followed by
  54:          4 octet VPN index identifying VPN according to OUI"
  55:     REFERENCE
  56:         "RFC 2685, Fox & Gleeson, 'Virtual Private
  57:          Networks Identifier', September 1999."
  58:     SYNTAX    OCTET STRING (SIZE (0..7))
  59: 
  60: END
  60: warning - warning: module name `L3VPN-TC-MIB-DRAFT-01' should match `*-MIB'
  61: 
  62: -- 
  63: --    Copyright (C) The Internet Society (2001). All Rights
  64: --    Reserved.
  65: -- 
  66: --    This document and translations of it may be copied and
  67: --    furnished to others, and derivative works that comment on
  68: --    or otherwise explain it or assist in its implementation
  69: --    may be prepared, copied, published and distributed, in
  70: --    whole or in part, without restriction of any kind,
  71: --    provided that the above copyright notice and this
  72: --    paragraph are included on all such copies and derivative
  73: --    works.  However, this document itself may not be modified
  74: --    in any way, such as by removing the copyright notice or
  75: --    references to the Internet Society or other Internet
  76: --    organizations, except as needed for the purpose of
  77: --    developing Internet standards in which case the
  78: --    procedures for copyrights defined in the Internet
  79: --    Standards process must be followed, or as required to
  80: --    translate it into languages other than English.
  81: --    The limited permissions granted above are perpetual and
  82: --    will not be revoked by the Internet Society or its
  83: --    successors or assigns. This document and the information
  84: --    contained herein is provided on an "AS IS" basis and THE
  85: --    INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE
  86: --    DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
  87: --    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
  88: --    INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY
  89: --    IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
  90: --    PARTICULAR PURPOSE.
  91: -- 
  92: -- 
  93: -- 8.0 Intellectual Property Considerations
  94: -- 
  95: --    The IETF takes no position regarding the validity or scope of any
  96: --    intellectual property or other rights that might be claimed to per-
  97: --    tain to the implementation or use of the technology described in this
  98: --    document or the extent to which any license under such rights might
  99: --    or might not be available; neither does it represent that it has made
 100: --    any effort to identify any such rights.  Information on the IETF's
 101: --    procedures with respect to rights in standards-track and standards-
 102: --    related documentation can be found in BCP-11.  Copies of claims of
 103: --    rights made available for publication and any assurances of licenses
 104: --    to be made available, or the result of an attempt made to obtain a
 105: --    general license or permission for the use of such proprietary rights
 106: --    by implementers or users of this specification can be obtained from
 107: --    the IETF Secretariat.
 108: -- 
 109: --    The IETF invites any interested party to bring to its attention any
 110: --    copyrights, patents or patent applications, or other proprietary
 111: --    rights which may cover technology that may be required to practice
 112: --    this standard.  Please address the information to the IETF Executive
 113: --    Director.
 114: