smilint output for ./SNMP-TRANSPORT-SM-MIB
Message Severities |
Severity | Count |
error | 1 |
Message Types |
Type | Count |
object-identifier-not-prefix (error) | 1 |
Messages:
SNMP-TRANSPORT-SM-MIB
1: -- extracted from draft-ietf-isms-transport-security-model-05.txt
2: -- at Tue Jul 10 06:08:47 2007
3:
4: SNMP-TRANSPORT-SM-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: snmpModules, Counter32
9: FROM SNMPv2-SMI
10: MODULE-COMPLIANCE, OBJECT-GROUP
11: FROM SNMPv2-CONF
12: ;
13:
14: tsmMIB MODULE-IDENTITY
15: LAST-UPDATED "200707050000Z"
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: Copyright (C) The IETF Trust (2007). This
50: version of this MIB module is part of RFC XXXX;
51: see the RFC itself for full legal notices.
52: -- NOTE to RFC editor: replace XXXX with actual RFC number
53: -- for this document and remove this note
54: "
55:
56: REVISION "200707050000Z"
57: DESCRIPTION "The initial version, published in RFC XXXX.
58: -- NOTE to RFC editor: replace XXXX with actual RFC number
59: -- for this document and remove this note
60: "
61:
62: ::= { snmpModules xxxx }
62: error -
Object identifier element `xxxx' name only allowed as first element
63:
64: -- RFC Ed.: replace xxxx with IANA-assigned number and
65: -- remove this note
66:
67: -- ---------------------------------------------------------- --
68: -- subtrees in the SNMP-TRANSPORT-SM-MIB
69: -- ---------------------------------------------------------- --
70:
71: tsmNotifications OBJECT IDENTIFIER ::= { tsmMIB 0 }
72: tsmMIBObjects OBJECT IDENTIFIER ::= { tsmMIB 1 }
73: tsmConformance OBJECT IDENTIFIER ::= { tsmMIB 2 }
74:
75: -- -------------------------------------------------------------
76: -- Objects
77: -- -------------------------------------------------------------
78:
79: -- Statistics for the Transport Security Model
80:
81:
82: tsmStats OBJECT IDENTIFIER ::= { tsmMIBObjects 1 }
83:
84: tsmInvalidCache OBJECT-TYPE
85: SYNTAX Counter32
86: MAX-ACCESS read-only
87: STATUS current
88: DESCRIPTION "The number of messages dropped because the
89: tmStateReference referred to an invalid cache.
90:
91: This value is not persistent across reboots.
92: "
93: ::= { tsmStats 1 }
94:
95: tsmInadequateSecurity OBJECT-TYPE
96: SYNTAX Counter32
97: MAX-ACCESS read-only
98: STATUS current
99: DESCRIPTION "The number of incoming messages dropped because
100: the actual securityLevel provided was less than
101: the requested securityLevel.
102:
103: This value is not persistent across reboots.
104: "
105: ::= { tsmStats 2 }
106:
107: -- -------------------------------------------------------------
108: -- tsmMIB - Conformance Information
109: -- -------------------------------------------------------------
110:
111: tsmGroups OBJECT IDENTIFIER ::= { tsmConformance 1 }
112: tsmCompliances OBJECT IDENTIFIER ::= { tsmConformance 2 }
113:
114: -- -------------------------------------------------------------
115: -- Units of conformance
116: -- -------------------------------------------------------------
117: tsmGroup OBJECT-GROUP
118: OBJECTS {
119: tsmInvalidCache,
120: tsmInadequateSecurity
121: }
122: STATUS current
123: DESCRIPTION "A collection of objects for maintaining
124: information of an SNMP engine which implements
125: the SNMP Transport Security Model.
126: "
127:
128: ::= { tsmGroups 2 }
129:
130: -- -------------------------------------------------------------
131: -- Compliance statements
132: -- -------------------------------------------------------------
133:
134: tsmCompliance MODULE-COMPLIANCE
135: STATUS current
136: DESCRIPTION
137: "The compliance statement for SNMP engines that support
138: the SNMP-TRANSPORT-SM-MIB"
139: MODULE
140: MANDATORY-GROUPS { tsmGroup }
141: ::= { tsmCompliances 1 }
142:
143: END
144:
145: --
146: -- Copyright (C) The IETF Trust (2007).
147: --
148: -- This document is subject to the rights, licenses and restrictions
149: -- contained in BCP 78, and except as set forth therein, the authors
150: -- retain all their rights.
151: --
152: -- This document and the information contained herein are provided on an
153: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
154: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
155: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
156: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
157: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
158: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
159: --
160: -- Intellectual Property
161: --
162: -- The IETF takes no position regarding the validity or scope of any
163: -- Intellectual Property Rights or other rights that might be claimed to
164: -- pertain to the implementation or use of the technology described in
165: -- this document or the extent to which any license under such rights
166: -- might or might not be available; nor does it represent that it has
167: -- made any independent effort to identify any such rights. Information
168: -- on the procedures with respect to rights in RFC documents can be
169: -- found in BCP 78 and BCP 79.
170: --
171: -- Copies of IPR disclosures made to the IETF Secretariat and any
172: -- assurances of licenses to be made available, or the result of an
173: -- attempt made to obtain a general license or permission for the use of
174: -- such proprietary rights by implementers or users of this
175: -- specification can be obtained from the IETF on-line IPR repository at
176: -- http://www.ietf.org/ipr.
177: --
178: -- The IETF invites any interested party to bring to its attention any
179: -- copyrights, patents or patent applications, or other proprietary
180: -- rights that may cover technology that may be required to implement
181: -- this standard. Please address the information to the IETF at
182: -- ietf-ipr@ietf.org.
183: --
184: