smilint output for ./UDPLITE-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| warning | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| index-exceeds-too-large (warning) | 1 |
| object-identifier-not-prefix (error) | 1 |
Messages:
UDPLITE-MIB
1: -- extracted from draft-ietf-tsvwg-udplite-mib-03.txt
2: -- at Tue Oct 30 07:09:11 2007
3:
4: UDPLITE-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY,
8: OBJECT-TYPE,
9: mib-2, Unsigned32,
10: Counter32, Counter64 FROM SNMPv2-SMI -- [RFC2578]
11:
12: TimeStamp FROM SNMPv2-TC -- [RFC2579]
13:
14: MODULE-COMPLIANCE,
15: OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
16:
17: InetAddress,
18: InetAddressType,
19: InetPortNumber FROM INET-ADDRESS-MIB; -- [RFC4001]
20:
21: udpliteMIB MODULE-IDENTITY
22: LAST-UPDATED "200710290000Z" -- Mon, 29th Oct 2007
23: ORGANIZATION "IETF TSV Working Group (TSVWG)"
24: CONTACT-INFO
25: "IETF TSV Working Group
26: http://www.ietf.org/html.charters/tsvwg-charter.html
27: Mailing List: tsvwg@ietf.org
28:
29: Gerrit Renker, Godred Fairhurst
30: Electronics Research Group
31: School of Engineering, University of Aberdeen
32: Fraser Noble Building, Aberdeen AB24 3UE, UK"
33: DESCRIPTION
34: "The MIB module for managing UDP-Lite implementations.
35: Copyright (C) The IETF Trust (2007). This version of
36: this MIB module is part of RFC ZZZ; see the RFC
37: itself for full legal notices."
38:
39: -- RFC Ed.: replace ZZZ with actual RFC number & remove this note
40:
41: REVISION "200710290000Z" -- Mon, 29th Oct 2007
42: DESCRIPTION
43: "Initial SMIv2 revision, based on the format of the UDP
44: MIB module (RFC 4113) and published as RFC ZZZ."
45:
46: -- RFC Ed.: replace ZZZ with actual RFC number & remove this note
47:
48: ::= { mib-2 XXX }
48: error -
`XXX' should start with a lower case letter
48: error -
Object identifier element `XXX' name only allowed as first element
49:
50: -- RFC Ed.: replace XXX with OBJECT-IDENTIFIER & remove this note
51:
52:
53: udplite OBJECT IDENTIFIER ::= { udpliteMIB 1 }
54:
55:
56: udpliteInDatagrams OBJECT-TYPE -- as in UDP-MIB
57: SYNTAX Counter64
58: MAX-ACCESS read-only
59: STATUS current
60: DESCRIPTION
61: "The total number of UDP-Lite datagrams that were
62: delivered to UDP-Lite users.
63: Discontinuities in the value of this counter can occur
64: at re-initialisation of the management system, and at
65: other times as indicated by the value of
66: udpliteStatsDiscontinuityTime."
67: ::= { udplite 1 }
68:
69: udpliteInPartialCov OBJECT-TYPE -- new in UDP-Lite
70: SYNTAX Counter64
71: MAX-ACCESS read-only
72: STATUS current
73: DESCRIPTION
74: "The total number of UDP-Lite datagrams that were
75: delivered to UDP-Lite users (applications) and whose
76: checksum coverage was strictly less than the datagram
77: length.
78: Discontinuities in the value of this counter can occur
79: at re-initialisation of the management system, and at
80: other times as indicated by the value of
81: udpliteStatsDiscontinuityTime."
82: ::= { udplite 2 }
83:
84:
85: udpliteNoPorts OBJECT-TYPE -- as in UDP-MIB
86: SYNTAX Counter32
87: MAX-ACCESS read-only
88: STATUS current
89: DESCRIPTION
90: "The total number of received UDP-Lite datagrams for
91: which there was no listener at the destination port.
92:
93: Discontinuities in the value of this counter can occur
94: at re-initialisation of the management system, and at
95: other times as indicated by the value of
96: udpliteStatsDiscontinuityTime."
97: ::= { udplite 3 }
98:
99:
100: udpliteInErrors OBJECT-TYPE -- as in UDP-MIB
101: SYNTAX Counter32
102: MAX-ACCESS read-only
103: STATUS current
104: DESCRIPTION
105: "The number of received UDP-Lite datagrams that could not
106: be delivered for reasons other than the lack of an
107: application at the destination port.
108: Discontinuities in the value of this counter can occur
109: at re-initialisation of the management system, and at
110: other times as indicated by the value of
111: udpliteStatsDiscontinuityTime."
112: ::= { udplite 4 }
113:
114: udpliteInBadChecksum OBJECT-TYPE -- new in UDP-Lite
115: SYNTAX Counter32
116: MAX-ACCESS read-only
117: STATUS current
118: DESCRIPTION
119: "The number of received UDP-Lite datagrams whose checksum
120: could not be validated. This includes illegal checksum
121: coverage values, as their use would lead to incorrect
122: checksums.
123: Discontinuities in the value of this counter can occur
124: at re-initialisation of the management system, and at
125: other times as indicated by the value of
126: udpliteStatsDiscontinuityTime."
127: REFERENCE "RFC 3828, section 3.1"
128: ::= { udplite 5 }
129:
130:
131: udpliteOutDatagrams OBJECT-TYPE -- as in UDP-MIB
132: SYNTAX Counter64
133: MAX-ACCESS read-only
134: STATUS current
135: DESCRIPTION
136: "The total number of UDP-Lite datagrams sent from this
137: entity.
138: Discontinuities in the value of this counter can occur
139: at re-initialisation of the management system, and at
140: other times as indicated by the value of
141: udpliteStatsDiscontinuityTime."
142: ::= { udplite 6 }
143:
144:
145: udpliteOutPartialCov OBJECT-TYPE -- new in UDP-Lite
146: SYNTAX Counter64
147: MAX-ACCESS read-only
148: STATUS current
149: DESCRIPTION
150: "The total number of udpliteOutDatagrams whose
151: checksum coverage was strictly less than the
152: datagram length.
153: Discontinuities in the value of this counter can occur
154: at re-initialisation of the management system, and at
155: other times as indicated by the value of
156: udpliteStatsDiscontinuityTime."
157: ::= { udplite 7 }
158:
159:
160: udpliteEndpointTable OBJECT-TYPE
161: SYNTAX SEQUENCE OF UdpLiteEndpointEntry
162: MAX-ACCESS not-accessible
163: STATUS current
164: DESCRIPTION
165: "A table containing information about this entity's
166: UDP-Lite endpoints on which a local application is
167: currently accepting or sending datagrams.
168:
169: The address type in this table represents the address
170: type used for the communication, irrespective of the
171: higher-layer abstraction. For example, an application
172: using IPv6 'sockets' to communicate via IPv4 between
173: ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use
174: InetAddressType ipv4(1).
175:
176: Like the udpTable in RFC 4113, this table also allows
177: the representation of an application that completely
178: specifies both local and remote addresses and ports. A
179: listening application is represented in three possible
180: ways:
181:
182: 1) An application that is willing to accept both IPv4
183: and IPv6 datagrams is represented by a
184: udpliteEndpointLocalAddressType of unknown(0) and a
185: udpliteEndpointLocalAddress of ''h (a zero-length
186: octet-string).
187:
188: 2) An application that is willing to accept only IPv4
189: or only IPv6 datagrams is represented by a
190: udpliteEndpointLocalAddressType of the appropriate
191: address type and a udpliteEndpointLocalAddress of
192: '0.0.0.0' or '::' respectively.
193:
194: 3) An application that is listening for datagrams only
195: for a specific IP address but from any remote
196: system is represented by a
197: udpliteEndpointLocalAddressType of the appropriate
198: address type, with udpliteEndpointLocalAddress
199: specifying the local address.
200:
201: In all cases where the remote address is a wildcard,
202: the udpliteEndpointRemoteAddressType is unknown(0),
203: the udpliteEndpointRemoteAddress is ''h (a zero-length
204: octet-string), and the udpliteEndpointRemotePort is 0.
205:
206: If the operating system is demultiplexing UDP-Lite
207: packets by remote address/port, or if the application
208: has 'connected' the socket specifying a default remote
209: address/port, the udpliteEndpointRemote* values should
210: be used to reflect this."
211: ::= { udplite 8 }
212:
213:
214: udpliteEndpointEntry OBJECT-TYPE
214: warning -
warning: index of row `udpliteEndpointEntry' can exceed OID size limit by 394 subidentifier(s)
215: SYNTAX UdpLiteEndpointEntry
216: MAX-ACCESS not-accessible
217: STATUS current
218: DESCRIPTION
219: "Information about a particular current UDP-Lite endpoint.
220:
221: Implementers need to pay attention to the sizes of
222: udpliteEndpointLocalAddress/RemoteAddress, as OIDs of
223: column instances in this table must have no more than
224: 128 sub-identifiers in order to remain accessible with
225: SNMPv1, SNMPv2c, and SNMPv3."
226: INDEX { udpliteEndpointLocalAddressType,
227: udpliteEndpointLocalAddress,
228: udpliteEndpointLocalPort,
229: udpliteEndpointRemoteAddressType,
230: udpliteEndpointRemoteAddress,
231: udpliteEndpointRemotePort,
232: udpliteEndpointInstance }
233: ::= { udpliteEndpointTable 1 }
234:
235:
236: UdpLiteEndpointEntry ::= SEQUENCE {
237: udpliteEndpointLocalAddressType InetAddressType,
238: udpliteEndpointLocalAddress InetAddress,
239: udpliteEndpointLocalPort InetPortNumber,
240: udpliteEndpointRemoteAddressType InetAddressType,
241: udpliteEndpointRemoteAddress InetAddress,
242: udpliteEndpointRemotePort InetPortNumber,
243: udpliteEndpointInstance Unsigned32,
244: udpliteEndpointProcess Unsigned32,
245: udpliteEndpointMinCoverage Unsigned32,
246: udpliteEndpointViolCoverage Counter32
247: }
248: udpliteEndpointLocalAddressType OBJECT-TYPE
249: SYNTAX InetAddressType
250: MAX-ACCESS not-accessible
251: STATUS current
252: DESCRIPTION
253: "The address type of udpliteEndpointLocalAddress. Only
254: IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
255: unknown(0) if datagrams for all local IP addresses are
256: accepted."
257: ::= { udpliteEndpointEntry 1 }
258:
259: udpliteEndpointLocalAddress OBJECT-TYPE
260: SYNTAX InetAddress
261: MAX-ACCESS not-accessible
262: STATUS current
263: DESCRIPTION
264: "The local IP address for this UDP-Lite endpoint.
265:
266: The value of this object can be represented in three
267: possible ways, depending on the characteristics of the
268: listening application:
269:
270: 1. For an application that is willing to accept both
271: IPv4 and IPv6 datagrams, the value of this object
272: must be ''h (a zero-length octet-string), with
273: the value of the corresponding instance of the
274: EndpointLocalAddressType object being unknown(0).
275:
276: 2. For an application that is willing to accept only
277: IPv4 or only IPv6 datagrams, the value of this
278: object must be '0.0.0.0' or '::', respectively,
279: while the corresponding instance of the
280: EndpointLocalAddressType object represents the
281: appropriate address type.
282:
283: 3. For an application that is listening for data
284: destined only to a specific IP address, the value
285: of this object is the specific IP address for
286: which this node is receiving packets, with the
287: corresponding instance of the
288: EndpointLocalAddressType object representing the
289: appropriate address type.
290:
291: As this object is used in the index for the
292: udpliteEndpointTable, implementors should be careful
293: not to create entries that would result in OIDs with
294: more than 128 sub-identifiers; this is because of SNMP
295: and SMI limitations."
296: ::= { udpliteEndpointEntry 2 }
297:
298:
299: udpliteEndpointLocalPort OBJECT-TYPE
300: SYNTAX InetPortNumber
301: MAX-ACCESS not-accessible
302: STATUS current
303: DESCRIPTION
304: "The local port number for this UDP-Lite endpoint."
305: ::= { udpliteEndpointEntry 3 }
306:
307: udpliteEndpointRemoteAddressType OBJECT-TYPE
308: SYNTAX InetAddressType
309: MAX-ACCESS not-accessible
310: STATUS current
311: DESCRIPTION
312: "The address type of udpliteEndpointRemoteAddress. Only
313: IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
314: unknown(0) if datagrams for all remote IP addresses are
315: accepted. Also, note that some combinations of
316: udpliteEndpointLocalAdressType and
317: udpliteEndpointRemoteAddressType are not supported. In
318: particular, if the value of this object is not
319: unknown(0), it is expected to always refer to the
320: same IP version as udpliteEndpointLocalAddressType."
321: ::= { udpliteEndpointEntry 4 }
322:
323:
324: udpliteEndpointRemoteAddress OBJECT-TYPE
325: SYNTAX InetAddress
326: MAX-ACCESS not-accessible
327: STATUS current
328: DESCRIPTION
329: "The remote IP address for this UDP-Lite endpoint. If
330: datagrams from any remote system are to be accepted,
331: this value is ''h (a zero-length octet-string).
332: Otherwise, it has the type described by
333: udpliteEndpointRemoteAddressType and is the address of
334: the remote system from which datagrams are to be
335: accepted (or to which all datagrams will be sent).
336:
337: As this object is used in the index for the
338: udpliteEndpointTable, implementors should be careful
339: not to create entries that would result in OIDs with
340: more than 128 sub-identifiers; this is because of SNMP
341: and SMI limitations."
342: ::= { udpliteEndpointEntry 5 }
343:
344:
345: udpliteEndpointRemotePort OBJECT-TYPE
346: SYNTAX InetPortNumber
347: MAX-ACCESS not-accessible
348: STATUS current
349: DESCRIPTION
350: "The remote port number for this UDP-Lite endpoint. If
351: datagrams from any remote system are to be accepted,
352: this value is zero."
353: ::= { udpliteEndpointEntry 6 }
354:
355: udpliteEndpointInstance OBJECT-TYPE
356: SYNTAX Unsigned32 (1..'ffffffff'h)
357: MAX-ACCESS not-accessible
358: STATUS current
359: DESCRIPTION
360: "The instance of this tuple. This object is used to
361: distinguish among multiple processes 'connected' to
362: the same UDP-Lite endpoint. For example, on a system
363: implementing the BSD sockets interface, this would be
364: used to support the SO_REUSEADDR and SO_REUSEPORT
365: socket options."
366: ::= { udpliteEndpointEntry 7 }
367:
368:
369: udpliteEndpointProcess OBJECT-TYPE
370: SYNTAX Unsigned32
371: MAX-ACCESS read-only
372: STATUS current
373: DESCRIPTION
374: "A unique value corresponding to a piece of software
375: running on this endpoint.
376:
377: If this endpoint is associated with more than one piece
378: of software, the agent should choose one of these; such
379: that subsequent reads will consistently return the same
380: value, as long as the representative piece of software
381: is running and still associated with the endpoint. The
382: implementation may use any algorithm satisfying these
383: constraints (e.g. choosing the entity with the oldest
384: start time).
385:
386: This identifier is platform-specific. Wherever possible,
387: it should use the system's native, unique identification
388: number as value.
389:
390: If the SYSAPPL-MIB module is available, the value should
391: be the same as sysApplElmtRunIndex. If not available, an
392: alternative should be used (e.g. the hrSWRunIndex of the
393: HOST-RESOURCES-MIB module).
394:
395: If it is not possible to uniquely identify the pieces of
396: software associated with this endpoint, then the value
397: zero should be used. (Note that zero is otherwise a
398: valid value for sysApplElmtRunIndex.)"
399: ::= { udpliteEndpointEntry 8 }
400:
401: udpliteEndpointMinCoverage OBJECT-TYPE -- new in UDP-Lite
402: SYNTAX Unsigned32
403: MAX-ACCESS read-only
404: STATUS current
405: DESCRIPTION
406: "The minimum checksum coverage expected by this endpoint.
407: A value of 0 indicates that only fully covered datagrams
408: are accepted."
409: REFERENCE "RFC 3828, section 3.1"
410: ::= { udpliteEndpointEntry 9 }
411:
412:
413: udpliteEndpointViolCoverage OBJECT-TYPE -- new / optional in UDP-Lite
414: SYNTAX Counter32
415: MAX-ACCESS read-only
416: STATUS current
417: DESCRIPTION
418: "The number of datagrams received by this endpoint whose
419: checksum coverage violated the minimum coverage threshold
420: set for this connection (i.e. all valid datagrams whose
421: checksum coverage was strictly smaller than the minimum,
422: as defined in RFC 3828).
423: Discontinuities in the value of this counter can occur
424: at re-initialisation of the management system, and at
425: other times as indicated by the value of
426: udpliteStatsDiscontinuityTime."
427: ::= { udpliteEndpointEntry 10 }
428:
429:
430: udpliteStatsDiscontinuityTime OBJECT-TYPE
431: SYNTAX TimeStamp
432: MAX-ACCESS read-only
433: STATUS current
434: DESCRIPTION
435: "The value of sysUpTime at the most recent occasion at
436: which one or more of the UDP-Lite counters suffered a
437: discontinuity.
438: A value of zero indicates no such discontinuity has
439: occurred since the last re-initialisation of the local
440: management subsystem."
441: ::= { udplite 9 }
442:
443:
444: -- Conformance Information
445:
446: udpliteMIBConformance OBJECT IDENTIFIER ::= { udpliteMIB 2 }
447:
448: udpliteMIBCompliance MODULE-COMPLIANCE
449: STATUS current
450: DESCRIPTION
451: "The compliance statement for systems that implement
452: UDP-Lite.
453:
454: There are a number of INDEX objects that cannot be
455: represented in the form of OBJECT clauses in SMIv2,
456: but for which we have the following compliance
457: requirements, expressed in OBJECT clause form in this
458: description clause:
459:
460: -- OBJECT udpliteEndpointLocalAddressType
461: -- SYNTAX InetAddressType { unknown(0), ipv4(1),
462: -- ipv6(2), ipv4z(3),
463: -- ipv6z(4) }
464: -- DESCRIPTION
465: -- Support for dns(16) is not required.
466: -- OBJECT udpliteEndpointLocalAddress
467:
468:
469:
470: -- SYNTAX InetAddress (SIZE(0|4|8|16|20))
471: -- DESCRIPTION
472: -- Support is only required for zero-length
473: -- octet-strings, and for scoped and unscoped
474: -- IPv4 and IPv6 addresses.
475: -- OBJECT udpliteEndpointRemoteAddressType
476: -- SYNTAX InetAddressType { unknown(0), ipv4(1),
477: -- ipv6(2), ipv4z(3),
478: -- ipv6z(4) }
479: -- DESCRIPTION
480: -- Support for dns(16) is not required.
481: -- OBJECT udpliteEndpointRemoteAddress
482: -- SYNTAX InetAddress (SIZE(0|4|8|16|20))
483: -- DESCRIPTION
484: -- Support is only required for zero-length
485: -- octet-strings, and for scoped and unscoped
486: -- IPv4 and IPv6 addresses.
487: "
488: MODULE -- this module
489: MANDATORY-GROUPS { udpliteBaseGroup,
490: udplitePartialCsumGroup,
491: udpliteEndpointGroup }
492: GROUP udpliteAppGroup
493: DESCRIPTION
494: "This group is optional and provides supplementary
495: information about the effectiveness of using minimum
496: checksum coverage thresholds on endpoints."
497: ::= { udpliteMIBConformance 1 }
498:
499:
500: udpliteMIBGroups OBJECT IDENTIFIER ::= { udpliteMIBConformance 2 }
501:
502:
503: udpliteBaseGroup OBJECT-GROUP -- as in UDP
504: OBJECTS { udpliteInDatagrams, udpliteNoPorts, udpliteInErrors,
505: udpliteOutDatagrams, udpliteStatsDiscontinuityTime }
506: STATUS current
507: DESCRIPTION
508: "The group of objects providing for counters of
509: basic UDP-like statistics."
510: ::= { udpliteMIBGroups 1 }
511:
512:
513: udplitePartialCsumGroup OBJECT-GROUP -- specific to UDP-Lite
514: OBJECTS { udpliteInPartialCov,
515: udpliteInBadChecksum,
516: udpliteOutPartialCov }
517: STATUS current
518: DESCRIPTION
519: "The group of objects providing for counters of
520: transport-layer statistics exclusive to UDP-Lite."
521: ::= { udpliteMIBGroups 2 }
522:
523:
524: udpliteEndpointGroup OBJECT-GROUP
525: OBJECTS { udpliteEndpointProcess, udpliteEndpointMinCoverage }
526: STATUS current
527: DESCRIPTION
528: "The group of objects providing for the IP version
529: independent management of UDP-Lite 'endpoints'."
530: ::= { udpliteMIBGroups 3 }
531:
532:
533: udpliteAppGroup OBJECT-GROUP
534: OBJECTS { udpliteEndpointViolCoverage }
535: STATUS current
536: DESCRIPTION
537: "The group of objects that provide application-level
538: information for the configuration management of
539: UDP-Lite 'endpoints'."
540: ::= { udpliteMIBGroups 4 }
541:
542: END
543:
544: --
545: -- Copyright (C) The IETF Trust (2007).
546: --
547: -- This document is subject to the rights, licenses and restrictions
548: -- contained in BCP 78, and except as set forth therein, the authors
549: -- retain all their rights.
550: --
551: -- This document and the information contained herein are provided on an
552: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
553: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
554: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
555: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
556: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
557: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
558: --
559: --
560: -- Intellectual Property
561: --
562: -- The IETF takes no position regarding the validity or scope of any
563: -- Intellectual Property Rights or other rights that might be claimed to
564: -- pertain to the implementation or use of the technology described in
565: -- this document or the extent to which any license under such rights
566: -- might or might not be available; nor does it represent that it has
567: -- made any independent effort to identify any such rights. Information
568: -- on the procedures with respect to rights in RFC documents can be
569: -- found in BCP 78 and BCP 79.
570: --
571: -- Copies of IPR disclosures made to the IETF Secretariat and any
572: -- assurances of licenses to be made available, or the result of an
573: -- attempt made to obtain a general license or permission for the use of
574: -- such proprietary rights by implementers or users of this
575: -- specification can be obtained from the IETF on-line IPR repository at
576: -- http://www.ietf.org/ipr.
577: --
578: -- The IETF invites any interested party to bring to its attention any
579: -- copyrights, patents or patent applications, or other proprietary
580: -- rights that may cover technology that may be required to implement
581: -- this standard. Please address the information to the IETF at
582: -- ietf-ipr@ietf.org.
583: --
584: --
585: -- Acknowledgment
586: --
587: -- Funding for the RFC Editor function is provided by the IETF
588: -- Administrative Support Activity (IASA).
589: