smilint output for ./TRANSPORT-ADDRESS-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| warning | 9 |
| Message Types |
|---|
| Type | Count |
|---|
| type-unref (warning) | 9 |
Messages:
TRANSPORT-ADDRESS-MIB
1: -- extracted from rfc3419.txt
2: -- at Mon Dec 23 06:11:32 2002
178:
179: TransportDomain ::= TEXTUAL-CONVENTION
179: warning -
warning: current type `TransportDomain' is not referenced in this module
180: STATUS current
181: DESCRIPTION
182: "A value that represents a transport domain.
183:
184: Some possible values, such as transportDomainUdpIpv4, are
185: defined in this module. Other possible values can be
186: defined in other MIB modules."
187: SYNTAX OBJECT IDENTIFIER
188:
189: --
190: -- The enumerated values of the textual convention below should
191: -- be identical to the last sub-identifier of the OID registered
192: -- for the same domain.
193: --
194:
195: TransportAddressType ::= TEXTUAL-CONVENTION
195: warning -
warning: current type `TransportAddressType' is not referenced in this module
196: STATUS current
197: DESCRIPTION
198: "A value that represents a transport domain. This is the
199: enumerated version of the transport domain registrations
200: in this MIB module. The enumerated values have the
201: following meaning:
202:
203: unknown(0) unknown transport address type
204: udpIpv4(1) transportDomainUdpIpv4
205: udpIpv6(2) transportDomainUdpIpv6
206: udpIpv4z(3) transportDomainUdpIpv4z
207: udpIpv6z(4) transportDomainUdpIpv6z
208: tcpIpv4(5) transportDomainTcpIpv4
209: tcpIpv6(6) transportDomainTcpIpv6
210: tcpIpv4z(7) transportDomainTcpIpv4z
211: tcpIpv6z(8) transportDomainTcpIpv6z
212: sctpIpv4(9) transportDomainSctpIpv4
213: sctpIpv6(10) transportDomainSctpIpv6
214: sctpIpv4z(11) transportDomainSctpIpv4z
215: sctpIpv6z(12) transportDomainSctpIpv6z
216: local(13) transportDomainLocal
217: udpDns(14) transportDomainUdpDns
218: tcpDns(15) transportDomainTcpDns
219: sctpDns(16) transportDomainSctpDns
220:
221: This textual convention can be used to represent transport
222: domains in situations where a syntax of TransportDomain is
223: unwieldy (for example, when used as an index).
224:
225: The usage of this textual convention implies that additional
226: transport domains can only be supported by updating this MIB
227: module. This extensibility restriction does not apply for the
228: TransportDomain textual convention which allows MIB authors
229: to define additional transport domains independently in
230: other MIB modules."
231: SYNTAX INTEGER {
232: unknown(0),
233: udpIpv4(1),
234: udpIpv6(2),
235: udpIpv4z(3),
236: udpIpv6z(4),
237: tcpIpv4(5),
238: tcpIpv6(6),
239: tcpIpv4z(7),
240: tcpIpv6z(8),
241: sctpIpv4(9),
242: sctpIpv6(10),
243: sctpIpv4z(11),
244: sctpIpv6z(12),
245: local(13),
246: udpDns(14),
247: tcpDns(15),
248: sctpDns(16)
249: }
250:
251: TransportAddress ::= TEXTUAL-CONVENTION
251: warning -
warning: current type `TransportAddress' is not referenced in this module
252: STATUS current
253: DESCRIPTION
254: "Denotes a generic transport address.
255:
256: A TransportAddress value is always interpreted within the
257: context of a TransportAddressType or TransportDomain value.
258: Every usage of the TransportAddress textual convention MUST
259: specify the TransportAddressType or TransportDomain object
260: which provides the context. Furthermore, MIB authors SHOULD
261: define a separate TransportAddressType or TransportDomain
262: object for each TransportAddress object. It is suggested that
263: the TransportAddressType or TransportDomain is logically
264: registered before the object(s) which use the
265: TransportAddress textual convention if they appear in the
266: same logical row.
267:
268: The value of a TransportAddress object must always be
269: consistent with the value of the associated
270: TransportAddressType or TransportDomain object. Attempts
271: to set a TransportAddress object to a value which is
272: inconsistent with the associated TransportAddressType or
273: TransportDomain must fail with an inconsistentValue error.
274:
275: When this textual convention is used as a syntax of an
276: index object, there may be issues with the limit of 128
277: sub-identifiers specified in SMIv2, STD 58. In this case,
278: the OBJECT-TYPE declaration MUST include a 'SIZE' clause
279: to limit the number of potential instance sub-identifiers."
280: SYNTAX OCTET STRING (SIZE (0..255))
281:
282: TransportAddressIPv4 ::= TEXTUAL-CONVENTION
282: warning -
warning: current type `TransportAddressIPv4' is not referenced in this module
283: DISPLAY-HINT "1d.1d.1d.1d:2d"
284: STATUS current
285: DESCRIPTION
286: "Represents a transport address consisting of an IPv4
287: address and a port number (as used for example by UDP,
288: TCP and SCTP):
289:
290: octets contents encoding
291: 1-4 IPv4 address network-byte order
292: 5-6 port number network-byte order
293:
294: This textual convention SHOULD NOT be used directly in object
295: definitions since it restricts addresses to a specific format.
296: However, if it is used, it MAY be used either on its own or
297: in conjunction with TransportAddressType or TransportDomain
298: as a pair."
299: SYNTAX OCTET STRING (SIZE (6))
300:
301: TransportAddressIPv6 ::= TEXTUAL-CONVENTION
301: warning -
warning: current type `TransportAddressIPv6' is not referenced in this module
302: DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x]0a:2d"
303: STATUS current
304: DESCRIPTION
305: "Represents a transport address consisting of an IPv6
306: address and a port number (as used for example by UDP,
307: TCP and SCTP):
308:
309: octets contents encoding
310: 1-16 IPv6 address network-byte order
311: 17-18 port number network-byte order
312:
313: This textual convention SHOULD NOT be used directly in object
314: definitions since it restricts addresses to a specific format.
315: However, if it is used, it MAY be used either on its own or
316: in conjunction with TransportAddressType or TransportDomain
317: as a pair."
318: SYNTAX OCTET STRING (SIZE (18))
319:
320: TransportAddressIPv4z ::= TEXTUAL-CONVENTION
320: warning -
warning: current type `TransportAddressIPv4z' is not referenced in this module
321: DISPLAY-HINT "1d.1d.1d.1d%4d:2d"
322: STATUS current
323: DESCRIPTION
324: "Represents a transport address consisting of an IPv4
325: address, a zone index and a port number (as used for
326: example by UDP, TCP and SCTP):
327:
328: octets contents encoding
329: 1-4 IPv4 address network-byte order
330: 5-8 zone index network-byte order
331: 9-10 port number network-byte order
332:
333: This textual convention SHOULD NOT be used directly in object
334: definitions since it restricts addresses to a specific format.
335: However, if it is used, it MAY be used either on its own or
336: in conjunction with TransportAddressType or TransportDomain
337: as a pair."
338: SYNTAX OCTET STRING (SIZE (10))
339:
340: TransportAddressIPv6z ::= TEXTUAL-CONVENTION
340: warning -
warning: current type `TransportAddressIPv6z' is not referenced in this module
341: DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x%4d]0a:2d"
342: STATUS current
343: DESCRIPTION
344: "Represents a transport address consisting of an IPv6
345: address, a zone index and a port number (as used for
346: example by UDP, TCP and SCTP):
347:
348: octets contents encoding
349: 1-16 IPv6 address network-byte order
350: 17-20 zone index network-byte order
351: 21-22 port number network-byte order
352:
353: This textual convention SHOULD NOT be used directly in object
354: definitions since it restricts addresses to a specific format.
355: However, if it is used, it MAY be used either on its own or
356: in conjunction with TransportAddressType or TransportDomain
357: as a pair."
358: SYNTAX OCTET STRING (SIZE (22))
359:
360: TransportAddressLocal ::= TEXTUAL-CONVENTION
360: warning -
warning: current type `TransportAddressLocal' is not referenced in this module
361: DISPLAY-HINT "1a"
362: STATUS current
363: DESCRIPTION
364: "Represents a POSIX Local IPC transport address:
365:
366: octets contents encoding
367: all POSIX Local IPC address string
368:
369: The Posix Local IPC transport domain subsumes UNIX domain
370: sockets.
371:
372: This textual convention SHOULD NOT be used directly in object
373: definitions since it restricts addresses to a specific format.
374: However, if it is used, it MAY be used either on its own or
375: in conjunction with TransportAddressType or TransportDomain
376: as a pair.
377:
378: When this textual convention is used as a syntax of an
379: index object, there may be issues with the limit of 128
380: sub-identifiers specified in SMIv2, STD 58. In this case,
381: the OBJECT-TYPE declaration MUST include a 'SIZE' clause
382: to limit the number of potential instance sub-identifiers."
383: REFERENCE
384: "Protocol Independent Interfaces (IEEE POSIX 1003.1g)"
385: SYNTAX OCTET STRING (SIZE (1..255))
386:
387: TransportAddressDns ::= TEXTUAL-CONVENTION
387: warning -
warning: current type `TransportAddressDns' is not referenced in this module
388: DISPLAY-HINT "1a"
389: STATUS current
390: DESCRIPTION
391: "Represents a DNS domain name followed by a colon ':'
392: (ASCII character 0x3A) and a port number in ASCII.
393: The name SHOULD be fully qualified whenever possible.
394:
395: Values of this textual convention are not directly useable as
396: transport-layer addressing information, and require runtime
397: resolution. As such, applications that write them must be
398: prepared for handling errors if such values are not
399: supported, or cannot be resolved (if resolution occurs at the
400: time of the management operation).
401:
402: The DESCRIPTION clause of TransportAddress objects that may
403: have TransportAddressDns values must fully describe how (and
404: when) such names are to be resolved to IP addresses and vice
405: versa.
406:
407: This textual convention SHOULD NOT be used directly in object
408: definitions since it restricts addresses to a specific format.
409: However, if it is used, it MAY be used either on its own or
410: in conjunction with TransportAddressType or TransportDomain
411: as a pair.
412:
413: When this textual convention is used as a syntax of an
414: index object, there may be issues with the limit of 128
415: sub-identifiers specified in SMIv2, STD 58. In this case,
416: the OBJECT-TYPE declaration MUST include a 'SIZE' clause
417: to limit the number of potential instance sub-identifiers."
418: SYNTAX OCTET STRING (SIZE (1..255))
419:
420: END
421:
422: --
423: -- Copyright (C) The Internet Society (2002). All Rights Reserved.
424: --
425: -- This document and translations of it may be copied and furnished to
426: -- others, and derivative works that comment on or otherwise explain it
427: -- or assist in its implementation may be prepared, copied, published
428: -- and distributed, in whole or in part, without restriction of any
429: -- kind, provided that the above copyright notice and this paragraph are
430: -- included on all such copies and derivative works. However, this
431: -- document itself may not be modified in any way, such as by removing
432: -- the copyright notice or references to the Internet Society or other
433: -- Internet organizations, except as needed for the purpose of
434: -- developing Internet standards in which case the procedures for
435: -- copyrights defined in the Internet Standards process must be
436: -- followed, or as required to translate it into languages other than
437: -- English.
438: --
439: -- The limited permissions granted above are perpetual and will not be
440: -- revoked by the Internet Society or its successors or assigns.
441: --
442: -- This document and the information contained herein is provided on an
443: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
444: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
445: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
446: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
447: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
448: --
449: