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