1
TRANSPORT-ADDRESS-MIB DEFINITIONS ::= BEGIN
4
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI
5
TEXTUAL-CONVENTION FROM SNMPv2-TC;
7
transportAddressMIB MODULE-IDENTITY
8
LAST-UPDATED "200211010000Z"
10
"IETF Operations and Management Area"
12
"Juergen Schoenwaelder (Editor)
15
38106 Braunschweig, Germany
16
Phone: +49 531 391-3289
17
EMail: schoenw@ibr.cs.tu-bs.de
19
Send comments to <mibs@ops.ietf.org>."
21
"This MIB module provides commonly used transport
24
Copyright (C) The Internet Society (2002). This version of
25
this MIB module is part of RFC 3419; see the RFC itself for
30
REVISION "200211010000Z"
32
"Initial version, published as RFC 3419."
36
transportDomains OBJECT IDENTIFIER ::= { transportAddressMIB 1 }
38
transportDomainUdpIpv4 OBJECT-IDENTITY
41
"The UDP over IPv4 transport domain. The corresponding
42
transport address is of type TransportAddressIPv4 for
43
global IPv4 addresses."
44
::= { transportDomains 1 }
46
transportDomainUdpIpv6 OBJECT-IDENTITY
49
"The UDP over IPv6 transport domain. The corresponding
50
transport address is of type TransportAddressIPv6 for
51
global IPv6 addresses."
52
::= { transportDomains 2 }
54
transportDomainUdpIpv4z OBJECT-IDENTITY
57
"The UDP over IPv4 transport domain. The corresponding
58
transport address is of type TransportAddressIPv4z for
59
scoped IPv4 addresses with a zone index."
60
::= { transportDomains 3 }
62
transportDomainUdpIpv6z OBJECT-IDENTITY
65
"The UDP over IPv6 transport domain. The corresponding
66
transport address is of type TransportAddressIPv6z for
67
scoped IPv6 addresses with a zone index."
68
::= { transportDomains 4 }
70
transportDomainTcpIpv4 OBJECT-IDENTITY
73
"The TCP over IPv4 transport domain. The corresponding
74
transport address is of type TransportAddressIPv4 for
75
global IPv4 addresses."
76
::= { transportDomains 5 }
78
transportDomainTcpIpv6 OBJECT-IDENTITY
81
"The TCP over IPv6 transport domain. The corresponding
82
transport address is of type TransportAddressIPv6 for
83
global IPv6 addresses."
84
::= { transportDomains 6 }
86
transportDomainTcpIpv4z OBJECT-IDENTITY
89
"The TCP over IPv4 transport domain. The corresponding
90
transport address is of type TransportAddressIPv4z for
91
scoped IPv4 addresses with a zone index."
92
::= { transportDomains 7 }
94
transportDomainTcpIpv6z OBJECT-IDENTITY
97
"The TCP over IPv6 transport domain. The corresponding
98
transport address is of type TransportAddressIPv6z for
99
scoped IPv6 addresses with a zone index."
100
::= { transportDomains 8 }
102
transportDomainSctpIpv4 OBJECT-IDENTITY
105
"The SCTP over IPv4 transport domain. The corresponding
106
transport address is of type TransportAddressIPv4 for
107
global IPv4 addresses. This transport domain usually
108
represents the primary address on multihomed SCTP
110
::= { transportDomains 9 }
112
transportDomainSctpIpv6 OBJECT-IDENTITY
115
"The SCTP over IPv6 transport domain. The corresponding
116
transport address is of type TransportAddressIPv6 for
117
global IPv6 addresses. This transport domain usually
118
represents the primary address on multihomed SCTP
120
::= { transportDomains 10 }
122
transportDomainSctpIpv4z OBJECT-IDENTITY
125
"The SCTP over IPv4 transport domain. The corresponding
126
transport address is of type TransportAddressIPv4z for
127
scoped IPv4 addresses with a zone index. This transport
128
domain usually represents the primary address on
129
multihomed SCTP endpoints."
130
::= { transportDomains 11 }
132
transportDomainSctpIpv6z OBJECT-IDENTITY
135
"The SCTP over IPv6 transport domain. The corresponding
136
transport address is of type TransportAddressIPv6z for
137
scoped IPv6 addresses with a zone index. This transport
138
domain usually represents the primary address on
139
multihomed SCTP endpoints."
140
::= { transportDomains 12 }
142
transportDomainLocal OBJECT-IDENTITY
145
"The Posix Local IPC transport domain. The corresponding
146
transport address is of type TransportAddressLocal.
148
The Posix Local IPC transport domain incorporates the
149
well-known UNIX domain sockets."
150
::= { transportDomains 13 }
152
transportDomainUdpDns OBJECT-IDENTITY
155
"The UDP transport domain using fully qualified domain
156
names. The corresponding transport address is of type
157
TransportAddressDns."
158
::= { transportDomains 14 }
160
transportDomainTcpDns OBJECT-IDENTITY
163
"The TCP transport domain using fully qualified domain
164
names. The corresponding transport address is of type
165
TransportAddressDns."
166
::= { transportDomains 15 }
168
transportDomainSctpDns OBJECT-IDENTITY
171
"The SCTP transport domain using fully qualified domain
172
names. The corresponding transport address is of type
173
TransportAddressDns."
174
::= { transportDomains 16 }
176
TransportDomain ::= TEXTUAL-CONVENTION
179
"A value that represents a transport domain.
181
Some possible values, such as transportDomainUdpIpv4, are
182
defined in this module. Other possible values can be
183
defined in other MIB modules."
184
SYNTAX OBJECT IDENTIFIER
189
TransportAddressType ::= TEXTUAL-CONVENTION
192
"A value that represents a transport domain. This is the
193
enumerated version of the transport domain registrations
194
in this MIB module. The enumerated values have the
197
unknown(0) unknown transport address type
198
udpIpv4(1) transportDomainUdpIpv4
199
udpIpv6(2) transportDomainUdpIpv6
200
udpIpv4z(3) transportDomainUdpIpv4z
201
udpIpv6z(4) transportDomainUdpIpv6z
202
tcpIpv4(5) transportDomainTcpIpv4
203
tcpIpv6(6) transportDomainTcpIpv6
204
tcpIpv4z(7) transportDomainTcpIpv4z
205
tcpIpv6z(8) transportDomainTcpIpv6z
206
sctpIpv4(9) transportDomainSctpIpv4
207
sctpIpv6(10) transportDomainSctpIpv6
208
sctpIpv4z(11) transportDomainSctpIpv4z
209
sctpIpv6z(12) transportDomainSctpIpv6z
210
local(13) transportDomainLocal
211
udpDns(14) transportDomainUdpDns
212
tcpDns(15) transportDomainTcpDns
213
sctpDns(16) transportDomainSctpDns
215
This textual convention can be used to represent transport
216
domains in situations where a syntax of TransportDomain is
217
unwieldy (for example, when used as an index).
219
The usage of this textual convention implies that additional
220
transport domains can only be supported by updating this MIB
221
module. This extensibility restriction does not apply for the
222
TransportDomain textual convention which allows MIB authors
223
to define additional transport domains independently in
245
TransportAddress ::= TEXTUAL-CONVENTION
248
"Denotes a generic transport address.
250
A TransportAddress value is always interpreted within the
251
context of a TransportAddressType or TransportDomain value.
252
Every usage of the TransportAddress textual convention MUST
253
specify the TransportAddressType or TransportDomain object
254
which provides the context. Furthermore, MIB authors SHOULD
255
define a separate TransportAddressType or TransportDomain
256
object for each TransportAddress object. It is suggested that
257
the TransportAddressType or TransportDomain is logically
258
registered before the object(s) which use the
259
TransportAddress textual convention if they appear in the
262
The value of a TransportAddress object must always be
263
consistent with the value of the associated
264
TransportAddressType or TransportDomain object. Attempts
265
to set a TransportAddress object to a value which is
266
inconsistent with the associated TransportAddressType or
267
TransportDomain must fail with an inconsistentValue error.
269
When this textual convention is used as a syntax of an
270
index object, there may be issues with the limit of 128
271
sub-identifiers specified in SMIv2, STD 58. In this case,
272
the OBJECT-TYPE declaration MUST include a 'SIZE' clause
273
to limit the number of potential instance sub-identifiers."
274
SYNTAX OCTET STRING (SIZE (0..255))
276
TransportAddressIPv4 ::= TEXTUAL-CONVENTION
277
DISPLAY-HINT "1d.1d.1d.1d:2d"
280
"Represents a transport address consisting of an IPv4
281
address and a port number (as used for example by UDP,
284
octets contents encoding
285
1-4 IPv4 address network-byte order
286
5-6 port number network-byte order
288
This textual convention SHOULD NOT be used directly in object
289
definitions since it restricts addresses to a specific format.
290
However, if it is used, it MAY be used either on its own or
291
in conjunction with TransportAddressType or TransportDomain
293
SYNTAX OCTET STRING (SIZE (6))
295
TransportAddressIPv6 ::= TEXTUAL-CONVENTION
296
DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x]0a:2d"
299
"Represents a transport address consisting of an IPv6
300
address and a port number (as used for example by UDP,
303
octets contents encoding
304
1-16 IPv6 address network-byte order
305
17-18 port number network-byte order
307
This textual convention SHOULD NOT be used directly in object
308
definitions since it restricts addresses to a specific format.
309
However, if it is used, it MAY be used either on its own or
310
in conjunction with TransportAddressType or TransportDomain
312
SYNTAX OCTET STRING (SIZE (18))
314
TransportAddressIPv4z ::= TEXTUAL-CONVENTION
315
DISPLAY-HINT "1d.1d.1d.1d%4d:2d"
318
"Represents a transport address consisting of an IPv4
319
address, a zone index and a port number (as used for
320
example by UDP, TCP and SCTP):
322
octets contents encoding
323
1-4 IPv4 address network-byte order
324
5-8 zone index network-byte order
325
9-10 port number network-byte order
327
This textual convention SHOULD NOT be used directly in object
328
definitions since it restricts addresses to a specific format.
329
However, if it is used, it MAY be used either on its own or
330
in conjunction with TransportAddressType or TransportDomain
332
SYNTAX OCTET STRING (SIZE (10))
334
TransportAddressIPv6z ::= TEXTUAL-CONVENTION
335
DISPLAY-HINT "0a[2x:2x:2x:2x:2x:2x:2x:2x%4d]0a:2d"
338
"Represents a transport address consisting of an IPv6
339
address, a zone index and a port number (as used for
340
example by UDP, TCP and SCTP):
342
octets contents encoding
343
1-16 IPv6 address network-byte order
344
17-20 zone index network-byte order
345
21-22 port number network-byte order
347
This textual convention SHOULD NOT be used directly in object
348
definitions since it restricts addresses to a specific format.
349
However, if it is used, it MAY be used either on its own or
350
in conjunction with TransportAddressType or TransportDomain
352
SYNTAX OCTET STRING (SIZE (22))
354
TransportAddressLocal ::= TEXTUAL-CONVENTION
358
"Represents a POSIX Local IPC transport address:
360
octets contents encoding
361
all POSIX Local IPC address string
363
The Posix Local IPC transport domain subsumes UNIX domain
366
This textual convention SHOULD NOT be used directly in object
367
definitions since it restricts addresses to a specific format.
368
However, if it is used, it MAY be used either on its own or
369
in conjunction with TransportAddressType or TransportDomain
372
When this textual convention is used as a syntax of an
373
index object, there may be issues with the limit of 128
374
sub-identifiers specified in SMIv2, STD 58. In this case,
375
the OBJECT-TYPE declaration MUST include a 'SIZE' clause
376
to limit the number of potential instance sub-identifiers."
378
"Protocol Independent Interfaces (IEEE POSIX 1003.1g)"
379
SYNTAX OCTET STRING (SIZE (1..255))
381
TransportAddressDns ::= TEXTUAL-CONVENTION
385
"Represents a DNS domain name followed by a colon ':'
386
(ASCII character 0x3A) and a port number in ASCII.
387
The name SHOULD be fully qualified whenever possible.
389
Values of this textual convention are not directly useable as
390
transport-layer addressing information, and require runtime
391
resolution. As such, applications that write them must be
392
prepared for handling errors if such values are not
393
supported, or cannot be resolved (if resolution occurs at the
394
time of the management operation).
396
The DESCRIPTION clause of TransportAddress objects that may
397
have TransportAddressDns values must fully describe how (and
398
when) such names are to be resolved to IP addresses and vice
401
This textual convention SHOULD NOT be used directly in object
402
definitions since it restricts addresses to a specific format.
403
However, if it is used, it MAY be used either on its own or
404
in conjunction with TransportAddressType or TransportDomain
407
When this textual convention is used as a syntax of an
408
index object, there may be issues with the limit of 128
409
sub-identifiers specified in SMIv2, STD 58. In this case,
410
the OBJECT-TYPE declaration MUST include a 'SIZE' clause
411
to limit the number of potential instance sub-identifiers."
412
SYNTAX OCTET STRING (SIZE (1..255))
added
removed
mibs/TRANSPORT-ADDRESS-MIB.txt
