Debian Codegraph @

rfc1283.html

raw
1 <pre>Network Working Group M. Rose
2 Request for Comments: 1283 Dover Beach Consulting, Inc.
3 Obsoletes: RFC <a href="./rfc1161">1161</a> December 1991
4
5
6 <span class="h1">SNMP over OSI</span>
7
8 Status of this Memo
9
10 This memo defines an Experimental Protocol for the Internet
11 community. Discussion and suggestions for improvement are requested.
12 Please refer to the current edition of the "IAB Official Protocol
13 Standards" for the standardization state and status of this protocol.
14 Distribution of this memo is unlimited.
15
16 Table of Contents
17
18 <a href="#section-1">1</a>. Background ............................................ <a href="#page-1">1</a>
19 <a href="#section-1.1">1.1</a> A Digression on User Interfaces ...................... <a href="#page-2">2</a>
20 <a href="#section-1.1.1">1.1.1</a> Addressing Conventions for UDP-based service ....... <a href="#page-3">3</a>
21 <a href="#section-1.2">1.2</a> A Digression of Layering ............................. <a href="#page-3">3</a>
22 <a href="#section-2">2</a>. Mapping onto CLTS ..................................... <a href="#page-3">3</a>
23 <a href="#section-2.1">2.1</a> Addressing Conventions ............................... <a href="#page-4">4</a>
24 <a href="#section-2.1.1">2.1.1</a> Conventions for CLNP-based service ................. <a href="#page-4">4</a>
25 <a href="#section-3">3</a>. Mapping onto COTS ..................................... <a href="#page-4">4</a>
26 <a href="#section-3.1">3.1</a> Addressing Conventions ............................... <a href="#page-5">5</a>
27 <a href="#section-3.1.1">3.1.1</a> Conventions for TP4/CLNP-based service ............. <a href="#page-5">5</a>
28 <a href="#section-3.1.2">3.1.2</a> Conventions for TP0/X.25-based service ............. <a href="#page-6">6</a>
29 <a href="#section-4">4</a>. Trap PDU .............................................. <a href="#page-6">6</a>
30 <a href="#section-5">5</a>. Acknowledgements ...................................... <a href="#page-7">7</a>
31 <a href="#section-6">6</a>. References ............................................ <a href="#page-7">7</a>
32 <a href="#section-7">7</a>. Security Considerations................................ <a href="#page-8">8</a>
33 <a href="#section-8">8</a>. Author's Address....................................... <a href="#page-8">8</a>
34
35 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Background</span>
36
37 The Simple Network Management Protocol (SNMP) as defined in [<a href="#ref-1" title="&quot;A Simple Network Management Protocol (SNMP)&quot;">1</a>] is
38 now used as an integral part of the network management framework for
39 TCP/IP-based internets. Together, with its companions standards,
40 which define the Structure of Management Information (SMI) [<a href="#ref-2" title="&quot;Structure and Identification of Management Information for TCP/IP-based internets&quot;">2</a>], and
41 the Management Information Base (MIB) [<a href="#ref-3" title="&quot;Management Information Base for Network Management of TCP/IP-based internets&quot;">3</a>], the SNMP has received
42 widespread deployment in many operational networks running the
43 Internet suite of protocols.
44
45 It should not be surprising that many of these sites might acquire
46 OSI capabilities and may wish to leverage their investment in SNMP
47 technology towards managing those OSI components. This memo
48 addresses these concerns by defining a framework for running the SNMP
49
50
51
52 <span class="grey">Rose [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1283">RFC 1283</a> SNMP over OSI December 1991</span>
55
56
57 in an environment which supports the OSI transport services.
58
59 In OSI, there are two such services, a connection-oriented transport
60 services (COTS) as defined in [<a href="#ref-4" title="&quot;Transport Service Definition&quot;">4</a>], and a connectionless-mode
61 transport service (CLTS) as defined in [<a href="#ref-5" title="&quot;Transport Service Definition - Addendum 1: Connectionless-mode Transmission&quot;">5</a>]. Although the primary
62 deployment of the SNMP is over the connectionless-mode transport
63 service provided by the Internet suite of protocols (i.e., the User
64 Datagram Protocol or UDP [<a href="#ref-6" title="&quot;User Datagram Protocol&quot;">6</a>]), a design goal of the SNMP was to be
65 able to use either a CO-mode or CL-mode transport service. As such,
66 this memo describes mappings from the SNMP onto both the COTS and the
67 CLTS.
68
69 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. A Digression on User Interfaces</span>
70
71 It is likely that user-interfaces to the SNMP will be developed that
72 support multiple transport backings. In an environment such as this,
73 it is often important to maintain a consistent addressing scheme for
74 users. Since the mappings described in this memo are onto the OSI
75 transport services, use of the textual scheme described in [<a href="#ref-7" title="&quot;A String Encoding of Presentation Address&quot;">7</a>], which
76 describes a string encoding for OSI presentation addresses, is
77 recommended. The syntax defined in [<a href="#ref-7" title="&quot;A String Encoding of Presentation Address&quot;">7</a>] is equally applicable towards
78 transport addresses.
79
80 In this context, a string encoding usually appears as:
81
82 [&lt;t-selector&gt;/]&lt;n-provider&gt;&lt;n-address&gt;[+&lt;n-info&gt;]
83
84 where:
85
86 (1) &lt;t-selector&gt; is usually either an ASCII string enclosed
87 in double-quotes (e.g., "snmp"), or a hexadecimal number
88 (e.g., '736e6d70'H);
89
90 (2) &lt;n-provider&gt; is one of several well-known providers of a
91 connectivity-service, one of: "Internet=" for a
92 transport-service from the Internet suite of protocols,
93 "Int-X25=" for the 1980 CCITT X.25 recommendation, or
94 "NS+" for the OSI network service;
95
96 (3) &lt;n-address&gt; is an address in a format specific to the
97 &lt;n-provider&gt;; and,
98
99 (4) &lt;n-info&gt; is any additional addressing information in a
100 format specific to the &lt;n-provider&gt;.
101
102 It is not the purpose of this memo to provide an exhaustive
103 description of string encodings such as these. Readers should
104 consult [<a href="#ref-7" title="&quot;A String Encoding of Presentation Address&quot;">7</a>] for detailed information on the syntax. However, this
105
106
107
108 <span class="grey">Rose [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1283">RFC 1283</a> SNMP over OSI December 1991</span>
111
112
113 memo recommends that, as an implementation option, user-interfaces to
114 the SNMP that support multiple transport backings SHOULD implement
115 this syntax.
116
117 <span class="h4"><a class="selflink" id="section-1.1.1" href="#section-1.1.1">1.1.1</a>. Addressing Conventions for UDP-based service</span>
118
119 In the context of a UDP-based transport backing, addresses would be
120 encoded as:
121
122 Internet=&lt;host&gt;+161+2
123
124 which says that the transport service is from the Internet suite of
125 protocols, residing at &lt;host&gt;, on port 161, using the UDP (2). The
126 token &lt;host&gt; may be either a domain name or a dotted-quad, e.g., both
127
128 Internet=cheetah.nyser.net+161+2
129
130 and
131
132 Internet=192.52.180.1+161+2
133
134 are both valid. Note however that if domain name "cheetah.nyser.net"
135 maps to multiple IP addresses, then this implies multiple transport
136 addresses. The number of addresses examined by the application (and
137 the order of examination) are specific to each application.
138
139 Of course, this memo does not require that other interface schemes
140 not be used. Clearly, use of a simple hostname is preferable to the
141 string encoding above. However, for the sake of uniformity, for
142 those user-interfaces to the SNMP that support multiple transport
143 backings, it is strongly RECOMMENDED that the syntax in [<a href="#ref-7" title="&quot;A String Encoding of Presentation Address&quot;">7</a>] be
144 adopted and even the mapping for UDP-based transport be valid.
145
146 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. A Digression of Layering</span>
147
148 Although other frameworks view network management as an application,
149 extensive experience with the SNMP suggests otherwise. In essense,
150 network management is a function unlike any other user of a transport
151 service. The citation [<a href="#ref-8" title="&quot;Network Management and the Design of SNMP&quot;">8</a>] develops this argument in full. As such,
152 it is inappropriate to map the SNMP onto the OSI application layer.
153 Rather, it is mapped to OSI transport services, in order to build on
154 the proven success of the Internet network management framework.
155
156 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Mapping onto CLTS</span>
157
158 Mapping the SNMP onto the CLTS is straight-forward. The elements of
159 procedure are identical to that of using the UDP, with one exception:
160 a slightly different Trap PDU is used. Further, note that the CLTS
161
162
163
164 <span class="grey">Rose [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1283">RFC 1283</a> SNMP over OSI December 1991</span>
167
168
169 and the service offered by the UDP both transmit packets of
170 information which contain full addressing information. Thus, mapping
171 the SNMP onto the CLTS, a "transport address" in the context of [<a href="#ref-1" title="&quot;A Simple Network Management Protocol (SNMP)&quot;">1</a>],
172 is simply a transport-selector and network address.
173
174 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Addressing Conventions</span>
175
176 Unlike the Internet suite of protocols, OSI does not use well-known
177 ports. Rather demultiplexing occurs on the basis of "selectors",
178 which are opaque strings of octets, which have meaning only at the
179 destination. In order to foster interoperable implementations of the
180 SNMP over the CLTS, it is necessary define a selector for this
181 purpose.
182
183 <span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. Conventions for CLNP-based service</span>
184
185 When the CLTS is used to provide the transport backing for the SNMP,
186 demultiplexing will occur on the basis of transport selector. The
187 transport selector used shall be the four ASCII characters
188
189 snmp
190
191 Thus, using the string encoding of [<a href="#ref-7" title="&quot;A String Encoding of Presentation Address&quot;">7</a>], such addresses may be
192 textual, described as:
193
194 "snmp"/NS+&lt;nsap&gt;
195
196 where:
197
198 (1) &lt;nsap&gt; is a hex string defining the nsap, e.g.,
199
200 "snmp"/NS+4900590800200038bafe00
201
202 Similarly, SNMP traps are, by convention, sent to a manager listening
203 on the transport selector
204
205 snmp-trap
206
207 which consists of nine ASCII characters.
208
209 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Mapping onto COTS</span>
210
211 Mapping the SNMP onto the COTS is more difficult as the SNMP does not
212 specifically require an existing connection. Thus, the mapping
213 consists of establishing a transport connection, sending one or more
214 SNMP messages on that connection, and then releasing the transport
215 connection. Further, a slightly different Trap PDU is used.
216
217
218
219
220 <span class="grey">Rose [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1283">RFC 1283</a> SNMP over OSI December 1991</span>
223
224
225 Consistent with the SNMP model, the initiator of a connection should
226 not require that responses to a request be returned on that
227 connection. However, if a responder to a connection sends SNMP
228 messages on a connection, then these MUST be in response to requests
229 received on that connection.
230
231 Ideally, the transport connection SHOULD be released by the
232 initiator, however, note that the responder may release the
233 connection due to resource limitations. Further note, that the
234 amount of time a connection remains established is implementation-
235 specific. Implementors should take care to choose an appropriate
236 dynamic algorithm.
237
238 Also consistent with the SNMP model, the initiator should not
239 associate any reliability characteristics with the use of a
240 connection. Issues such as retransmission of SNMP messages, etc.,
241 always remain with the SNMP application, not with the transport
242 service.
243
244 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Addressing Conventions</span>
245
246 Unlike the Internet suite of protocols, OSI does not use well-known
247 ports. Rather demultiplexing occurs on the basis of "selectors",
248 which are opaque strings of octets, which have meaning only at the
249 destination. In order to foster interoperable implementations of the
250 SNMP over the COTS, it is necessary define a selector for this
251 purpose. However, to be consistent with the various connectivity-
252 services, different conventions, based on the actual underlying
253 service, will be used.
254
255 <span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Conventions for TP4/CLNP-based service</span>
256
257 When a COTS based on the TP4/CLNP is used to provide the transport
258 backing for the SNMP, demultiplexing will occur on the basis of
259 transport selector. The transport selector used shall be the four
260 ASCII characters
261
262 snmp
263
264 Thus, using the string encoding of [<a href="#ref-7" title="&quot;A String Encoding of Presentation Address&quot;">7</a>], such addresses may be
265 textual, described as:
266
267 "snmp"/NS+&lt;nsap&gt;
268 where:
269
270 (1) &lt;nsap&gt; is a hex string defining the nsap, e.g.,
271
272 "snmp"/NS+4900590800200038bafe00
273
274
275
276 <span class="grey">Rose [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1283">RFC 1283</a> SNMP over OSI December 1991</span>
279
280
281 Similarly, SNMP traps are, by convention, sent to a manager listening
282 on the transport selector
283
284 snmp-trap
285
286 which consists of nine ASCII characters.
287
288 <span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Conventions for TP0/X.25-based service</span>
289
290 When a COTS based on the TP0/X.25 is used to provide the transport
291 backing for the SNMP, demultiplexing will occur on the basis of X.25
292 protocol-ID. The protocol-ID used shall be the four octets
293
294 03018200
295
296 This is the X.25 protocol-ID assigned for local management purposes.
297 Thus, using the string encoding of [<a href="#ref-7" title="&quot;A String Encoding of Presentation Address&quot;">7</a>], such addresses may be textual
298 described as:
299
300 Int-X25=&lt;dte&gt;+PID+03018200
301
302 where:
303
304 (1) &lt;dte&gt; is the X.121 DTE, e.g.,
305
306 Int-X25=23421920030013+PID+03018200
307
308 Similarly, SNMP traps are, by convention, sent to a manager listening
309 on the protocol-ID
310
311 03019000
312
313 This is an X.25 protocol-ID assigned for local purposes.
314
315 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Trap PDU</span>
316
317 The Trap-PDU defined in [<a href="#ref-1" title="&quot;A Simple Network Management Protocol (SNMP)&quot;">1</a>] is designed to represent traps generated
318 on IP networks. As such, a slightly different PDU must be used when
319 representing traps generated on OSI networks.
320
321 <a href="./rfc1283">RFC1283</a> DEFINTIONS ::= BEGIN
322
323 IMPORTS
324 TimeTicks
325 FROM <a href="./rfc1155">RFC1155</a>-SMI -- [<a href="#ref-2" title="&quot;Structure and Identification of Management Information for TCP/IP-based internets&quot;">2</a>] --
326 VarBindList
327 FROM <a href="./rfc1157">RFC1157</a>-SNMP -- [<a href="#ref-1" title="&quot;A Simple Network Management Protocol (SNMP)&quot;">1</a>] --
328 ClnpAddress
329
330
331
332 <span class="grey">Rose [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1283">RFC 1283</a> SNMP over OSI December 1991</span>
335
336
337 FROM CLNS-MIB -- [<a href="#ref-9" title="&quot;CLNS MIB for use with CLNP and ES-IS&quot;">9</a>] --;
338
339 Trap-PDU ::=
340 [<a href="#ref-4" title="&quot;Transport Service Definition&quot;">4</a>]
341 IMPLICT SEQUENCE {
342 enterprise -- type of object generating
343 OBJECT IDENTIFIER, -- trap, see sysObjectID
344
345 agent-addr -- address of object generating
346 ClnpAddress, -- trap
347
348 generic-trap -- generic trap type
349 INTEGER {
350 coldStart(0),
351 warmStart(1),
352 linkDown(2),
353 linkUp(3),
354 authenticationFailure(4),
355 egpNeighborLoss(5),
356 enterpriseSpecific(6)
357 },
358
359 specific-trap -- specific code, present even
360 INTEGER, -- if generic-trap is not
361 -- enterpriseSpecific
362
363 time-stamp -- time elapsed between the last
364 TimeTicks, -- (re)initialization of the
365 -- network entity and the
366 -- generation of the trap
367
368 variable-bindings -- "interesting" information
369 VarBindList
370 }
371
372 END
373
374 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
375
376 The predecessor of this document (<a href="./rfc1161">RFC 1161</a>) was produced by the SNMP
377 Working Group, and subsequently modified by the editor to reflect
378 operational experience gained since the original publication.
379
380 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
381
382 [<a id="ref-1">1</a>] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "A Simple
383 Network Management Protocol (SNMP)", <a href="./rfc1157">RFC 1157</a>, SNMP Research,
384 Performance Systems International, Performance Systems
385
386
387
388 <span class="grey">Rose [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1283">RFC 1283</a> SNMP over OSI December 1991</span>
391
392
393 International, and MIT Laboratory for Computer Science, May 1990.
394
395 [<a id="ref-2">2</a>] Rose M., and K. McCloghrie, "Structure and Identification of
396 Management Information for TCP/IP-based internets", <a href="./rfc1155">RFC 1155</a>,
397 Performance Systems International, Hughes LAN Systems, May 1990.
398
399 [<a id="ref-3">3</a>] McCloghrie K., and M. Rose, Editors, "Management Information Base
400 for Network Management of TCP/IP-based internets", <a href="./rfc1213">RFC 1213</a>,
401 Hughes LAN Systems, Performance Systems International, March
402 1991.
403
404 [<a id="ref-4">4</a>] Information Processing Systems - Open Systems Interconnection,
405 "Transport Service Definition", International Organization for
406 Standardization, International Standard 8072, June 1986.
407
408 [<a id="ref-5">5</a>] Information Processing Systems - Open Systems Interconnection,
409 "Transport Service Definition - Addendum 1: Connectionless-mode
410 Transmission", International Organization for Standardization,
411 International Standard 8072/AD 1, December 1986.
412
413 [<a id="ref-6">6</a>] Postel, J., "User Datagram Protocol", <a href="./rfc768">RFC 768</a>, USC/Information
414 Sciences Institute, November 1980.
415
416 [<a id="ref-7">7</a>] Kille, S., "A String Encoding of Presentation Address", <a href="./rfc1278">RFC 1278</a>,
417 Department of Computer Science, University College London,
418 November 1991.
419
420 [<a id="ref-8">8</a>] Case, J., Davin, J., Fedor, M., and M. Schoffstall, "Network
421 Management and the Design of SNMP", ConneXions (ISSN 0894-5926),
422 Volume 3, Number 3, March 1989.
423
424 [<a id="ref-9">9</a>] Satz, G., "CLNS MIB for use with CLNP and ES-IS", <a href="./rfc1238">RFC 1238</a>, cisco
425 Systems, June 1991.
426
427 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
428
429 Security issues are not discussed in this memo.
430
431 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span>
432
433 Marshall T. Rose
434 Dover Beach Consulting, Inc.
435 420 Whisman Court
436 Mountain View, CA 94043-2112
437
438 Phone: (415) 968-1052
439 Email: [email protected]
440 X.500: mrose, dbc, us
441
442
443
444 Rose [Page 8]
445 </pre>