idnits 2.17.1 draft-ietf-rmonmib-pmcaps-01.txt: ** The Abstract section seems to be numbered 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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** 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? == 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 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 are 5 instances 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 == Line 1130 has weird spacing: '...imed to perta...' -- 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 (14 July 2000) is 8680 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: 'TBD' is mentioned on line 1078, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'APM' -- Possible downref: Non-RFC (?) normative reference: ref. 'TPM' ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2021 (Obsoleted by RFC 4502) ** Downref: Normative reference to an Informational RFC: RFC 2330 ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2679 (Obsoleted by RFC 7679) ** Obsolete normative reference: RFC 2680 (Obsoleted by RFC 7680) Summary: 22 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Andy Bierman 3 Cisco Systems, Inc. 4 14 July 2000 6 Performance Measurement Capabilities MIB 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with all 13 provisions of Section 10 of RFC2026 [RFC2026]. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF), its areas, and its working groups. Note that other groups 17 may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet- Drafts as reference material 22 or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Distribution of this document is unlimited. Please send comments to the 31 authors. 33 1. Copyright Notice 35 Copyright (C) The Internet Society (2000). All Rights Reserved. 37 2. Abstract 39 This memo defines a portion of the Management Information Base (MIB) for 40 use with network management protocols in the Internet community. In 41 particular, it describes managed objects used for classifying and 42 characterizing the performance measurement (PM) capabilities of various 43 standard and proprietary PM techniques. 45 3. Table of Contents 47 1 Copyright Notice ................................................ 1 48 2 Abstract ........................................................ 1 49 3 Table of Contents ............................................... 2 50 4 The SNMP Management Framework ................................... 3 51 5 Overview ........................................................ 4 52 5.1 Terms ......................................................... 4 53 5.1.1 Performance Measurement (PM) ................................ 4 54 5.1.2 PM Data ..................................................... 4 55 5.1.3 APM Device .................................................. 4 56 5.1.4 TPM Device .................................................. 5 57 5.1.5 PM Collection Point ......................................... 5 58 5.1.6 PM Study Class .............................................. 5 59 5.1.7 PM Study .................................................... 5 60 5.1.8 PM Report Class ............................................. 6 61 5.1.9 APM Report .................................................. 6 62 5.1.10 TPM Report ................................................. 6 63 5.1.11 PM Location ................................................ 6 64 5.1.12 PM Class ................................................... 6 65 5.2 Relationship to RMON-2 MIB .................................... 7 66 5.3 Relationship to IPPM .......................................... 7 67 5.4 Relationship to Other MIBs .................................... 7 68 6 PM Framework Components ......................................... 7 69 6.1 Performance Criteria .......................................... 7 70 6.2 Performance Measurement Granularity ........................... 8 71 6.3 Network Traffic Selection Criteria ............................ 8 72 6.4 Network Traffic Generation Configuration ...................... 8 73 6.5 Set of Metrics ................................................ 8 74 6.6 PM Study Class Capabilities ................................... 8 75 6.7 PM Collection Point Location .................................. 9 76 6.8 PM Study Configuration ........................................ 9 77 6.9 PM Study Results Storage and Retrieval ........................ 9 78 7 PM Caps MIB Groups .............................................. 9 79 7.1 PM Capabilities ............................................... 9 80 8 Definitions ..................................................... 9 81 9 Intellectual Property ........................................... 27 82 10 References ..................................................... 27 83 11 Security Considerations ........................................ 31 84 12 Author's Address ............................................... 32 85 13 Full Copyright Statement ....................................... 33 86 4. The SNMP Management Framework 88 The SNMP Management Framework presently consists of five major 89 components: 91 o An overall architecture, described in RFC 2571 [RFC2571]. 93 o Mechanisms for describing and naming objects and events for the 94 purpose of management. The first version of this Structure of 95 Management Information (SMI) is called SMIv1 and described in 96 RFC 1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. 97 The second version, called SMIv2, is described in RFC 2578 98 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 [RFC2580]. 100 o Message protocols for transferring management information. The 101 first version of the SNMP message protocol is called SNMPv1 and 102 described in RFC 1157 [RFC1157]. A second version of the SNMP 103 message protocol, which is not an Internet standards track 104 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 105 and RFC 1906 [RFC1906]. The third version of the message 106 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 107 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 109 o Protocol operations for accessing management information. The 110 first set of protocol operations and associated PDU formats is 111 described in RFC 1157 [RFC1157]. A second set of protocol 112 operations and associated PDU formats is described in RFC 1905 113 [RFC1905]. 115 o A set of fundamental applications described in RFC 2573 116 [RFC2573] and the view-based access control mechanism described 117 in RFC 2575 [RFC2575]. 119 A more detailed introduction to the current SNMP Management Framework 120 can be found in RFC 2570 [RFC2570]. 122 Managed objects are accessed via a virtual information store, termed 123 the Management Information Base or MIB. Objects in the MIB are 124 defined using the mechanisms defined in the SMI. 126 This memo specifies a MIB module that is compliant to the SMIv2. A 127 MIB conforming to the SMIv1 can be produced through the appropriate 128 translations. The resulting translated MIB must be semantically 129 equivalent, except where objects or events are omitted because no 130 translation is possible (use of Counter64). Some machine readable 131 information in SMIv2 will be converted into textual descriptions in 132 SMIv1 during the translation process. However, this loss of machine 133 readable information is not considered to change the semantics of the 134 MIB. 136 5. Overview 138 There is a need for a standardized way of characterizing the performance 139 measurement capabilities of remote monitoring tools which provide 140 statistics based on these measurements. There are many different 141 techniques for measuring and characterizing the performance of specific 142 network-based applications available at this time. A standardized 143 framework for describing the capabilities of a particular technique is 144 needed as a pre-requisite for a standardized Performance Measurement 145 results reporting framework. 147 This memo addresses the specific requirements of the Performance 148 Measurement capabilities framework. Other aspects of this framework, 149 such as configuration and results reporting are not addressed in this 150 memo. 152 5.1. Terms 154 Some new terms are used throughout this document: 156 5.1.1. Performance Measurement (PM) 158 This term refers to any implementation-specific PM Data collection 159 mechanism, for the purpose of instrumenting the Application Performance 160 Measurement (APM) MIB [APM] and/or the Transport Performance Metrics 161 (TPM) MIB [TPM]. 163 5.1.2. PM Data 165 The actual measurements, kept in some internal representation, collected 166 from one or more PM Collection Points. This data is converted into one 167 or more APM and/or TPM Reports, in an implementation-specific manner. 169 5.1.3. APM Device 171 A device which contains an SNMP agent which implements the APM MIB. For 172 the purpose of the standard, the APM device is the entity that is 173 reporting the APM results, in the form of standard MIB objects. An APM 174 Device can obtain PM data from one or more PM Collection Points. 176 5.1.4. TPM Device 178 A device which contains an SNMP agent which implements the TPM MIB. For 179 the purpose of the standard, the TPM device is the entity that is 180 reporting the TPM results, in the form of standard MIB objects. A TPM 181 Device can obtain PM data from one or more PM Collection Points. 183 5.1.5. PM Collection Point 185 The general location, within the spectrum of possible vantage points, 186 that PM Data is collected, for one or more APM or TPM Studies (and 187 perhaps more than one APM or TPM device). The interaction between an 188 APM or TPM device and a PM Collection Point is outside the scope of this 189 standard. 191 5.1.6. PM Study Class 193 The unique set of mechanisms and parameters that classifies and 194 identifies a particular APM or TPM collection capability. E.g., 196 - the set of protocols collected 198 - test attributes (standard and proprietary) 200 - collection technique(s) 202 - PM Collection Point information 204 - report capabilities 206 - vendor-specific Study Class ID 208 5.1.7. PM Study 210 This is an instantiation of a particular PM Study Class, for the purpose 211 of generating APM and/or TPM reports. Some parameters, such as: 213 - the dataSource to monitor 215 - any resource restrictions to enforce 217 - the specific set of result data to collect 219 are relevant only in the context of an PM Study, not a PM Study Class. 221 5.1.8. PM Report Class 223 The type of APM or TPM report produced on behalf of a particular PM 224 Study Class. E.g., 226 - distribution-based aggregation 228 - statistica-based aggregation 230 - exception-based reporting 232 5.1.9. APM Report 234 The set of result data for a particular PM Study. This is in the form 235 of standard MIB objects and notifications in the APM MIB [APM]. 237 5.1.10. TPM Report 239 The set of result data for a particular PM Study. This is in the form 240 of standard MIB objects and notifications in the TPM MIB [TPM]. 242 5.1.11. PM Location 244 The notion of where a PM Collection Point is obtaining PM Data. At the 245 highest level, the possible locations are: 247 - client 249 - network 251 - server 253 5.1.12. PM Class 255 At the highest level, there are three classes of PM technology. 257 - passive collection 258 No test traffic is introduced into the system being measured. PM 259 Data is derived from observable 'user activity' in the actual 260 operating environment. 262 - active collection 263 Some form of test traffic is introduced into the system being 264 measured. PM Data is derived from measured attributes of this test 265 traffic. 267 - built-in collection 268 Measurement mechanisms are somehow embedded in actual network 269 traffic, for the purpose of PM Data collection. PM Data is derived 270 from measured attributes, via these built-in mechanisms. 272 5.2. Relationship to RMON-2 MIB 274 This MIB uses the protocolDirTable [RFC2021] to identify the protocols 275 which are relevant to a particular PM Study Class. Implementation of the 276 protocolDirectoryGroup is required. 278 5.3. Relationship to IPPM 280 This MIB uses the Metric definitions found in IPPM documents ([RFC2330] 281 [RFC2678] [RFC2679] [RFC2680] [RFC2681]) to define derived metrics for 282 use with the APM and TPM MIBs. 284 5.4. Relationship to Other MIBs 286 This MIB assumes that a standard Application Performance Measurement MIB 287 [APM] will be produced, which will provide support for basic 288 configuration and collection of APM Reports. 290 This MIB also assumes that a standard Transport Performance Measurement 291 MIB [TPM] will be produced, which will provide additional 'drill-down' 292 support for transport layer protocols and additional metrics not 293 directly supported by the APM MIB. 295 6. PM Framework Components 297 A PM Study is executed and reported within the PM Framework. Usually, 298 some sort of network infrastructure is assumed, in which client devices, 299 application servers, forwarding devices, and one or more PM monitoring 300 devices are connected. However, non-networking based methodologies can 301 also be used. 303 Some basic attributes of the PM Framework are listed below. 305 6.1. Performance Criteria 307 A set of network, transport, and/or application performance criteria is 308 needed, based on some combination of network traffic attributes. The 309 specification and evaluation of performance test results is beyond the 310 scope of this document. 312 6.2. Performance Measurement Granularity 314 Each PM Study Class explicitly defines the granularity of the test, in 315 terms of the purpose, selected metrics, and other attributes. 317 6.3. Network Traffic Selection Criteria 319 For PM techniques which monitor or generate network traffic, a set of 320 rules is needed which specifies which packets will be included for 321 measurement in a particular performance test. This includes device 322 attributes such as interface identity, and packet attributes such as 323 VLAN ID, QoS value, IP subnet or host addresses, application type(s), 324 and application payload. 326 6.4. Network Traffic Generation Configuration 328 Active PM techniques require that the traffic generation mechanism(s) be 329 properly configured prior to execution of any PM Studies. These 330 configuration requirements are outside the scope of this document. 332 6.5. Set of Metrics 334 For each PM Study Class, there are one or more metrics, appropriate for 335 the associated network traffic and performance selection criteria, which 336 are measured by the APM and/or TPM device(s) used for an individual PM 337 Study. 339 6.6. PM Study Class Capabilities 341 For each PM Study Class supported by an APM or TPM Device, there is a 342 set of capabilities associated with the selected set of metrics and 343 performance criteria. There is also a set of possible report output 344 capabilities associated with each class. 346 6.7. PM Collection Point Location 348 The physical location of each PM Collection Point is an important 349 attribute of each PM Study Class. 351 +------------+ +---------+ +----------+ +----------+ 352 | | | Last | | Last Hop | | | 353 | Client |<-->| Hop for |<--> ... <-->| for Net |<-->| Network | 354 | | | Client | | Service | | Service | 355 +------------+ +---------+ +----------+ +----------+ 357 <------------- Measurement Device Location ------------> 359 For the purposes of this MIB, a PM Collection Point resides in either 360 the 'client', the 'network', or the 'server'. 362 6.8. PM Study Configuration 364 Each PM Study may require some combination of generic and test-specific 365 configuration commands in order to prepare the network environment for 366 measurement. Specific PM Study configuration mechanisms are beyond the 367 scope of this document. 369 6.9. PM Study Results Storage and Retrieval 371 Each APM or TPM Device must be able to store the APM or TPM Reports 372 generated on behalf of each PM Study, and convey these reports to a 373 management application. The specification of these mechanisms are 374 beyond the scope of this document. 376 7. PM Caps MIB Groups 378 The PM Caps MIB contains one MIB group. 380 7.1. PM Capabilities 382 This group contains MIB objects used to report the capabilities of the 383 PM Study Classes supported by a particular APM or TPM Device. 385 8. Definitions 387 PMCAPS-MIB DEFINITIONS ::= BEGIN 389 IMPORTS 390 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32 391 FROM SNMPv2-SMI 392 TruthValue, RowPointer 393 FROM SNMPv2-TC 394 MODULE-COMPLIANCE, OBJECT-GROUP 395 FROM SNMPv2-CONF 396 SnmpAdminString 397 FROM SNMP-FRAMEWORK-MIB 398 rmon 399 FROM RMON-MIB 400 protocolDirLocalIndex, protocolDirectoryGroup 401 PROM RMON2-MIB; 403 pmCapsMIB MODULE-IDENTITY 404 LAST-UPDATED "200007140000Z" 405 ORGANIZATION "IETF RMONMIB WG" 406 CONTACT-INFO 407 " Andy Bierman 408 Cisco Systems, Inc. 409 RMONMIB WG Chair and PMCAPS MIB Editor 411 Postal: 170 West Tasman Drive 412 San Jose, CA USA 95134 413 Tel: +1 408 527-3711 414 E-mail: abierman@cisco.com 416 Send comments to 417 Mailing list subscription information: 418 http://www.ietf.org/mailman/listinfo/rmonmib " 419 DESCRIPTION 420 "The MIB module for representing Performance 421 Measurement Capabilities." 422 REVISION "200007140000Z" 423 DESCRIPTION 424 "Initial Version of the Performance Measurement 425 Capabilities MIB." 426 ::= { rmon 25 } 428 pmCapsMIBObjects OBJECT IDENTIFIER ::= { pmCapsMIB 1 } 429 pmCaps OBJECT IDENTIFIER ::= { pmCapsMIBObjects 1 } 430 pmMetrics OBJECT IDENTIFIER ::= { pmCapsMIBObjects 2 } 432 -- 433 -- PM Metric Table 434 -- 435 pmMetricTable OBJECT-TYPE 436 SYNTAX SEQUENCE OF PmMetricEntry 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "This table contains one row per PM Metric supported by this 441 agent, and should be populated during system 442 initialization." 443 ::= { pmCaps 1 } 445 pmMetricEntry OBJECT-TYPE 446 SYNTAX PmMetricEntry 447 MAX-ACCESS not-accessible 448 STATUS current 449 DESCRIPTION 450 "Information about a particular PM Metric." 451 INDEX { pmMetricID } 452 ::= { pmMetricTable 1 } 454 PmMetricEntry ::= SEQUENCE { 455 pmMetricID OBJECT IDENTIFIER, 456 pmMetricType INTEGER, 457 pmMetricDirType INTEGER, 458 pmMetricName SnmpAdminString, 459 pmMetricReference SnmpAdminString 460 } 462 pmMetricID OBJECT-TYPE 463 SYNTAX OBJECT IDENTIFIER 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "The index for this entry. This object identifies the 468 standard or vendor-specific registration OBJECT IDENTIFER 469 defined for a particular PM metric." 470 ::= { pmMetricEntry 1 } 472 pmMetricType OBJECT-TYPE 473 SYNTAX INTEGER { 474 other(1), 475 connectMetric(2), 476 delayMetric(3), 477 lossMetric(4) 478 } 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The basic type of metric indicated by this entry. 484 The value 'other(1)' indicates that this metric cannot be 485 characterized by any of the remaining enumerations specified 486 for this object. 488 The value 'connectMetric(2)' indicates that this metric 489 measures connectivity characteristics. 491 The value 'delayMetric(3)' indicates that this metric 492 measures delay characteristics. 494 The value 'lossMetric(4)' indicates that this metric 495 measures loss characteristics." 496 ::= { pmMetricEntry 2 } 498 pmMetricDirType OBJECT-TYPE 499 SYNTAX INTEGER { 500 oneWay(1), 501 twoWay(2), 502 multiWay(3) 503 } 504 MAX-ACCESS read-only 505 STATUS current 506 DESCRIPTION 507 "The directional characteristics of the this metric. 509 The value 'oneWay(1)' indicates that this metric is measured 510 with some sort of uni-directional test. 512 The value 'twoWay(2)' indicates that this metric is measured 513 with some sort of bi-directional test. 515 The value 'multiWay(3)' indicates that this metric is 516 measured with some combination of uni-directional and/or bi- 517 directional tests." 518 ::= { pmMetricEntry 3 } 520 pmMetricName OBJECT-TYPE 521 SYNTAX SnmpAdminString 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The textual name of this metric." 526 ::= { pmMetricEntry 4 } 528 pmMetricReference OBJECT-TYPE 529 SYNTAX SnmpAdminString 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "This object contains a reference to the document which 534 defines this metric. If this document is available online 535 via electronic download, then a URL should be specified in 536 this object. 538 For example, if this pmMetricEntry identified the IPPM 539 metric 'Type-P-Round-Trip-Delay', then this object should 540 contain the value 'http://www.ietf.org/rfc/rfc2681.txt'." 541 ::= { pmMetricEntry 5 } 543 -- 544 -- PM Study Class Table 545 -- 547 pmStudyClassTable OBJECT-TYPE 548 SYNTAX SEQUENCE OF PmStudyClassEntry 549 MAX-ACCESS not-accessible 550 STATUS current 551 DESCRIPTION 552 "This table contains one row per PM Study Class supported by 553 this APM/TPM Device, and should be populated during system 554 initialization." 555 ::= { pmCaps 2 } 557 pmStudyClassEntry OBJECT-TYPE 558 SYNTAX PmStudyClassEntry 559 MAX-ACCESS not-accessible 560 STATUS current 561 DESCRIPTION 562 "Information about a particular PM Study Class." 563 INDEX { pmStudyClassID } 564 ::= { pmStudyClassTable 1 } 566 PmStudyClassEntry ::= SEQUENCE { 567 pmStudyClassID OBJECT IDENTIFIER, 568 pmStudyClassMeasLoc BITS, 569 pmStudyClassMeasType BITS, 570 pmStudyClassCollectPts Integer32, 571 pmStudyClassCollectCaps BITS, 572 pmStudyClassOutputCaps BITS, 573 pmStudyClassCtlTablePtr RowPointer 574 } 576 pmStudyClassID OBJECT-TYPE 577 SYNTAX OBJECT IDENTIFIER 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "The index for this entry. This object identifier should 582 specify the standard or vendor-specific registration OID for 583 this PM Study Class." 584 ::= { pmStudyClassEntry 1 } 586 pmStudyClassMeasLoc OBJECT-TYPE 587 SYNTAX BITS { 588 pmClient(0), 589 pmNetwork(1), 590 pmServer(2) 591 } 592 MAX-ACCESS read-only 593 STATUS current 594 DESCRIPTION 595 "The measurement location characteristics of the PM Data 596 collection methodologies employed by this PM Study Class. 598 If this PM Study class utilizes some sort of measurement 599 technology located on the host machine being monitored, then 600 the 'pmClient' BIT will be set. Note that this bit should 601 only be set if any PM technology is installed on the client, 602 in addition to the 'normal' protocol operations supported by 603 that machine. 605 If this PM Study class utilizes some sort of measurement 606 technology located on one or more networking devices (e.g., 607 routers, switches, RMON probes), then the 'pmNetwork' BIT 608 will be set. 610 If this PM Study class utilizes some sort of measurement 611 technology located on the application server being 612 monitored, then the 'pmServer' BIT will be set. Note that 613 this bit should only be set if any PM technology is 614 installed on the server, in addition to the 'normal' 615 protocol operations supported by that machine." 616 ::= { pmStudyClassEntry 2 } 618 pmStudyClassMeasType OBJECT-TYPE 619 SYNTAX BITS { 620 pmPassive(0), 621 pmActive(1), 622 pmBuiltin(2) 623 } 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The type(s) of collection methodologies employed by this PM 628 Study Class. 630 If this PM Study class utilizes some sort of passive 631 monitoring technology, (i.e., UI operations and/or protocol 632 transactions of real users are measured) the 'pmPassive' BIT 633 will be set. 635 If this PM Study class utilizes some sort of active 636 monitoring technology, (i.e., protocol transactions 637 generated for the purpose of obtaining PM Data) the 638 'pmPassive' BIT will be set. 640 If this PM Study class utilizes some sort of built-in 641 monitoring technology, (i.e., UI operations and/or protocol 642 transactions of real users are somehow altered to provide PM 643 Data) the 'pmBuiltin' BIT will be set." 644 ::= { pmStudyClassEntry 3 } 646 pmStudyClassCollectPts OBJECT-TYPE 647 SYNTAX Integer32 (1..2147483647) 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "The number of PM Collection Points utilized in this PM 652 Study Class. If this is a variable quantity, then this 653 object should contain the minimum number needed for this PM 654 Study Class to function." 655 ::= { pmStudyClassEntry 4 } 657 pmStudyClassCollectCaps OBJECT-TYPE 658 SYNTAX BITS { 659 pmCollectTrans(0), 660 pmCollectApp(1), 661 pmCollectFlow(2), 662 pmCollectNonNet(3) 663 } 664 MAX-ACCESS read-only 665 STATUS current 666 DESCRIPTION 667 "This object identifies some generic characteristics of the 668 collection methodologies employed by this PM Study Class. 670 If this PM Study class utilizes some sort of transport layer 671 PM Data collection technology, then the 'pmCollectTrans' BIT 672 will be set. 674 If this PM Study class utilizes some sort of application 675 layer PM Data collection technology, then the 'pmCollectApp' 676 BIT will be set. 678 If this PM Study class utilizes PM Data collection 679 technology based on monitoring of some sort of network flow 680 summary information, then the 'pmCollectFlow' BIT will be 681 set. 683 If this PM Study class utilizes some sort of PM Data 684 collection technology based on monitoring of non-network 685 events, such as UI monitoring of window events, then the 686 'pmCollectNonNet' BIT will be set." 687 ::= { pmStudyClassEntry 5 } 689 pmStudyClassOutputCaps OBJECT-TYPE 690 SYNTAX BITS { 691 pmOutputOther(0), 692 pmOutputApmDist(1), 693 pmOutputApmStat(2), 694 pmOutputApmHist(3), 695 pmOutputApmFlow(4), 696 pmOutputApmExcept(5), 697 pmOutputApmProp(6), 698 pmOutputTpmDist(7), 699 pmOutputTpmStat(8), 700 pmOutputTpmHist(9), 701 pmOutputTpmExcept(10), 702 pmOutputTpmProp(11) 703 } 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "The type(s) of APM and/or TPM Reports that this PM Study 708 Class can provide. [ed. - this list will change as the APM 709 and TPM MIBs are finalized.] 711 If this PM Study class can generate standard reports not 712 described by any of the provided BITS here, then the 713 'pmOutputOther' BIT will be set. 715 If this PM Study class can generate distribution-oriented 716 reports for application layer protocols, then the 717 'pmOutputApmDist' BIT will be set. 719 If this PM Study class can generate statistics-oriented 720 reports for application layer protocols, then the 721 'pmOutputApmStat' BIT will be set. 723 If this PM Study class can generate historical analysis 724 oriented reports for application layer protocols, then the 725 'pmOutputApmHist' BIT will be set. 727 If this PM Study class can generate flow decomposition 728 analysis oriented reports for application layer protocols, 729 then the 'pmOutputApmFlow' BIT will be set. 731 If this PM Study class can generate profile exception 732 oriented reports for application layer protocols, then the 733 'pmOutputApmExcept' BIT will be set. 735 If this PM Study class can generate vendor-specific 736 proprietary reports for application layer protocols, in 737 addition to standard reports, then the 'pmOutputApmProp' BIT 738 will be set. 740 If this PM Study class can generate distribution-oriented 741 reports for transport layer protocols, then the 742 'pmOutputTpmDist' BIT will be set. 744 If this PM Study class can generate statistics-oriented 745 reports for transport layer protocols, then the 746 'pmOutputTpmStat' BIT will be set. 748 If this PM Study class can generate historical analysis 749 oriented reports for transport layer protocols, then the 750 'pmOutputTpmHist' BIT will be set. 752 If this PM Study class can generate flow decomposition 753 analysis oriented reports for transport layer protocols, 754 then the 'pmOutputTpmFlow' BIT will be set. 756 If this PM Study class can generate profile exception 757 oriented reports for transport layer protocols, then the 758 'pmOutputTpmExcept' BIT will be set. 760 If this PM Study class can generate vendor-specific 761 proprietary reports for transport layer protocols, in 762 addition to standard reports, then the 'pmOutputTpmProp' BIT 763 will be set." 764 ::= { pmStudyClassEntry 6 } 766 pmStudyClassCtlTablePtr OBJECT-TYPE 767 SYNTAX RowPointer 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "This object identifies a specific MIB table that can be 772 used to configure detailed aspects of the collection or 773 report processing functions for this PM Study Class. 775 This object just identifies a particular row in the MIB 776 table to use, not any particular agent which implements this 777 MIB table. This agent may or may not contain an 778 implementation of the specified MIB, and/or the specified 779 MIB may not be accessible in the same views as the this MIB. 781 If no appropriate row in a MIB table can be identified, then 782 the value { 0 0 } is returned." 783 ::= { pmStudyClassEntry 7 } 785 -- 786 -- PM Study Metric Table 787 -- 788 pmStudyMetricTable OBJECT-TYPE 789 SYNTAX SEQUENCE OF PmStudyMetricEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "This table contains one row for each metric supported by 794 the specified PM Study Class, and should be populated during 795 system initialization." 796 ::= { pmCaps 3 } 798 pmStudyMetricEntry OBJECT-TYPE 799 SYNTAX PmStudyMetricEntry 800 MAX-ACCESS not-accessible 801 STATUS current 802 DESCRIPTION 803 "Metrics information related to a particular PM Study Class. 805 The pmStudyClassID value in the index identifies the 806 pmStudyClassEntry with the same index value." 807 INDEX { pmStudyClassID } 808 ::= { pmStudyMetricTable 1 } 810 PmStudyMetricEntry ::= SEQUENCE { 811 pmStudyMetricID OBJECT IDENTIFIER 812 } 814 pmStudyMetricID OBJECT-TYPE 815 SYNTAX OBJECT IDENTIFIER 816 MAX-ACCESS read-only 817 STATUS current 818 DESCRIPTION 819 "This object identifies the PM Metric associated with this 820 PM Study, and contains the same value as the pmMetricID 821 index for that pmMetricEntry." 822 ::= { pmStudyMetricEntry 1 } 824 -- 825 -- PM Study Protocol Table 826 -- 828 pmStudyProtocolTable OBJECT-TYPE 829 SYNTAX SEQUENCE OF PmStudyProtocolEntry 830 MAX-ACCESS not-accessible 831 STATUS current 832 DESCRIPTION 833 "This table contains one row for each protocol supported by 834 the specified PM Study Class, and should be populated during 835 system initialization. 837 This is an indication of the protocols the indicated PM 838 Study Class is capable of measuring. The actual protocols 839 present in a given APM or TPM Report may be a subset of the 840 protocols identified in this table. 842 This table contain entries which reference any protocol in 843 the protocolDirTable. If the index of this entry identifies 844 an internal node in the protocolDirTable, then the 845 pmStudyProtocolIsSubtree object is relevant." 846 ::= { pmCaps 4 } 848 pmStudyProtocolEntry OBJECT-TYPE 849 SYNTAX PmStudyProtocolEntry 850 MAX-ACCESS not-accessible 851 STATUS current 852 DESCRIPTION 853 "Protocol information about a particular PM Study Class. 855 The pmStudyClassID value in the index identifies the 856 pmStudyClassEntry with the same index value, associated with 857 the list of protocols in this table. 859 The protocolDirLocalIndex value identifies the 860 protocolDirEntry which contains the same value in the 861 protocolDirLocalIndex object." 862 INDEX { pmStudyClassID, protocolDirLocalIndex } 863 ::= { pmStudyProtocolTable 1 } 865 PmStudyProtocolEntry ::= SEQUENCE { 866 pmStudyProtocolIsSubtree TruthValue 867 } 869 pmStudyProtocolIsSubtree OBJECT-TYPE 870 SYNTAX TruthValue 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "This object indicates whether or not this entry identifies 875 one node or an entire subtree of the protocolDirTable. 877 If set to 'true(1)' then the specified protocolDirEntry, and 878 all its children, are supported by the specified PM Study 879 Class. 881 If set to 'false(2)', then the specified protocolDirEntry 882 identified by this entry is supported by the PM Study 883 Class." 884 ::= { pmStudyProtocolEntry 1 } 886 -- 887 -- APM Metric Registry 888 -- 890 -- APM Avaiability Metric for all transaction types 891 pmAppAvailMetric OBJECT-IDENTITY 892 STATUS current 893 DESCRIPTION 894 "Metric Name: 895 Type-P-APM-Availability 897 Metric Definition: 898 This metric characterizes the availability of a 899 network service by measuring the percentage of 900 successful transactions the network service 901 delivers over a given time interval. 903 This metric is calculated by first measuring 904 the IPPM metric 905 'Type-P-Interval-Bidirectional-Connectivity' 906 for the interval starting at the instant 'Src' 907 initiates a transaction of Type-P with the 'Dst' 908 host, and ending at the instant the last packet 909 of the transaction has been received. In addition to 910 successful connectivity over this interval, the 911 particular application request must also succeed, 912 for a transaction to be considered successful. 913 If either condition is false, then that transaction 914 is considered to be unsuccessful. 916 The derived metric is defined as the total number 917 of successful transactions between Src and Dst, 918 divided by the total number of transaction attempts 919 between Src and Dst, during the time interval dT. 921 Metric Parameters: 922 Src, the network address of a host 923 Dst, the network address of a host 924 dT, a time interval 926 Metric Units: 927 Percentage 929 Mapping of Type P: 930 Type P refers to an application protocol 931 encapsulation, identified by a specific 932 protocolDirEntry. 934 Metric Type: connectMetric(1) 935 Metric Dir Type: twoWay(2)" 936 REFERENCE 937 "IPPM Metrics for Measuring Connectivity, RFC 2678 938 [RFC2678], Section 5, September 1999." 939 ::= { pmMetrics 1 } 941 -- APM Responsiveness Metric for Transaction-oriented applications 942 pmAppTransRespMetric OBJECT-IDENTITY 943 STATUS current 944 DESCRIPTION 945 "Metric Name: 946 Type-P-APM-Transaction-Responsiveness 948 Metric Definition: 949 This metric characterizes the speed at which a 950 transaction-oriented network application delivers 951 a requested service, by measuring the speed of 952 individual application transactions. 954 This metric is calculated by utilizing a variation of 955 the IPPM metric 'Type-P-Round-trip-Delay'. The 956 total transaction time (dT) is determined by summing 957 all the packet transactions of Type-P between the 958 Src and Dst hosts. The bi-directional flight times 959 are measured (as specified by the IPPM metric definition), 960 but the server response time for each request is included 961 in the measurement. 963 The derived metric is defined as the total number 964 of tenths of seconds for the transaction between 965 Src and Dst to complete. 967 Metric Parameters: 968 Src, the network address of a host 969 Dst, the network address of a host 970 dT, a time interval 972 Metric Units: 973 Tenths of seconds 975 Mapping of Type P: 976 Type P refers to an application protocol 977 encapsulation, identified by a specific 978 protocolDirEntry, which is characterized 979 as a transaction-oriented protocol. 981 Metric Type: delayMetric(2) 982 Metric Dir Type: twoWay(2)" 983 REFERENCE 984 "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681], 985 Section 2, September 1999." 986 ::= { pmMetrics 2 } 988 -- APM Responsiveness Metric for Throughput-oriented applications 989 -- [ed., in progress] 990 pmAppTputRespMetric OBJECT-IDENTITY 991 STATUS current 992 DESCRIPTION 993 "Metric Name: 994 Type-P-APM-Throughput-Responsiveness 996 Metric Definition: 997 This metric characterizes the speed at which a 998 throughput-oriented network application delivers 999 a requested service, by measuring the transfer rate 1000 of individual application transactions. 1002 This metric is calculated by ... [rest of para is TBD] 1004 The derived metric is normalized and inverted, into 1005 units of 'seconds per terabit'. For transactions 1006 up to one terabit in size, it is defined as the 1007 total number of seconds it would take for the 1008 transaction between Src and Dst to complete, if 1009 the transaction size included one terabit of data. 1010 For transactions over one terabit in size, it 1011 is defined as the average number of seconds for the 1012 transaction between Src and Dst to complete, for 1013 each terabit of data. 1015 E.g., a transfer rate of 2Kbps equals 500,000,000 and 1016 a transfer rate of 1Gbps = 1000. 1018 Metric Parameters: 1019 Src, the network address of a host 1020 Dst, the network address of a host 1021 dT, a time interval 1022 B, a number of terabits 1024 Metric Units: 1025 Seconds Per Terabit 1027 Mapping of Type P: 1028 Type P refers to an application protocol 1029 encapsulation, identified by a specific 1030 protocolDirEntry, which is characterized 1031 as a throughput-oriented protocol. 1033 Metric Type: delayMetric(2) 1034 Metric Dir Type: twoWay(2)" 1035 REFERENCE 1036 "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681], 1037 Section 2, September 1999." 1038 ::= { pmMetrics 3 } 1040 -- APM Responsiveness Metric for Stream-oriented applications 1041 -- [ed., in progress] 1042 pmAppStreamRespMetric OBJECT-IDENTITY 1043 STATUS current 1044 DESCRIPTION 1045 "Metric Name: 1046 Type-P-APM-Stream-Responsiveness 1048 Metric Definition: 1049 This metric characterizes the 'quality' at which a 1050 streaming-oriented network application delivers 1051 a requested service, by measuring the percentage 1052 of time that the service is degraded or interrupted 1053 to the total time to deliver the service. 1055 [Rest of definition TBD] 1057 Metric Parameters: 1058 Src, the network address of a host 1059 Dst, the network address of a host 1061 Metric Units: 1062 [TBD] 1064 Mapping of Type P: 1065 Type P refers to an application protocol 1066 encapsulation, identified by a specific 1067 protocolDirEntry, which is characterized 1068 as a streaming-oriented protocol. 1070 Metric Type: delayMetric(2) 1071 Metric Dir Type: twoWay(2)" 1072 REFERENCE 1073 "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681], 1074 Section 2, September 1999." 1075 ::= { pmMetrics 4 } 1077 -- 1078 -- TPM Metric Registry [TBD] 1079 -- 1081 -- placeholder for notifications 1082 pmCapsNotifications OBJECT IDENTIFIER ::= { pmCapsMIB 2 } 1084 -- conformance information 1085 pmCapsConformance OBJECT IDENTIFIER ::= { pmCapsMIB 3 } 1087 pmCapsCompliances OBJECT IDENTIFIER ::= { pmCapsConformance 1 } 1088 pmCapsGroups OBJECT IDENTIFIER ::= { pmCapsConformance 2 } 1090 -- compliance statements 1091 pmCapsCompliance MODULE-COMPLIANCE 1092 STATUS current 1093 DESCRIPTION 1094 "The compliance statement for SNMP entities which implement 1095 version 1 of the APM Capabilities MIB." 1096 MODULE -- this module 1097 MANDATORY-GROUPS { 1098 protocolDirectoryGroup, 1099 pmCapsGroup 1100 } 1101 ::= { pmCapsCompliances 1 } 1103 -- MIB groupings 1104 pmCapsGroup OBJECT-GROUP 1105 OBJECTS { 1106 pmMetricType, 1107 pmMetricDirType, 1108 pmMetricName, 1109 pmMetricReference, 1110 pmStudyClassMeasLoc, 1111 pmStudyClassMeasType, 1112 pmStudyClassCollectPts, 1113 pmStudyClassCollectCaps, 1114 pmStudyClassOutputCaps, 1115 pmStudyClassCtlTablePtr, 1116 pmStudyMetricID, 1117 pmStudyProtocolIsSubtree 1118 } 1119 STATUS current 1120 DESCRIPTION 1121 "The collection of objects which are used to represent 1122 application performance measurement capabilities, for which 1123 a single agent provides management information." 1124 ::= { pmCapsGroups 1 } 1126 END 1127 9. Intellectual Property 1129 The IETF takes no position regarding the validity or scope of any 1130 intellectual property or other rights that might be claimed to pertain 1131 to the implementation or use of the technology described in this 1132 document or the extent to which any license under such rights might or 1133 might not be available; neither does it represent that it has made any 1134 effort to identify any such rights. Information on the IETF's 1135 procedures with respect to rights in standards-track and standards- 1136 related documentation can be found in BCP-11. Copies of claims of 1137 rights made available for publication and any assurances of licenses to 1138 be made available, or the result of an attempt made to obtain a general 1139 license or permission for the use of such proprietary rights by 1140 implementors or users of this specification can be obtained from the 1141 IETF Secretariat. 1143 The IETF invites any interested party to bring to its attention any 1144 copyrights, patents or patent applications, or other proprietary rights 1145 which may cover technology that may be required to practice this 1146 standard. Please address the information to the IETF Executive 1147 Director. 1149 10. References 1151 [APM] 1152 Waldbusser, S., "Application Performance Measurement MIB", , May 2000. 1155 [TPM] 1156 Dietz, R., "Transport Performance Metrics MIB", , May 2000. 1159 [RFC1155] 1160 Rose, M., and K. McCloghrie, "Structure and Identification of 1161 Management Information for TCP/IP-based Internets", RFC 1155, STD 1162 16, Performance Systems International, Hughes LAN Systems, May 1163 1990. 1165 [RFC1157] 1166 Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1167 Management Protocol", RFC 1157, STD 15, SNMP Research, Performance 1168 Systems International, Performance Systems International, MIT 1169 Laboratory for Computer Science, May 1990. 1171 [RFC1212] 1172 Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1173 STD 16, Performance Systems International, Hughes LAN Systems, 1174 March 1991. 1176 [RFC1215] 1177 M. Rose, "A Convention for Defining Traps for use with the SNMP", 1178 RFC 1215, Performance Systems International, March 1991. 1180 [RFC1901] 1181 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1182 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1183 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1184 International Network Services, January 1996. 1186 [RFC1905] 1187 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1188 Operations for Version 2 of the Simple Network Management Protocol 1189 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1190 Dover Beach Consulting, Inc., International Network Services, 1191 January 1996. 1193 [RFC1906] 1194 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1195 Mappings for Version 2 of the Simple Network Management Protocol 1196 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1197 Dover Beach Consulting, Inc., International Network Services, 1198 January 1996. 1200 [RFC2021] 1201 S. Waldbusser, "Remote Network Monitoring MIB (RMON-2)", RFC 2021, 1202 International Network Services, January 1997. 1204 [RFC2026] 1205 Bradner, S., "The Internet Standards Process -- Revision 3", RFC 1206 2026, Harvard University, October, 1996. 1208 [RFC2330] 1209 Paxson, V., Almes, G., Mahdavi, J. and M. Mathis, "Framework for IP 1210 Performance Metrics", RFC 2330, May 1998. 1212 [RFC2570] 1213 Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1214 Version 3 of the Internet-standard Network Management Framework", 1215 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, 1216 Inc., Ericsson, Cisco Systems, April 1999. 1218 [RFC2571] 1219 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1220 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1221 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1222 1999. 1224 [RFC2572] 1225 Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1226 Processing and Dispatching for the Simple Network Management 1227 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 1228 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. 1230 [RFC2573] 1231 Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1232 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1233 Systems, April 1999. 1235 [RFC2574] 1236 Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1237 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1238 2574, IBM T. J. Watson Research, April 1999. 1240 [RFC2575] 1241 Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1242 Control Model (VACM) for the Simple Network Management Protocol 1243 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1244 Cisco Systems, Inc., April 1999. 1246 [RFC2578] 1247 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1248 and S. Waldbusser, "Structure of Management Information Version 2 1249 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1250 Braunschweig, SNMP Research, First Virtual Holdings, International 1251 Network Services, April 1999. 1253 [RFC2579] 1254 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1255 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 1256 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 1257 Virtual Holdings, International Network Services, April 1999. 1259 [RFC2580] 1260 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1261 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 1262 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1263 First Virtual Holdings, International Network Services, April 1999. 1265 [RFC2678] 1266 Mahdavi, J., and V. Paxson, "IPPM Metrics for Measuring 1267 Connectivity", RFC 2678, September 1999. 1269 [RFC2679] 1270 Almes, G., Kalidindi, S., and M. Zekauskas, A One-Way Delay Metric 1271 for IPPM", RFC 2679, September 1999. 1273 [RFC2680] 1274 Almes, G., Kalidindi, S., and M. Zekauskas, A One-Way Packet Loss 1275 Metric for IPPM", RFC 2680, September 1999. 1277 [RFC2681] 1278 Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay 1279 Metric for IPPM", RFC 2681, September 1999. 1281 11. Security Considerations 1283 There are no management objects defined in this MIB that have a MAX- 1284 ACCESS clause of read-write and/or read-create. So, if this MIB is 1285 implemented correctly, then there is no risk that an intruder can alter 1286 or create any management objects of this MIB via direct SNMP SET 1287 operations. 1289 SNMPv1 by itself is not a secure environment. Even if the network 1290 itself is secure (for example by using IPSec), even then, there is no 1291 control as to who on the secure network is allowed to access and GET/SET 1292 (read/change/create/delete) the objects in this MIB. 1294 It is recommended that the implementers consider the security features 1295 as provided by the SNMPv3 framework. Specifically, the use of the User- 1296 based Security Model RFC 2574 [RFC2574] and the View- based Access 1297 Control Model RFC 2575 [RFC2575] is recommended. 1299 It is then a customer/user responsibility to ensure that the SNMP entity 1300 giving access to an instance of this MIB, is properly configured to give 1301 access to the objects only to those principals (users) that have 1302 legitimate rights to indeed GET or SET (change/create/delete) them. 1304 12. Author's Address 1306 Andy Bierman 1307 Cisco Systems, Inc. 1308 170 West Tasman Drive 1309 San Jose, CA 95134 USA 1310 Phone: +1 408-527-3711 1311 Email: abierman@cisco.com 1313 13. Full Copyright Statement 1315 Copyright (C) The Internet Society (2000). All Rights Reserved. 1317 This document and translations of it may be copied and furnished to 1318 others, and derivative works that comment on or otherwise explain it or 1319 assist in its implementation may be prepared, copied, published and 1320 distributed, in whole or in part, without restriction of any kind, 1321 provided that the above copyright notice and this paragraph are included 1322 on all such copies and derivative works. However, this document itself 1323 may not be modified in any way, such as by removing the copyright notice 1324 or references to the Internet Society or other Internet organizations, 1325 except as needed for the purpose of developing Internet standards in 1326 which case the procedures for copyrights defined in the Internet 1327 Standards process must be followed, or as required to translate it into 1328 languages other than English. 1330 The limited permissions granted above are perpetual and will not be 1331 revoked by the Internet Society or its successors or assigns. 1333 This document and the information contained herein is provided on an "AS 1334 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1335 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1336 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1337 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1338 FITNESS FOR A PARTICULAR PURPOSE.