smilint output for ./PW-L2TPv3-DRAFT-00-MIB
Message Severities |
Severity | Count |
error | 2 |
Message Types |
Type | Count |
bad-identifier-case (error) | 1 |
object-identifier-not-prefix (error) | 1 |
Messages:
PW-L2TPv3-DRAFT-00-MIB
1: -- extracted from draft-nadeau-l2tpext-pw-l2tpv3-mib-01.txt
2: -- at Sat Jun 30 06:08:28 2007
3:
4: PW-L2TPv3-DRAFT-00-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, transmission
8: FROM SNMPv2-SMI -- [RFC2578]
9:
10: MODULE-COMPLIANCE, OBJECT-GROUP
11: FROM SNMPv2-CONF -- [RFC2580]
12:
13: StorageType, RowStatus
14: FROM SNMPv2-TC -- [RFC2579]
15:
16: InterfaceIndexOrZero
17: FROM IF-MIB -- [RFC2863]
18:
19: SnmpAdminString
20: FROM SNMP-FRAMEWORK-MIB
21:
22: pwIndex -- [RFCxxxx]
23: -- RFC Editor: Please replace XXXX with RFC number & remove this
24: -- note.
25: FROM PW-STD-MIB
26:
27: ;
28:
29: pwL2tpv3Draft00MIB MODULE-IDENTITY
30: LAST-UPDATED "200610051200Z" -- 05 Oct 2006 12:00:00 GMT
31: ORGANIZATION "IETF L2TP Working Group"
32: CONTACT-INFO
33: "Layer Two Tunneling Protocol Extensions WG
34: Working Group Area: Internet
35: Working Group Name: l2tpext
36: General Discussion: l2tp@l2tp.net"
37:
38: DESCRIPTION
39: "This MIB module complements the PW-STD-MIB module for PW
40: operation over L2TPv3.
41:
42: Copyright (C) The Internet Society (2006). This version
43: of this MIB module is part of RFC yyyy; see the RFC
44: itself for full legal notices.
45: -- RFC Ed.: replace yyyy with actual RFC number & remove
46: -- this note
47: "
48: -- Revision history.
49: REVISION "200610051200Z" -- 05 Oct 2006 12:00:00 GMT
50: DESCRIPTION
51: " First published as RFCWXYZ. "
52: -- RFC Editor: Please replace WXYZ with correct # and remove this
53: -- note
54:
55: ::= { transmission XXX }
55: error -
`XXX' should start with a lower case letter
55: error -
Object identifier element `XXX' name only allowed as first element
56: -- RFC Editor: To be assigned by IANA. Please replace XXX
57: -- with the assigned value and remove this note.
58:
59: -- Top-level components of this MIB.
60:
61:
62:
63: -- Notifications
64: pwL2tpv3Notifications OBJECT IDENTIFIER
65: ::= { pwL2tpv3Draft00MIB 0 }
66:
67: -- Tables, Scalars
68: pwL2tpv3Objects OBJECT IDENTIFIER
69: ::= { pwL2tpv3Draft00MIB 1 }
70: -- Conformance
71: pwL2tpv3Conformance OBJECT IDENTIFIER
72: ::= { pwL2tpv3Draft00MIB 2 }
73:
74: -- PW L2TPv3 table
75:
76: pwL2tpv3Table OBJECT-TYPE
77: SYNTAX SEQUENCE OF PwL2tpv3Entry
78: MAX-ACCESS not-accessible
79: STATUS current
80: DESCRIPTION
81: "This table controls L2TPv3 specific parameters when the PW is
82: going to be carried over L2TPv3."
83: ::= { pwL2tpv3Objects 1 }
84:
85: pwL2tpv3Entry OBJECT-TYPE
86: SYNTAX PwL2tpv3Entry
87: MAX-ACCESS not-accessible
88: STATUS current
89: DESCRIPTION
90: "A row in this table represents parameters
91: specific to L2TPv3 for a pseudo wire (PW).
92:
93: A row MUST be created automatically by the local agent
94: for every entry in the pwTable if the pwPsnType is
95: l2tp. Each entry is indexed by pwIndex, which uniquely
96: identifies a singular PW.
97:
98: A row can also be created manually in this table.
99: "
100: INDEX { pwIndex }
101:
102: -- Ed Note: Do we need to have pwL2tpv3CtrlCfgIfIndex as an index?
103:
104: ::= { pwL2tpv3Table 1 }
105:
106: PwL2tpv3Entry ::= SEQUENCE {
107: pwL2tpv3SessionCfgIfIndex InterfaceIndexOrZero,
108: pwL2tpv3CtrlCfgRouterID SnmpAdminString,
109: pwL2tpv3LocalSessionID Unsigned32,
110: pwL2tpv3RemoteSessionID Unsigned32,
111: pwL2tpv3OperType BITS,
112: pwL2tpv3DataSequencing INTEGER,
113: pwL2tpv3AddrResol INTEGER,
114: pwL2tpv3Mtu Unsigned32,
115: pwL2tpv3StorageType StorageType,
116: pwL2tpv3RowStatus RowStatus
117: }
118:
119: pwL2tpv3SessionCfgIfIndex OBJECT-TYPE
120: SYNTAX InterfaceIndexOrZero
121: MAX-ACCESS read-create
122: STATUS current
123: DESCRIPTION
124: "The interface index for the corresponding L2TP
125: interface to which this PW session is associated.
126:
127: The value of this object must correspond to the
128: value of l2tpv3SessionCfgIfIndex in the
129: l2tpv3SessionCfgTable."
130: ::= { pwL2tpv3Entry 1 }
131:
132:
133: pwL2tpv3CtrlCfgRouterID OBJECT-TYPE
134: SYNTAX SnmpAdminString
135: MAX-ACCESS read-create
136: STATUS current
137: DESCRIPTION
138: "The local router ID of this peer, as communicated via
139: the Router ID AVP for this control connection.
140:
141: The value of this object corresponds to the
142: value of l2tpv3CtrlCfgRouterID in l2tpv3CtrlCfgTable."
143: ::= { pwL2tpv3Entry 2 }
144:
145:
146: pwL2tpv3LocalSessionID OBJECT-TYPE
147: SYNTAX Unsigned32
148: MAX-ACCESS read-create
149: STATUS current
150: DESCRIPTION
151: "The local L2TPv3 session id for this PW. The value
152: of this object corresponds to the
153: l2tpv3SessionCfgLocalID in l2tpv3SessionCfgTable."
154: ::= { pwL2tpv3Entry 3 }
155:
156: pwL2tpv3RemoteSessionID OBJECT-TYPE
157: SYNTAX Unsigned32
158: MAX-ACCESS read-create
159: STATUS current
160: DESCRIPTION
161: "The remote L2TPv3 session id for this PW. The value
162: of this object corresponds to the
163: l2tpv3SessionCfgRemoteID in l2tpv3SessionCfgTable."
164: ::= { pwL2tpv3Entry 4 }
165:
166: pwL2tpv3OperType OBJECT-TYPE
167: SYNTAX BITS {
168: ifToIf (0),
169: vcToVc (1),
170: ifToVc (2),
171: vcToIf (3)
172: }
173: MAX-ACCESS read-create
174: STATUS current
175: DESCRIPTION
176: "Set by the operator to indicate the operation type of this
177: PW. "
178: REFERENCE
179: "[PW-IP] section 6."
180: ::= { pwL2tpv3Entry 5 }
181:
182: pwL2tpv3DataSequencing OBJECT-TYPE
183: SYNTAX INTEGER {
184: noSeq (0),
185: nonIpSeq (1),
186: allSeq (2)
187: }
188:
189: MAX-ACCESS read-create
190: STATUS current
191: DESCRIPTION
192: "Set by the operator to indicate data sequencing.
193: noSeq(0) - No incoming data packets require sequencing.
194: nonIpSeq(0)- Only non-IP data packets require sequencing.
195: allSeq(2) - All incoming data packets require sequencing."
196: REFERENCE
197: "[PW-IP] section 4.2."
198: DEFVAL { allSeq }
199: ::= { pwL2tpv3Entry 6 }
200:
201: pwL2tpv3AddrResol OBJECT-TYPE
202: SYNTAX INTEGER {
203: static (0),
204: dynamic (1)
205: }
206: MAX-ACCESS read-create
207: STATUS current
208: DESCRIPTION
209: "The value of this object indicates the point-to-point
210: address resolution mechanism for this PW."
211: REFERENCE
212: "[PW-IP] section 5."
213: DEFVAL { static }
214: ::= { pwL2tpv3Entry 7 }
215:
216: pwL2tpv3Mtu OBJECT-TYPE
217: SYNTAX Unsigned32
218: MAX-ACCESS read-create
219: STATUS current
220: DESCRIPTION
221: "Set by the operator to indicate the PW MTU value to be
222: used on the PW."
223: REFERENCE
224: "[PW-IP] section 4.3."
225: DEFVAL { 1500 }
226: ::= { pwL2tpv3Entry 8 }
227:
228: pwL2tpv3StorageType OBJECT-TYPE
229: SYNTAX StorageType
230: MAX-ACCESS read-create
231: STATUS current
232: DESCRIPTION
233: "This variable indicates the storage type for this row.
234: Conceptual rows having the value 'permanent'
235: need not allow write-access to any columnar
236: objects in the row."
237: DEFVAL { volatile }
238: ::= { pwL2tpv3Entry 9 }
239:
240: pwL2tpv3RowStatus OBJECT-TYPE
241: SYNTAX RowStatus
242: MAX-ACCESS read-create
243: STATUS current
244: DESCRIPTION
245: "This variable is used to create, modify, and/or
246: delete a row in this table. When a row in this
247: table is in active(1) state, no objects in that row
248: can be modified by the agent except
249: pwL2tpv3RowStatus and pwL2tpv3StorageType."
250: ::= { pwL2tpv3Entry 10 }
251:
252: -- End of PW L2TPv3 table
253:
254:
255:
256: -- conformance information
257:
258: pwL2tpv3Groups OBJECT IDENTIFIER ::= { pwL2tpv3Conformance 1 }
259: pwL2tpv3Compliances OBJECT IDENTIFIER ::= { pwL2tpv3Conformance 2 }
260:
261: -- Compliance requirement for fully compliant implementations.
262:
263: pwL2tpv3ModuleFullCompliance MODULE-COMPLIANCE
264: STATUS current
265: DESCRIPTION
266: "The compliance statement for agents that provide full
267: support for PW-L2TP MIB Module. Such devices can
268: then be monitored and also be configured using
269: this MIB module."
270:
271: MODULE -- this module
272: MANDATORY-GROUPS { pwL2tpv3Group
273: }
274:
275: ::= { pwL2tpv3Compliances 1 }
276:
277: -- Compliance requirement for Read Only compliant implementations.
278:
279: pwL2tpv3ModuleReadOnlyCompliance MODULE-COMPLIANCE
280: STATUS current
281: DESCRIPTION
282: "The compliance statement for agents that provide read
283: only support for PW-L2TP MIB Module. Such devices can
284: then be monitored but cannot be configured using this
285: MIB module."
286:
287:
288:
289: MODULE -- this module
290: MANDATORY-GROUPS { pwL2tpv3Group
291: }
292:
293:
294: ::= { pwL2tpv3Compliances 2 }
295:
296: -- Units of conformance.
297:
298: pwL2tpv3Group OBJECT-GROUP
299: OBJECTS {
300: pwL2tpv3SessionCfgIfIndex,
301: pwL2tpv3CtrlCfgRouterID,
302: pwL2tpv3LocalSessionID,
303: pwL2tpv3RemoteSessionID,
304: pwL2tpv3OperType,
305: pwL2tpv3DataSequencing,
306: pwL2tpv3AddrResol,
307: pwL2tpv3Mtu,
308: pwL2tpv3StorageType,
309: pwL2tpv3RowStatus
310: }
311: STATUS current
312: DESCRIPTION
313: "Collection of objects needed for PW over L2TPv3 PSN
314: configuration."
315: ::= { pwL2tpv3Groups 1 }
316:
317:
318: END
319:
320: --
321: -- Copyright (C) The IETF Trust (2007).
322: --
323: -- This document is subject to the rights, licenses and restrictions
324: -- contained in BCP 78, and except as set forth therein, the authors
325: -- retain all their rights.
326: --
327: -- This document and the information contained herein are provided on an
328: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
329: -- REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
330: -- IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
331: -- WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
332: -- WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
333: -- ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
334: -- FOR A PARTICULAR PURPOSE.
335: --
336: --
337: -- 12 Intellectual Property Notice
338: --
339: -- The IETF takes no position regarding the validity or scope of any
340: -- Intellectual Property Rights or other rights that might be claimed to
341: -- pertain to the implementation or use of the technology described in
342: -- this document or the extent to which any license under such rights
343: -- might or might not be available; nor does it represent that it has
344: -- made any independent effort to identify any such rights. Information
345: -- on the procedures with respect to rights in RFC documents can be
346: -- found in BCP 78 and BCP 79.
347: -- Copies of IPR disclosures made to the IETF Secretariat and any
348: -- assurances of licenses to be made available, or the result of an
349: -- attempt made to obtain a general license or permission for the use
350: -- of such proprietary rights by implementers or users of this
351: -- specification can be obtained from the IETF on-line IPR repository
352: -- at http://www.ietf.org/ipr.
353: --
354: -- The IETF invites any interested party to bring to its attention any
355: -- copyrights, patents or patent applications, or other proprietary
356: -- rights that may cover technology that may be required to implement
357: -- this standard. Please address the information to the IETF at ietf-
358: -- ipr@ietf.org.
359: --
360: -- Disclaimer of Validity
361: --
362: -- This document and the information contained herein are provided
363: -- on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
364: -- REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
365: -- IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
366: -- WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
367: -- WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
368: -- ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
369: -- FOR A PARTICULAR PURPOSE.
370: