idnits 2.17.00 (12 Aug 2021) /tmp/idnits29753/draft-irtf-nmrg-get-subtree-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 2000) is 7850 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: '16' is mentioned on line 588, but not defined ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) Summary: 17 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Dave Thaler 3 Internet-Draft Microsoft Corporation 4 Expires: May 2001 Satyen Chandragiri 5 Lucent Technologies 6 November 2000 8 Subtree Retrieval MIB 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other 23 documents at any time. It is inappropriate to use Internet- Drafts 24 as reference material or to cite them other than as "work in 25 progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Copyright Notice 35 Copyright (C) The Internet Society (2000). All Rights Reserved. 37 Draft GET-SUBTREE MIB November 2000 39 1. Introduction 41 This memo defines a portion of the Management Information Base 42 (MIB) for use with network management protocols in the Internet 43 community. In particular, it describes managed objects used for 44 retrieving subtrees of MIB objects without the overshoot problems 45 of the SNMP GetBulkRequest operation. 47 2. The SNMP Network Management Framework 49 The SNMP Management Framework presently consists of five major 50 components: 52 o An overall architecture, described in RFC 2571 [1]. 54 o Mechanisms for describing and naming objects and events for 55 the purpose of management. The first version of this 56 Structure of Management Information (SMI) is called SMIv1 and 57 described in RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The 58 second version, called SMIv2, is described in RFC 2578 [5], 59 RFC 2579 [6] and RFC 2580 [7]. 61 o Message protocols for transferring management information. 62 The first version of the SNMP message protocol is called 63 SNMPv1 and described in RFC 1157 [8]. A second version of the 64 SNMP message protocol, which is not an Internet standards 65 track protocol, is called SNMPv2c and described in RFC 1901 66 [9] and RFC 1906 [10]. The third version of the message 67 protocol is called SNMPv3 and described in RFC 1906 [10], RFC 68 2572 [11] and RFC 2574 [12]. 70 o Protocol operations for accessing management information. The 71 first set of protocol operations and associated PDU formats 72 is described in RFC 1157 [8]. A second set of protocol 73 operations and associated PDU formats is described in RFC 74 1905 [13]. 76 o A set of fundamental applications described in RFC 2573 [14] 77 and the view-based access control mechanism described in RFC 78 2575 [15]. 80 Managed objects are accessed via a virtual information store, 81 termed the Management Information Base or MIB. Objects in the MIB 82 are defined using the mechanisms defined in the SMI. 84 Draft GET-SUBTREE MIB November 2000 86 This memo specifies a MIB module that is compliant with the SMIv2. 87 A MIB conforming to the SMIv1 can be produced through the 88 appropriate translations. The resulting translated MIB must be 89 semantically equivalent, except where objects or events are 90 omitted because no translation is possible (use of Counter64). 91 Some machine readable information in SMIv2 will be converted into 92 textual descriptions in SMIv1 during the translation process. 93 However, this loss of machine readable information is not 94 considered to change the semantics of the MIB. 96 3. Overview 98 A major shortcoming of SNMP is the lack of a mechanism to 99 efficiently retrieve large amounts of MIB data from a device. 100 SNMPv1, though widely deployed, contains no provision for bulk 101 retrieval and the manager must use GetNextRequests to traverse the 102 MIB. This requires a large number of request-response exchanges 103 leading to high latency. To address this problem, the 104 GetBulkRequest operation [13] was introduced in SNMPv2. 106 The GetBulkRequest operation aims to minimize the number of 107 protocol exchanges required to retrieve a large amount of 108 management information by returning a series of variable bindings 109 in a single response. The requester is required to specify a "max- 110 repetitions" count, and the agent then fills in as many variable 111 bindings as it can without exceeding either this count, or the 112 maximum message size. 114 The main problem with retrieving tables using GetBulkRequest is 115 that the manager typically does not know the number of rows in the 116 table, and hence cannot set max-repetitions to the optimal value. 117 As a result, the manager must either set max-repetitions to some 118 huge value, resulting in a potentially large waste of bandwidth 119 when many more variable bindings are returned than are needed 120 (sometimes called "overshoot"), or else must issue multiple 121 GetBulkRequests sequentially to traverse a large table such as the 122 routing table in a backbone router. 124 This document describes a MIB that can be used by an application 125 to retrieve MIB information in a more efficient way without any 126 change to the SNMP protocol or SNMP protocol engines. This 127 operation, referred to as a "GetSubtree" request, allows a manager 128 to request the agent to retrieve a subtree of MIB data starting at 129 the root OID (specified by the manager) and including all object 130 Draft GET-SUBTREE MIB November 2000 132 instances whose OID is prefixed by the root OID. The manager is 133 also provided the facility to specify several subtrees of data to 134 be retrieved in parallel by the agent. 136 This approach eliminates the guesswork involved in using the 137 GetBulkRequest operation and makes good use of bandwidth as only 138 those MIB objects of interest to the manager are retrieved (albeit 139 with some overhead). 141 3.1. Structure of the MIB 143 This MIB consists of two tables: 145 o getSubtreeRootTable - this table stores the root OID(s) of 146 the subtree(s) to be retrieved. Rows in this table are 147 indexed by getSubtreeRootOperationID which uniquely 148 identifies the retrieval operation in progress, and a 149 secondary index (getSubtreeRootOIDIndex) which identifies the 150 root OIDs associated with the request. 152 o getSubtreeControlTable - this table stores the main 153 getSubtree request information. The manager must create a row 154 which identifies the application (represented by an entry in 155 the snmpTargetAddrTable) as the response destination. Rows in 156 this table are indexed by getSubtreeRootOperationID from the 157 getSubtreeRootTable. 159 Note: The application must have been pre-configured as a 160 legal notification target in the SNMP-TARGET-MIB [14]. 162 3.2. Operation 164 To set up a retrieval, an application issues a SetRequest to 165 perform a row creation in the getSubtreeRootTable using an 166 arbitrarily selected value for the primary index 167 (getSubtreeRootOperationID), a value of "1" for the secondary 168 index (getSubtreeRootOIDIndex), and the root OID of the subtree to 169 be retrieved. If the application wishes to retrieve multiple 170 subtrees simultaneously, it may do so by creating additional rows 171 for each subtree's root OID using the same primary index value and 172 sequentially increasing values for getSubtreeRootOIDIndex. The 173 purpose of starting the secondary index values at "1" for each new 174 GetSubtree operation is to avoid concurrency problems if another 175 Draft GET-SUBTREE MIB November 2000 177 management application happens to select the same value of the 178 primary index for creating its rows in this table. Note that 179 creating rows in the getSubtreeRootTable in itself does not start 180 the retrieval process. 182 The manager must then create a row in the getSubtreeControlTable 183 using the same value of getSubtreeRootOperationID as the index and 184 identifying itself via the getSubtreeControlTarget object. 185 Creating a row in this table triggers the agent to begin sending 186 traps containing the requested information to the application, so 187 long as there are one or more entries in the getSubtreeRootTable 188 indexed by the same value of getSubtreeRootOperationID. If there 189 are no such entries, then this newly created row in the 190 getSubtreeControlTable will be deleted automatically by the agent. 191 It may also be that a manager may make one or more rows in the 192 getSubtreeRootTable and fail to make any entries in the 193 getSubtreeControlTable to drive the operation. In this case, the 194 agent may choose what to do with these "orphaned" entries. Options 195 include, but are not limited to: letting them exist indefinitely; 196 deleting them after some timeout period has elapsed; or deleting 197 them if there is a resource shortage. The choice is implementation 198 dependent. 200 Each trap generated by the agent contains a sequence number object 201 (which can be used to detect losses), a counter object, a flag 202 object signalling whether the trap is the final one in the 203 sequence, and a series of varbinds containing the next chunk from 204 the requested subtree. The agent will send as many varbinds in the 205 trap as possible without exceeding the maximum message size and 206 without going beyond the subtree. Multiple traps will be sent 207 until the entire subtree has been retrieved. If more than one 208 subtree has been requested, the agent will send repetitions 209 containing varbinds from each subtree until all subtrees have been 210 retrieved. The agent must ensure that each trap contains only an 211 integral number of repetitions. 213 If a manager detects a lost trap (or a sequence of lost traps), it 214 can request that portion of the subtree to be retransmitted using 215 a GetBulkRequest. The counter in each trap indicates the number of 216 repetitions transmitted thus far (including those sent in the 217 current trap). A management application can use this counter as a 218 hint when selecting a value for the max-repetitions field in the 219 GetBulkRequest when sending the retransmission request. 221 Once the entire retrieval operation is complete, the request will 222 Draft GET-SUBTREE MIB November 2000 224 be deleted from getSubtreeControlTable along with all its 225 corresponding rows in getSubtreeRootTable. 227 Furthermore, if the request was in error (e.g., a human entered a 228 different OID from what was intended, causing the application to 229 receive large amounts of unwanted data), the MIB also provides a 230 way to halt an operation in progress, if the agent is able to 231 support this. Halting an operation in progress is accomplished 232 simply by allowing the application to delete the conceptual row in 233 getSubtreeControlTable corresponding to the outstanding operation. 234 If the retrieval operation is successfully aborted, the agent will 235 also automatically delete the rows from getSubtreeRootTable 236 corresponding to that operation. 238 3.3. Limitations 240 The limitations of this approach that come with not changing SNMP 241 include: 243 o To use this MIB to retrieve subtrees of information, the 244 application must be able to issue SETs (at least to this 245 MIB), not just GETs. 247 o The command responder and notification originator need to be 248 tightly coupled, as well as the command generator and 249 notification responder. 251 o The subagent implementing this MIB must be able to call back 252 into the SNMP engine to walk other MIBs, without causing a 253 deadlock. 255 Draft GET-SUBTREE MIB November 2000 257 4. Definitions 259 GET-SUBTREE-MIB DEFINITIONS ::= BEGIN 261 IMPORTS 262 MODULE-IDENTITY, OBJECT-TYPE, 263 NOTIFICATION-TYPE, Unsigned32, 264 Counter32 FROM SNMPv2-SMI 265 RowStatus, TruthValue FROM SNMPv2-TC 266 MODULE-COMPLIANCE, OBJECT-GROUP, 267 NOTIFICATION-GROUP FROM SNMPv2-CONF 268 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 270 getSubtreeMIB MODULE-IDENTITY 271 LAST-UPDATED "0010201200Z" 272 ORGANIZATION "IRTF Network Management Research Group" 273 CONTACT-INFO 274 "Dave Thaler 275 Microsoft Corporation 276 One Microsoft Way 277 Redmond, WA 98052-6399 278 EMail: dthaler@microsoft.com 280 Satyen Chandragiri 281 Lucent Technologies, Inc. 282 101 Crawfords Corner Road 283 Holmdel, NJ 07733-3030 284 EMail: satyen@lucent.com" 285 DESCRIPTION 286 "This MIB module provides the ability to retrieve 287 arbitrary subtrees of OIDs (in parallel) by receiving 288 traps." 289 ::= { XXX } 291 getSubtreeMIBObjects OBJECT IDENTIFIER ::= { getSubtreeMIB 1 } 293 getSubtree OBJECT IDENTIFIER ::= { getSubtreeMIBObjects 1 } 294 getSubtreeTraps OBJECT IDENTIFIER ::= { getSubtreeMIBObjects 2 } 296 -- 297 -- GetSubtree Root Table 298 -- 300 getSubtreeRootTable OBJECT-TYPE 301 Draft GET-SUBTREE MIB November 2000 303 SYNTAX SEQUENCE OF GetSubtreeRootEntry 304 MAX-ACCESS not-accessible 305 STATUS current 306 DESCRIPTION 307 "The (conceptual) table containing the root OID(s) of 308 the MIB subtree(s) to be retrieved. Multiple rows with 309 different values for getSubtreeRootOID may be created 310 if the manager wishes to retrieve several subtrees 311 simultaneously" 312 ::= { getSubtree 1 } 314 getSubtreeRootEntry OBJECT-TYPE 315 SYNTAX GetSubtreeRootEntry 316 MAX-ACCESS not-accessible 317 STATUS current 318 DESCRIPTION 319 "An entry (conceptual row) specifying the root OID of 320 the MIB subtree to be retrieved" 321 INDEX { getSubtreeRootOperationID, getSubtreeRootOIDIndex } 322 ::= { getSubtreeRootTable 1 } 324 GetSubtreeRootEntry ::= SEQUENCE { 325 getSubtreeRootOperationID Unsigned32, 326 getSubtreeRootOIDIndex Unsigned32, 327 getSubtreeRootOID OBJECT IDENTIFIER, 328 getSubtreeRootStatus RowStatus 329 } 331 getSubtreeRootOperationID OBJECT-TYPE 332 SYNTAX Unsigned32 333 MAX-ACCESS not-accessible 334 STATUS current 335 DESCRIPTION 336 "An integer uniquely identifying the GetSubtree 337 operation in progress. This value should be randomly 338 generated by a manager before attempting to create the 339 row." 340 ::= { getSubtreeRootEntry 1 } 342 getSubtreeRootOIDIndex OBJECT-TYPE 343 SYNTAX Unsigned32 344 MAX-ACCESS not-accessible 345 STATUS current 346 DESCRIPTION 347 "An index value used to associate various root OIDs 349 Draft GET-SUBTREE MIB November 2000 351 with the same GetSubtree operation. This value should 352 be one for the first entry associated with a 353 particular retrieval operation and should be 354 sequentially incremented for each additional entry." 355 ::= { getSubtreeRootEntry 2 } 357 getSubtreeRootOID OBJECT-TYPE 358 SYNTAX OBJECT IDENTIFIER 359 MAX-ACCESS read-create 360 STATUS current 361 DESCRIPTION 362 "The root OID of the subtree to be retrieved." 363 ::= { getSubtreeRootEntry 3 } 365 getSubtreeRootStatus OBJECT-TYPE 366 SYNTAX RowStatus 367 MAX-ACCESS read-create 368 STATUS current 369 DESCRIPTION 370 "The status of this row. The manager should create one 371 row for each subtree to be retrieved. After the entire 372 subtree retrieval operation is completed (or if the 373 operation is aborted by the user) all rows in this 374 table corresponding to that operation are 375 automatically deleted by the agent. 377 Objects in this table cannot be modified while a 378 GetSubtree retrieval operation is in progress." 379 ::= { getSubtreeRootEntry 4 } 381 -- 382 -- GetSubtree Control Table 383 -- 385 getSubtreeControlTable OBJECT-TYPE 386 SYNTAX SEQUENCE OF GetSubtreeControlEntry 387 MAX-ACCESS not-accessible 388 STATUS current 389 DESCRIPTION 390 "The (conceptual) table used to control GetSubtree 391 operations in progress. This table is used in 392 conjunction with getSubtreeRootTable. 394 A manager interested in retrieving a subtree of MIB 396 Draft GET-SUBTREE MIB November 2000 398 objects must first create an entry in the 399 getSubtreeRootTable specifying the root OID (s) of the 400 subtree(s) to be retrieved. It must then make a 401 corresponding entry in this table using the same 402 getSubtreeRootOperationID value and identifying itself 403 (via getSubtreeControlTarget) as the recipient of the 404 traps. 406 When the agent completes retrieval of all MIB 407 instances within the specified subtree(s) this 408 conceptual row will be automatically deleted." 409 ::= { getSubtree 2 } 411 getSubtreeControlEntry OBJECT-TYPE 412 SYNTAX GetSubtreeControlEntry 413 MAX-ACCESS not-accessible 414 STATUS current 415 DESCRIPTION 416 "An entry (conceptual row) containing the information 417 on a particular GetSubtree operation in progress." 418 INDEX { getSubtreeRootOperationID } 419 ::= { getSubtreeControlTable 1 } 421 GetSubtreeControlEntry ::= SEQUENCE { 422 getSubtreeControlTarget SnmpAdminString, 423 getSubtreeControlSeqNumber Counter32, 424 getSubtreeControlCount Counter32, 425 getSubtreeControlDone TruthValue, 426 getSubtreeControlStatus RowStatus 427 } 429 getSubtreeControlTarget OBJECT-TYPE 430 SYNTAX SnmpAdminString 431 MAX-ACCESS read-create 432 STATUS current 433 DESCRIPTION 434 "This object selects a management target defined in 435 the snmpTargetAddrTable (in the SNMP-TARGET-MIB). The 436 selected target is defined by an entry in the 437 snmpTargetAddrTable whose index value 438 (snmpTargetAddrName) is equal to this object." 439 ::= { getSubtreeControlEntry 2 } 441 getSubtreeControlSeqNumber OBJECT-TYPE 442 SYNTAX Counter32 444 Draft GET-SUBTREE MIB November 2000 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "The number of trap responses previously sent for this 450 GetSubtree request." 451 ::= { getSubtreeControlEntry 3 } 453 getSubtreeControlCount OBJECT-TYPE 454 SYNTAX Counter32 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The number of repetitions transmitted thus far (up to 459 and including those sent in the current trap)" 460 ::= { getSubtreeControlEntry 4 } 462 getSubtreeControlDone OBJECT-TYPE 463 SYNTAX TruthValue 464 MAX-ACCESS read-only 465 STATUS current 466 DESCRIPTION 467 "This is set to true in the last trap sent, and is set 468 to false otherwise." 469 ::= { getSubtreeControlEntry 5 } 471 getSubtreeControlStatus OBJECT-TYPE 472 SYNTAX RowStatus 473 MAX-ACCESS read-create 474 STATUS current 475 DESCRIPTION 476 "The status of this row, by which new entries may be 477 created, or old entries deleted from this table. Once 478 created, the row may be deleted, but other objects in 479 the row may not be modified. A row (and corresponding 480 rows in the getSubtreeRootTable) will be deleted 481 automatically by the agent once the operation has 482 completed. A row may be created using an instance 483 value for getSubtreeRootOperationID even if no entries 484 exist in getSubtreeRootTable indexed by that value. 486 Creating a row will cause the subtree retrieval 487 operation to commence if there are entries in the 488 getSubtreeRootTable indexed by the same value of 489 getSubtreeRootOperationID as this row. If the agent 490 allows aborting operations in progress, deleting a row 492 Draft GET-SUBTREE MIB November 2000 494 will cause the operation to halt. If the operation is 495 successfully aborted, the rows in the 496 getSubtreeRootTable corresponding to this request will 497 also be automatically deleted by the agent." 498 ::= { getSubtreeControlEntry 6 } 500 -- traps 502 getSubtreeTrapPrefix OBJECT IDENTIFIER ::= { getSubtreeTraps 0 } 504 getSubtreeResponse NOTIFICATION-TYPE 505 OBJECTS { 506 getSubtreeControlSeqNumber, 507 getSubtreeControlCount, 508 getSubtreeControlDone 509 } 510 STATUS current 511 DESCRIPTION 512 "In addition to the three objects above, this trap 513 also contains a series of varbinds containing the next 514 chunk of the subtree. The generating entity will 515 append, in order, as many variables to the variable- 516 bindings field as it can without exceeding the maximum 517 message size, and without going beyond the subtree of 518 OIDs requested. A series of such traps will be 519 generated until the end of the subtree is reached." 520 ::= { getSubtreeTrapPrefix 1 } 522 -- conformance information 524 getSubtreeMIBConformance 525 OBJECT IDENTIFIER ::= { getSubtreeMIB 2 } 526 getSubtreeMIBCompliances 527 OBJECT IDENTIFIER ::= { getSubtreeMIBConformance 1 } 528 getSubtreeMIBGroups OBJECT IDENTIFIER ::= { getSubtreeMIBConformance 2 } 530 -- compliance statements 532 getSubtreeMIBCompliance MODULE-COMPLIANCE 533 STATUS current 534 DESCRIPTION 535 "The compliance statement for the GetSubtree MIB." 536 MODULE -- this module 537 MANDATORY-GROUPS { 539 Draft GET-SUBTREE MIB November 2000 541 getSubtreeObjectGroup, 542 getSubtreeNotificationGroup 543 } 544 ::= { getSubtreeMIBCompliances 1 } 546 -- units of conformance 548 getSubtreeObjectGroup OBJECT-GROUP 549 OBJECTS { 550 getSubtreeRootOID, 551 getSubtreeRootStatus, 552 getSubtreeControlTarget, 553 getSubtreeControlSeqNumber, 554 getSubtreeControlCount, 555 getSubtreeControlDone, 556 getSubtreeControlStatus 557 } 558 STATUS current 559 DESCRIPTION 560 "A collection of objects to support requests for 561 subtree retrieval operations." 562 ::= { getSubtreeMIBGroups 1 } 564 getSubtreeNotificationGroup NOTIFICATION-GROUP 565 NOTIFICATIONS { getSubtreeResponse } 566 STATUS current 567 DESCRIPTION 568 "The notification which an entity is required to 569 implement." 570 ::= { getSubtreeMIBGroups 2 } 572 END 573 Draft GET-SUBTREE MIB November 2000 575 5. Security Considerations 577 While unauthorized read access to the objects in this MIB is 578 relatively innocuous, unauthorized write access could trigger 579 sending of a potentially large amount of data to an authorized 580 notification receiver, which could be viewed as a denial-of- 581 service attack. 583 Hence, the support for SNMP operations in a non-secure environment 584 without proper protection can have a negative effect on network 585 operations. 587 SNMPv1 by itself is such an insecure environment. Even if the 588 network itself is secure (for example by using IPSec [16]), even 589 then, there is no control as to who on the secure network is 590 allowed to access and SET (change/create/delete) the objects in 591 this MIB. 593 It is recommended that the implementers consider the security 594 features as provided by the SNMPv3 framework. Specifically, the 595 use of the User-based Security Model RFC 2274 [12] and the View- 596 based Access Control Model RFC 2275 [15] is recommended. 598 It is then a customer/user responsibility to ensure that the SNMP 599 entity giving access to this MIB, is properly configured to give 600 access to those objects only to those principals (users) that have 601 legitimate rights to access them. 603 6. Authors' Addresses 605 Dave Thaler 606 Microsoft Corporation 607 One Microsoft Way 608 Redmond, WA 98052-6399 609 Phone: +1 425 703 8835 610 EMail: dthaler@microsoft.com 612 Satyen Chandragiri 613 Lucent Technologies, Inc. 614 101 Crawfords Corner Road 615 Holmdel, NJ 07733-3030 616 Phone: +1 732 949 2080 617 EMail: satyen@lucent.com 619 Draft GET-SUBTREE MIB November 2000 621 7. References 623 [1] Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture 624 for Describing SNMP Management Frameworks", RFC 2571, 625 Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson 626 Research, April 1999. 628 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 629 Management Information for TCP/IP-based Internets", STD 16, 630 RFC 1155, Performance Systems International, Hughes LAN 631 Systems, May 1990. 633 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 634 16, RFC 1212, Performance Systems International, Hughes LAN 635 Systems, March 1991. 637 [4] M. Rose, "A Convention for Defining Traps for use with the 638 SNMP", RFC 1215, Performance Systems International, March 639 1991. 641 [5] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure 642 of Management Information Version 2 (SMIv2)", STD 58, RFC 643 2578, April 1999. 645 [6] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual 646 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 648 [7] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 649 "Conformance Statements for SMIv2", STD 58, RFC 2580, April 650 1999. 652 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 653 Network Management Protocol", STD 15, RFC 1157, SNMP 654 Research, Performance Systems International, Performance 655 Systems International, MIT Laboratory for Computer Science, 656 May 1990. 658 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 659 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 660 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 661 Inc., International Network Services, January 1996. 663 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 664 "Transport Mappings for Version 2 of the Simple Network 665 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 667 Draft GET-SUBTREE MIB November 2000 669 Cisco Systems, Inc., Dover Beach Consulting, Inc., 670 International Network Services, January 1996. 672 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 673 Processing and Dispatching for the Simple Network Management 674 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron 675 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 676 April 1999. 678 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model 679 (USM) for version 3 of the Simple Network Management Protocol 680 (SNMPv3)", RFC 2574, IBM T. J. Watson Research, April 1999. 682 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 683 "Protocol Operations for Version 2 of the Simple Network 684 Management Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., 685 Cisco Systems, Inc., Dover Beach Consulting, Inc., 686 International Network Services, January 1996. 688 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 689 RFC 2573, SNMP Research, Inc., Secure Computing Corporation, 690 Cisco Systems, April 1999. 692 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 693 Access Control Model (VACM) for the Simple Network Management 694 Protocol (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC 695 Software, Inc., Cisco Systems, Inc., April 1999. 697 8. Full Copyright Statement 699 Copyright (C) The Internet Society (2000). All Rights Reserved. 701 This document and translations of it may be copied and furnished 702 to others, and derivative works that comment on or otherwise 703 explain it or assist in its implmentation may be prepared, copied, 704 published and distributed, in whole or in part, without 705 restriction of any kind, provided that the above copyright notice 706 and this paragraph are included on all such copies and derivative 707 works. However, this document itself may not be modified in any 708 way, such as by removing the copyright notice or references to the 709 Internet Society or other Internet organizations, except as needed 710 for the purpose of developing Internet standards in which case the 711 procedures for copyrights defined in the Internet Standards 712 process must be followed, or as required to translate it into 713 Draft GET-SUBTREE MIB November 2000 715 languages other than English. 717 The limited permissions granted above are perpetual and will not 718 be revoked by the Internet Society or its successors or assigns. 720 This document and the information contained herein is provided on 721 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 722 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 723 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 724 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 725 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.