smilint output for ./SNMP-TSM-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| object-identifier-not-prefix (error) | 1 |
Messages:
SNMP-TSM-MIB
1: -- extracted from draft-ietf-isms-transport-security-model-06.txt
2: -- at Sat Sep 22 06:09:25 2007
3:
4: SNMP-TSM-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: mib-2, Counter32
9: FROM SNMPv2-SMI
10: MODULE-COMPLIANCE, OBJECT-GROUP
11: FROM SNMPv2-CONF
12: ;
13:
14: snmpTsmMIB MODULE-IDENTITY
15: LAST-UPDATED "200710140000Z"
16: ORGANIZATION "ISMS Working Group"
17: CONTACT-INFO "WG-EMail: isms@lists.ietf.org
18: Subscribe: isms-request@lists.ietf.org
19:
20: Chairs:
21: Juergen Quittek
22: NEC Europe Ltd.
23: Network Laboratories
24: Kurfuersten-Anlage 36
25: 69115 Heidelberg
26: Germany
27: +49 6221 90511-15
28: quittek@netlab.nec.de
29:
30: Juergen Schoenwaelder
31: Jacobs University Bremen
32: Campus Ring 1
33: 28725 Bremen
34: Germany
35: +49 421 200-3587
36: j.schoenwaelder@iu-bremen.de
37:
38: Editor:
39: David Harrington
40: Huawei Technologies USA
41: 1700 Alma Dr.
42: Plano TX 75075
43: USA
44: +1 603-436-8634
45: ietfdbh@comcast.net
46: "
47: DESCRIPTION "The Transport Security Model MIB
48:
49: In keeping with the RFC 3411 design decisions
50: to use self-contained documents, the RFC which
51: contains the definition of this MIB module also
52: includes the elements of procedure which are
53: needed for processing the Transport Security
54: Model for SNMP. These MIB objects
55: SHOULD NOT be modified via other documents.
56: This allows the Transport Security Model
57: for SNMP to be designed and documented as
58: independent and self- contained, having no
59: direct impact on other modules, and this
60: allows this module to be upgraded and
61: supplemented as the need arises, and to
62: move along the standards track on different
63: time-lines from other modules.
64:
65: Copyright (C) The IETF Trust (2007). This
66: version of this MIB module is part of RFC XXXX;
67: see the RFC itself for full legal notices.
68: -- NOTE to RFC editor: replace XXXX with actual RFC number
69: -- for this document and remove this note
70: "
71:
72: REVISION "200710140000Z"
73: DESCRIPTION "The initial version, published in RFC XXXX.
74: -- NOTE to RFC editor: replace XXXX with actual RFC number
75: -- for this document and remove this note
76: "
77:
78: ::= { mib-2 xxxx }
78: error -
Object identifier element `xxxx' name only allowed as first element
79: -- RFC Ed.: replace xxxx with IANA-assigned number and
80: -- remove this note
81:
82: -- ---------------------------------------------------------- --
83: -- subtrees in the SNMP-TRANSPORT-SM-MIB
84: -- ---------------------------------------------------------- --
85: snmpTsmNotifications OBJECT IDENTIFIER ::= { snmpTsmMIB 0 }
86: snmpTsmMIBObjects OBJECT IDENTIFIER ::= { snmpTsmMIB 1 }
87: snmpTsmConformance OBJECT IDENTIFIER ::= { snmpTsmMIB 2 }
88:
89: -- -------------------------------------------------------------
90: -- Objects
91: -- -------------------------------------------------------------
92:
93: -- Statistics for the Transport Security Model
94:
95:
96: snmpTsmStats OBJECT IDENTIFIER ::= { snmpTsmMIBObjects 1 }
97:
98: snmpTsmInvalidCaches OBJECT-TYPE
99: SYNTAX Counter32
100: MAX-ACCESS read-only
101: STATUS current
102: DESCRIPTION "The number of messages dropped because the
103: tmStateReference referred to an invalid cache.
104: "
105: ::= { snmpTsmStats 1 }
106:
107: snmpTsmInadequateSecurityLevels OBJECT-TYPE
108: SYNTAX Counter32
109: MAX-ACCESS read-only
110: STATUS current
111: DESCRIPTION "The number of incoming messages dropped because
112: the actual securityLevel provided was less than
113: the requested securityLevel.
114: "
115: ::= { snmpTsmStats 2 }
116:
117: -- -------------------------------------------------------------
118: -- snmpTsmMIB - Conformance Information
119: -- -------------------------------------------------------------
120:
121: snmpTsmCompliances OBJECT IDENTIFIER ::= { snmpTsmConformance 1 }
122:
123: snmpTsmGroups OBJECT IDENTIFIER ::= { snmpTsmConformance 2 }
124:
125: -- -------------------------------------------------------------
126: -- Compliance statements
127: -- -------------------------------------------------------------
128:
129: snmpTsmCompliance MODULE-COMPLIANCE
130: STATUS current
131: DESCRIPTION
132: "The compliance statement for SNMP engines that support
133: the SNMP-TRANSPORT-SM-MIB"
134: MODULE
135: MANDATORY-GROUPS { snmpTsmGroup }
136: ::= { snmpTsmCompliances 1 }
137:
138: -- -------------------------------------------------------------
139: -- Units of conformance
140: -- -------------------------------------------------------------
141: snmpTsmGroup OBJECT-GROUP
142: OBJECTS {
143: snmpTsmInvalidCaches,
144: snmpTsmInadequateSecurityLevels
145: }
146: STATUS current
147: DESCRIPTION "A collection of objects for maintaining
148: information of an SNMP engine which implements
149: the SNMP Transport Security Model.
150: "
151:
152: ::= { snmpTsmGroups 2 }
153:
154:
155: END
156:
157: --
158: -- Copyright (C) The IETF Trust (2007).
159: --
160: -- This document is subject to the rights, licenses and restrictions
161: -- contained in BCP 78, and except as set forth therein, the authors
162: -- retain all their rights.
163: --
164: -- This document and the information contained herein are provided on an
165: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
166: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
167: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
168: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
169: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
170: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
171: --
172: -- Intellectual Property
173: --
174: -- The IETF takes no position regarding the validity or scope of any
175: -- Intellectual Property Rights or other rights that might be claimed to
176: -- pertain to the implementation or use of the technology described in
177: -- this document or the extent to which any license under such rights
178: -- might or might not be available; nor does it represent that it has
179: -- made any independent effort to identify any such rights. Information
180: -- on the procedures with respect to rights in RFC documents can be
181: -- found in BCP 78 and BCP 79.
182: --
183: -- Copies of IPR disclosures made to the IETF Secretariat and any
184: -- assurances of licenses to be made available, or the result of an
185: -- attempt made to obtain a general license or permission for the use of
186: -- such proprietary rights by implementers or users of this
187: -- specification can be obtained from the IETF on-line IPR repository at
188: -- http://www.ietf.org/ipr.
189: --
190: -- The IETF invites any interested party to bring to its attention any
191: -- copyrights, patents or patent applications, or other proprietary
192: -- rights that may cover technology that may be required to implement
193: -- this standard. Please address the information to the IETF at
194: -- ietf-ipr@ietf.org.
195: --
196: