smilint output for ./IPV6LOWPAN-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
Messages:
IPV6LOWPAN-MIB
1: -- extracted from draft-daniel-lowpan-mib-00.txt
2: -- at Thu Mar 1 06:08:22 2007
3:
4: IPV6LOWPAN-MIB DEFINITIONS ::= BEGIN
5: IMPORTS
6: TruthValue
7: FROM SNMPv2-TC
8: OBJECT-GROUP, MODULE-COMPLIANCE
9: FROM SNMPv2-CONF
10: MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, mib-2
11: FROM SNMPv2-SMI
12: LowpanIEEEEUI64Address, LowpanShortAddress
13: FROM LOWPAN-TC-MIB;
14:
15: lowpanMIB MODULE-IDENTITY
16: LAST-UPDATED "200701231307Z"
17: ORGANIZATION "IETF 6lowpan Working Group"
18: CONTACT-INFO "Ki-Hyung Kim, Editor
19: Ajou University
20: San 5 Wonchun-dong, Yeongtong-gu
21: Suwon-si, Gyeonggi-do 442-749
22: KOREA
23:
24: Phone: +82 31 219 2433
25: Email: kkim86@ajou.ac.kr
26:
27:
28: Seung Wha Yoo
29: Ajou University
30: San 5 Wonchun-dong, Yeongtong-gu
31: Suwon-si, Gyeonggi-do 442-749
32: KOREA
33:
34: Phone: +82 31 219 1603
35: Email: swyoo@ajou.ac.kr
36:
37:
38: Hamid Mukhtar
39: Ajou University
40: San 5 Wonchun-dong, Yeongtong-gu
41: Suwon-si, Gyeonggi-do 442-749
42: KOREA
43:
44: Phone: +82 10 2892 2469
45: Email: hamid@ajou.ac.kr
46:
47:
48: Soohong Daniel Park, Editor
49: Mobile Platform Laboratory, SAMSUNG Electronics
50: 416 Maetan-3dong, Yeongtong-gu
51: Suwon-si, Gyeonggi-do 442-742
52: KOREA
53:
54: Phone: +82 31 200 4508
55: Email: soohong.park@samsung.com
56:
57: Support Group E-mail: 6lowpan@ietf.org"
58:
59: DESCRIPTION "The MIB module for monitoring 6lowpan
60: entities.
61:
62: Copyright (C) The Internet Society 2007. This
63: version of this MIB module is part of RFC XXXX;
64: see the RFC itself for full legal notices."
65: -- RFC Ed.: replace XXXX with actual RFC number & remove this note
66:
67: REVISION "200701231307Z"
68: DESCRIPTION "Initial version, published as RFC XXXX."
69: -- RFC Ed.: replace XXXX with actual RFC number & remove this note
70:
71: ::= { mib-2 YYY } -- will be assigned by IANA
71: error -
`YYY' should start with a lower case letter
71: error -
Object identifier element `YYY' name only allowed as first element
72:
73: -- IANA Reg.: Please assign a value for "YYY" under the 'mib-2'
74: -- subtree and record the assignment in the SMI Numbers registry.
75:
76: -- RFC Ed.: When the above assignment has been made, please
77: -- remove the above note
78: -- replace "YYY" here with the assigned value and
79: -- remove this note.
80:
81: -- The major groups
82:
83: lowpanNotifications OBJECT IDENTIFIER ::= { lowpanMIB 0 }
84: lowpanObjects OBJECT IDENTIFIER ::= { lowpanMIB 1 }
85: lowpanConformance OBJECT IDENTIFIER ::= { lowpanMIB 2 }
86:
87: lowpanDeviceRole OBJECT-TYPE
88: SYNTAX INTEGER { coordinator ( 0 ) , router ( 1 ) ,
89: endDevice ( 2 ) }
90: MAX-ACCESS read-only
91: STATUS current
92: DESCRIPTION "The device in 6lowpan can play three roles.
93: coordinator(0) indicates that the device is a
94: PAN Coordinator which is the primary controller
95: of the PAN. Its a full-function device (FFD).
96: It MAY initiate the synchronization of the
97: entire 6LoWPAN by transmitting beacons.
98: router(1) a FFD which has the capability of
99: routing packets to the next hop device in
100: 6LoWPAN.
101: endDevice(2) RFD (Reduced function device) or
102: FFD in a 6LoWPAN, which is neither the
103: coordinator nor a router."
104: ::= { lowpanObjects 1 }
105:
106: lowpanDeviceCapabilities OBJECT-TYPE
107: SYNTAX BITS { alternatePANcoordinator ( 0 ) ,
108: deviceType ( 1 ) , powerSource ( 2 ) ,
109: recieverOnWhenIdle ( 3 ) , securityCapability
110: ( 6 ) , allocateAddress ( 7 ) }
111: MAX-ACCESS read-only
112: STATUS current
113: DESCRIPTION "alternatePANcoordinator(0)- The alternate PAN
114: coordinator subfield shall be set to 1 if the
115: device is capable of becoming a PAN
116: coordinator. Otherwise, the alternate PAN
117: coordinator subfield shall be set to 0.
118:
119: deviceType(1) -The device type subfield shall
120: be set to 1 if the device is an FFD.
121: Otherwise, the device type subfield shall be
122: set to 0 to indicate an RFD.
123:
124: powerSource(2)- The power source subfield
125: shall be set to 1 if the device is receiving
126: power from the alternating current mains.
127: Otherwise, the power source subfield shall
128: be set to 0.
129:
130: recieverOnWhenIdle(3) - The receiver on when
131: idle shall be set to 1 if the device does not
132: disable its receiver to conserve power
133: during idle periods. Otherwise, the receiver
134: on when idle subfield shall be set to 0.
135: securityCapability(6)- The security capability
136: subfield shall be set to 1 if the device is
137: capable of sending and receiving MAC frames
138: secured using the security suite. Otherwise
139: the security capability subfield shall be
140: set to 0.
141:
142: allocateAddress(7)- The allocate address
143: subfield shall be set to 1 if the device
144: wishes the coordinator to allocate a short
145: address as a result of the association
146: procedure. If this subfield is set to 0, the
147: special short address of 0 x fffe shall be
148: allocated to the device and returned through
149: the association response command. In this
150: case, the device shall communicate on the
151: PAN using only its 64 bit extended address.
152:
153: BITS 4-5 are reserved."
154: REFERENCE "IEEE Std 802.15.4 specifications section
155: 7.3.1.1.2"
156: ::= { lowpanObjects 2 }
157:
158:
159: lowpanRoutingTable OBJECT-TYPE
160: SYNTAX SEQUENCE OF LowpanRoutingEntry
161: MAX-ACCESS not-accessible
162: STATUS current
163: DESCRIPTION "The routing table entries of a device."
164: ::= { lowpanObjects 3 }
165:
166: lowpanRoutingEntry OBJECT-TYPE
167: SYNTAX LowpanRoutingEntry
168: MAX-ACCESS not-accessible
169: STATUS current
170: DESCRIPTION "This entry represents a conceptual row in the
171: routing table. It represents a single routing
172: entry."
173: INDEX { lowpanRouteDestAddress }
174: ::= { lowpanRoutingTable 1 }
175:
176: LowpanRoutingEntry ::= SEQUENCE {
177: lowpanRouteDestAddress LowpanShortAddress,
178: lowpanRouteNextHopAddress LowpanShortAddress,
179: lowpanRouteProtocol INTEGER
180: }
181:
182: lowpanRouteDestAddress OBJECT-TYPE
183: SYNTAX LowpanShortAddress
184: MAX-ACCESS not-accessible
185: STATUS current
186: DESCRIPTION "The 16-bit short address of destination of this
187: route."
188: ::= { lowpanRoutingEntry 1 }
189:
190:
191: lowpanRouteNextHopAddress OBJECT-TYPE
192: SYNTAX LowpanShortAddress
193: MAX-ACCESS read-only
194: STATUS current
195: DESCRIPTION "The short address of the next hop which leads
196: to the destination."
197: ::= { lowpanRoutingEntry 2 }
198:
199:
200: lowpanRouteProtocol OBJECT-TYPE
201: SYNTAX INTEGER { other ( 0 ), dymoLow ( 1 ), hiLow
202: ( 2 ) , load ( 3 ) }
203: MAX-ACCESS read-only
204: STATUS current
205: DESCRIPTION "6lowpan currently supports three routing
206: protocols
207: dymoLow(1) - Dynamic MANET On-demand routing
208: for 6LoWPAN
209: hiLow(2) - Hierarchical Routing over 6LoWPAN
210: load(3) -Ad Hoc On-Demand Distance Vector
211: Routing for 6lowpan"
212: REFERENCE "IETF 6lowpan WG
213: draft-daniel-6lowpan-load-adhoc-routing
214: (Work in progress), IETF 6lowpan WG
215: draft-montenegro-6lowpan-dymo-low-routing
216: (Work in progress), IETF 6lowpan WG
217: draft-daniel-6lowpan-hilow-hierarchical-routing
218: (Work in progress)"
219: ::= { lowpanRoutingEntry 3 }
220:
221: lowpanNeighborTable OBJECT-TYPE
222: SYNTAX SEQUENCE OF LowpanNeighborEntry
223: MAX-ACCESS not-accessible
224: STATUS current
225: DESCRIPTION "The neighbor table entries of a device"
226: ::= { lowpanObjects 4 }
227:
228: lowpanNeighborEntry OBJECT-TYPE
229: SYNTAX LowpanNeighborEntry
230: MAX-ACCESS not-accessible
231: STATUS current
232: DESCRIPTION "This entry represents a conceptual row in the
233: neighbor table. It represents a single
234: neighbor table entry."
235: INDEX { lowpanNeighborEUI64Address }
236: ::= { lowpanNeighborTable 1 }
237:
238: LowpanNeighborEntry ::= SEQUENCE {
239: lowpanNeighborPanID Unsigned32,
240: lowpanNeighborEUI64Address LowpanIEEEEUI64Address,
241: lowpanNeighborShortAddress LowpanShortAddress,
242: lowpanNeighborDeviceType INTEGER,
243: lowpanNeighborIsParent TruthValue
244: }
245:
246: lowpanNeighborPanID OBJECT-TYPE
247: SYNTAX Unsigned32 (0..65536)
248: MAX-ACCESS read-only
249: STATUS current
250: DESCRIPTION "The Personal area network Identifier
251: (PanID) of the neighbor entry."
252: ::= { lowpanNeighborEntry 1 }
253:
254:
255: lowpanNeighborEUI64Address OBJECT-TYPE
256: SYNTAX LowpanIEEEEUI64Address
257: MAX-ACCESS not-accessible
258: STATUS current
259: DESCRIPTION "The EUI64 bit address of the neighbor entry."
260: ::= { lowpanNeighborEntry 2 }
261:
262:
263: lowpanNeighborShortAddress OBJECT-TYPE
264: SYNTAX LowpanShortAddress
265: MAX-ACCESS read-only
266: STATUS current
267: DESCRIPTION "The 16-bit short address of the neighbor entry."
268: ::= { lowpanNeighborEntry 3 }
269:
270:
271: lowpanNeighborDeviceType OBJECT-TYPE
272: SYNTAX INTEGER { coordinator ( 0 ) , router ( 1 ) ,
273: endDevice ( 2 )}
274: MAX-ACCESS read-only
275: STATUS current
276: DESCRIPTION "The device type of the neighbor entry."
277: ::= { lowpanNeighborEntry 4 }
278:
279: lowpanNeighborIsParent OBJECT-TYPE
280: SYNTAX TruthValue
281: MAX-ACCESS read-only
282: STATUS current
283: DESCRIPTION "The value 'true(1)' indicates that the
284: neighbor is a topological parent of the
285: device."
286: ::= { lowpanNeighborEntry 5 }
287:
288:
289: lowpanUseHierarchicalRouting OBJECT-TYPE
290: SYNTAX TruthValue
291: MAX-ACCESS read-only
292: STATUS current
293: DESCRIPTION "The value 'true(1)' indicates that the
294: entity uses tree based routing. 'false(2)'
295: indicates that entity is not using
296: tree based routing."
297: ::= { lowpanObjects 5 }
298:
299: lowpanBroadcastSequenceNumber OBJECT-TYPE
300: SYNTAX Unsigned32 (0..65536)
301: MAX-ACCESS read-only
302: STATUS current
303: DESCRIPTION "The last value of the sequence number
304: that was added to the 6lowpan broadcast or
305: multicast frame."
306: REFERENCE "Section 11 draft-ietf-6lowpan-format (work in
307: progress)"
308: ::= { lowpanObjects 6 }
309:
310: lowpanAckTimeout OBJECT-TYPE
311: SYNTAX Unsigned32
312: UNITS "milli-seconds"
313: MAX-ACCESS read-write
314: STATUS current
315: DESCRIPTION "The maximum time allowed for retransmission
316: of a broadcast message"
317: ::= { lowpanObjects 7 }
318:
319: lowpanBroadcastRetries OBJECT-TYPE
320: SYNTAX Unsigned32
321: MAX-ACCESS read-write
322: STATUS current
323: DESCRIPTION "The maximum number of retries allowed for a
324: broadcast message."
325: ::= { lowpanObjects 8 }
326:
327: -- Conformance information
328: lowpanGroups OBJECT IDENTIFIER ::= { lowpanConformance 1 }
329: lowpanCompliances OBJECT IDENTIFIER ::= { lowpanConformance 2 }
330:
331: lowpanGeneralGroup OBJECT-GROUP
332: OBJECTS { lowpanDeviceCapabilities , lowpanDeviceRole,
333: lowpanUseHierarchicalRouting,
334: lowpanAckTimeout, lowpanBroadcastRetries,
335: lowpanBroadcastSequenceNumber,
336: lowpanNeighborDeviceType,
337: lowpanNeighborPanID,
338: lowpanNeighborIsParent,
339: lowpanNeighborShortAddress,
340: lowpanRouteNextHopAddress,
341: lowpanRouteProtocol }
342: STATUS current
343: DESCRIPTION "A collection of objects for basic 6lowpan
344: monitoring"
345: ::= { lowpanGroups 1 }
346:
347: lowpanCoreCompliance MODULE-COMPLIANCE
348: STATUS current
349: DESCRIPTION
350: "The compliance statement for SNMP entities
351: which implement the LOWPAN-MIB."
352: MODULE -- this module
353: MANDATORY-GROUPS { lowpanGeneralGroup }
354:
355: ::= { lowpanCompliances 1 }
356:
357: lowpanCoreReadOnlyCompliance MODULE-COMPLIANCE
358: STATUS current
359: DESCRIPTION
360: "The compliance statement for SNMP entities
361: which implement the LOWPAN-MIB without support
362: for read-write (i.e. in read-only mode) .
363: "
364: MODULE -- this module
365: MANDATORY-GROUPS { lowpanGeneralGroup }
366:
367: OBJECT lowpanAckTimeout
368: MIN-ACCESS read-only
369: DESCRIPTION
370: "Write access is not required."
371:
372: OBJECT lowpanBroadcastRetries
373: MIN-ACCESS read-only
374: DESCRIPTION
375: "Write access is not required."
376:
377: ::= { lowpanCompliances 2 }
378:
379:
380:
381: END
382:
383: --
384: -- Copyright (C) The IETF Trust (2007).
385: --
386: -- This document is subject to the rights, licenses and restrictions
387: -- contained in BCP 78, and except as set forth therein, the authors
388: -- retain all their rights.
389: --
390: -- This document and the information contained herein are provided on an
391: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
392: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
393: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
394: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
395: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
396: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
397: --
398: -- Intellectual Property
399: --
400: -- The IETF takes no position regarding the validity or scope of any
401: -- Intellectual Property Rights or other rights that might be claimed to
402: -- pertain to the implementation or use of the technology described in
403: -- this document or the extent to which any license under such rights
404: -- might or might not be available; nor does it represent that it has
405: -- made any independent effort to identify any such rights. Information
406: -- on the procedures with respect to rights in RFC documents can be
407: -- found in BCP 78 and BCP 79.
408: --
409: -- Copies of IPR disclosures made to the IETF Secretariat and any
410: -- assurances of licenses to be made available, or the result of an
411: -- attempt made to obtain a general license or permission for the use of
412: -- such proprietary rights by implementers or users of this
413: -- specification can be obtained from the IETF on-line IPR repository at
414: -- http://www.ietf.org/ipr.
415: --
416: -- The IETF invites any interested party to bring to its attention any
417: -- copyrights, patents or patent applications, or other proprietary
418: -- rights that may cover technology that may be required to implement
419: -- this standard. Please address the information to the IETF at
420: -- ietf-ipr@ietf.org.
421: --
422: