smilint output for ./UDP-PROC-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 1 |
| warning | 7 |
| Message Types |
|---|
| Type | Count |
|---|
| empty-description (warning) | 2 |
| import-unused (warning) | 4 |
| index-exceeds-too-large (warning) | 1 |
| object-identifier-unknown (severe) | 1 |
Messages:
UDP-PROC-MIB
1: -- extracted from draft-persson-v6ops-mib-issue-01.txt
2: -- at Thu Nov 9 06:07:30 2006
3:
4: UDP-PROC-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: Integer32, Counter32, Counter64,
8: warning -
warning: identifier `Integer32' imported from module `SNMPv2-SMI' is never used
8: warning -
warning: identifier `Counter32' imported from module `SNMPv2-SMI' is never used
8: warning -
warning: identifier `Counter64' imported from module `SNMPv2-SMI' is never used
9: TimeTicks, Unsigned32,IpAddress,
9: warning -
warning: identifier `IpAddress' imported from module `SNMPv2-SMI' is never used
10: mib-2 FROM SNMPv2-SMI
11:
12: MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
13: InetAddress, InetAddressType,
14: InetPortNumber FROM INET-ADDRESS-MIB
15: udpEndpointEntry
16: FROM UDP-MIB;
17:
18: udpProcMIB MODULE-IDENTITY
19: LAST-UPDATED "200610010000Z"
20: ORGANIZATION "IETF IPv6 Working Group"
21: CONTACT-INFO
22: "Alain Durand
23: Comcast Cable
24: 1500 Market st
25: Philadelphia
26: PA 19102 USA
27: Email: alain_durand@cable.comcast.com
28:
29: Anders Persson
30: SUN Microsystems inc.
31: 17 Network Circle
32: Menlo Park
33: CA 94025 USA
34: Email: anders.persson@sun.com
35:
36: Paul Schauer
37: Comcast Cable
38: 183 Inverness Dr West
39: Englewood
40: CO 80112 USA
41: Email: paul_schauer@cable.comcast.com
42:
43: David Thaler
44: Microsoft
45: One Microsoft Way
46: Redmond
47: WA 98052 USA
48: Email: dthaler@microsoft.com"
49:
50: DESCRIPTION
51: "Test branch for proposed UDP listener information tables"
52:
53: REVISION "200610010000Z"
54: DESCRIPTION
55: "Initial version"
56:
57:
58: ::= { mib-2 994 }
59:
60: udpProc OBJECT IDENTIFIER ::= { mib-2 996 }
61:
62: --
63: -- The proposed new UDP Endpoint Info table.
64: --
65:
66: udpEndpointInfoTable OBJECT-TYPE
67: SYNTAX SEQUENCE OF UdpEndpointInfoEntry
68: MAX-ACCESS not-accessible
69: STATUS current
70: DESCRIPTION
71: "A table containing additional information about existing UDP
72: endpoints. This table augments the existing udpEndpointTable
73: by providing information for the process that created the
74: endpoint on the listed address/port, not just the
75: process currently associated with the endpoint. This
76: aids identifying processes sharing connections on the same
77: port."
78:
79: ::= { udpProc 1 }
80:
81: udpEndpointInfoEntry OBJECT-TYPE
82: SYNTAX UdpEndpointInfoEntry
83: MAX-ACCESS not-accessible
84: STATUS current
85:
86: DESCRIPTION
87: "The additional time field allows an operator to identify
88: when a partcular UDP endpoint came into existance."
89:
90: AUGMENTS { udpEndpointEntry }
91:
92: ::= { udpEndpointInfoTable 1 }
93:
94: UdpEndpointInfoEntry ::= SEQUENCE {
95: udpEndpointInfoCreatorPID Unsigned32,
96: udpEndpointInfoProcessCreateTime TimeTicks
97: }
98:
99: udpEndpointInfoCreatorPID OBJECT-TYPE
100: SYNTAX Unsigned32
101: MAX-ACCESS read-only
102: STATUS current
103: DESCRIPTION
104: "The system's process ID for the process that created
105: this endpoint, even if this process no longer exists
106: or is no longer associated with this connection."
107:
108: ::= { udpEndpointInfoEntry 1 }
109:
110: udpEndpointInfoProcessCreateTime OBJECT-TYPE
111: SYNTAX TimeTicks
112: MAX-ACCESS read-only
113: STATUS current
114: DESCRIPTION
115: "This field provides the time the process created the
116: endpoint on this port.
117: "
118: ::= { udpEndpointInfoEntry 2 }
119:
120: --
121: -- The proposed new UDP Endpoint process table.
122: --
123:
124: udpEndpointProcTable OBJECT-TYPE
125: SYNTAX SEQUENCE OF UdpEndpointProcEntry
126: MAX-ACCESS not-accessible
127: STATUS current
128: DESCRIPTION
129: "A table containing information about this entity's UDP
130: endpoints on which a local application is currently
131: accepting or sending datagrams.
132: This table delivers functionality beyond the existing
133: udpEndpointTable by providing an entry for each process that
134: creates a shared endpoint on the same port for operating systems
135: that support this functionality. An entry in the
136: udpEndpointTable implies the existance of one or more entries in
137: this table for the connection, and vice-versa."
138:
139: ::= { udpProc 2 }
140:
141: udpEndpointProcEntry OBJECT-TYPE
141: warning -
warning: index of row `udpEndpointProcEntry' can exceed OID size limit by 400 subidentifier(s)
142: SYNTAX UdpEndpointProcEntry
143: MAX-ACCESS not-accessible
144: STATUS current
145:
146: DESCRIPTION
147: "Information about a particular current UDP endpoint.
148:
149: Implementers need to be aware that if the total number
150: of elements (octets or sub-identifiers) in
151: udpEndpointProcLocalAddress and udpEndpointProcRemoteAddress
152: exceeds 111, then OIDs of column instances in this table
153: will have more than 128 sub-identifiers and cannot be
154: accessed using SNMPv1, SNMPv2c, or SNMPv3."
155: INDEX { udpEndpointProcLocalAddressType,
156: udpEndpointProcLocalAddress,
157: udpEndpointProcLocalPort,
158: udpEndpointProcRemoteAddressType,
159: udpEndpointProcRemoteAddress,
160: udpEndpointProcRemotePort,
161: udpEndpointProcInstance,
162: udpEndpointProcPID
163: }
164: ::= { udpEndpointProcTable 1 }
165:
166: UdpEndpointProcEntry ::= SEQUENCE {
167: udpEndpointProcLocalAddressType InetAddressType,
168: udpEndpointProcLocalAddress InetAddress,
169: udpEndpointProcLocalPort InetPortNumber,
170: udpEndpointProcRemoteAddressType InetAddressType,
171: udpEndpointProcRemoteAddress InetAddress,
172: udpEndpointProcRemotePort InetPortNumber,
173: udpEndpointProcInstance Unsigned32,
174: udpEndpointProcPID Unsigned32
175: }
176:
177: udpEndpointProcLocalAddressType OBJECT-TYPE
178: SYNTAX InetAddressType
179: MAX-ACCESS not-accessible
180: STATUS current
181: DESCRIPTION
182: "The address type of udpEndpointProcLocalAddress. Only
183: IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
184: unknown(0) if datagrams for all local IP addresses are
185: accepted."
186:
187: ::= { udpEndpointProcEntry 1 }
188:
189: udpEndpointProcLocalAddress OBJECT-TYPE
190: SYNTAX InetAddress
191: MAX-ACCESS not-accessible
192: STATUS current
193: DESCRIPTION
194: "The local IP address for this UDP endpoint.
195:
196: The value of this object can be represented in three
197: possible ways, depending on the characteristics of the
198: listening application:
199:
200: 1. For an application that is willing to accept both
201: IPv4 and IPv6 datagrams, the value of this object
202: must be ''h (a zero-length octet-string), with
203: the value of the corresponding instance of the
204: udpEndpointLocalAddressType object being unknown(0).
205:
206: 2. For an application that is willing to accept only IPv4
207: or only IPv6 datagrams, the value of this object
208: must be '0.0.0.0' or '::', respectively, while the
209: corresponding instance of the
210: udpEndpointLocalAddressType object represents the
211: appropriate address type.
212:
213: 3. For an application that is listening for data
214: destined only to a specific IP address, the value
215: of this object is the specific IP address for which
216: this node is receiving packets, with the
217: corresponding instance of the
218: udpEndpointLocalAddressType object representing the
219: appropriate address type.
220:
221: As this object is used in the index for the
222: udpEndpointProcTable, implementors of this table should be
223: careful not to create entries that would result in OIDs
224: with more than 128 subidentifiers; else the information
225: cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3."
226:
227: ::= { udpEndpointProcEntry 2 }
228:
229: udpEndpointProcLocalPort OBJECT-TYPE
230: SYNTAX InetPortNumber
231: MAX-ACCESS not-accessible
232: STATUS current
233: DESCRIPTION
234: "The local port number for this UDP endpoint."
235:
236: ::= { udpEndpointProcEntry 3 }
237:
238: udpEndpointProcRemoteAddressType OBJECT-TYPE
239: SYNTAX InetAddressType
240: MAX-ACCESS not-accessible
241: STATUS current
242: DESCRIPTION
243: "The address type of udpEndpointProcRemoteAddress. Only
244: IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
245: unknown(0) if datagrams for all remote IP addresses are
246: accepted. Also, note that some combinations of
247: udpEndpointProcLocalAddressType and
248: udpEndpointProcRemoteAddressType are not supported. In
249: particular, if the value of this object is not
250: unknown(0), it is expected to always refer to the
251: same IP version as udpEndpointProcLocalAddressType."
252:
253: ::= { udpEndpointProcEntry 4 }
254:
255: udpEndpointProcRemoteAddress OBJECT-TYPE
256: SYNTAX InetAddress
257: MAX-ACCESS not-accessible
258: STATUS current
259: DESCRIPTION
260: "The remote IP address for this UDP endpoint. If
261: datagrams from any remote system are to be accepted,
262: this value is ''h (a zero-length octet-string).
263: Otherwise, it has the type described by
264: udpEndpointProcRemoteAddressType and is the address of the
265: remote system from which datagrams are to be accepted
266: (or to which all datagrams will be sent).
267:
268: As this object is used in the index for the
269: udpEndpointProcTable, implementors of this table should be
270: careful not to create entries that would result in OIDs
271: with more than 128 subidentifiers; else the information
272: cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3."
273:
274: ::= { udpEndpointProcEntry 5 }
275:
276: udpEndpointProcRemotePort OBJECT-TYPE
277: SYNTAX InetPortNumber
278: MAX-ACCESS not-accessible
279: STATUS current
280: DESCRIPTION
281: "The remote port number for this UDP endpoint. If
282: datagrams from any remote system are to be accepted,
283: this value is zero."
284:
285: ::= { udpEndpointProcEntry 6 }
286:
287: udpEndpointProcInstance OBJECT-TYPE
288: SYNTAX Unsigned32 (1..'ffffffff'h)
289: MAX-ACCESS not-accessible
290: STATUS current
291: DESCRIPTION
292: "The instance of this tuple. This object is used to
293: distinguish among multiple processes 'connected' to
294: the same UDP endpoint. For example, on a system
295: implementing the BSD sockets interface, this would be
296: used to support the SO_REUSEADDR and SO_REUSEPORT
297: socket options."
298:
299: ::= { udpEndpointProcEntry 7 }
300:
301: udpEndpointProcPID OBJECT-TYPE
302: SYNTAX Unsigned32
303: MAX-ACCESS read-only
304: STATUS current
305: DESCRIPTION
306: "The system's process ID for the process associated with
307: this endpoint.
308: This value corresponds to a row in
309: HOST-RESOURCES-MIB::hrSWRunIndex and SYSAPPL-MIB::
310: sysApplElmtRunIndex for operating systems that
311: support this functionality and the corresponding MIBs."
312:
313: ::= { udpEndpointProcEntry 8 }
314:
315: -- compliance statements
316: udpProcMIBConformance OBJECT IDENTIFIER ::= { udpProcMIB 1 }
317:
318: udpProcMIBCompliances OBJECT IDENTIFIER ::= { udpProcMIBConformance 1 }
319: udpProcMIBGroup OBJECT IDENTIFIER ::= { udpProcMIBConformance 2 }
320:
321: udpProcMIBCompliance MODULE-COMPLIANCE
322: STATUS current
323: DESCRIPTION
324: "The compliance statement for systems that implement the
325: UDP Process MIB."
326: MODULE -- this module
327: MANDATORY-GROUPS { udpEndpointInfoGroup }
328: GROUP udpEndpointProcessGroup
329: DESCRIPTION
330: "This group should be implemented for operating systems that
331: support multiple listening processes sharing a single
332: address/port. It is left as optional to accommodate
333: operating systems that do not provide sufficient information
334: to express this data."
335:
336: ::= { udpProcMIBCompliances 1 }
337:
338: -- units of conformance
339:
340: udpEndpointInfoGroup OBJECT-GROUP
341: OBJECTS { udpEndpointInfoCreatorPID,
342: udpEndpointInfoProcessCreateTime }
343: STATUS current
344: DESCRIPTION
345: ""
345: warning -
warning: zero-length description string
346: ::= { udpProcMIBGroups 1 }
346: severe -
unknown object identifier label `udpProcMIBGroups'
347:
348: udpEndpointProcessGroup OBJECT-GROUP
349: OBJECTS { udpEndpointProcPID }
350: STATUS current
351: DESCRIPTION
352: ""
352: warning -
warning: zero-length description string
353: ::= { udpProcMIBGroups 2 }
354:
355: END
356:
357: --
358: -- Copyright (C) The Internet Society (2006).
359: --
360: -- This document is subject to the rights, licenses and restrictions
361: -- contained in BCP 78, and except as set forth therein, the authors
362: -- retain all their rights.
363: --
364: -- This document and the information contained herein are provided on an
365: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
366: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
367: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
368: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
369: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
370: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
371: --
372: --
373: -- Intellectual Property
374: --
375: -- The IETF takes no position regarding the validity or scope of any
376: -- Intellectual Property Rights or other rights that might be claimed to
377: -- pertain to the implementation or use of the technology described in
378: -- this document or the extent to which any license under such rights
379: -- might or might not be available; nor does it represent that it has
380: -- made any independent effort to identify any such rights. Information
381: -- on the procedures with respect to rights in RFC documents can be
382: -- found in BCP 78 and BCP 79.
383: --
384: -- Copies of IPR disclosures made to the IETF Secretariat and any
385: -- assurances of licenses to be made available, or the result of an
386: -- attempt made to obtain a general license or permission for the use of
387: -- such proprietary rights by implementers or users of this
388: -- specification can be obtained from the IETF on-line IPR repository at
389: -- http://www.ietf.org/ipr.
390: --
391: -- The IETF invites any interested party to bring to its attention any
392: -- copyrights, patents or patent applications, or other proprietary
393: -- rights that may cover technology that may be required to implement
394: -- this standard. Please address the information to the IETF at
395: -- ietf-ipr@ietf.org.
396: --
397: --
398: -- Acknowledgment
399: --
400: -- Funding for the RFC Editor function is provided by the IETF
401: -- Administrative Support Activity (IASA).
402: