Debian Codegraph @

rfc1445.html

raw
1 <pre> Network Working Group J. Galvin
2 Request for Comments: 1445 Trusted Information Systems
3 K. McCloghrie
4 Hughes LAN Systems
5 April 1993
6
7
8 <span class="h1">Administrative Model</span>
9 <span class="h1">for version 2 of the</span>
10 <span class="h1">Simple Network Management Protocol (SNMPv2)</span>
11
12
13
14
15
16
17 Status of this Memo
18
19 This RFC specifes an IAB standards track protocol for the
20 Internet community, and requests discussion and suggestions
21 for improvements. Please refer to the current edition of the
22 "IAB Official Protocol Standards" for the standardization
23 state and status of this protocol. Distribution of this memo
24 is unlimited.
25
26
27 Table of Contents
28
29
30 <a href="#section-1">1</a> Introduction .......................................... <a href="#page-2">2</a>
31 <a href="#section-1.1">1.1</a> A Note on Terminology ............................... <a href="#page-2">2</a>
32 <a href="#section-2">2</a> Elements of the Model ................................. <a href="#page-3">3</a>
33 <a href="#section-2.1">2.1</a> SNMPv2 Party ........................................ <a href="#page-3">3</a>
34 <a href="#section-2.2">2.2</a> SNMPv2 Entity ....................................... <a href="#page-6">6</a>
35 <a href="#section-2.3">2.3</a> SNMPv2 Management Station ........................... <a href="#page-7">7</a>
36 <a href="#section-2.4">2.4</a> SNMPv2 Agent ........................................ <a href="#page-7">7</a>
37 <a href="#section-2.5">2.5</a> View Subtree ........................................ <a href="#page-7">7</a>
38 <a href="#section-2.6">2.6</a> MIB View ............................................ <a href="#page-8">8</a>
39 <a href="#section-2.7">2.7</a> Proxy Relationship .................................. <a href="#page-8">8</a>
40 <a href="#section-2.8">2.8</a> SNMPv2 Context ...................................... <a href="#page-10">10</a>
41 <a href="#section-2.9">2.9</a> SNMPv2 Management Communication ..................... <a href="#page-10">10</a>
42 <a href="#section-2.10">2.10</a> SNMPv2 Authenticated Management Communication ...... <a href="#page-12">12</a>
43 <a href="#section-2.11">2.11</a> SNMPv2 Private Management Communication ............ <a href="#page-13">13</a>
44 <a href="#section-2.12">2.12</a> SNMPv2 Management Communication Class .............. <a href="#page-14">14</a>
45 <a href="#section-2.13">2.13</a> SNMPv2 Access Control Policy ....................... <a href="#page-14">14</a>
46 <a href="#section-3">3</a> Elements of Procedure ................................. <a href="#page-17">17</a>
47 <a href="#section-3.1">3.1</a> Generating a Request ................................ <a href="#page-17">17</a>
48 <a href="#section-3.2">3.2</a> Processing a Received Communication ................. <a href="#page-18">18</a>
49 <a href="#section-3.3">3.3</a> Generating a Response ............................... <a href="#page-21">21</a>
50
51
52
53
54
55 <span class="grey"> Galvin &amp; McCloghrie [Page i]</span></pre>
56 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-1" ></span>
57 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
58
59
60 <a href="#section-4">4</a> Application of the Model .............................. <a href="#page-23">23</a>
61 <a href="#section-4.1">4.1</a> Non-Secure Minimal Agent Configuration .............. <a href="#page-23">23</a>
62 <a href="#section-4.2">4.2</a> Secure Minimal Agent Configuration .................. <a href="#page-26">26</a>
63 <a href="#section-4.3">4.3</a> MIB View Configurations ............................. <a href="#page-28">28</a>
64 <a href="#section-4.4">4.4</a> Proxy Configuration ................................. <a href="#page-32">32</a>
65 <a href="#section-4.4.1">4.4.1</a> Foreign Proxy Configuration ....................... <a href="#page-33">33</a>
66 <a href="#section-4.4.2">4.4.2</a> Native Proxy Configuration ........................ <a href="#page-37">37</a>
67 <a href="#section-4.5">4.5</a> Public Key Configuration ............................ <a href="#page-41">41</a>
68 <a href="#section-5">5</a> Security Considerations ............................... <a href="#page-44">44</a>
69 <a href="#section-6">6</a> Acknowledgements ...................................... <a href="#page-45">45</a>
70 <a href="#section-7">7</a> References ............................................ <a href="#page-46">46</a>
71 <a href="#section-8">8</a> Authors' Addresses .................................... <a href="#page-47">47</a>
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110 <span class="grey"> Galvin &amp; McCloghrie [Page 1]</span></pre>
111 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
112 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
113
114
115 1. Introduction
116
117 A network management system contains: several (potentially
118 many) nodes, each with a processing entity, termed an agent,
119 which has access to management instrumentation; at least one
120 management station; and, a management protocol, used to convey
121 management information between the agents and management
122 stations. Operations of the protocol are carried out under an
123 administrative framework which defines both authentication and
124 authorization policies.
125
126 Network management stations execute management applications
127 which monitor and control network elements. Network elements
128 are devices such as hosts, routers, terminal servers, etc.,
129 which are monitored and controlled through access to their
130 management information.
131
132 It is the purpose of this document, the Administrative Model
133 for SNMPv2, to define how the administrative framework is
134 applied to realize effective network management in a variety
135 of configurations and environments.
136
137 The model described here entails the use of distinct
138 identities for peers that exchange SNMPv2 messages. Thus, it
139 represents a departure from the community-based administrative
140 model of the original SNMP [<a href="#ref-1" title="&quot;Simple Network Management Protocol&quot;">1</a>]. By unambiguously identifying
141 the source and intended recipient of each SNMPv2 message, this
142 new strategy improves upon the historical community scheme
143 both by supporting a more convenient access control model and
144 allowing for effective use of asymmetric (public key) security
145 protocols in the future.
146
147
148 1.1. A Note on Terminology
149
150 For the purpose of exposition, the original Internet-standard
151 Network Management Framework, as described in RFCs 1155, 1157,
152 and 1212, is termed the SNMP version 1 framework (SNMPv1).
153 The current framework is termed the SNMP version 2 framework
154 (SNMPv2).
155
156
157
158
159
160
161
162
163
164
165 <span class="grey"> Galvin &amp; McCloghrie [Page 2]</span></pre>
166 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
167 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
168
169
170 2. Elements of the Model
171
172 2.1. SNMPv2 Party
173
174 A SNMPv2 party is a conceptual, virtual execution environment
175 whose operation is restricted (for security or other purposes)
176 to an administratively defined subset of all possible
177 operations of a particular SNMPv2 entity (see <a href="#section-2.2">Section 2.2</a>).
178 Whenever a SNMPv2 entity processes a SNMPv2 message, it does
179 so by acting as a SNMPv2 party and is thereby restricted to
180 the set of operations defined for that party. The set of
181 possible operations specified for a SNMPv2 party may be
182 overlapping or disjoint with respect to the sets of other
183 SNMPv2 parties; it may also be a proper or improper subset of
184 all possible operations of the SNMPv2 entity.
185
186 Architecturally, each SNMPv2 party comprises
187
188 o a single, unique party identity,
189
190 o a logical network location at which the party executes,
191 characterized by a transport protocol domain and
192 transport addressing information,
193
194 o a single authentication protocol and associated
195 parameters by which all protocol messages originated by
196 the party are authenticated as to origin and integrity,
197 and
198
199 o a single privacy protocol and associated parameters by
200 which all protocol messages received by the party are
201 protected from disclosure.
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220 <span class="grey"> Galvin &amp; McCloghrie [Page 3]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
222 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
223
224
225 Conceptually, each SNMPv2 party may be represented by an ASN.1
226 value with the following syntax:
227
228 SnmpParty ::= SEQUENCE {
229 partyIdentity
230 OBJECT IDENTIFIER,
231 partyTDomain
232 OBJECT IDENTIFIER,
233 partyTAddress
234 OCTET STRING,
235 partyMaxMessageSize
236 INTEGER,
237 partyAuthProtocol
238 OBJECT IDENTIFIER,
239 partyAuthClock
240 INTEGER,
241 partyAuthPrivate
242 OCTET STRING,
243 partyAuthPublic
244 OCTET STRING,
245 partyAuthLifetime
246 INTEGER,
247 partyPrivProtocol
248 OBJECT IDENTIFIER,
249 partyPrivPrivate
250 OCTET STRING,
251 partyPrivPublic
252 OCTET STRING
253 }
254
255 For each SnmpParty value that represents a SNMPv2 party, the
256 following statements are true:
257
258 o Its partyIdentity component is the party identity.
259
260 o Its partyTDomain component is called the transport domain
261 and indicates the kind of transport service by which the
262 party receives network management traffic. An example of
263 a transport domain is snmpUDPDomain (SNMPv2 over UDP,
264 using SNMPv2 parties).
265
266 o Its partyTAddress component is called the transport
267 addressing information and represents a transport service
268 address by which the party receives network management
269 traffic.
270
271
272
273
274
275 <span class="grey"> Galvin &amp; McCloghrie [Page 4]</span></pre>
276 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
277 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
278
279
280 o Its partyMaxMessageSize component is called the maximum
281 message size and represents the length in octets of the
282 largest SNMPv2 message this party is prepared to accept.
283
284 o Its partyAuthProtocol component is called the
285 authentication protocol and identifies a protocol and a
286 mechanism by which all messages generated by the party
287 are authenticated as to integrity and origin. In this
288 context, the value noAuth signifies that messages
289 generated by the party are not authenticated as to
290 integrity and origin.
291
292 o Its partyAuthClock component is called the authentication
293 clock and represents a notion of the current time that is
294 specific to the party. The significance of this
295 component is specific to the authentication protocol.
296
297 o Its partyAuthPrivate component is called the private
298 authentication key and represents any secret value needed
299 to support the authentication protocol. The significance
300 of this component is specific to the authentication
301 protocol.
302
303 o Its partyAuthPublic component is called the public
304 authentication key and represents any public value that
305 may be needed to support the authentication protocol.
306 The significance of this component is specific to the
307 authentication protocol.
308
309 o Its partyAuthLifetime component is called the lifetime
310 and represents an administrative upper bound on
311 acceptable delivery delay for protocol messages generated
312 by the party. The significance of this component is
313 specific to the authentication protocol.
314
315 o Its partyPrivProtocol component is called the privacy
316 protocol and identifies a protocol and a mechanism by
317 which all protocol messages received by the party are
318 protected from disclosure. In this context, the value
319 noPriv signifies that messages received by the party are
320 not protected from disclosure.
321
322 o Its partyPrivPrivate component is called the private
323 privacy key and represents any secret value needed to
324 support the privacy protocol. The significance of this
325
326
327
328
329
330 <span class="grey"> Galvin &amp; McCloghrie [Page 5]</span></pre>
331 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
332 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
333
334
335 component is specific to the privacy protocol.
336
337 o Its partyPrivPublic component is called the public
338 privacy key and represents any public value that may be
339 needed to support the privacy protocol. The significance
340 of this component is specific to the privacy protocol.
341
342 If, for all SNMPv2 parties realized by a SNMPv2 entity, the
343 authentication protocol is noAuth and the privacy protocol is
344 noPriv, then that entity is called non-secure.
345
346
347 2.2. SNMPv2 Entity
348
349 A SNMPv2 entity is an actual process which performs network
350 management operations by generating and/or responding to
351 SNMPv2 protocol messages in the manner specified in [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>]. When
352 a SNMPv2 entity is acting as a particular SNMPv2 party (see
353 <a href="#section-2.1">Section 2.1</a>), the operation of that entity must be restricted
354 to the subset of all possible operations that is
355 administratively defined for that party.
356
357 By definition, the operation of a SNMPv2 entity requires no
358 concurrency between processing of any single protocol message
359 (by a particular SNMPv2 party) and processing of any other
360 protocol message (by a potentially different SNMPv2 party).
361 Accordingly, implementation of a SNMPv2 entity to support more
362 than one party need not be multi-threaded. However, there may
363 be situations where implementors may choose to use multi-
364 threading.
365
366 Architecturally, every SNMPv2 entity maintains a local
367 database that represents all SNMPv2 parties known to it -
368 those whose operation is realized locally, those whose
369 operation is realized by proxy interactions with remote
370 parties or devices, and those whose operation is realized by
371 remote entities. In addition, every SNMPv2 entity maintains a
372 local database that represents all managed object resources
373 (see <a href="#section-2.8">Section 2.8</a>) which are known to the SNMPv2 entity.
374 Finally, every SNMPv2 entity maintains a local database that
375 represents an access control policy (see <a href="#section-2.11">Section 2.11</a>) that
376 defines the access privileges accorded to known SNMPv2
377 parties.
378
379
380
381
382
383
384
385 <span class="grey"> Galvin &amp; McCloghrie [Page 6]</span></pre>
386 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
387 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
388
389
390 2.3. SNMPv2 Management Station
391
392 A SNMPv2 management station is the operational role assumed by
393 a SNMPv2 party when it initiates SNMPv2 management operations
394 by the generation of appropriate SNMPv2 protocol messages or
395 when it receives and processes trap notifications.
396
397 Sometimes, the term SNMPv2 management station is applied to
398 partial implementations of the SNMPv2 (in graphics
399 workstations, for example) that focus upon this operational
400 role. Such partial implementations may provide for
401 convenient, local invocation of management services, but they
402 may provide little or no support for performing SNMPv2
403 management operations on behalf of remote protocol users.
404
405
406 2.4. SNMPv2 Agent
407
408 A SNMPv2 agent is the operational role assumed by a SNMPv2
409 party when it performs SNMPv2 management operations in
410 response to received SNMPv2 protocol messages such as those
411 generated by a SNMPv2 management station (see <a href="#section-2.3">Section 2.3</a>).
412
413 Sometimes, the term SNMPv2 agent is applied to partial
414 implementations of the SNMPv2 (in embedded systems, for
415 example) that focus upon this operational role. Such partial
416 implementations provide for realization of SNMPv2 management
417 operations on behalf of remote users of management services,
418 but they may provide little or no support for local invocation
419 of such services.
420
421
422 2.5. View Subtree
423
424 A view subtree is the set of all MIB object instances which
425 have a common ASN.1 OBJECT IDENTIFIER prefix to their names.
426 A view subtree is identified by the OBJECT IDENTIFIER value
427 which is the longest OBJECT IDENTIFIER prefix common to all
428 (potential) MIB object instances in that subtree.
429
430 When the OBJECT IDENTIFIER prefix identifying a view subtree
431 is longer than the OBJECT IDENTIFIER of an object type defined
432 according to the SMI [<a href="#ref-3" title="&quot;Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">3</a>], then the use of such a view subtree
433 for access control has granularity at the object instance
434 level. Such granularity is considered beyond the scope of a
435
436
437
438
439
440 <span class="grey"> Galvin &amp; McCloghrie [Page 7]</span></pre>
441 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
442 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
443
444
445 SNMPv2 entity acting in an agent role. As such, no
446 implementation of a SNMPv2 entity acting in an agent role is
447 required to support values of viewSubtree [<a href="#ref-6" title="&quot;Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">6</a>] which have more
448 sub-identifiers than is necessary to identify a particular
449 leaf object type. However, access control information is also
450 used in determining which SNMPv2 entities acting in a manager
451 role should receive trap notifications (Section 4.2.6 of [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>]).
452 As such, agent implementors might wish to provide instance-
453 level granularity in order to allow a management station to
454 use fine-grain configuration of trap notifications.
455
456
457 2.6. MIB View
458
459 A MIB view is a subset of the set of all instances of all
460 object types defined according to the SMI [<a href="#ref-3" title="&quot;Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">3</a>] (i.e., of the
461 universal set of all instances of all MIB objects), subject to
462 the following constraints:
463
464 o Each element of a MIB view is uniquely named by an ASN.1
465 OBJECT IDENTIFIER value. As such, identically named
466 instances of a particular object type (e.g., in different
467 agents) must be contained within different MIB views.
468 That is, a particular object instance name resolves
469 within a particular MIB view to at most one object
470 instance.
471
472 o Every MIB view is defined as a collection of view
473 subtrees.
474
475
476 2.7. Proxy Relationship
477
478 A proxy relationship exists when, in order to process a
479 received management request, a SNMPv2 entity must communicate
480 with another, logically remote, entity. A SNMPv2 entity which
481 processes management requests using a proxy relationship is
482 termed a SNMPv2 proxy agent.
483
484 When communication between a logically remote party and a
485 SNMPv2 entity is via the SNMPv2 (over any transport protocol),
486 then the proxy party is called a SNMPv2 native proxy
487 relationship. Deployment of SNMPv2 native proxy relationships
488 is a means whereby the processing or bandwidth costs of
489 management may be amortized or shifted - thereby facilitating
490
491
492
493
494
495 <span class="grey"> Galvin &amp; McCloghrie [Page 8]</span></pre>
496 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
497 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
498
499
500 the construction of large management systems.
501
502 When communication between a logically remote party and a
503 SNMPv2 entity party is not via the SNMPv2, then the proxy
504 party is called a SNMPv2 foreign proxy relationship.
505 Deployment of foreign proxy relationships is a means whereby
506 otherwise unmanageable devices or portions of an internet may
507 be managed via the SNMPv2.
508
509 The transparency principle that defines the behavior of a
510 SNMPv2 entity in general applies in particular to a SNMPv2
511 proxy relationship:
512
513 The manner in which one SNMPv2 entity processes SNMPv2
514 protocol messages received from another SNMPv2 entity is
515 entirely transparent to the latter.
516
517 The transparency principle derives directly from the
518 historical SNMP philosophy of divorcing architecture from
519 implementation. To this dichotomy are attributable many of
520 the most valuable benefits in both the information and
521 distribution models of the Internet-standard Network
522 Management Framework, and it is the architectural cornerstone
523 upon which large management systems may be built. Consistent
524 with this philosophy, although the implementation of SNMPv2
525 proxy agents in certain environments may resemble that of a
526 transport-layer bridge, this particular implementation
527 strategy (or any other!) does not merit special recognition
528 either in the SNMPv2 management architecture or in standard
529 mechanisms for proxy administration.
530
531 Implicit in the transparency principle is the requirement that
532 the semantics of SNMPv2 management operations are preserved
533 between any two SNMPv2 peers. In particular, the "as if
534 simultaneous" semantics of a Set operation are extremely
535 difficult to guarantee if its scope extends to management
536 information resident at multiple network locations. For this
537 reason, proxy configurations that admit Set operations that
538 apply to information at multiple locations are discouraged,
539 although such operations are not explicitly precluded by the
540 architecture in those rare cases where they might be supported
541 in a conformant way.
542
543 Also implicit in the transparency principle is the requirement
544 that, throughout its interaction with a proxy agent, a
545
546
547
548
549
550 <span class="grey"> Galvin &amp; McCloghrie [Page 9]</span></pre>
551 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
552 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
553
554
555 management station is supplied with no information about the
556 nature or progress of the proxy mechanisms by which its
557 requests are realized. That is, it should seem to the
558 management station - except for any distinction in underlying
559 transport address - as if it were interacting via SNMPv2
560 directly with the proxied device. Thus, a timeout in the
561 communication between a proxy agent and its proxied device
562 should be represented as a timeout in the communication
563 between the management station and the proxy agent.
564 Similarly, an error response from a proxied device should - as
565 much as possible - be represented by the corresponding error
566 response in the interaction between the proxy agent and
567 management station.
568
569
570 2.8. SNMPv2 Context
571
572 A SNMPv2 context is a collection of managed object resources
573 accessible by a SNMPv2 entity. The object resources
574 identified by a context are either local or remote.
575
576 A SNMPv2 context referring to local object resources is
577 identified as a MIB view. In this case, a SNMPv2 entity uses
578 local mechanisms to access the management information
579 identified by the SNMPv2 context.
580
581 A remote SNMPv2 context referring to remote object resources
582 is identified as a proxy relationship. In this case, a SNMPv2
583 entity acts as a proxy agent to access the management
584 information identified by the SNMPv2 context.
585
586
587 2.9. SNMPv2 Management Communication
588
589 A SNMPv2 management communication is a communication from one
590 specified SNMPv2 party to a second specified SNMPv2 party
591 about management information that is contained in a SNMPv2
592 context accessible by the appropriate SNMPv2 entity. In
593 particular, a SNMPv2 management communication may be
594
595 o a query by the originating party about information
596 accessible to the addressed party (e.g., getRequest,
597 getNextRequest, or getBulkRequest),
598
599
600
601
602
603
604
605 <span class="grey"> Galvin &amp; McCloghrie [Page 10]</span></pre>
606 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
607 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
608
609
610 o an indicative assertion to the addressed party about
611 information accessible to the originating party (e.g.,
612 Response, InformRequest, or SNMPv2-Trap),
613
614 o an imperative assertion by the originating party about
615 information accessible to the addressed party (e.g.,
616 setRequest), or
617
618 o a confirmation to the addressed party about information
619 received by the originating party (e.g., a Response
620 confirming an InformRequest).
621
622 A management communication is represented by an ASN.1 value
623 with the following syntax:
624
625 SnmpMgmtCom ::= [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>] IMPLICIT SEQUENCE {
626 dstParty
627 OBJECT IDENTIFIER,
628 srcParty
629 OBJECT IDENTIFIER,
630 context
631 OBJECT IDENTIFIER,
632 pdu
633 PDUs
634 }
635
636 For each SnmpMgmtCom value that represents a SNMPv2 management
637 communication, the following statements are true:
638
639 o Its dstParty component is called the destination and
640 identifies the SNMPv2 party to which the communication is
641 directed.
642
643 o Its srcParty component is called the source and
644 identifies the SNMPv2 party from which the communication
645 is originated.
646
647 o Its context component identifies the SNMPv2 context
648 containing the management information referenced by the
649 communication.
650
651 o Its pdu component has the form and significance
652 attributed to it in [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>].
653
654
655
656
657
658
659
660 <span class="grey"> Galvin &amp; McCloghrie [Page 11]</span></pre>
661 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
662 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
663
664
665 2.10. SNMPv2 Authenticated Management Communication
666
667 A SNMPv2 authenticated management communication is a SNMPv2
668 management communication (see <a href="#section-2.9">Section 2.9</a>) for which the
669 originating SNMPv2 party is (possibly) reliably identified and
670 for which the integrity of the transmission of the
671 communication is (possibly) protected. An authenticated
672 management communication is represented by an ASN.1 value with
673 the following syntax:
674
675 SnmpAuthMsg ::= [<a href="#ref-1" title="&quot;Simple Network Management Protocol&quot;">1</a>] IMPLICIT SEQUENCE {
676 authInfo
677 ANY, -- defined by authentication protocol
678 authData
679 SnmpMgmtCom
680 }
681
682 For each SnmpAuthMsg value that represents a SNMPv2
683 authenticated management communication, the following
684 statements are true:
685
686 o Its authInfo component is called the authentication
687 information and represents information required in
688 support of the authentication protocol used by the SNMPv2
689 party originating the message. The detailed significance
690 of the authentication information is specific to the
691 authentication protocol in use; it has no effect on the
692 application semantics of the communication other than its
693 use by the authentication protocol in determining whether
694 the communication is authentic or not.
695
696 o Its authData component is called the authentication data
697 and represents a SNMPv2 management communication.
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715 <span class="grey"> Galvin &amp; McCloghrie [Page 12]</span></pre>
716 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
717 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
718
719
720 2.11. SNMPv2 Private Management Communication
721
722 A SNMPv2 private management communication is a SNMPv2
723 authenticated management communication (see <a href="#section-2.10">Section 2.10</a>) that
724 is (possibly) protected from disclosure. A private management
725 communication is represented by an ASN.1 value with the
726 following syntax:
727
728 SnmpPrivMsg ::= [<a href="#ref-1" title="&quot;Simple Network Management Protocol&quot;">1</a>] IMPLICIT SEQUENCE {
729 privDst
730 OBJECT IDENTIFIER,
731 privData
732 [<a href="#ref-1" title="&quot;Simple Network Management Protocol&quot;">1</a>] IMPLICIT OCTET STRING
733 }
734
735 For each SnmpPrivMsg value that represents a SNMPv2 private
736 management communication, the following statements are true:
737
738 o Its privDst component is called the privacy destination
739 and identifies the SNMPv2 party to which the
740 communication is directed.
741
742 o Its privData component is called the privacy data and
743 represents the (possibly encrypted) serialization
744 (according to the conventions of [<a href="#ref-5" title="&quot;Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>]) of a SNMPv2
745 authenticated management communication (see <a href="#section-2.10">Section</a>
746 <a href="#section-2.10">2.10</a>).
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770 <span class="grey"> Galvin &amp; McCloghrie [Page 13]</span></pre>
771 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
772 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
773
774
775 2.12. SNMPv2 Management Communication Class
776
777 A SNMPv2 management communication class corresponds to a
778 specific SNMPv2 PDU type defined in [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>]. A management
779 communication class is represented by an ASN.1 INTEGER value
780 according to the type of the identifying PDU (see Table 1).
781
782
783 Get 1
784 GetNext 2
785 Response 4
786 Set 8
787 -- unused 16
788 GetBulk 32
789 Inform 64
790 SNMPv2-Trap 128
791
792
793 Table 1: Management Communication Classes
794
795
796 The value by which a communication class is represented is
797 computed as 2 raised to the value of the ASN.1 context-
798 specific tag for the appropriate SNMPv2 PDU.
799
800 A set of management communication classes is represented by
801 the ASN.1 INTEGER value that is the sum of the representations
802 of the communication classes in that set. The null set is
803 represented by the value zero.
804
805
806 2.13. SNMPv2 Access Control Policy
807
808 A SNMPv2 access control policy is a specification of a local
809 access policy in terms of a SNMPv2 context and the management
810 communication classes which are authorized between a pair of
811 SNMPv2 parties. Architecturally, such a specification
812 comprises four parts:
813
814 o the targets of SNMPv2 access control - the SNMPv2 parties
815 that may perform management operations as requested by
816 management communications received from other parties,
817
818 o the subjects of SNMPv2 access control - the SNMPv2
819 parties that may request, by sending management
820
821
822
823
824
825 <span class="grey"> Galvin &amp; McCloghrie [Page 14]</span></pre>
826 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
827 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
828
829
830 communications to other parties, that management
831 operations be performed,
832
833 o the managed object resources of SNMPv2 access control -
834 the SNMPv2 contexts which identify the management
835 information on which requested management operations are
836 to be performed, and
837
838 o the policy that specifies the classes of SNMPv2
839 management communications pertaining to a particular
840 SNMPv2 context that a particular target is authorized to
841 accept from a particular subject.
842
843 Conceptually, a SNMPv2 access policy is represented by a
844 collection of ASN.1 values with the following syntax:
845
846 AclEntry ::= SEQUENCE {
847 aclTarget
848 OBJECT IDENTIFIER,
849 aclSubject
850 OBJECT IDENTIFIER,
851 aclResources
852 OBJECT IDENTIFIER,
853 aclPrivileges
854 INTEGER
855 }
856
857 For each such value that represents one part of a SNMPv2
858 access policy, the following statements are true:
859
860 o Its aclTarget component is called the target and
861 identifies the SNMPv2 party to which the partial policy
862 permits access.
863
864 o Its aclSubject component is called the subject and
865 identifies the SNMPv2 party to which the partial policy
866 grants privileges.
867
868 o Its aclResources component is called the managed object
869 resources and identifies the SNMPv2 context referenced by
870 the partial policy.
871
872 o Its aclPrivileges component is called the privileges and
873 represents a set of SNMPv2 management communication
874 classes which, when they reference the specified SNMPv2
875
876
877
878
879
880 <span class="grey"> Galvin &amp; McCloghrie [Page 15]</span></pre>
881 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
882 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
883
884
885 context, are authorized to be processed by the specified
886 target party when received from the specified subject
887 party.
888
889 The application of SNMPv2 access control policy only occurs on
890 receipt of management communications; it is not applied on
891 transmission of management communications. Note, however,
892 that ASN.1 values, having the syntax AclEntry, are also used
893 in determining the destinations of a SNMPv2-Trap [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>].
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935 <span class="grey"> Galvin &amp; McCloghrie [Page 16]</span></pre>
936 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
937 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
938
939
940 3. Elements of Procedure
941
942 This section describes the procedures followed by a SNMPv2
943 entity in processing SNMPv2 messages. These procedures are
944 independent of the particular authentication and privacy
945 protocols that may be in use.
946
947
948 3.1. Generating a Request
949
950 This section describes the procedure followed by a SNMPv2
951 entity whenever either a management request or a trap
952 notification is to be transmitted by a SNMPv2 party.
953
954 (1) A SnmpMgmtCom value is constructed for which the srcParty
955 component identifies the originating party, for which the
956 dstParty component identifies the receiving party, for
957 which the context component identifies the desired SNMPv2
958 context, and for which the pdu component represents the
959 desired management operation.
960
961 (2) The local database of party information is consulted to
962 determine the authentication protocol and other relevant
963 information for the originating and receiving SNMPv2
964 parties.
965
966 (3) A SnmpAuthMsg value is constructed with the following
967 properties:
968
969 Its authInfo component is constructed according to
970 the authentication protocol specified for the
971 originating party.
972
973 In particular, if the authentication protocol for
974 the originating SNMPv2 party is identified as
975 noAuth, then this component corresponds to the
976 OCTET STRING value of zero length.
977
978 Its authData component is the constructed SnmpMgmtCom
979 value.
980
981 (4) The local database of party information is consulted to
982 determine the privacy protocol and other relevant
983 information for the receiving SNMPv2 party.
984
985
986
987
988
989
990 <span class="grey"> Galvin &amp; McCloghrie [Page 17]</span></pre>
991 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
992 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
993
994
995 (5) A SnmpPrivMsg value is constructed with the following
996 properties:
997
998 Its privDst component identifies the receiving
999 SNMPv2 party.
1000
1001 Its privData component is the (possibly encrypted)
1002 serialization of the SnmpAuthMsg value according to
1003 the conventions of [<a href="#ref-5" title="&quot;Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>].
1004
1005 In particular, if the privacy protocol for the
1006 receiving SNMPv2 party is identified as noPriv,
1007 then the privData component is unencrypted.
1008 Otherwise, the privData component is processed
1009 according to the privacy protocol.
1010
1011 (6) The constructed SnmpPrivMsg value is serialized according
1012 to the conventions of [<a href="#ref-5" title="&quot;Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>].
1013
1014 (7) The serialized SnmpPrivMsg value is transmitted using the
1015 transport address and transport domain for the receiving
1016 SNMPv2 party.
1017
1018 Note that the above procedure does not include any application
1019 of any SNMPv2 access control policy (see <a href="#section-2.13">section 2.13</a>).
1020
1021
1022 3.2. Processing a Received Communication
1023
1024 This section describes the procedure followed by a SNMPv2
1025 entity whenever a management communication is received.
1026
1027 (1) The snmpStatsPackets counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is incremented. If the
1028 received message is not the serialization (according to
1029 the conventions of [<a href="#ref-5" title="&quot;Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>]) of an SnmpPrivMsg value, then
1030 that message is discarded without further processing.
1031 (If the first octet of the packet has the value
1032 hexadecimal 30, then the snmpStats30Something counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>]
1033 is incremented prior to discarding the message; otherwise
1034 the snmpStatsEncodingErrors counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is incremented.)
1035
1036 (2) The local database of party information is consulted for
1037 information about the receiving SNMPv2 party identified
1038 by the privDst component of the SnmpPrivMsg value.
1039
1040
1041
1042
1043
1044
1045 <span class="grey"> Galvin &amp; McCloghrie [Page 18]</span></pre>
1046 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1047 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1048
1049
1050 (3) If information about the receiving SNMPv2 party is absent
1051 from the local database of party information, or
1052 indicates that the receiving party's operation is not
1053 realized by the local SNMPv2 entity, then the received
1054 message is discarded without further processing, after
1055 the snmpStatsUnknownDstParties counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is
1056 incremented.
1057
1058 (4) An ASN.1 OCTET STRING value is constructed (possibly by
1059 decryption, according to the privacy protocol in use)
1060 from the privData component of said SnmpPrivMsg value.
1061
1062 In particular, if the privacy protocol recorded for the
1063 party is noPriv, then the OCTET STRING value corresponds
1064 exactly to the privData component of the SnmpPrivMsg
1065 value.
1066
1067 (5) If the OCTET STRING value is not the serialization
1068 (according to the conventions of [<a href="#ref-5" title="&quot;Transport Mappings for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">5</a>]) of an SnmpAuthMsg
1069 value, then the received message is discarded without
1070 further processing, after the snmpStatsEncodingErrors
1071 counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is incremented.
1072
1073 (6) If the dstParty component of the authData component of
1074 the obtained SnmpAuthMsg value is not the same as the
1075 privDst component of the SnmpPrivMsg value, then the
1076 received message is discarded without further processing,
1077 after the snmpStatsDstPartyMismatches counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is
1078 incremented.
1079
1080 (7) The local database of party information is consulted for
1081 information about the originating SNMPv2 party identified
1082 by the srcParty component of the authData component of
1083 the SnmpAuthMsg value.
1084
1085 (8) If information about the originating SNMPv2 party is
1086 absent from the local database of party information, then
1087 the received message is discarded without further
1088 processing, after the snmpStatsUnknownSrcParties counter
1089 [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is incremented.
1090
1091 (9) The obtained SnmpAuthMsg value is evaluated according to
1092 the authentication protocol and other relevant
1093 information associated with the originating and receiving
1094 SNMPv2 parties in the local database of party
1095
1096
1097
1098
1099
1100 <span class="grey"> Galvin &amp; McCloghrie [Page 19]</span></pre>
1101 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1102 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1103
1104
1105 information.
1106
1107 In particular, if the authentication protocol is
1108 identified as noAuth, then the SnmpAuthMsg value is
1109 always evaluated as authentic.
1110
1111 (10) If the SnmpAuthMsg value is evaluated as unauthentic,
1112 then the received message is discarded without further
1113 processing, and if the snmpV2EnableAuthenTraps object [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>]
1114 is enabled, then the SNMPv2 entity sends
1115 authorizationFailure traps [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] according to its
1116 configuration (<a href="#section-4.2.6">Section 4.2.6</a> of[2]).
1117
1118 (11) The SnmpMgmtCom value is extracted from the authData
1119 component of the SnmpAuthMsg value.
1120
1121 (12) The local database of context information is consulted
1122 for information about the SNMPv2 context identified by
1123 the context component of the SnmpMgmtCom value.
1124
1125 (13) If information about the SNMPv2 context is absent from
1126 the local database of context information, then the
1127 received message is discarded without further processing,
1128 after the snmpStatsUnknownContexts counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is
1129 incremented.
1130
1131 (14) The local database of access policy information is
1132 consulted for access privileges permitted by the local
1133 access policy to the originating SNMPv2 party with
1134 respect to the receiving SNMPv2 party and the indicated
1135 SNMPv2 context.
1136
1137 (15) The management communication class is determined from the
1138 ASN.1 tag value associated with the PDUs component of the
1139 SnmpMgmtCom value. If the management information class
1140 of the received message is either 32, 8, 2, or 1 (i.e.,
1141 GetBulk, Set, GetNext or Get) and the SNMPv2 context is
1142 not realized by the local SNMPv2 entity, then the
1143 received message is discarded without further processing,
1144 after the snmpStatsUnknownContexts counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is
1145 incremented.
1146
1147 (16) If the management communication class of the received
1148 message is either 128, 64 or 4 (i.e., SNMPv2-Trap,
1149 Inform, or Response) and this class is not among the
1150
1151
1152
1153
1154
1155 <span class="grey"> Galvin &amp; McCloghrie [Page 20]</span></pre>
1156 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1157 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1158
1159
1160 access privileges, then the received message is discarded
1161 without further processing, after the
1162 snmpStatsBadOperations counter [<a href="#ref-7" title="&quot;Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">7</a>] is incremented.
1163
1164 (17) If the management communication class of the received
1165 message is not among the access privileges, then the
1166 received message is discarded without further processing
1167 after generation and transmission of a response message.
1168 This response message is directed to the originating
1169 SNMPv2 party on behalf of the receiving SNMPv2 party.
1170 Its context, var-bind-list and request-id components are
1171 identical to those of the received request. Its error-
1172 index component is zero and its error-status component is
1173 authorizationError [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>].
1174
1175 (18) If the SNMPv2 context refers to local object resources,
1176 then the management operation represented by the
1177 SnmpMgmtCom value is performed by the receiving SNMPv2
1178 entity with respect to the MIB view identified by the
1179 SNMPv2 context according to the procedures set forth in
1180 [<a href="#ref-2" title="&quot;Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">2</a>].
1181
1182 (19) If the SNMPv2 context refers to remote object resources,
1183 then the management operation represented by the
1184 SnmpMgmtCom value is performed through the appropriate
1185 proxy relationship.
1186
1187
1188 3.3. Generating a Response
1189
1190 The procedure for generating a response to a SNMPv2 management
1191 request is identical to the procedure for transmitting a
1192 request (see <a href="#section-3.1">Section 3.1</a>), with these exceptions:
1193
1194 (1) In Step 1, the dstParty component of the responding
1195 SnmpMgmtCom value is taken from the srcParty component of
1196 the original SnmpMgmtCom value; the srcParty component of
1197 the responding SnmpMgmtCom value is taken from the
1198 dstParty component of the original SnmpMgmtCom value; the
1199 context component of the responding SnmpMgmtCom value is
1200 taken from the context component of the original
1201 SnmpMgmtCom value; and, the pdu component of the
1202 responding SnmpMgmtCom value is the response which
1203 results from applying the operation specified in the
1204 original SnmpMgmtCom value.
1205
1206
1207
1208
1209
1210 <span class="grey"> Galvin &amp; McCloghrie [Page 21]</span></pre>
1211 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1212 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1213
1214
1215 (2) In Step 7, the serialized SnmpPrivMsg value is
1216 transmitted using the transport address and transport
1217 domain from which its corresponding request originated -
1218 even if that is different from the transport information
1219 recorded in the local database of party information.
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265 <span class="grey"> Galvin &amp; McCloghrie [Page 22]</span></pre>
1266 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1267 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1268
1269
1270 4. Application of the Model
1271
1272 This section describes how the administrative model set forth
1273 above is applied to realize effective network management in a
1274 variety of configurations and environments. Several types of
1275 administrative configurations are identified, and an example
1276 of each is presented.
1277
1278
1279 4.1. Non-Secure Minimal Agent Configuration
1280
1281 This section presents an example configuration for a minimal,
1282 non-secure SNMPv2 agent that interacts with one or more SNMPv2
1283 management stations. Table 2 presents information about
1284 SNMPv2 parties that is known both to the minimal agent and to
1285 the manager, while Table 3 presents similarly common
1286 information about the local access policy.
1287
1288 As represented in Table 2, the example agent party operates at
1289 UDP port 161 at IP address 1.2.3.4 using the party identity
1290 gracie; the example manager operates at UDP port 2001 at IP
1291 address 1.2.3.5 using the identity george. At minimum, a
1292 non-secure SNMPv2 agent implementation must provide for
1293 administrative configuration (and non-volatile storage) of the
1294 identities and transport addresses of two SNMPv2 parties:
1295 itself and a remote peer. Strictly speaking, other
1296 information about these two parties (including access policy
1297 information) need not be configurable.
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320 <span class="grey"> Galvin &amp; McCloghrie [Page 23]</span></pre>
1321 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1322 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1323
1324
1325 Identity gracie george
1326 (agent) (manager)
1327 Domain snmpUDPDomain snmpUDPDomain
1328 Address 1.2.3.4, 161 1.2.3.5, 2001
1329 Auth Prot noAuth noAuth
1330 Auth Priv Key "" ""
1331 Auth Pub Key "" ""
1332 Auth Clock 0 0
1333 Auth Lifetime 0 0
1334 Priv Prot noPriv noPriv
1335 Priv Priv Key "" ""
1336 Priv Pub Key "" ""
1337
1338
1339 Table 2: Party Information for Minimal Agent
1340
1341
1342
1343
1344 Target Subject Context Privileges
1345 gracie george local 35 (Get, GetNext &amp; GetBulk)
1346 george gracie local 132 (Response &amp; SNMPv2-Trap)
1347
1348
1349 Table 3: Access Information for Minimal Agent
1350
1351
1352
1353 Suppose that the managing party george wishes to interrogate
1354 management information about the SNMPv2 context named "local"
1355 held by the agent named gracie by issuing a SNMPv2 GetNext
1356 request message. The manager consults its local database of
1357 party information. Because the authentication protocol for
1358 the party george is recorded as noAuth, the GetNext request
1359 message generated by the manager is not authenticated as to
1360 origin and integrity. Because, according to the manager's
1361 local database of party information, the privacy protocol for
1362 the party gracie is noPriv, the GetNext request message is not
1363 protected from disclosure. Rather, it is simply assembled,
1364 serialized, and transmitted to the transport address (IP
1365 address 1.2.3.4, UDP port 161) associated in the manager's
1366 local database of party information with the party gracie.
1367
1368 When the GetNext request message is received at the agent, the
1369 identity of the party to which it is directed (gracie) is
1370
1371
1372
1373
1374
1375 <span class="grey"> Galvin &amp; McCloghrie [Page 24]</span></pre>
1376 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1377 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1378
1379
1380 extracted from the message, and the receiving entity consults
1381 its local database of party information. Because the privacy
1382 protocol for the party gracie is recorded as noPriv, the
1383 received message is assumed not to be protected from
1384 disclosure. Similarly, the identity of the originating party
1385 (george) is extracted, and the local database of party
1386 information is consulted. Because the authentication protocol
1387 for the party george is recorded as noAuth, the received
1388 message is immediately accepted as authentic.
1389
1390 The received message is fully processed only if the agent's
1391 local database of access policy information authorizes GetNext
1392 request communications by the party george to the agent party
1393 gracie with respect to the SNMPv2 context "local". The
1394 database of access policy information presented as Table 3
1395 authorizes such communications (as well as Get and GetBulk
1396 operations).
1397
1398 When the received request is processed, a Response message is
1399 generated which references the SNMPv2 context "local" and
1400 identifies gracie as the source party and george, the party
1401 from which the request originated, as the destination party.
1402 Because the authentication protocol for gracie is recorded in
1403 the local database of party information as noAuth, the
1404 generated Response message is not authenticated as to origin
1405 or integrity. Because, according to the local database of
1406 party information, the privacy protocol for the party george
1407 is noPriv, the response message is not protected from
1408 disclosure. The response message is transmitted to the
1409 transport address from which the corresponding request
1410 originated - without regard for the transport address
1411 associated with george in the local database of party
1412 information.
1413
1414 When the generated response is received by the manager, the
1415 identity of the party to which it is directed (george) is
1416 extracted from the message, and the manager consults its local
1417 database of party information. Because the privacy protocol
1418 for the party george is recorded as noPriv, the received
1419 response is assumed not to be protected from disclosure.
1420 Similarly, the identity of the originating party (gracie) is
1421 extracted, and the local database of party information is
1422 consulted. Because the authentication protocol for the party
1423 gracie is recorded as noAuth, the received response is
1424 immediately accepted as authentic.
1425
1426
1427
1428
1429
1430 <span class="grey"> Galvin &amp; McCloghrie [Page 25]</span></pre>
1431 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1432 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1433
1434
1435 The received message is fully processed only if the manager's
1436 local database of access policy information authorizes
1437 Response communications from the party gracie to the manager
1438 party george which reference the SNMPv2 context "local". The
1439 database of access policy information presented as Table 3
1440 authorizes such Response messages (as well as SNMPv2-Trap
1441 messages).
1442
1443
1444 4.2. Secure Minimal Agent Configuration
1445
1446 This section presents an example configuration for a secure,
1447 minimal SNMPv2 agent that interacts with a single SNMPv2
1448 management station. Table 4 presents information about SNMPv2
1449 parties that is known both to the minimal agent and to the
1450 manager, while Table 5 presents similarly common information
1451 about the local access policy.
1452
1453 The interaction of manager and agent in this configuration is
1454 very similar to that sketched above for the non-secure minimal
1455 agent - except that all protocol messages are authenticated as
1456 to origin and integrity and protected from disclosure. This
1457 example requires encryption in order to support distribution
1458 of secret keys via the SNMPv2 itself. A more elaborate
1459 example comprising an additional pair of SNMPv2 parties could
1460 support the exchange of non-secret information in
1461 authenticated messages without incurring the cost of
1462 encryption.
1463
1464 An actual secure agent configuration may require SNMPv2
1465 parties for which the authentication and privacy protocols are
1466 noAuth and noPriv, respectively, in order to support clock
1467 synchronization (see [<a href="#ref-6" title="&quot;Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">6</a>]). For clarity, these additional
1468 parties are not represented in this example.
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485 <span class="grey"> Galvin &amp; McCloghrie [Page 26]</span></pre>
1486 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1487 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1488
1489
1490 Identity ollie stan
1491 (agent) (manager)
1492 Domain snmpUDPDomain snmpUDPDomain
1493 Address 1.2.3.4, 161 1.2.3.5, 2001
1494 Auth Prot v2md5AuthProtocol v2md5AuthProtocol
1495 Auth Priv Key "0123456789ABCDEF" "GHIJKL0123456789"
1496 Auth Pub Key "" ""
1497 Auth Clock 0 0
1498 Auth Lifetime 300 300
1499 Priv Prot desPrivProtocol desPrivProtocol
1500 Priv Priv Key "MNOPQR0123456789" "STUVWX0123456789"
1501 Priv Pub Key "" ""
1502
1503
1504 Table 4: Party Information for Secure Minimal Agent
1505
1506
1507
1508
1509 Target Subject Context Privileges
1510 ollie stan local 35 (Get, GetNext &amp; GetBulk)
1511 stan ollie local 132 (Response &amp; SNMPv2-Trap)
1512
1513
1514 Table 5: Access Information for Secure Minimal Agent
1515
1516
1517 As represented in Table 4, the example agent party operates at
1518 UDP port 161 at IP address 1.2.3.4 using the party identity
1519 ollie; the example manager operates at UDP port 2001 at IP
1520 address 1.2.3.5 using the identity stan. At minimum, a secure
1521 SNMPv2 agent implementation must provide for administrative
1522 configuration (and non-volatile storage) of relevant
1523 information about two SNMPv2 parties: itself and a remote
1524 peer. Both ollie and stan authenticate all messages that they
1525 generate by using the SNMPv2 authentication protocol
1526 v2md5AuthProtocol and their distinct, private authentication
1527 keys. Although these private authentication key values
1528 ("0123456789ABCDEF" and "GHIJKL0123456789") are presented here
1529 for expository purposes, knowledge of private authentication
1530 keys is not normally afforded to human beings and is confined
1531 to those portions of the protocol implementation that require
1532 it.
1533
1534
1535
1536
1537
1538
1539
1540 <span class="grey"> Galvin &amp; McCloghrie [Page 27]</span></pre>
1541 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1542 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1543
1544
1545 When using the v2md5AuthProtocol, the public authentication
1546 key for each SNMPv2 party is never used in authentication and
1547 verification of SNMPv2 exchanges. Also, because the
1548 v2md5AuthProtocol is symmetric in character, the private
1549 authentication key for each party must be known to another
1550 SNMPv2 party with which authenticated communication is
1551 desired. In contrast, asymmetric (public key) authentication
1552 protocols would not depend upon sharing of a private key for
1553 their operation.
1554
1555 All protocol messages generated for transmission to the party
1556 stan are encrypted using the desPrivProtocol privacy protocol
1557 and the private key "STUVWX0123456789"; they are decrypted
1558 upon reception according to the same protocol and key.
1559 Similarly, all messages generated for transmission to the
1560 party ollie are encrypted using the desPrivProtocol protocol
1561 and private privacy key "MNOPQR0123456789"; they are
1562 correspondingly decrypted on reception. As with
1563 authentication keys, knowledge of private privacy keys is not
1564 normally afforded to human beings and is confined to those
1565 portions of the protocol implementation that require it.
1566
1567
1568 4.3. MIB View Configurations
1569
1570 This section describes a convention for the definition of MIB
1571 views and, using that convention, presents example
1572 configurations of MIB views for SNMPv2 contexts that refer to
1573 local object resources.
1574
1575 A MIB view is defined by a collection of view subtrees (see
1576 <a href="#section-2.6">Section 2.6</a>), and any MIB view may be represented in this way.
1577 Because MIB view definitions may, in certain cases, comprise a
1578 very large number of view subtrees, a convention for
1579 abbreviating MIB view definitions is desirable.
1580
1581 The convention adopted in [<a href="#ref-4" title="&quot;Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">4</a>] supports abbreviation of MIB
1582 view definitions in terms of families of view subtrees that
1583 are either included in or excluded from the definition of the
1584 relevant MIB view. By this convention, a table locally
1585 maintained by each SNMPv2 entity defines the MIB view
1586 associated with each SNMPv2 context that refers to local
1587 object resources. Each entry in the table represents a family
1588 of view subtrees that (according to the type of that entry) is
1589 either included in or excluded from the MIB view of some
1590
1591
1592
1593
1594
1595 <span class="grey"> Galvin &amp; McCloghrie [Page 28]</span></pre>
1596 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1597 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1598
1599
1600 SNMPv2 context. Each table entry represents a subtree family
1601 as a pairing of an OBJECT IDENTIFIER value (called the family
1602 name) together with a bitstring value (called the family
1603 mask). The family mask indicates which sub-identifiers of the
1604 associated family name are significant to the definition of
1605 the represented subtree family. For each possible MIB object
1606 instance, that instance belongs to the view subtree family
1607 represented by a particular table entry if
1608
1609 o the OBJECT IDENTIFIER name of that MIB object instance
1610 comprises at least as many sub-identifiers as does the
1611 family name for said table entry, and
1612
1613 o each sub-identifier in the name of said MIB object
1614 instance matches the corresponding sub-identifier of the
1615 relevant family name whenever the corresponding bit of
1616 the associated family mask is non-zero.
1617
1618 The appearance of a MIB object instance in the MIB view for a
1619 particular SNMPv2 context is related to the membership of that
1620 instance in the subtree families associated with that SNMPv2
1621 context in local table entries:
1622
1623 o If a MIB object instance belongs to none of the relevant
1624 subtree families, then that instance is not in the MIB
1625 view for the relevant SNMPv2 context.
1626
1627 o If a MIB object instance belongs to the subtree family
1628 represented by exactly one of the relevant table entries,
1629 then that instance is included in, or excluded from, the
1630 relevant MIB view according to the type of that entry.
1631
1632 o If a MIB object instance belongs to the subtree families
1633 represented by more than one of the relevant table
1634 entries, then that instance is included in, or excluded
1635 from, the relevant MIB view according to the type of the
1636 single such table entry for which, first, the associated
1637 family name comprises the greatest number of sub-
1638 identifiers, and, second, the associated family name is
1639 lexicographically greatest.
1640
1641 The subtree family represented by a table entry for which the
1642 associated family mask is all ones corresponds to the single
1643 view subtree identified by the family name for that entry.
1644 Because the convention of [<a href="#ref-4" title="&quot;Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">4</a>] provides for implicit extension
1645
1646
1647
1648
1649
1650 <span class="grey"> Galvin &amp; McCloghrie [Page 29]</span></pre>
1651 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1652 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1653
1654
1655 of family mask values with ones, the subtree family
1656 represented by a table entry with a family mask of zero length
1657 always corresponds to a single view subtree.
1658
1659
1660 Context Type Family Name Family Mask
1661 lucy included internet ''H
1662
1663
1664 Table 6: View Definition for Minimal Agent
1665
1666
1667 Using this convention for abbreviating MIB view definitions,
1668 some of the most common definitions of MIB views may be
1669 conveniently expressed. For example, Table 6 illustrates the
1670 MIB view definitions required for a minimal SNMPv2 entity that
1671 having a single SNMPv2 context for which the associated MIB
1672 view embraces all instances of all MIB objects defined within
1673 the SNMPv2 Network Management Framework. The represented
1674 table has a single entry. The SNMPv2 context (lucy) for which
1675 that entry defines the MIB view is identified in the first
1676 column. The type of that entry (included) signifies that any
1677 MIB object instance belonging to the subtree family
1678 represented by that entry may appear in the MIB view for the
1679 SNMPv2 context lucy. The family name for that entry is
1680 internet, and the zero-length family mask value signifies that
1681 the relevant subtree family corresponds to the single view
1682 subtree rooted at that node.
1683
1684 Another example of MIB view definition (see Table 7) is that
1685 of a SNMPv2 entity having multiple SNMPv2 contexts with
1686 distinct MIB views. The MIB view associated with the SNMPv2
1687 context lucy comprises all instances of all MIB objects
1688 defined within the SNMPv2 Network Management Framework, except
1689 those pertaining to the administration of SNMPv2 parties. In
1690 contrast, the MIB view attributed to the SNMPv2 context ricky
1691 contains only MIB object instances defined in the system group
1692 of the Internet-standard MIB together with those object
1693 instances by which SNMPv2 parties are administered.
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705 <span class="grey"> Galvin &amp; McCloghrie [Page 30]</span></pre>
1706 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1707 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1708
1709
1710 Context Type Family Name Family Mask
1711 lucy included internet ''H
1712 lucy excluded snmpParties ''H
1713 ricky included system ''H
1714 ricky included snmpParties ''H
1715
1716
1717 Table 7: View Definition for Multiple Contexts
1718
1719
1720 A more complicated example of MIB view configuration
1721 illustrates the abbreviation of related collections of view
1722 subtrees by view subtree families (see Table 8). In this
1723 example, the MIB view associated with the SNMPv2 context lucy
1724 includes all object instances in the system group of the
1725 Internet-standard MIB together with some information related
1726 to the second network interface attached to the managed
1727 device. However, this interface-related information does not
1728 include the speed of the interface. The family mask value
1729 'FFA0'H in the second table entry signifies that a MIB object
1730 instance belongs to the relevant subtree family if the initial
1731 prefix of its name places it within the ifEntry portion of the
1732 registration hierarchy and if the eleventh sub-identifier of
1733 its name is 2. The MIB object instance representing the speed
1734 of the second network interface belongs to the subtree
1735 families represented by both the second and third entries of
1736 the table, but that particular instance is excluded from the
1737 MIB view for the SNMPv2 context lucy because the
1738 lexicographically greater of the relevant family names appears
1739 in the table entry with type excluded.
1740
1741 The MIB view for the SNMPv2 context ricky is also defined in
1742 this example. The MIB view attributed to the SNMPv2 context
1743 ricky includes all object instances in the icmp group of the
1744 Internet-standard MIB, together with all information relevant
1745 to the fifth network interface attached to the managed device.
1746 In addition, the MIB view attributed to the SNMPv2 context
1747 ricky includes the number of octets received on the fourth
1748 attached network interface.
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760 <span class="grey"> Galvin &amp; McCloghrie [Page 31]</span></pre>
1761 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1762 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1763
1764
1765 Context Type Family Name Family Mask
1766 lucy included system ''H
1767 lucy included { ifEntry 0 2 } 'FFA0'H
1768 lucy excluded { ifSpeed 2 } ''H
1769 ricky included icmp ''H
1770 ricky included { ifEntry 0 5 } 'FFA0'H
1771 ricky included { ifInOctets 4 } ''H
1772
1773
1774 Table 8: More Elaborate View Definitions
1775
1776
1777 While, as suggested by the examples above, a wide range of MIB
1778 view configurations are efficiently supported by the
1779 abbreviated representation of [<a href="#ref-4" title="&quot;Party MIB for version 2 of the Simple Network Management Protocol (SNMPv2)&quot;">4</a>], prudent MIB design can
1780 sometimes further reduce the size and complexity of the most
1781 likely MIB view definitions. On one hand, it is critical that
1782 mechanisms for MIB view configuration impose no absolute
1783 constraints either upon the access policies of local
1784 administrations or upon the structure of MIB namespaces; on
1785 the other hand, where the most common access policies are
1786 known, the configuration costs of realizing those policies may
1787 be slightly reduced by assigning to distinct portions of the
1788 registration hierarchy those MIB objects for which local
1789 policies most frequently require distinct treatment.
1790
1791
1792 4.4. Proxy Configuration
1793
1794 This section presents examples of SNMPv2 proxy configurations.
1795 On one hand, foreign proxy configurations provide the
1796 capability to manage non-SNMP devices. On the other hand,
1797 native proxy configurations allow an administrator to shift
1798 the computational burden of rich management functionality away
1799 from network devices whose primary task is not management. To
1800 the extent that SNMPv2 proxy agents function as points of
1801 aggregation for management information, proxy configurations
1802 may also reduce the bandwidth requirements of large-scale
1803 management activities.
1804
1805 The example configurations in this section are simplified for
1806 clarity: actual configurations may require additional parties
1807 in order to support clock synchronization and distribution of
1808 secrets.
1809
1810
1811
1812
1813
1814
1815 <span class="grey"> Galvin &amp; McCloghrie [Page 32]</span></pre>
1816 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1817 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1818
1819
1820 4.4.1. Foreign Proxy Configuration
1821
1822 This section presents an example configuration by which a
1823 SNMPv2 management station may manage network elements that do
1824 not themselves support the SNMPv2. This configuration centers
1825 on a SNMPv2 proxy agent that realizes SNMPv2 management
1826 operations by interacting with a non-SNMPv2 device using a
1827 proprietary protocol.
1828
1829 Table 9 presents information about SNMPv2 parties that is
1830 recorded in the SNMPv2 proxy agent's local database of party
1831 information. Table 10 presents information about proxy
1832 relationships that is recorded in the SNMPv2 proxy agent's
1833 local database of context information. Table 11 presents
1834 information about SNMPv2 parties that is recorded in the
1835 SNMPv2 management station's local database of party
1836 information. Table 12 presents information about the database
1837 of access policy information specified by the local
1838 administration.
1839
1840
1841 Identity groucho chico harpo
1842 (manager) (proxy agent) (proxy dst)
1843 Domain snmpUDPDomain snmpUDPDomain acmeMgmtPrtcl
1844 Address 1.2.3.4, 2002 1.2.3.5, 161 0x98765432
1845 Auth Prot v2md5AuthProtocol v2md5AuthProtocol noAuth
1846 Auth Priv Key "0123456789ABCDEF" "GHIJKL0123456789" ""
1847 Auth Pub Key "" "" ""
1848 Auth Clock 0 0 0
1849 Auth Lifetime 300 300 0
1850 Priv Prot noPriv noPriv noPriv
1851 Priv Priv Key "" "" ""
1852 Priv Pub Key "" "" ""
1853
1854
1855 Table 9: Party Information for Proxy Agent
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870 <span class="grey"> Galvin &amp; McCloghrie [Page 33]</span></pre>
1871 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
1872 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1873
1874
1875 Context Proxy Destination Proxy Source Proxy Context
1876 ducksoup harpo n/a n/a
1877
1878
1879 Table 10: Proxy Relationships for Proxy Agent
1880
1881
1882
1883
1884 Identity groucho chico
1885 (manager) (proxy agent)
1886 Domain snmpUDPDomain snmpUDPDomain
1887 Address 1.2.3.4, 2002 1.2.3.5, 161
1888 Auth Prot v2md5AuthProtocol v2md5AuthProtocol
1889 Auth Priv Key "0123456789ABCDEF" "GHIJKL0123456789"
1890 Auth Pub Key "" ""
1891 Auth Clock 0 0
1892 Auth Lifetime 300 300
1893 Priv Prot noPriv noPriv
1894 Priv Priv Key "" ""
1895 Priv Pub Key "" ""
1896
1897
1898 Table 11: Party Information for Management Station
1899
1900
1901
1902
1903 Target Subject Context Privileges
1904 chico groucho ducksoup 35 (Get, GetNext &amp; GetBulk)
1905 groucho chico ducksoup 132 (Response &amp; SNMPv2-Trap)
1906
1907
1908 Table 12: Access Information for Foreign Proxy
1909
1910
1911 As represented in Table 9, the proxy agent party operates at
1912 UDP port 161 at IP address 1.2.3.5 using the party identity
1913 chico; and, the example manager operates at UDP port 2002 at
1914 IP address 1.2.3.4 using the identity groucho. Both groucho
1915 and chico authenticate all messages that they generate by
1916 using the protocol v2md5AuthProtocol and their distinct,
1917 private authentication keys. Although these private
1918 authentication key values ("0123456789ABCDEF" and
1919 "GHIJKL0123456789") are presented here for expository
1920
1921
1922
1923
1924
1925 <span class="grey"> Galvin &amp; McCloghrie [Page 34]</span></pre>
1926 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
1927 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1928
1929
1930 purposes, knowledge of private keys is not normally afforded
1931 to human beings and is confined to those portions of the
1932 protocol implementation that require it.
1933
1934 The party harpo does not send or receive SNMPv2 protocol
1935 messages; rather, all communication with that party proceeds
1936 via a hypothetical proprietary protocol identified by the
1937 value acmeMgmtPrtcl. Because the party harpo does not
1938 participate in the SNMPv2, many of the attributes recorded for
1939 that party in the local database of party information are
1940 ignored.
1941
1942 Table 10 shows the proxy relationships known to the proxy
1943 agent. In particular, the SNMPv2 context ducksoup refers to a
1944 relationship that is satisfied by the party harpo. (The
1945 transport domain of the proxy destination party determines the
1946 interpretation of the proxy source and proxy context
1947 identities - in this case, use of the acmeMgmtPrtcl indicates
1948 that the proxy source and context identities are ignored.)
1949
1950 In order to interrogate the proprietary device associated with
1951 the party harpo, the management station groucho constructs a
1952 SNMPv2 GetNext request contained within a SnmpMgmtCom value
1953 which references the SNMPv2 context ducksoup, and transmits it
1954 to the party chico operating (see Table 11) at UDP port 161,
1955 and IP address 1.2.3.5. This request is authenticated using
1956 the private authentication key "0123456789ABCDEF".
1957
1958 When that request is received by the party chico, the
1959 originator of the message is verified as being the party
1960 groucho by using local knowledge (see Table 9) of the private
1961 authentication key "0123456789ABCDEF". Because party groucho
1962 is authorized to issue GetNext (as well as Get and GetBulk)
1963 requests with respect to party chico and the SNMPv2 context
1964 ducksoup by the relevant access control policy (Table 12), the
1965 request is accepted. Because the local database of context
1966 information indicates that the SNMPv2 context ducksoup refers
1967 to a proxy relationship, the request is satisfied by its
1968 translation into appropriate operations of the acmeMgmtPrtcl
1969 directed at party harpo. These new operations are transmitted
1970 to the party harpo at the address 0x98765432 in the
1971 acmeMgmtPrtcl domain.
1972
1973 When and if the proprietary protocol exchange between the
1974 proxy agent and the proprietary device concludes, a SNMPv2
1975
1976
1977
1978
1979
1980 <span class="grey"> Galvin &amp; McCloghrie [Page 35]</span></pre>
1981 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
1982 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
1983
1984
1985 Response management operation is constructed by the SNMPv2
1986 party chico to relay the results to party groucho again
1987 referring to the SNMPv2 context ducksoup. This response
1988 communication is authenticated as to origin and integrity
1989 using the authentication protocol v2md5AuthProtocol and
1990 private authentication key "GHIJKL0123456789" specified for
1991 transmissions from party chico. It is then transmitted to the
1992 SNMPv2 party groucho operating at the management station at IP
1993 address 1.2.3.4 and UDP port 2002 (the source address for the
1994 corresponding request).
1995
1996 When this response is received by the party groucho, the
1997 originator of the message is verified as being the party chico
1998 by using local knowledge (see Table 11) of the private
1999 authentication key "GHIJKL0123456789". Because party chico is
2000 authorized to issue Response communications with respect to
2001 party groucho and SNMPv2 context ducksoup by the relevant
2002 access control policy (Table 12), the response is accepted,
2003 and the interrogation of the proprietary device is complete.
2004
2005 It is especially useful to observe that the local database of
2006 party information recorded at the proxy agent (Table 9) need
2007 be neither static nor configured exclusively by the management
2008 station. For instance, suppose that, in this example, the
2009 acmeMgmtPrtcl was a proprietary, MAC-layer mechanism for
2010 managing stations attached to a local area network. In such
2011 an environment, the SNMPv2 party chico would reside at a
2012 SNMPv2 proxy agent attached to such a LAN and could, by
2013 participating in the LAN protocols, detect the attachment and
2014 disconnection of various stations on the LAN. In this
2015 scenario, the SNMPv2 proxy agent could easily adjust its local
2016 database of party information to support indirect management
2017 of the LAN stations by the SNMPv2 management station. For
2018 each new LAN station detected, the SNMPv2 proxy agent would
2019 add to its local database of party information an entry
2020 analogous to that for party harpo (representing the new LAN
2021 station itself), and also add to its local database of context
2022 information an entry analogous to that for SNMPv2 context
2023 ducksoup (representing a proxy relationship for that new
2024 station in the SNMPv2 domain).
2025
2026 By using the SNMPv2 to interrogate the local database of party
2027 information held by the SNMPv2 proxy agent, a SNMPv2
2028 management station can discover and interact with new stations
2029 as they are attached to the LAN.
2030
2031
2032
2033
2034
2035 <span class="grey"> Galvin &amp; McCloghrie [Page 36]</span></pre>
2036 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
2037 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2038
2039
2040 4.4.2. Native Proxy Configuration
2041
2042 This section presents an example configuration that supports
2043 SNMPv2 native proxy operations - indirect interaction between
2044 a SNMPv2 agent and a management station that is mediated by a
2045 second SNMPv2 (proxy) agent.
2046
2047 This example configuration is similar to that presented in the
2048 discussion of SNMPv2 foreign proxy above. In this example,
2049 however, the party associated with the identity harpo receives
2050 messages via the SNMPv2, and, accordingly interacts with the
2051 SNMPv2 proxy agent chico using authenticated SNMPv2
2052 communications.
2053
2054 Table 13 presents information about SNMPv2 parties that is
2055 recorded in the SNMPv2 proxy agent's local database of party
2056 information. Table 14 presents information about proxy
2057 relationships that is recorded in the SNMPv2 proxy agent's
2058 local database of context information. Table 11 presents
2059 information about SNMPv2 parties that is recorded in the
2060 SNMPv2 management station's local database of party
2061 information. Table 15 presents information about the database
2062 of access policy information specified by the local
2063 administration.
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090 <span class="grey"> Galvin &amp; McCloghrie [Page 37]</span></pre>
2091 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
2092 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2093
2094
2095 Identity groucho chico
2096 (manager) (proxy agent)
2097 Domain snmpUDPDomain snmpUDPDomain
2098 Address 1.2.3.4, 2002 1.2.3.5, 161
2099 Auth Prot v2md5AuthProtocol v2md5AuthProtocol
2100 Auth Priv Key "0123456789ABCDEF" "GHIJKL0123456789"
2101 Auth Pub Key "" ""
2102 Auth Clock 0 0
2103 Auth Lifetime 300 300
2104 Priv Prot noPriv noPriv
2105 Priv Priv Key "" ""
2106 Priv Pub Key "" ""
2107
2108
2109 Identity harpo zeppo
2110 (proxy dst) (proxy src)
2111 Domain snmpUDPDomain snmpUDPDomain
2112 Address 1.2.3.6, 161 1.2.3.5, 161
2113 Auth Prot v2md5AuthProtocol v2md5AuthProtocol
2114 Auth Priv Key "MNOPQR0123456789" "STUVWX0123456789"
2115 Auth Pub Key "" ""
2116 Auth Clock 0 0
2117 Auth Lifetime 300 300
2118 Priv Prot noPriv noPriv
2119 Priv Priv Key "" ""
2120 Priv Pub Key "" ""
2121
2122
2123 Table 13: Party Information for Proxy Agent
2124
2125
2126
2127
2128 Context Proxy Destination Proxy Source Proxy Context
2129 ducksoup harpo zeppo bigstore
2130 bigstore groucho chico ducksoup
2131
2132
2133 Table 14: Proxy Relationships for Proxy Agent
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145 <span class="grey"> Galvin &amp; McCloghrie [Page 38]</span></pre>
2146 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
2147 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2148
2149
2150 Target Subject Context Privileges
2151 chico groucho ducksoup 35 (Get, GetNext &amp; GetBulk)
2152 groucho chico ducksoup 132 (Response &amp; SNMPv2-Trap)
2153 harpo zeppo bigstore 35 (Get, GetNext &amp; GetBulk)
2154 zeppo harpo bigstore 132 (Response &amp; SNMPv2-Trap)
2155
2156
2157 Table 15: Access Information for Native Proxy
2158
2159
2160 As represented in Table 13, the proxy agent party operates at
2161 UDP port 161 at IP address 1.2.3.5 using the party identity
2162 chico; the example manager operates at UDP port 2002 at IP
2163 address 1.2.3.4 using the identity groucho; the proxy source
2164 party operates at UDP port 161 at IP address 1.2.3.5 using the
2165 party identity zeppo; and, the proxy destination party
2166 operates at UDP port 161 at IP address 1.2.3.6 using the party
2167 identity harpo. Messages generated by all four SNMPv2 parties
2168 are authenticated as to origin and integrity by using the
2169 authentication protocol v2md5AuthProtocol and distinct,
2170 private authentication keys. Although these private
2171 authentication key values ("0123456789ABCDEF",
2172 "GHIJKL0123456789", "MNOPQR0123456789", and
2173 "STUVWX0123456789") are presented here for expository
2174 purposes, knowledge of private keys is not normally afforded
2175 to human beings and is confined to those portions of the
2176 protocol implementation that require it.
2177
2178 Table 14 shows the proxy relationships known to the proxy
2179 agent. In particular, the SNMPv2 context ducksoup refers to a
2180 relationship that is satisfied when the SNMPv2 party zeppo
2181 communicates with the SNMPv2 party harpo and references the
2182 SNMPv2 context bigstore.
2183
2184 In order to interrogate the proxied device associated with the
2185 party harpo, the management station groucho constructs a
2186 SNMPv2 GetNext request contained with a SnmpMgmtCom value
2187 which references the SNMPv2 context ducksoup, and transmits it
2188 to the party chico operating (see Table 11) at UDP port 161
2189 and IP address 1.2.3.5. This request is authenticated using
2190 the private authentication key "0123456789ABCDEF".
2191
2192 When that request is received by the party chico, the
2193 originator of the message is verified as being the party
2194 groucho by using local knowledge (see Table 13) of the private
2195
2196
2197
2198
2199
2200 <span class="grey"> Galvin &amp; McCloghrie [Page 39]</span></pre>
2201 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
2202 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2203
2204
2205 authentication key "0123456789ABCDEF". Because party groucho
2206 is authorized to issue GetNext (as well as Get and GetBulk)
2207 requests with respect to party chico and the SNMPv2 context
2208 ducksoup by the relevant access control policy (Table 15), the
2209 request is accepted. Because the local database of context
2210 information indicates that the SNMPv2 context ducksoup refers
2211 to a proxy relationship, the request is satisfied by its
2212 translation into a corresponding SNMPv2 GetNext request
2213 directed from party zeppo to party harpo referencing SNMPv2
2214 context bigstore. This new communication is authenticated
2215 using the private authentication key "STUVWX0123456789" and
2216 transmitted to party harpo at the IP address 1.2.3.6.
2217
2218 When this new request is received by the party harpo, the
2219 originator of the message is verified as being the party zeppo
2220 by using local knowledge of the private authentication key
2221 "STUVWX0123456789". Because party zeppo is authorized to
2222 issue GetNext (as well as Get and GetBulk) requests with
2223 respect to party harpo and the SNMPv2 context bigstore by the
2224 relevant access control policy (Table 15), the request is
2225 accepted. A SNMPv2 Response message representing the results
2226 of the query is then generated by party harpo to party zeppo
2227 referencing SNMPv2 context bigstore. This response
2228 communication is authenticated as to origin and integrity
2229 using the private authentication key "MNOPQR0123456789" and
2230 transmitted to party zeppo at IP address 1.2.3.5 (the source
2231 address for the corresponding request).
2232
2233 When this response is received by party zeppo, the originator
2234 of the message is verified as being the party harpo by using
2235 local knowledge (see Table 13) of the private authentication
2236 key "MNOPQR0123456789". Because party harpo is authorized to
2237 issue Response communications with respect to party zeppo and
2238 SNMPv2 context bigstore by the relevant access control policy
2239 (Table 15), the response is accepted, and is used to construct
2240 a response to the original GetNext request, indicating a
2241 SNMPv2 context of ducksoup. This response, from party chico
2242 to party groucho, is authenticated as to origin and integrity
2243 using the private authentication key "GHIJKL0123456789" and is
2244 transmitted to the party groucho at IP address 1.2.3.4 (the
2245 source address for the original request).
2246
2247 When this response is received by the party groucho, the
2248 originator of the message is verified as being the party chico
2249 by using local knowledge (see Table 13) of the private
2250
2251
2252
2253
2254
2255 <span class="grey"> Galvin &amp; McCloghrie [Page 40]</span></pre>
2256 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
2257 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2258
2259
2260 authentication key "GHIJKL0123456789". Because party chico is
2261 authorized to issue Response communications with respect to
2262 party groucho and SNMPv2 context ducksoup by the relevant
2263 access control policy (Table 15), the response is accepted,
2264 and the interrogation is complete.
2265
2266
2267 4.5. Public Key Configuration
2268
2269 This section presents an example configuration predicated upon
2270 a hypothetical security protocol. This hypothetical protocol
2271 would be based on asymmetric (public key) cryptography as a
2272 means for providing data origin authentication (but not
2273 protection against disclosure). This example illustrates the
2274 consistency of the administrative model with public key
2275 technology, and the extension of the example to support
2276 protection against disclosure should be apparent.
2277
2278
2279 Identity ollie stan
2280 (agent) (manager)
2281 Domain snmpUDPDomain snmpUDPDomain
2282 Address 1.2.3.4, 161 1.2.3.5, 2004
2283 Auth Prot pkAuthProtocol pkAuthProtocol
2284 Auth Priv Key "0123456789ABCDEF" ""
2285 Auth Pub Key "0123456789abcdef" "ghijkl0123456789"
2286 Auth Clock 0 0
2287 Auth Lifetime 300 300
2288 Priv Prot noPriv noPriv
2289 Priv Priv Key "" ""
2290 Priv Pub Key "" ""
2291
2292
2293 Table 16: Party Information for Public Key Agent
2294
2295
2296 The example configuration comprises a single SNMPv2 agent that
2297 interacts with a single SNMPv2 management station. Tables 16
2298 and 17 present information about SNMPv2 parties that is by the
2299 agent and manager, respectively, while Table 5 presents
2300 information about the local access policy that is known to
2301 both manager and agent.
2302
2303
2304
2305
2306
2307
2308
2309
2310 <span class="grey"> Galvin &amp; McCloghrie [Page 41]</span></pre>
2311 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
2312 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2313
2314
2315 Identity ollie stan
2316 (agent) (manager)
2317 Domain snmpUDPDomain snmpUDPDomain
2318 Address 1.2.3.4, 161 1.2.3.5, 2004
2319 Auth Prot pkAuthProtocol pkAuthProtocol
2320 Auth Priv Key "" "GHIJKL0123456789"
2321 Auth Pub Key "0123456789abcdef" "ghijkl0123456789"
2322 Auth Clock 0 0
2323 Auth Lifetime 300 300
2324 Priv Prot noPriv noPriv
2325 Priv Priv Key "" ""
2326 Priv Pub Key "" ""
2327
2328
2329 Table 17: Party Information for Public Key Management Station
2330
2331
2332 As represented in Table 16, the example agent party operates
2333 at UDP port 161 at IP address 1.2.3.4 using the party identity
2334 ollie; the example manager operates at UDP port 2004 at IP
2335 address 1.2.3.5 using the identity stan. Both ollie and stan
2336 authenticate all messages that they generate as to origin and
2337 integrity by using the hypothetical SNMPv2 authentication
2338 protocol pkAuthProtocol and their distinct, private
2339 authentication keys. Although these private authentication
2340 key values ("0123456789ABCDEF" and "GHIJKL0123456789") are
2341 presented here for expository purposes, knowledge of private
2342 keys is not normally afforded to human beings and is confined
2343 to those portions of the protocol implementation that require
2344 it.
2345
2346 In most respects, the interaction between manager and agent in
2347 this configuration is almost identical to that in the example
2348 of the minimal, secure SNMPv2 agent described above. The most
2349 significant difference is that neither SNMPv2 party in the
2350 public key configuration has knowledge of the private key by
2351 which the other party authenticates its transmissions.
2352 Instead, for each received authenticated SNMPv2 communication,
2353 the identity of the originator is verified by applying an
2354 asymmetric cryptographic algorithm to the received message
2355 together with the public authentication key for the
2356 originating party. Thus, in this configuration, the agent
2357 knows the manager's public key ("ghijkl0123456789") but not
2358 its private key ("GHIJKL0123456789"); similarly, the manager
2359 knows the agent's public key ("0123456789abcdef") but not its
2360
2361
2362
2363
2364
2365 <span class="grey"> Galvin &amp; McCloghrie [Page 42]</span></pre>
2366 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
2367 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2368
2369
2370 private key ("0123456789ABCDEF").
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420 <span class="grey"> Galvin &amp; McCloghrie [Page 43]</span></pre>
2421 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
2422 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2423
2424
2425 5. Security Considerations
2426
2427 In order to participate in the administrative model set forth
2428 in this memo, SNMPv2 implementations must support local, non-
2429 volatile storage of the local database of party information.
2430 Accordingly, every attempt has been made to minimize the
2431 amount of non-volatile storage required.
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475 <span class="grey"> Galvin &amp; McCloghrie [Page 44]</span></pre>
2476 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
2477 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2478
2479
2480 6. Acknowledgements
2481
2482 This document is based, almost entirely, on <a href="./rfc1351">RFC 1351</a>.
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530 <span class="grey"> Galvin &amp; McCloghrie [Page 45]</span></pre>
2531 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
2532 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2533
2534
2535 7. References
2536
2537 [<a id="ref-1">1</a>] Case, J., Fedor, M., Schoffstall, M., Davin, J., "Simple
2538 Network Management Protocol", STD 15, <a href="./rfc1157">RFC 1157</a>, SNMP
2539 Research, Performance Systems International, MIT
2540 Laboratory for Computer Science, May 1990.
2541
2542 [<a id="ref-2">2</a>] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
2543 "Protocol Operations for version 2 of the Simple Network
2544 Management Protocol (SNMPv2)", <a href="./rfc1448">RFC 1448</a>, SNMP Research,
2545 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc.,
2546 Carnegie Mellon University, April 1993.
2547
2548 [<a id="ref-3">3</a>] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
2549 "Structure of Management Information for version 2 of the
2550 Simple Network Management Protocol (SNMPv2)", <a href="./rfc1442">RFC 1442</a>,
2551 SNMP Research, Inc., Hughes LAN Systems, Dover Beach
2552 Consulting, Inc., Carnegie Mellon University, April 1993.
2553
2554 [<a id="ref-4">4</a>] McCloghrie, K., and Galvin, J., "Party MIB for version 2
2555 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1447">RFC</a>
2556 <a href="./rfc1447">1447</a>, Hughes LAN Systems, Trusted Information Systems,
2557 April 1993.
2558
2559 [<a id="ref-5">5</a>] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
2560 "Transport Mappings for version 2 of the Simple Network
2561 Management Protocol (SNMPv2)", <a href="./rfc1449">RFC 1449</a>, SNMP Research,
2562 Inc., Hughes LAN Systems, Dover Beach Consulting, Inc.,
2563 Carnegie Mellon University, April 1993.
2564
2565 [<a id="ref-6">6</a>] Galvin, J., and McCloghrie, K., "Security Protocols for
2566 version 2 of the Simple Network Management Protocol
2567 (SNMPv2)", <a href="./rfc1446">RFC 1446</a>, Trusted Information Systems, Hughes
2568 LAN Systems, April 1993.
2569
2570 [<a id="ref-7">7</a>] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
2571 "Management Information Base for version 2 of the Simple
2572 Network Management Protocol (SNMPv2)", <a href="./rfc1450">RFC 1450</a>, SNMP
2573 Research, Inc., Hughes LAN Systems, Dover Beach
2574 Consulting, Inc., Carnegie Mellon University, April 1993.
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585 <span class="grey"> Galvin &amp; McCloghrie [Page 46]</span></pre>
2586 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
2587 <span class="grey"> <a href="./rfc1445">RFC 1445</a> Administrative Model for SNMPv2 April 1993</span>
2588
2589
2590 8. Authors' Addresses
2591
2592 James M. Galvin
2593 Trusted Information Systems, Inc.
2594 3060 Washington Road, Route 97
2595 Glenwood, MD 21738
2596
2597 Phone: +1 301 854-6889
2598 EMail: [email protected]
2599
2600
2601 Keith McCloghrie
2602 Hughes LAN Systems
2603 1225 Charleston Road
2604 Mountain View, CA 94043
2605 US
2606
2607 Phone: +1 415 966 7934
2608 Email: [email protected]
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640 Galvin &amp; McCloghrie [Page 47]
2641 </pre>