idnits 2.17.1 draft-ietf-ippm-reporting-mib-02.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? == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 9 longer pages, the longest (page 30) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 74 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 9. Security Considerations' ) ** 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.) ** There are 3 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** There are 2564 instances of lines with control characters in the document. ** The abstract seems to contain references ([20], [15], [2], [3], [21], [16], [4], [17], [5], [18], [19], [6], [7], [8], [9], [10], [11], [12], [13], [1], [14]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 3119: '...rk. The measurement parameters MUST be...' RFC 2119 keyword, line 3132: '... methodologies SHOULD include approp...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 1103 has weird spacing: '... field octet...' == Line 1508 has weird spacing: '...mOwners objec...' == Line 2599 has weird spacing: '... metric thres...' == Line 3245 has weird spacing: '...essType with...' -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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 section? '1' on line 3313 looks like a reference -- Missing reference section? '2' on line 3316 looks like a reference -- Missing reference section? '6' on line 3328 looks like a reference -- Missing reference section? '7' on line 3331 looks like a reference -- Missing reference section? '8' on line 3335 looks like a reference -- Missing reference section? '9' on line 3338 looks like a reference -- Missing reference section? '10' on line 3341 looks like a reference -- Missing reference section? '11' on line 3345 looks like a reference -- Missing reference section? '12' on line 3349 looks like a reference -- Missing reference section? '13' on line 3353 looks like a reference -- Missing reference section? '14' on line 3356 looks like a reference -- Missing reference section? '15' on line 3359 looks like a reference -- Missing reference section? '16' on line 126 looks like a reference -- Missing reference section? '17' on line 3367 looks like a reference -- Missing reference section? '18' on line 3371 looks like a reference -- Missing reference section? '19' on line 3375 looks like a reference -- Missing reference section? '20' on line 3378 looks like a reference -- Missing reference section? '21' on line 3382 looks like a reference -- Missing reference section? '3' on line 3319 looks like a reference -- Missing reference section? '4' on line 3322 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 10 warnings (==), 22 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Stephan/J. Jewitt 3 Internet Draft France Telecom R&D 4 Document: draft-ietf-ippm-reporting-mib-02.txt March 1st, 2003 6 IPPM reporting MIB 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with 11 all provisions of Section 10 of RFC2026 [1]. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that other 15 groups may also distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six months 17 and may be updated, replaced, or made obsolete by other documents at 18 any time. It is inappropriate to use Internet- Drafts as reference 19 material or to cite them other than as "work in progress." 21 The list of current Internet-Drafts can be accessed at 22 http://www.ietf.org/ietf/1id-abstracts.txt. 24 The list of Internet-Draft Shadow Directories can be accessed at 25 http://www.ietf.org/shadow.html. 27 Abstract 29 This memo defines a portion of the Management Information Base (MIB) 30 designed for use with network management protocols in TCP/IP-based 31 internets. 32 In particular, this MIB specifies the objects used for managing the 33 results of the IPPM metrics measures, for pushing alarms, and for 34 reporting the measures results. 36 Table of Contents 38 1. Introduction................................................3 39 2. The IPPM Framework..........................................3 40 3. The SNMP Management Framework...............................3 41 4. Overview....................................................5 42 4.1. Textual Conventions.........................................6 43 4.2. Structure of the MIB........................................8 44 4.3. Row identification in an application namespace.............10 45 4.4. Relationship of IPPM MIB tables............................11 46 5. IPPM-REPORTING-MIB conceptual presentation.................15 47 5.1. IPPM-REPORTING-MIB diagram.................................15 48 5.2. Conceptual programming interface...........................16 49 5.3. SNMP mapping...............................................16 50 6. Measurement architectures..................................17 51 6.1. Proxy architecture.........................................17 52 6.2. Reporting architecture.....................................18 53 6.3. Gateway architecture.......................................20 54 6.4. Security...................................................20 55 7. Reporting mode integration.................................21 56 7.1. Integration................................................21 57 7.2. Setup of the measure.......................................21 58 7.3. Setup of the measurement report............................22 59 7.4. Writing the results in the IPPM-REPORTING-MIB..............22 60 7.5. Report download and upload.................................23 61 7.6. Default value..............................................23 62 8. Definition.................................................24 63 9. Security Considerations....................................67 64 9.1. Privacy....................................................67 65 9.2. Measurement aspects........................................67 66 9.3. Management aspects.........................................68 67 10. Document management........................................69 68 10.1. Open issues.................................................69 69 10.2. changes since release 00....................................69 70 10.3. Changes since release 01....................................70 71 11. References.................................................72 72 12. Acknowledgments............................................73 73 13. Authors Addresses..........................................73 74 1. Introduction 75 This memo defines a MIB for managing measures based upon the IP 76 performance metrics specified by the IPPM Working Group. 78 The definition of objects in the IPPM MIB are built on notions 79 introduced and discussed in the IPPM Framework document, RFC 2330 80 [ii]. 82 This memo defines a Management Information Base (MIB), and as such it 83 is intended to be respectful of the "Boilerplate for IETF MIBs" 84 defined in http://www.ops.ietf.org/mib-boilerplate.html. 86 There are companion documents to the IPPM-REPORTING-MIB both in the 87 Transport Area (See section 2), and in the Operations and Management 88 Area (See section 3). The reader should be familiar with these 89 documents. 91 2. The IPPM Framework 93 The IPPM Framework consists of 3 major components: 95 A general framework for defining performance metrics, as described in 96 the Framework for IP Performance Metrics, RFC 2330 [2]; 98 A set of standardized metrics which conform to this framework: The 99 IPPM Metrics for Measuring Connectivity, RFC 2678 [iii]; The One-way 100 Delay Metric for IPPM, RFC 2679 [iv]; The One-way Packet Loss Metric 101 for IPPM, RFC 2680 [v]; The Round-trip Delay Metric for IPPM, RFC 102 2681 [vi]. 104 Emerging metrics that are being specified in respect of this 105 framework. 107 3. The SNMP Management Framework 109 The SNMP Management Framework consists of five major components: 111 An overall architecture, described in RFC 2571 [6]. 113 Mechanisms for describing and naming objects and events for the 114 purpose of management. The first version of this Structure of 115 Management Information (SMI) is called SMIv1 and described in STD 16, 116 RFC 1155 [7], STD 16, RFC 1212 [8] and RFC 1215 [9]. The second 117 version, called SMIv2, is described in STD 58, RFC 2578 [10], STD 58, 118 RFC 2579 [11] and STD 58, RFC 2580 [12]. 120 Message protocols for transferring management information. The 121 first version of the SNMP message protocol is called SNMPv1 and 122 described in STD 15, RFC 1157 [13]. A second version of the SNMP 123 message protocol, which is not an Internet standards track protocol, 124 is called SNMPv2c and described in RFC 1901 [14] and RFC 1906 [15]. 125 The third version of the message protocol is called SNMPv3 and 126 described in RFC 1906 [15], RFC 2572 [16] and RFC 2574 [17]. 128 Protocol operations for accessing management information. The 129 first set of protocol operations and associated PDU formats is 130 described in STD 15, RFC 1157 [13]. A second set of protocol 131 operations and associated PDU formats is described in RFC 1905 [18]. 133 A set of fundamental applications described in RFC 2573 [19] and 134 the view-based access control mechanism described in RFC 2575 [20]. 136 A more detailed introduction to the current SNMP Management Framework 137 can be found in RFC 2570 [21]. 139 Managed objects are accessed via a virtual information store, termed 140 the Management Information Base or MIB. Objects in the MIB are 141 defined using the mechanisms defined in the SMI. 143 This memo specifies a MIB module that is compliant to the SMIv2. A 144 MIB conforming to the SMIv1 can be produced through the appropriate 145 translations. The resulting translated MIB must be semantically 146 equivalent, except where objects or events are omitted because no 147 translation is possible (use of Counter64). Some machine readable 148 information in SMIv2 will be converted into textual descriptions in 149 SMIv1 during the translation process. However, this loss of machine 150 readable information is not considered to change the semantics of the 151 MIB. 153 Managed objects are accessed via a virtual information store, termed 154 the Management Information Base or MIB. Objects in the MIB are 155 defined using the subset of Abstract Syntax Notation One (ASN.1) 156 defined in the SMI. In particular, each object type is named by an 157 OBJECT IDENTIFIER, an administratively assigned name. 159 The object type together with an object instance serves to uniquely 160 identify a specific instantiation of the object. For human 161 convenience, we often use a textual string, termed the descriptor, to 162 refer to the object type. 164 4. Overview 166 Although the number of measurement devices that implement IPPM 167 metrics is growing, there is not currently any standardized 168 management interface to manage remotely the measurement of these 169 metrics. This memo defines a Management Information Base for managing 170 the measurement of IPPM metrics. 172 To permit metrics to be referenced by other MIBs and other protocols, 173 the IPPM WG has defined a registry of the current metrics and a 174 framework for the integration of future metrics in the [IPPM metrics 175 registry]. 177 As the specification of new metrics is a continuous process, this 178 memo defines a framework for the integration of the future 179 standardized metrics. To address future needs specialized tables may 180 be created, while augmenting the definition of the ippmMeasureTable. 182 The MIB architecture is inspired by the RMON model [xxiii],[xxiv] 183 which specifies the MIB for the monitoring of a single point of 184 measure. The IPPM-REPORTING-MIB differs from this model in that IPPM 185 metrics measurement involves several points of measure and requires 186 common references for time and for measure identification. 188 The IPPM-REPORTING-MIB introduces a framework where each application 189 identifies its measures in an owner namespace. Using the namespace 190 framework, an application may grant other owners access to its 191 measurement results for aggregated metrics computation, reporting, or 192 alarming. 194 Different architectures may be used to perform metric measurements, 195 using a control protocol and a test protocol. Different control 196 frameworks are suitable for performing measurements. The memo lists 197 them, while also looking for a way to integrate them with the IPPM- 198 REPORTING-MIB. This section is for informational purposes only, and 199 is intended to help to specify the relationship among the test 200 protocol, the control protocol and IPPM-REPORTING-MIB. 202 Special care has been taken to provide a reporting mode suitable for 203 control protocols and test protocols. It addresses the need to 204 provide access to results for the applications. Moreover, it may be 205 used to reduce the number of control frameworks. 207 This MIB is intended to handle multiple concurrent sessions by SNMP 208 applications. However, the SNMP requests are not necessarily to be 209 handled explicitly by the measurement devices, but can be sent to 210 middleware performing an aggregation function. This allows for 211 continuous collection of measurements and statistics computation. 213 4.1. Textual Conventions 215 Five types of data are introduced as a textual convention in this 216 document: TypeP, TypePaddress, GMTTimeStamp, IppmStandardMetrics and 217 IppmReportDefinition. 219 4.1.1. TypeP and TypePaddress 221 Section 13 of the IPPM framework [2] introduces the generic notion of 222 a "packet of type P" because in some contexts the metric's value 223 depends on the type of the packets involved in the metric. In the 224 definition of a metric, the type P will be explicitly defined, 225 partially defined, or left generic. Measurement of metrics defined 226 with generic type P are made specific when performing actual 227 measurements. This naming convention serves as an important reminder 228 that one must be conscious of the exact type of traffic being 229 measured. 231 The standardization of the management of the IPPM measures relies on 232 the capability to finely and unambiguously configure the type P of 233 the packets, and the parameters of the protocol suites of the type P. 235 RMON2 introduced the concept of protocol identifiers. RFC2895 [xxv] 236 specifies a macro for the definition of protocol identifier. The 237 RFC2896 [xxvi] defines the protocol identifiers for different 238 protocol encapsulation trees. 240 The type P implementation relies on the MACRO PROTOCOL-IDENTIFIER 241 defined for identifying protocol suites in RMON2. It is achieved by 242 defining the TypeP and the TypePaddress as new syntax in SMIv2 243 TEXTUAL-CONVENTION. 245 4.1.1.1. Internet addresses 247 The section 14 of the IPPM framework defines (for the usual case of a 248 unidirectional path through the Internet) the term "Src" and "Dst". 249 "Src" denotes the IP address of the beginning of the path, and "Dst" 250 denotes the IP address of the end. 252 The section 3 of the RMON PI Reference specifies the Protocol 253 Identifier Encoding rules, which consists briefly in a recursive 254 length value format. "Src" and "Dst" are protocol identifier 255 parameters. Their values are encoded in separated fields using the 256 encoding rules of the protocol identifier, but without trailing 257 parameters. 259 The packet encapsulation defined in an instance of TypeP embeds the 260 format of "Src" and "Dst" and their values. The type and value of 261 these addresses depend on the type P of the packet, IP version 4, 262 IPV6, IP in IP... Both participate in the completion of the packet 263 encoding. 265 Examples: 267 RFC2896 defines the protocol identifiers ip and ipip4. Should there 268 be an Internet tunnel end-point of the IP address 192.168.1.1 in the 269 tunnel 128.2.6.7. the TypeP of the source address of the tunnel, Src, 270 is 'ip.ipip4'. The encoding of 'ip.ipip4' using the RFC2895 rules 271 adds a trailer 2.0.0. It means that an instance of this protocol 272 identifier has 2 parameters, which values will be set only when 273 implemented. In the IPPM TypeP context these 2 parameters are 274 provided in Src (or Dst). In the current example the value of Src is 275 "192.168.1.1 128.2.6.7". 277 4.1.2. GMTTimeStamp 279 This textual convention defines the time at which an event occurred. 280 It is very similar to the NTP timestamp format except that it 281 represents the time elapsed since January 1st, 2000 instead of 282 January 1st, 1900. 284 4.1.3. IppmStandardMetrics 286 Each standard metric is identified in the IPPM-METRICS-REGISTRY under 287 the node rfc in a chronological order. This textual convention 288 defines an octet string to permit several metrics to be performed in 289 a single measure. 291 4.1.4. Report definition 293 A report consists of sending, or logging, a subset of results of 294 measurements that have been taken over a period of time. The report 295 consists of actions that are taken on the measurement results. An 296 action is performed either: 298 + For each result 299 + On the results corresponding to a measurement cycle 300 + On the results available at the measurement completion. 302 To preserve the scalability of the whole measurement system, it 303 limits: 305 + The amount of data sent to the applications 306 + The bandwidth consumption for uploading the result 307 + The number of alarms sent to the applications 308 + The amount of data saved in the point of measure 309 The comparison of the measures results in a metric threshold that 310 identifies particular measure values and times that directly impact 311 service availability. 313 The comparison of the duration of repeated events with a duration 314 threshold identifies particular measure values and times that 315 directly affect an SLA. 317 The combination of IPPM metric results, threshold events, and event 318 filtering provides a very efficient mechanism to report results, 319 events, and alarms. 321 A report is described using the TEXTUAL-CONVENTION 322 IppmReportDefinition. The report setup must not dramatically increase 323 the amount of data needed by the control protocol to setup a measure: 325 + A basic report is defined in the object ippmReportSetupDefinition; 326 + More elaborate reports are described using a metric threshold to 327 generate alarms and events. 328 + Pushing of alarms and reports requires a management station 329 address to which the data will be sent. 330 + SLA alarms are described using an events duration threshold. 332 The TEXTUAL-CONVENTION IppmReportDefinition specifies the list of 333 events and actions that are used to create a report. 335 4.2. Structure of the MIB 337 The MIB is arranged as follow: 339 - ippmNotifications 341 - ippmOwnersGroup 343 - ippmSystemGroup 345 - ippmMeasureGroup 347 - ippmHistoryGroup 349 - ippmNetworkMeasureGroup 351 - ippmAggrMeasureGroup 353 - ippmReportGroup 354 4.2.1. The ippmOwners Group 356 This group identifies an owner, or group of owners that have access 357 to measurements on a probe. 359 4.2.2. The ippmSystem Group 361 This group consists of a set of parameters describing the clock 362 synchronization at a particular point of measure over time. 364 This group is critical to the implementation of the IPPM MIB. 366 Section 6.3. of the IPPM Framework states that 367 "Those who develop such measurement methodologies should strive to: 368 + Minimize their uncertainties/errors, 369 + Understand and document the sources of uncertainty/error, and 370 + Quantify the amounts of uncertainty/error." 372 The aim of this group is to have these values available to compute 373 reliable statistics. The implementation of this group is mandatory, 374 whether the time synchronization is automatic or not. 376 4.2.3. The ippmMeasureGroup 378 This group displays all the measures configured on the measurement 379 entity. It consists of the ippmMetricsTable and ippmMeasureTable. The 380 ippmMeasureTable holds the common part of a measure, while the 381 specific parameters are handled in the corresponding auxiliary table 382 (ippmNetworkMeasure, ippmAggrMeasureTable...) . 384 The measurement entity describes in the ippmMetricsTable of the SNMP 385 agent the local implementation of the standardized metrics. All 386 standardized metrics should be displayed in this table, with the 387 capability object defining whether the metric is implemented or not. 389 The control protocol registers a description of the existing measures 390 in the ippmMeasureTable and in the auxiliary measure tables. The 391 ippmMeasureTable table is read-create, but only allows for the 392 creation of "aggregated" measures when defined in conjunction with 393 the ippmAggrMeasureTable. Network measures are not allowed to be 394 created directly by the management entity, and as such the measure 395 table values for these measures should be display only. 397 The results of the measurements are logged in the ippmHistoryTable. 399 4.2.4. The ippmNetworkMeasure Group 401 The control protocol registers a description of the existing network 402 measures in the ippmNetworkMeasureTable and in the ippmMeasureTable. 404 This group displays the network measures defined by the control 405 protocol. The results are saved in the ippmHistoryTable. 407 ippmNetworkMeasureTable is an auxiliary table of ippmMeasureTable, 408 and is responsible for the configuration of the network measure. 410 4.2.5. The ippmAggrMeasure Group 412 ippmAggrMeasureTable is an auxiliary table of ippmMeasureTable, and 413 is responsible for the consolidation of the results previously 414 measured and saved in the ippmHistoryTable. The aggregated results 415 are saved in the ippmHistoryTable and may be used for higher 416 aggregated measures. 418 4.2.6. The Report Group 420 This group displays the existing reports of the measures collected. 421 ippmReportSetupTable is an auxiliary table of ippmMeasureTable, and 422 is responsible for the configuration of the reports. 423 The reports are saved in the ippmReportTable, or sent directly to the 424 applications. 426 4.2.7. The Notification Group 428 The Notification group specifies a list of valid notifications. They 429 are used to push alarms or reports to the applications. 431 4.3. Row identification in an application namespace 433 The control protocol or the test protocol adds rows in the namespace 434 of the corresponding measure. 436 An identifier of an instance of an object is defined as a list of 437 objects in the clause INDEX. An object instance identifier in an 438 owner namespace is defined as a list of objects in the clause INDEX 439 where the first object type is IppmOwnerString. 441 As the OBJECT IDENTIFIER, which identifies the instance, begins with 442 the owner value, the remaining values of the index fields may be 443 chosen independently from one namespace to another. 445 This allows the user to choose arbitrary values for the remaining 446 fields of the INDEX clause without checking that the values of these 447 fields exists in the MIB tables. This allows the owner to use the 448 same values across MIB implementations. 450 Thus, it avoids polling to determine the next free index. Also, as a 451 consequence, two applications will never find the same free index 452 value. 454 The usage of owner namespace increases the speed of the management 455 operations while reducing bandwidth consumption and CPU load in the 456 agents and applications. 458 Measurements are requested by management applications. An instance of 459 an object managed by a management station is identified by the 460 management station IppmOwnerString and the private index provided by 461 the MS. 463 As the MS manages its private range of indices, it simply chooses one 464 when it wishes to create a new control entry. For the same reason, 465 the setup of a measure on several points of measures consists of 466 simply sending the same copy of the measure setup to the different 467 points of measures involved. 469 4.4. Relationship of IPPM MIB tables 471 There is inherently a relationship between various tables in the IPPM 472 Mib, and as such, the data integrity must be assured. This 473 relationship is depicted in the following examples. 475 4.4.1. Relationship between the Owners Table and the Measure Table 477 The owners table contains the list of "owners" that can create and 478 activate remote IPPM measurements in an agent. As the table is 479 "Read/Create", these users and their associated 480 "access" rights on metric measurements can be directly configured. It 481 is recommended to make use of "view based access control" in order to 482 restrict access to this table. For example, the 483 master user "acme" may be given "write" privileges on the 484 ippmOwnersTable, whereas all others are restricted to "read" access. 485 The user "acme" can then setup the list of other users that have 486 access to measures. 488 There must be at least 1 owner in the owners table. This owner may be 489 either setup by default by the IPPM agent, or configured as stated 490 above. 492 An owner may have multiple corresponding entries in the measure 493 table. Each entry in the measure table must be associated with one, 494 and only one, entry in the owners table. That is to say, that a 495 defined measure may NOT have multiple owners. 497 Thus, we have a 1:N relationship between the owners table and the 498 measure table. 500 +---------------------+ +---------------------------+ 501 | ippmOwnersTable | | ippmMeasureTable | 502 +---------------------+ 1:N +---------------------------+ 503 | OwnersOwner: "Acme" |--------------| Measure Owner: "Acme" | 504 | "Foo" | | Measure Name:"OneWayDelay"| 505 | . | |...... | 506 | . | | Measure Owner: "Foo" | 507 | . | | Measure Name: "PacketLoss"| 508 | | | Measure Owner: "Foo" | 509 +---------------------+ +---------------------------+ 511 4.4.2. Relationship between the Measure Table and the Network Measure 512 Table/Aggregated Measure Table 514 The network measure table and the aggregated measure table can be 515 seen as logical "extensions" to the measure table. 516 The measure table contains information that is common to both types 517 of measurements. The information found in the Network Measure Table 518 and the Aggregated Measure Table is specific to each type of measure. 520 As the network measure table is read-only, entries in this table must 521 be populated by the agent upon startup. 522 The agent could potentially read a database that contains network 523 measures configured by a 3rd party proprietary management system that 524 directly interacts with the points of measure. An entry can not be 525 created in the network measure table without creating the 526 corresponding entry in the measure table associated to the measure. 527 This also implies that the "owner" of the measure be defined in the 528 owners table. 530 The aggregated measure table allows for an "owner" to create 531 aggregated measures (such as average, minimum, maximum) on existing 532 measures that are in the measure table. If an "owner" (A) wishes to 533 create an aggregated measure on a measure "owned" by another 534 "owner" (B), then "owner" (B) must grant "owner" (A) access to his 535 measures. This can be done in the resultsharing table. 537 Even though the Measure Table is read-create, an "owner" should only 538 be able to create, or modify entries in the measure table that 539 correspond to aggregated measure types. Should an "owner" attempt to 540 update an entry in the measure table that corresponds to an entry 541 in the network measure table, than access should be denied. 543 +---------------------------+ +----------------------------------+ 544 | ippmMeasureTable | | ippmNetworkMeasureTable | 545 +---------------------------+ +----------------------------------+ 546 | Measure Owner: "Acme" | | MeasureSrc: "Src1" | 547 | Measure Name:"OneWayDelay | ---| MeasureDst: "Dst1" | 548 | ....... | | ........ | 549 | Measure Owner: "Foo" | | MeasureSrc: "Src2" | 550 | Measure Name: "PacketLoss"| | MeasureDst: "Dst2" | 551 | | +----------------------------------+ 552 | | 553 | | +----------------------------------+ 554 | | | ippmAggrMeasureTable | 555 | | +----------------------------------+ 556 | Measure Owner: "Acme" | | AMHistoryOwner: "Foo" | 557 | Measure Name: "AvgPLoss" | ---| AMHistoryMetric: "PacketLoss" | 558 +---------------------------+ +----------------------------------+ 560 +---------------------------+ +----------------------------------+ 561 | ippmHistoryTable | | ippmResultSharingTable | 562 | (ex: with OWPL values) | | | 563 +---------------------------+ +----------------------------------+ 564 | Idx: Meas. Owner"Foo " | | SharingOwner: "Foo" | 565 | Measure Index: 1 | | SharingMeasureOwner:"PacketLoss"| 566 | Metrix Indx: 12 | | | 567 | | | SharingGrantedOwner: "Acme" | 568 | HistorySqceNdx: 1 | +----------------------------------+ 569 | GMTTimeStampValue | 570 | Value: 5 | 571 +---------------------------+ 572 | Idx: Meas. Owner "Foo" | 573 | Mesure Index: 1 | 574 | Metric Index: 12 | 575 | HistorySqceNdx: 2 | 576 | GMTTimeStampValue | 577 | Value: 15 | 578 | Idx: Meas. "Acme" | 579 | Measure Index: 3 | 580 | Metric Index: 14 | 581 | HistorySqceNdx: 1 | 582 | GMTTimeStampValue | 583 | Value: 10 | 584 +---------------------------+ 586 As the aggregated measure table essentially "inherits" from the 587 measure table, one can not create an entry is this table without 588 first creating an entry in the measure table. Likewise, one can not 589 delete an entry in the measure table without first deleting the 590 corresponding row in the aggregated measure table. This logic ensures 591 that there are no "orphaned" table entries in the aggregated measure 592 table. 594 5. IPPM-REPORTING-MIB conceptual presentation 596 5.1. IPPM-REPORTING-MIB diagram 598 Conceptual view of objects configured using the IPPM-REPORTING-MIB 600 +--------------------------------------------------------+ 601 | IPPM-REPORTING-MIB entity | 602 | | 603 | +---------------------+ +-------------------+ | 604 | | | | | | 605 | | Measure scheduler | | Result storage | | 606 | | | | | | 607 | | ^ | | ^ ^^^ | | 608 | | | | | | ||| | | 609 | +----------|----------+ +-|---|||-----------+ | 610 | | | ||| | 611 | +----------|--------------|---|||-----------+ | 612 | | | owner | ||| | | 613 | | | Acces | ||| | | 614 | | | Control | ||| | | 615 | +----------|--------------|---|||-----------+ | 616 | | | ||| | 617 +------------------|--------------|---|||----------------+ 618 | | ||| 619 | | ||| 620 +----------------+ | +----------+-+ ||| +-------------+ 621 | ControlMeasure | | | GetResult | ||| | CreateResult| 622 |----------------+-+ |------------| ||+--+-------------| 623 | | | | || | | 624 | owner | | owner | || | owner | 625 | privateNdx | | privateNdx | || | privateNdx | 626 | metrics | | metric | || | metrics | 627 | scheduler | | timestamp | || | timestamp | 628 | addresses | +------------+ || | value | 629 | status | || +-------------+ 630 +----------------+ || 631 || 632 +---------------------------+| 633 | | 634 +---------+---------+ +------+-----------------+ 635 |GetMeasureResults | |GetMeasureMetricResults | 636 |-------------------| |------------------------| 637 | | | owner | 638 | owner | | privateNdx | 639 | privateNdx | | metric | 640 +-------------------+ +------------------------+ 642 The managed objects of the IPPM-REPORTING-MIB are the measures and 643 the results. 645 5.2. Conceptual programming interface 647 This section describes a conceptual programming interface for the 648 integration of the IPPM-REPORTING-MIB in a point of measure. 650 5.2.1. Measure control 652 A measure is created/deleted/suspended through the ControlMeasure() 653 call. 655 5.2.2. Result log 657 A result of a measure is created in the IPPM-REPORTING-MIB History 658 table using a CreateResult() call. Results belonging to a measure are 659 managed according to the setup of the measure. 661 5.2.3. Reporting 663 Results are reported using the method GetResult(), 664 GetMeasureMetricResults() and GetMeasureResults() respectively to get 665 a singleton result, the singleton result of a metric measure, and 666 finally to get the singleton result of a measure. 668 5.2.4. Logical calls 670 Objects are managed using 5 main primitives: 672 controlMeasure(); 673 CreateResult(); 674 GetResult(); 675 GetMeasureMetricResults(); 676 GetMeasureResults(). 678 5.3. SNMP mapping 680 ControlMeasure() corresponds to a SNMP set-request on a conceptual 681 row of ippmMeasureEntry and on a conceptual row of 682 ippmNetworkMeasureEntry. 684 CreateResult() is a internal interface for adding measure results in 685 the ippmHistoryTable. 687 GetResult() corresponds to an SNMP get-request on a result. 689 GetMeasureMetricResults() corresponds to a SNMP walk on the results 690 of a metric measure subtree. 692 GetMeasureResults() corresponds to a SNMP walk on the results of a 693 measure subtree. 695 6. Measurement architectures 697 There are four main measurement architectures. 699 6.1. Proxy architecture 701 +----+ +----+ 702 |NMS1| |NMS2| 703 +----+ +----+ 704 ^ ^ 705 | | 706 +----------+ +----------+ 707 | | 708 SNMP or Sibling 709 | | 710 v v 711 +--------------------------+ 712 | IPPM-REPORTING-MIB agent | 713 +--------------------------+ 714 ^ ^ 715 | | 716 OWDP-Control 717 | | 718 +----------+ +----------+ 719 | | 720 v v 721 +----------------+ +------------------+ 722 | Packets-Sender |--OWDP-Test-->| Packets-Receiver | 723 +----------------+ +------------------+ 725 In this architecture, the different NMS�s query the IPPM-REPORTING- 726 MIB agent for measurements. The agent controls whether the NMS is 727 granted access to perform the measure requested. Each NMS accesses 728 the results of its measurements in the IPPM-REPORTING-MIB statistics 729 table. 731 The measurement setup/teardown and the data collection are done using 732 the control protocol and the test protocol. 734 In this mode the NMS does not depend either on the control protocol 735 nor on the test protocol. The entities involved in the measurement do 736 not need to implement the IPPM-REPORTING-MIB nor SNMP. This mode 737 allows for lightweight implementation in the point of measure, and 738 also for heterogeneous control protocols to coexist. 740 Finally, the proxy is a checkpoint where measurement activity may be 741 logged, and where access to measurement setups may be tightly 742 controlled. Thus, it provides a reliable architecture to manage the 743 security of a measurement system. 745 6.2. Reporting architecture 747 In this architecture the SNMP protocol is only used to read the 748 results of the measurements in the IPPM-REPORTING-MIB History Table, 749 and also to inform the NMS that an event has occurred. 751 +----+ +----+ 752 |NMS1| |NMS2| 753 +----+ +----+ 754 ^ ^ ^ ^ 755 | | | | 756 SNMP| SNMP| 757 | | | | 758 | | | | 759 | OWDP | OWDP 760 |Control |Control 761 | | | | 762 | | +------------------------------+ 763 | | | | | 764 | | +--|---------------------------+ | 765 | | | | | | 766 | +--|--|------------------------+ | | 767 | | | | | | | 768 +--------+---------------------+ | | 769 | | | | | | | | 770 | | | | | | | | 771 v v v v v v v v 772 +------------------+ +------------------+ 773 |IPPM-REPORTING-MIB| |IPPM-REPORTING-MIB| 774 | agent | | agent | 775 +------------------+ +------------------+ 776 | Packets-Sender |--OWDP-Test-->| Packets-Receiver | 777 +------------------+ +------------------+ 779 The activation of a measure by the control protocol or the test 780 protocol creates a measure in the IPPM-REPORTING-MIB Measure table. 781 The table in question may be not accessible by SNMP. In this case, a 782 list of the measure identifiers (owner, index) is handled by the 783 measurement software. 785 Each timestamped result of the measure is logged on the fly in the 786 IPPM-REPORTING-MIB History table in order to allow read access to the 787 NMS�s and event handling. 789 On completion, the measurement results are managed according to the 790 measure setup: 791 + The results may be sent to an NMS using a SNMP Trap PDU or a 792 SNMP Inform PDU. The NMS may be the sender entity or the control 793 entity; 794 + They may be dropped from the IPPM-REPORTING-MIB History table. 796 In this mode, it is recommended to use an SNMPv2 Inform PDU to send 797 the result because it ensures that the entire block of the result is 798 received. There is no control using SNMP Trap PDU. 800 6.3. Gateway architecture 802 The gateway architecture combines the proxy mode and the reporting 803 mode. 805 +-------+ +------+ 806 | NMS1 | | NMS2 | 807 +-------+ +------+ 808 ^ ^ 809 | | 810 SNMP SNMP 811 | | 812 | +----------------------------------------+ 813 | | | 814 +-------------+ +------------------+ 815 | | | | | 816 +----------------------------------------+ | 817 | | | | | | 818 | | v v | | 819 | | +------------------------+ | | 820 | | | IPPM-REPORTING-MIB | | | 821 | | | scheduler | | | 822 | | +------------------------+ | | 823 | | | control server | | | 824 | | +------------------------+ | | 825 | | ^ ^ | | 826 | | | | | | 827 | | OWDP-Control protocol | | 828 | | | | | | 829 | | +-----+ +-------+ | | 830 | | | | | | 831 v v v v v v 832 +-------------+---------+ +--------+-------------+ 833 | IPPM- | Packets | |Packets | IPPM | 834 |REPORTING-MIB| Sender | |Receiver|REPORTING-MIB| 835 | agent | |-OWDP-Test->| | agent | 836 +-------------+---------+ +--------+-------------+ 838 The NMS measurement queries are registered in the IPPM-REPORTING-MIB 839 scheduler and performed by the control and the test protocol. The NMS 840 directly consults the result in the corresponding points of measure. 842 6.4. Security 844 The proxy mode provides flexibility and control of the access to the 845 points of measure, while allowing lightweight control protocol and 846 test protocol implementations in the points of measure. Different 847 security rules may be applied to the NMS domain and to measurement 848 system domains. 850 The reporting mode has 2 security domains: 851 +The control of the measurement setups relies on the control and 852 the test protocol security mechanisms. 853 + The control of access to the results depends on the SNMP 854 security mechanisms. 856 The gateway mode security relies on the security of the proxy mode 857 and of the reporting mode. 859 7. Reporting mode integration 861 The IPPM-REPORTING-MIB standardizes the parameters that: 863 + Define the configuration of the IPPM metrics measures; 864 + Define the format of the results of the measure; 865 + Define the report of the IPPM metric measures results. 867 It introduces the concept of owner namespace to allow for fast 868 configuration and reporting across multiple points of measurement. 870 A measure is a distributed object describing a task to be performed 871 by the control and the test protocols. A measure is identified by its 872 owner and its owner index. This identifier is the same in all the 873 points of measure. As the owner chooses the index, there is no need 874 for negotiation between the NMS and the points of measure before 875 activating the measure. 877 A measure is primarily defined by its identifier, the metrics to 878 measure, the description of the end point addresses and the 879 description of the scheduling of the measure. 881 The description of the measure is distributed to the points of 882 measure involved. The distribution may not be synchronized. 884 7.1. Integration 886 The control protocol, test protocol and the IPPM-REPORTING-MIB share 887 the same semantic. 889 The integration of the IPPM-REPORTING-MIB, and the test and control 890 protocols, relies on the use of the conceptual programming interface 891 described in section 6. It consists in pushing the measure 892 setup/teardown parameters and the result values from the measurement 893 software to the IPPM-REPORTING-MIB agent. 895 7.2. Setup of the measure 897 The creation of the measure consists only in transferring the measure 898 description from the measurement software to the MIB. The management 899 of the measure is done using the ControlMeasure(). 901 The protocol, which provides the parameters of the measure to manage, 902 may be the control protocol of the test protocol. 904 Different frameworks may be used to setup a measure. 906 7.2.1. Synchronous setup 908 The control protocol sets up the measure both in the sender and the 909 receiver before the measurement. 911 7.2.2. Asynchronous setup 913 The control protocol sets up the measure only in the sender. In this 914 case, the receiver has a service already activated (or pending )for 915 the typeP of the measurement. 917 As the first test packet includes the description of the measure, it 918 may differ from regular test packets. If the first test packet is not 919 consistent with the regular test packets, it must not be used for 920 performing metrics measurement. 922 7.3. Setup of the measurement report 924 The report description is an extension to the definition of a 925 measure. It describes the event and the data to include in the 926 report. A report is read by an NMS in the ippmReportTable, or pushed 927 to a NMS using a SNMP Trap PDU, a SNMP Inform PDU, an email, or a 928 SMS. 930 The control protocol, or the test protocol, includes the description 931 of the report in the setup of the measure. 933 Different types of reports may be combined: 935 + A trivial report defines the results to be saved in the 936 ippmReportTable; 937 + A basic report defines the host to which the results are pushed 938 on completion of the measure; 939 + An alarm report defines a threshold on the results of the 940 measure. A message is sent to a host when the result raises or 941 fall the threshold; 942 + An SLA report defines a threshold on the results of the 943 measure. The events are filtered using a staircase method. The 944 report consists in the results of the measure (time and value) of 945 the filtered events. The reports are sent at each measure cycle 946 or when the measure completes. 948 7.4. Writing the results in the IPPM-REPORTING-MIB 950 Results have to be written by the measurement task in the agent 951 implementing the IPPM MIB. 953 Adding the results of a measurement consists in the transfer of the 954 result from the measurement software to the agent. The protocol that 955 provides the result may be the control protocol, or the test 956 protocol. 958 Writing a result is done using the CreateResult(). 960 7.5. Report download and upload 962 A report is read in the ippmReportTable using SNMP, or pushed by the 963 IPPM_MIB agent using a SNMP Trap PDU, a SNMP Inform PDU, an email or 964 a SMS. 966 7.6. Default value 968 The default values correspond to IP version 4. 970 8. Definition 972 IPPM-REPORTING-MIB DEFINITIONS ::= BEGIN 974 IMPORTS 975 MODULE-IDENTITY, 976 NOTIFICATION-TYPE, 977 OBJECT-TYPE, 978 experimental ,Integer32 979 FROM SNMPv2-SMI 980 -- 981 -- ippm 982 -- FROM IPPM-REGISTRY 983 -- 984 InetAddressType, 985 InetAddress 986 FROM INET-ADDRESS-MIB 987 SnmpAdminString 988 FROM SNMP-FRAMEWORK-MIB 989 RowStatus, 990 StorageType, 991 TEXTUAL-CONVENTION 992 FROM SNMPv2-TC 993 MODULE-COMPLIANCE, 994 OBJECT-GROUP, 995 NOTIFICATION-GROUP 996 FROM SNMPv2-CONF; 998 ippmReportingMib MODULE-IDENTITY 999 LAST-UPDATED "200203171200Z" -- March 17, 2002 1000 ORGANIZATION "France Telecom - R&D" 1001 CONTACT-INFO 1002 "Emile Stephan 1003 France Telecom - R&D 1004 2, Avenue Pierre Marzin 1005 Technopole Anticipa 1006 22307 Lannion Cedex 1007 FRANCE 1008 Tel: + 33 2 96 05 36 10 1009 E-mail: emile.stephan@francetelecom.com 1011 Jessie Jewitt 1012 France Telecom - R&D 1013 801 Gateway Blvd. Suit 500 1014 South San Francisco, CA 94080 1015 Tel : 1 650 875-1524 1016 E-mail : jessie.jewitt@rd.francetelecom.com" 1018 DESCRIPTION 1019 " This memo defines a portion of the Management Information Base 1020 (MIB) for use with network management protocols in TCP/IP-based 1021 internets. In particular, it specifies the objects used for 1022 managing the results of the IPPM metrics measurements, alarms and 1023 reporting the measures results." 1025 REVISION "200210181200Z" -- 18 October 2002 1026 DESCRIPTION 1027 "General cleanup 1028 Change 5 tables to read write" 1030 REVISION "200302141200Z" -- 14 February 2003 1031 DESCRIPTION 1032 "Modifications based upon feedback from IETF-55" 1034 ::= { experimental 10001 } 1036 ippm OBJECT IDENTIFIER ::= { experimental 10000 } 1038 -- 1039 -- TEXTUAL-CONVENTION 1040 -- 1042 IppmOwnerString ::= TEXTUAL-CONVENTION 1043 STATUS current 1044 DESCRIPTION 1045 "An OwnerString, which length is limited to 32." 1046 SYNTAX OCTET STRING (SIZE (0..32)) 1048 TimeUnit ::= TEXTUAL-CONVENTION 1049 STATUS current 1050 DESCRIPTION 1051 "A list of time units." 1052 SYNTAX INTEGER { 1053 year(1), 1054 month(2), 1055 week(3), 1056 day(4), 1057 hour(5), 1058 second(6), 1059 millisecond(7), 1060 microsecond(8), 1061 nanosecond(9) 1062 } 1063 -- 1064 -- 1066 IppmStandardMetrics ::= TEXTUAL-CONVENTION 1067 STATUS current 1068 DESCRIPTION 1069 " Each standard metric is identified in the IPPM-METRICS- 1070 REGISTRY under the node rfc in a chronological order. To permit 1071 several metrics to be performed in a single measure there is an 1072 need 1073 to describe in a bit string the metrics to be performed, 1074 granted... 1075 This textual convention defines an octet string that gathered in 1076 a 1077 bit string a sequence of bits. The bit order corresponds to the 1078 order 1079 of the metrics identifiers in the registry. 1080 The first bit of the string has the index 0. The index 1 1081 corresponds to the first metric of the registry 1082 (instantaneousUnidirectionalConnectivity ). 1084 Example: 1085 One-way-Delay(6) is identified as the leaf number 6 of the node 1086 rfc of the 1087 registry. One-way-Packet-Loss(12) is identified as the leaf 1088 number 12 of the node 1089 rfc of the registry. A network measure performing both One-way- 1090 Delay(6) and One- 1091 way-Packet-Loss(12) will be described as '0001000001000000'b, 1092 '1040'B. 1093 " 1094 SYNTAX OCTET STRING 1096 GMTTimeStamp ::= TEXTUAL-CONVENTION 1097 STATUS current 1098 DESCRIPTION 1099 "The value of the ippmSystemTime object at which a specific 1100 occurrence happened. The specific occurrence must be defined in 1101 the description of any object defined using this type. 1103 field octets contents range 1104 ----- ------ -------- ----- 1105 1 1-4 second since 1 Jan 2000 0H00* 0..2^31 - 1 1106 2 5-8 fractional part of the second* 0..2^32 - 1 1107 * the value is in network-byte order 1109 The timestamp format is directly inspired from the NTP timestamp 1110 format. 1111 It differs because it counts the second since 1 Jan 2000 0H00 1112 instead of 1 Jan 1900 0H00. The most significant bit of the part 1113 that represents the second is reserved. It will wrap in year 2068 1114 (The NTP timestamp will wrap in year 2036). 1116 This bit is set to indicate if the fractional part of the second 1117 contains a precision field and a synchronization field as 1118 initially proposed in the OWAMP draft. 1120 When this bit is not set the resolution is maximal. 1122 The maximal resolution is close to 250 picoseconds. 1124 The precision of the timestamp must be provided in another field. 1125 " 1126 SYNTAX OCTET STRING (SIZE (8)) 1128 TypeP ::= TEXTUAL-CONVENTION 1129 STATUS current 1130 DESCRIPTION 1131 "This textual convention is a display string used to describe the 1132 protocol encapsulation list of a packet, and is used as the value 1133 of the SYNTAX clause for the type of the Src and Dst of an IPPM 1134 measure. The RFC2895 specifies a macro named PROTOCOL-IDENTIFIER 1135 for the definition of protocol identifiers while its companion 1136 document, the RFC2896 defines a set of protocol identifiers. 1138 TypeP is defined as a display string. It consists in a list of 1139 dot separated protocol names. Each protocol name has been 1140 previously defined using the macro PROTOCOL-IDENTIFIER of the RFC 1141 2895. 1143 Examples: 1144 The RFC2896 defines the protocol identifiers 'ether2', 'ip', 1145 'ipip4', 'udp', 'tcp', 'telnet'... 1147 The TypeP of the source address corresponding to telnet is the 1148 string 'ip.tcp.telnet'. 1150 The TypeP of the source address corresponding to UDP packets sent 1151 in an IP tunnel is the string 'ip.ipip4.udp'. 1153 Notes: 1154 An IPPM measure is active, so generally a TypeP value does not 1155 describe the link layer (i.e. ether2...). Valid Internet packets 1156 are sent from Src to Dst. Then the choice of the link layer 1157 relies on the Internet stack." 1158 SYNTAX OCTET STRING (SIZE (0..255)) 1160 TypePaddress ::= TEXTUAL-CONVENTION 1161 DISPLAY-HINT "255a" 1162 STATUS current 1163 DESCRIPTION 1164 "This textual convention is a Display string used to describe the 1165 parameters of the protocol encapsulation list of a packet, 1166 basically the address. 1168 TypePaddress is defined as a display string. It consists in a 1169 list of space separated parameter list. Each parameter in the 1170 list corresponds a parameter of a PROTOCOL-IDENTIFIER of the 1171 TypeP. 1172 Example: 1173 The TypeP 'ip.ipip4' has 2 parameters. A valid TypePaddress value 1174 is '192.168.1.1 128.2.6.7'." 1175 SYNTAX OCTET STRING (SIZE (0..255)) 1177 IppmReportDefinition ::= TEXTUAL-CONVENTION 1178 STATUS current 1179 DESCRIPTION 1180 "IppmReportDefinition is intended to be used for describing the 1181 report resulting from a measurement. By default, all the results of a 1182 measure belong to the report of this measure. 1184 The first step of the report definition sets up triggers on the value 1185 of the measure, and on the distribution over time of the events 1186 generated by these triggers. 1188 The resulting measures corresponding to an event are reported 1189 periodically, or sent in alarms as soon as the event occurs. 1191 The end of the description describes housekeeping tasks. 1193 An action is performed if the corresponding bit is set to 1. 1195 onSingleton(1): 1196 The actions are performed each time a new result of the measure 1197 occurs. 1199 onMeasureCycle(2): 1200 The actions are performed on the results of the measure at the end of 1201 each cycle of measure. 1203 onMeasureCompletion(3): 1204 The actions are performed on the results of the measure at the end of 1205 the measure. 1207 reportOnlyUptoDownMetricResults(4): 1208 Report the contiguous results that are on opposite sides of the 1209 metric threshold. 1211 reportOnlyExceededEventsDuration(5): 1212 Report the current result of a series of contiguous results that 1213 exceed the metric threshold when the duration of the series is over 1214 the events duration threshold seconds. 1216 inIppmReportTable(6): 1217 Store the report in the local ippmReportTable. 1219 inSNMPTrapPDU(7): 1220 Send the report using a SNMP-Trap-PDU. 1222 inSNMPv2TrapPDU(8): 1223 Send the report using a SNMPv2-Trap-PDU. 1225 inInformRequestPDU(9): 1226 Send the report using a SNMP InformRequest-PDU. 1228 inEmail(10): 1229 Send the report using an email. 1231 inSMS(11): 1232 Send the report using a SMS. 1234 onReportDeliveryClearHistory(12): 1235 Remove all the results corresponding to this measure from the 1236 ippmHistoryTable when the report has been delivered. 1238 onReportDeliveryClearReport(13): 1239 Remove all the results corresponding to this measure from the 1240 ippmReportTable when the report has been delivered. 1241 " 1242 SYNTAX BITS { 1243 none(0), -- reserved 1244 onSingleton(1), 1245 onMeasureCycle(2), 1246 onMeasureCompletion(3), 1247 reportOnlyUptoDownMetricResults(4), 1248 reportOnlyExceededEventsDuration(5), 1249 inIppmReportTable(6), 1250 inSNMPTrapPDU(7), 1251 inSNMPv2TrapPDU(8), 1252 inInformRequestPDU(9), 1253 inEmail(10), 1254 inSMS(11), 1255 onReportDeliveryClearHistory (12), 1256 onReportDeliveryClearReport (13) 1257 } 1259 -- 1260 -- IPPM Notifications 1261 -- 1262 ippmNotifications OBJECT IDENTIFIER ::= { ippm 0 } 1264 -- 1265 -- IPPM Conformance 1266 -- 1267 ippmConformance OBJECT IDENTIFIER ::= { ippm 1 } 1269 -- 1270 -- IPPM Mib objects definitions 1271 -- 1273 ippmSystem OBJECT IDENTIFIER ::= { ippmReportingMib 1 } 1274 ippmOwners OBJECT IDENTIFIER ::= { ippmReportingMib 2 } 1275 ippmMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 3 } 1276 ippmHistory OBJECT IDENTIFIER ::= { ippmReportingMib 4 } 1277 ippmNetworkMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 5 } 1278 ippmAggrMeasure OBJECT IDENTIFIER ::= { ippmReportingMib 6 } 1279 ippmReport OBJECT IDENTIFIER ::= { ippmReportingMib 7 } 1281 -- 1282 -- ippmSystem Group 1283 -- 1284 -- 1286 ippmSystemTime OBJECT-TYPE 1287 SYNTAX GMTTimeStamp 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The current time of the measurement system." 1292 ::= { ippmSystem 1 } 1294 ippmSystemSynchronizationType OBJECT-TYPE 1295 SYNTAX INTEGER { 1296 other(0), 1297 ntp(1), 1298 gps(2), 1299 cdma(3) 1300 } 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "ippmSystemSynchronizationType describes the mechanism 1305 used to synchronize the system. 1307 Other(0) 1308 The synchronization process must be defined 1309 in the ippmSystemSynchonizationDescription. 1311 Ntp(1) 1312 The system is synchronized using the network 1313 time protocol. The NTP synchronization must be described 1314 in the ippmSystemSynchonizationDescription. 1316 Gps (2) 1317 The system is synchronized using the GPS clocks. 1319 Cdma(3) 1320 The system is synchronized using the CDMA clocks." 1321 ::= { ippmSystem 2 } 1323 ippmSystemSynchronizationDesc OBJECT-TYPE 1324 SYNTAX SnmpAdminString 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "The description of the synchronization process." 1329 ::= { ippmSystem 3 } 1331 ippmSystemClockResolution OBJECT-TYPE 1332 SYNTAX Integer32 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "ippmSystemClockResolution provides the precision of the clock 1337 used for the measures. The unit is the picosecond. For example, 1338 the clock on an old Unix host might advance only once every 10 1339 msec, and thus have a resolution of only 10 msec. So its 1340 resolution is 100000 picosecond and the value of 1341 ippmSystemClockResolution is 100000." 1342 ::= { ippmSystem 4 } 1344 ippmSystemCurrentSynchronization OBJECT-TYPE 1345 SYNTAX Integer32 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "The index on the last synchronization event in the 1350 ippmSynchronizationTable." 1351 ::= { ippmSystem 5 } 1353 ippmSynchronizationTable OBJECT-TYPE 1354 SYNTAX SEQUENCE OF IppmSynchronizationEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "This table registers the event related to the synchronization of 1359 the point of measure. Each event is described in an 1360 ippmSynchronizationEntry. 1361 ippmSynchronizationTable is mandatory. 1362 ippmSynchronizationTable content is read only." 1363 ::= { ippmSystem 6 } 1365 ippmSynchronizationEntry OBJECT-TYPE 1366 SYNTAX IppmSynchronizationEntry 1367 MAX-ACCESS not-accessible 1368 STATUS current 1369 DESCRIPTION 1370 "An entry describes a modification of the synchronization status. 1371 " 1372 INDEX { ippmSynchronizationIndex } 1373 ::= { ippmSynchronizationTable 1 } 1375 IppmSynchronizationEntry ::= 1376 SEQUENCE { 1377 ippmSynchronizationIndex Integer32, 1378 ippmSynchronizationTime GMTTimeStamp, 1379 ippmSynchronizationStratum Integer32, 1380 ippmSynchronizationResolution Integer32 1381 } 1383 ippmSynchronizationIndex OBJECT-TYPE 1384 SYNTAX Integer32 (1 .. 65535) 1385 MAX-ACCESS not-accessible 1386 STATUS current 1387 DESCRIPTION 1388 "An index that identifies the synchronization events in 1389 chronological order." 1390 ::= { ippmSynchronizationEntry 1 } 1392 ippmSynchronizationTime OBJECT-TYPE 1393 SYNTAX GMTTimeStamp 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "The time when the synchronization event occurs." 1399 ::= { ippmSynchronizationEntry 2 } 1401 ippmSynchronizationStratum OBJECT-TYPE 1402 SYNTAX Integer32 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "The stratum level of the clock computed when the synchronization 1407 event occurs." 1408 ::= { ippmSynchronizationEntry 3 } 1410 ippmSynchronizationResolution OBJECT-TYPE 1411 SYNTAX Integer32 1412 UNITS "NanoSeconds" 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "The new time resolution computed after the synchronization event 1417 occured." 1418 ::= { ippmSynchronizationEntry 4 } 1420 ippmPointOfMeasureTable OBJECT-TYPE 1421 SYNTAX SEQUENCE OF IppmPointOfMeasureEntry 1422 MAX-ACCESS not-accessible 1423 STATUS current 1424 DESCRIPTION 1425 " A lookup table that identifies the management software in 1426 charge of the point of measures. 1428 ippmPointOfMeasureTable content is read only. It means that the 1429 measurement software handles the table internally 1431 ippmPointOfMeasureTable is mandatory." 1432 ::= { ippmSystem 7 } 1434 ippmPointOfMeasureEntry OBJECT-TYPE 1435 SYNTAX IppmPointOfMeasureEntry 1436 MAX-ACCESS not-accessible 1437 STATUS current 1438 DESCRIPTION 1439 " An entry may be the management address of a middleware in 1440 charge of the management of a set of probes. It may the 1441 management address of a probe that contains several line cards. 1443 An entry describes the capability of a point of measure. The 1444 description may make the use of wildcards to define multiple 1445 capabilities." 1446 INDEX { ippmPointOfMeasureIndex } 1447 ::= { ippmPointOfMeasureTable 1 } 1449 IppmPointOfMeasureEntry ::= 1450 SEQUENCE { 1451 ippmPointOfMeasureIndex Integer32, 1452 ippmPointOfMeasureMgmtAddrType InetAddressType, 1453 ippmPointOfMeasureMgmtAddress InetAddress, 1454 ippmPointOfMeasureTypePAddress TypeP, 1455 ippmPointOfMeasureAddress InetAddress 1456 } 1458 ippmPointOfMeasureIndex OBJECT-TYPE 1459 SYNTAX Integer32 (1 .. 65535) 1460 MAX-ACCESS not-accessible 1461 STATUS current 1462 DESCRIPTION 1463 "The index of the entry." 1464 ::= { ippmPointOfMeasureEntry 1 } 1465 ippmPointOfMeasureMgmtAddrType OBJECT-TYPE 1466 SYNTAX InetAddressType 1467 MAX-ACCESS read-only 1468 STATUS current 1469 DESCRIPTION 1470 "The type of address associated with management address" 1471 ::= { ippmPointOfMeasureEntry 2 } 1473 ippmPointOfMeasureMgmtAddress OBJECT-TYPE 1474 SYNTAX InetAddress (SIZE (1..128)) 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "The management address on the point of measure" 1479 ::= { ippmPointOfMeasureEntry 3 } 1481 ippmPointOfMeasureTypePAddress OBJECT-TYPE 1482 SYNTAX TypeP 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "Defines the type P of the address of the point of measure." 1487 DEFVAL { "ip" } 1488 ::= { ippmPointOfMeasureEntry 4 } 1490 ippmPointOfMeasureAddress OBJECT-TYPE 1491 SYNTAX InetAddress 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "Specifies the address of the point of measure. 1497 It is represented as an octet string with specific semantics and 1498 length as identified by the ippmPointOfMeasureTypePAddress. 1500 For example, if the ippmPointOfMeasureTypePAddress indicates an 1501 encapsulation of 'ip', this object length is 4, followed by the 4 1502 octets of the IP address, in network byte order." 1503 ::= { ippmPointOfMeasureEntry 5} 1505 -- 1506 -- ippmOwners Group 1507 -- 1508 -- The ippmOwners objects are responsible for managing 1509 -- the owners access to the measurements. 1510 -- 1511 -- 1512 ippmOwnersTable OBJECT-TYPE 1513 SYNTAX SEQUENCE OF IppmOwnersEntry 1514 MAX-ACCESS not-accessible 1515 STATUS current 1516 DESCRIPTION 1517 "A management entity wishing to create and activate remote Ippm 1518 measurements in an agent must previously be registered in the 1519 ippmOwnersTable. 1520 ippmOwnersTable content is read-create. It contains at least the 1521 owner 'monitor'. It is mandatory, except if the VACM framework is 1522 used." 1523 ::= { ippmOwners 1 } 1525 ippmOwnersEntry OBJECT-TYPE 1526 SYNTAX IppmOwnersEntry 1527 MAX-ACCESS not-accessible 1528 STATUS current 1529 DESCRIPTION 1530 "The description of the resources granted to an SNMP application. 1532 For example, an instance of ippmOwnersOwner with an 1533 IppmOwnerString 'acme', which represents the 14th owner created 1534 in ippmOwnersTable would be named ippmOwnersEntryOwner.14. 1536 Notes: 1538 The ippmOwnersIndex value is a local index managed directly by 1539 the agent. The management application must poll to get the next 1540 available index value. 1541 It is not used in anyway in the other IPPM tables." 1542 INDEX { ippmOwnersIndex } 1543 ::= { ippmOwnersTable 1 } 1545 IppmOwnersEntry ::= SEQUENCE { 1546 ippmOwnersIndex Integer32, 1547 ippmOwnersOwner SnmpAdminString, 1548 ippmOwnersGrantedMetrics IppmStandardMetrics, 1549 ippmOwnersGrantedRules BITS, 1550 ippmOwnersIpAddressType InetAddressType, 1551 ippmOwnersIpAddress InetAddress, 1552 ippmOwnersEmail SnmpAdminString, 1553 ippmOwnersSMS SnmpAdminString, 1554 ippmOwnersStatus RowStatus 1555 } 1557 ippmOwnersIndex OBJECT-TYPE 1558 SYNTAX Integer32 (1.. 65535) 1559 MAX-ACCESS not-accessible 1560 STATUS current 1561 DESCRIPTION 1562 "An arbitrary index that identifies an entry in this table" 1563 ::= { ippmOwnersEntry 1 } 1565 ippmOwnersOwner OBJECT-TYPE 1567 SYNTAX SnmpAdminString 1568 MAX-ACCESS read-create 1569 STATUS current 1570 DESCRIPTION 1571 "The owner described by this entry." 1572 ::= { ippmOwnersEntry 2 } 1574 ippmOwnersGrantedMetrics OBJECT-TYPE 1575 SYNTAX IppmStandardMetrics 1576 MAX-ACCESS read-create 1577 STATUS current 1578 DESCRIPTION 1579 " Defines the metrics granted to an owner." 1580 ::= { ippmOwnersEntry 3 } 1582 ippmOwnersGrantedRules OBJECT-TYPE 1583 SYNTAX BITS { 1584 all(0), 1585 readonly(1), 1586 permanent(2), 1587 sender(3), 1588 receiver(4), 1589 report(5), 1590 alarm(6) 1591 } 1592 MAX-ACCESS read-create 1593 STATUS current 1594 DESCRIPTION 1595 "Defines the rules this owner may act on in the current IPPM MIB 1596 instance. 1597 all(0): 1598 The owner is granted all the rules. 1599 readonly(1): 1600 The measures (not only the metrics) that this owner may access 1601 are setup by the manager of the point of measure. The owner can 1602 not add new measures for these metrics. The creation and the 1603 configuration of the measures corresponding to these metrics are 1604 managed by the manager of the point of measure. 1605 permanent(2): 1606 The measures (not only the metrics) that this owner may access 1607 are determined by the manager of the point of measure. The owner 1608 can not add new measures for these metrics. The creation and the 1609 first configuration of the measures corresponding to these 1610 metrics are managed by the manager of the point of measure. The 1611 owner may modify the measures parameters of the entries of the 1612 corresponding ippmMeasureEntry whose access is read-write. 1613 Typically this allows the owner to suspend the measures, to 1614 change the beginning and end of the measures. 1616 sender(3): 1618 The owner may only activate measures for those metrics that send 1619 packets from the current point of measure. This flag is only 1620 suitable for network measures. It shall be ignored for derived 1621 metrics. 1622 receiver(4): 1623 The owner may only activate measures for those metrics that 1624 receive packets on the current point of measure. This flag is 1625 only suitable for network measures. It shall be ignored for 1626 derived metrics. Such control increases the security. The owner 1627 may not generate packets from the probe. 1629 report(5): 1630 The owner may setup aggregated metrics on the measures 1631 corresponding to these metrics. 1633 alarm(6): 1634 The owner may setup alarms on the results of the measures 1635 metrics. 1636 e.g.: 1637 if the owner Acme is granted with the metric Instantaneous- 1638 Unidirectional-Connectivity as a Receiver in the current point of 1639 measure, then Acme can not setup a Instantaneous-Unidirectional- 1640 Connectivity to another point of measure." 1641 DEFVAL { 1 } 1642 ::= { ippmOwnersEntry 4 } 1644 ippmOwnersIpAddressType OBJECT-TYPE 1645 SYNTAX InetAddressType 1646 MAX-ACCESS read-create 1647 STATUS current 1648 DESCRIPTION 1649 "The IP address type of the management entity corresponding to 1650 this owner." 1651 ::= { ippmOwnersEntry 5 } 1653 ippmOwnersIpAddress OBJECT-TYPE 1654 SYNTAX InetAddress (SIZE (1..128)) 1655 MAX-ACCESS read-create 1656 STATUS current 1657 DESCRIPTION 1658 "The IP address of the management entity corresponding to this 1659 owner. The address is human readable and is represented using the 1660 dot format." 1661 ::= { ippmOwnersEntry 6 } 1663 ippmOwnersEmail OBJECT-TYPE 1664 SYNTAX SnmpAdminString 1665 MAX-ACCESS read-create 1666 STATUS current 1667 DESCRIPTION 1668 "The email address of the management entity corresponding to this 1669 owner." 1670 ::= { ippmOwnersEntry 7 } 1672 ippmOwnersSMS OBJECT-TYPE 1673 SYNTAX SnmpAdminString 1674 MAX-ACCESS read-create 1675 STATUS current 1676 DESCRIPTION 1677 "The SMS phone number of the management entity corresponding to 1678 this owner." 1679 ::= { ippmOwnersEntry 8 } 1681 ippmOwnersStatus OBJECT-TYPE 1682 SYNTAX RowStatus 1683 MAX-ACCESS read-create 1684 STATUS current 1685 DESCRIPTION 1686 "The status of this table entry." 1687 ::= { ippmOwnersEntry 9 } 1689 -- 1690 -- ippmResultSharingTable 1691 -- 1693 ippmResultSharingTable OBJECT-TYPE 1694 SYNTAX SEQUENCE OF IppmResultSharingEntry 1695 MAX-ACCESS not-accessible 1696 STATUS current 1697 DESCRIPTION 1698 " The ippmResultSharingTable controls the access of an owner to 1699 the measure results of other owners. An owner may grant another 1700 access to read the result of its measure. 1702 Entries may exist in ippmResultSharingTable even if the measures 1703 to be shared are not yet defined. Deleting a measure entry in the 1704 ippmMeasureTable does not delete the entries corresponding to 1705 this measure in the ippmResultSharingTable. This table is 1706 optional. 1708 ippmResultSharingTable content is read-create. 1710 If this table is not implemented then the owner has only access 1711 to its own measurement results." 1712 ::= { ippmOwners 2 } 1714 ippmResultSharingEntry OBJECT-TYPE 1716 SYNTAX IppmResultSharingEntry 1717 MAX-ACCESS not-accessible 1718 STATUS current 1719 DESCRIPTION 1720 "An entry allows an owner to read the results of a measure owned 1721 by another owner. 1722 It permits 2 typical usages: 1723 1) Creating derived measurements on these results 1724 2) Reading the results from a remote management station. 1726 Example: if acme.12 is a One-way-Delay(6) measure, Acme may allow 1727 Peter to make derived metrics on the results of this measure." 1728 INDEX { ippmResultSharingOwner, ippmResultSharingIndex} 1729 ::= { ippmResultSharingTable 1 } 1731 IppmResultSharingEntry ::= SEQUENCE { 1732 ippmResultSharingOwner IppmOwnerString, 1733 ippmResultSharingIndex Integer32, 1734 ippmResultSharingMeasureOwner IppmOwnerString, 1735 ippmResultSharingMeasureIndex Integer32, 1736 ippmResultSharingGrantedOwner IppmOwnerString, 1737 ippmResultSharingStatus RowStatus 1738 } 1739 ippmResultSharingOwner OBJECT-TYPE 1740 SYNTAX IppmOwnerString 1741 MAX-ACCESS not-accessible 1742 STATUS current 1743 DESCRIPTION 1744 " The owner of this result control entry. Typically the owner who 1745 created this conceptual row." 1746 ::= { ippmResultSharingEntry 1 } 1748 ippmResultSharingIndex OBJECT-TYPE 1749 SYNTAX Integer32 (1.. 65535) 1750 MAX-ACCESS not-accessible 1751 STATUS current 1752 DESCRIPTION 1753 " The index of this result control entry. The value is managed by 1754 the owner. On creation a SNMP error 'inconsistentValue' is 1755 returned if this value is already in use by this owner." 1756 ::= { ippmResultSharingEntry 2 } 1758 ippmResultSharingMeasureOwner OBJECT-TYPE 1759 SYNTAX IppmOwnerString 1760 MAX-ACCESS read-create 1761 STATUS current 1762 DESCRIPTION 1763 "The owner of the measure to be shared. The couple 1764 ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex 1765 identifies absolutely a measure" 1766 ::= { ippmResultSharingEntry 3 } 1768 ippmResultSharingMeasureIndex OBJECT-TYPE 1769 SYNTAX Integer32 (1.. 65535) 1770 MAX-ACCESS read-create 1771 STATUS current 1772 DESCRIPTION 1773 "The index of the measure to be shared." 1774 ::= { ippmResultSharingEntry 4 } 1776 ippmResultSharingGrantedOwner OBJECT-TYPE 1777 SYNTAX IppmOwnerString 1778 MAX-ACCESS read-create 1779 STATUS current 1780 DESCRIPTION 1782 "The owner who is granted access to the result of the measure 1783 described by the couple ippmResultSharingMeasureOwner, 1784 ippmResultSharingMeasureIndex." 1785 ::= { ippmResultSharingEntry 5 } 1787 ippmResultSharingStatus OBJECT-TYPE 1788 SYNTAX RowStatus 1789 MAX-ACCESS read-create 1790 STATUS current 1791 DESCRIPTION 1792 " The status of this table entry. Once the entry status is set to 1793 active." 1794 ::= { ippmResultSharingEntry 6 } 1796 -- 1798 -- 1799 -- 1800 -- ippmMeasure Group 1801 -- 1802 -- 1803 -- 1805 ippmMetricTable OBJECT-TYPE 1806 SYNTAX SEQUENCE OF IppmMetricEntry 1807 MAX-ACCESS not-accessible 1808 STATUS current 1809 DESCRIPTION 1810 "This table describes the current implementation and is 1811 mandatory. Each IPPM standardized metric must be described in the 1812 table. 1814 In reporting mode, the entries of this table may be not 1815 accessible. It means that the measurement software handles the 1816 table internally. 1818 ippmMetricTable is mandatory. 1819 ippmMetricTable content is read only." 1820 ::= { ippmMeasure 1 } 1822 ippmMetricEntry OBJECT-TYPE 1823 SYNTAX IppmMetricEntry 1824 MAX-ACCESS not-accessible 1825 STATUS current 1826 DESCRIPTION 1827 "An entry describes the static capabilities of a metric 1828 implementation." 1829 INDEX { ippmMetricIndex } 1830 ::= { ippmMetricTable 1 } 1832 IppmMetricEntry ::= 1833 SEQUENCE { 1834 ippmMetricIndex Integer32, 1835 ippmMetricCapabilities INTEGER, 1836 ippmMetricUnit INTEGER, 1837 ippmMetricDescription SnmpAdminString, 1838 ippmMetricMaxHistorySize Integer32 1839 } 1841 ippmMetricIndex OBJECT-TYPE 1842 SYNTAX Integer32 (1.. 65535) 1843 MAX-ACCESS not-accessible 1844 STATUS current 1845 DESCRIPTION 1846 "ippmMetricIndex defines an unambiguous index for each 1847 standardized metric. Its value is the value of the node of the 1848 metric in the IPPM-REPORTING-MIB metrics registry 1849 ippmMib.metrics.rfc. 1850 Each metric registered in the standard registry must be present 1851 in this table. 1852 This index is used to identify the metric calculated between the 1853 IPPM-REPORTING-MIB entities involved in the measure. 1854 Example: 1855 The index of the metric onewayPacketLossAverage which is 1856 registered as ippmMib.metrics.rfc.onewayPacketLossAverage will 1857 always have the value 14." 1858 ::= { ippmMetricEntry 1 } 1860 ippmMetricCapabilities OBJECT-TYPE 1861 SYNTAX INTEGER { 1862 notImplemented(0), 1863 implemented(1) 1864 } 1865 MAX-ACCESS read-only 1866 STATUS current 1867 DESCRIPTION 1868 "A value of notImplemented implies the metric is not implemented. 1869 A value of implemented implies the metric is implemented." 1870 DEFVAL { implemented } 1871 ::= { ippmMetricEntry 2 } 1873 ippmMetricUnit OBJECT-TYPE 1874 SYNTAX INTEGER { 1875 noUnit(0), 1876 second(1), 1877 ms(2), 1878 us(3), 1879 ns(4), 1880 percentage(5), 1881 packets(6), 1882 byte(7), 1883 kbyte(8), 1884 megabyte(9) 1885 } 1886 MAX-ACCESS read-only 1887 STATUS current 1888 DESCRIPTION 1889 "The unit used in the current entity for the results of the 1890 measurement of this metric." 1891 ::= { ippmMetricEntry 3 } 1893 ippmMetricDescription OBJECT-TYPE 1894 SYNTAX SnmpAdminString 1895 MAX-ACCESS read-only 1896 STATUS current 1897 DESCRIPTION 1898 "A textual description of the metric implementation." 1899 ::= { ippmMetricEntry 4 } 1901 ippmMetricMaxHistorySize OBJECT-TYPE 1902 SYNTAX Integer32 1903 MAX-ACCESS read-only 1904 STATUS current 1905 DESCRIPTION 1906 "Specifies the maximum number of results that a metric measure 1907 can save in the ippmHistoryTable." 1908 DEFVAL { 200 } 1909 ::= { ippmMetricEntry 5 } 1910 -- 1911 -- ippmMeasureTable 1912 -- 1913 -- 1915 ippmMeasureTable OBJECT-TYPE 1916 SYNTAX SEQUENCE OF IppmMeasureEntry 1917 MAX-ACCESS not-accessible 1918 STATUS current 1919 DESCRIPTION 1920 "The table of all the IPPM measures which are running in the 1921 device. They may not all be active. 1923 A measure consists of a subset of metrics to compute. The results 1924 of the measure may be saved in the ippmHistoryTable. The 1925 configuration of the measure sets the size of the history 1926 requested in ippmMeasureHistorySize. 1928 The maximum number of MIB objects to be collected in the portion 1929 of ippmHistoryTable associated with this metric depends on the 1930 value of the ippmMetricMaxHistorySize. 1932 The value of each metric ippmMeasureHistorySize must not be over 1933 the value of ippmMetricMaxHistorySize corresponding to this 1934 metric in the ippmMetricTable. 1936 The ippmMeasureTable is mandatory. 1938 ippmMeasureTable content is read-create. The table is handled 1939 internally by the measurement software for network measures. 1941 The setup of network is not permitted through the IPPM REPORTING 1942 MIB. OWAP provides a setup protocol to enable and teardown 1943 networks measures." 1944 ::= { ippmMeasure 2 } 1946 ippmMeasureEntry OBJECT-TYPE 1947 SYNTAX IppmMeasureEntry 1948 MAX-ACCESS not-accessible 1949 STATUS current 1950 DESCRIPTION 1951 "The measure entries are created/deleted internally by the 1952 measurement software." 1953 INDEX { ippmMeasureOwner, ippmMeasureIndex } 1954 ::= { ippmMeasureTable 1 } 1956 IppmMeasureEntry ::= 1957 SEQUENCE { 1958 ippmMeasureOwner IppmOwnerString, 1959 ippmMeasureIndex Integer32, 1960 ippmMeasureName SnmpAdminString, 1961 ippmMeasureMetrics IppmStandardMetrics, 1962 ippmMeasureBeginTime GMTTimeStamp, 1963 ippmMeasureClockPeriodUnit TimeUnit, 1964 ippmMeasureClockPeriod Integer32, 1965 ippmMeasureDurationUnit TimeUnit, 1966 ippmMeasureDuration Integer32, 1967 ippmMeasureHistorySize Integer32, 1968 ippmMeasureStorageType StorageType, 1969 ippmMeasureStatus RowStatus 1970 } 1972 ippmMeasureOwner OBJECT-TYPE 1973 SYNTAX IppmOwnerString 1974 MAX-ACCESS not-accessible 1975 STATUS current 1976 DESCRIPTION 1977 "The owner who has configured this entry." 1978 ::= { ippmMeasureEntry 1 } 1980 ippmMeasureIndex OBJECT-TYPE 1981 SYNTAX Integer32 (1.. 65535) 1982 MAX-ACCESS not-accessible 1983 STATUS current 1984 DESCRIPTION 1985 "The owner index of the measure. The value is managed by the 1986 owner." 1987 ::= { ippmMeasureEntry 2 } 1989 ippmMeasureName OBJECT-TYPE 1990 SYNTAX SnmpAdminString 1991 MAX-ACCESS read-create 1992 STATUS current 1993 DESCRIPTION 1994 "The name of the instance of the metric. It illustrates the 1995 specificity of the metric and includes the metric and the typeP. 1997 example: IP-port-HTTP-connectivity" 1998 ::= { ippmMeasureEntry 3 } 2000 ippmMeasureMetrics OBJECT-TYPE 2001 SYNTAX IppmStandardMetrics 2002 MAX-ACCESS read-create 2003 STATUS current 2004 DESCRIPTION 2005 "Defines the metrics to compute within this measure. A measure 2006 may be configured for the result of different metric singletons 2007 to be archived in the ippmHistoryTable. The ippmMetricIndex of 2008 the created result has the value of the bit index of the 2009 corresponding ippmMeasureMetrics as explained above in the 2010 ippmMetricIndex definition. 2012 Example: 2013 A measure asking for One-way-Delay(6) and One-way-Packet-Loss(12) 2014 generated a flow of singletons which are logged in the 2015 ippmHistoryTable. The singletons created for the One-way-Delay 2016 measure have a value of ippmMetricIndex of 6 while the created 2017 singletons for the One-way-Packet-Loss measure have a value of 2018 ippmMetricIndex of 12." 2019 -- { one-way-Delay, one-way-Packet-Loss } 2020 DEFVAL { '0001000001000000'b } 2021 ::= { ippmMeasureEntry 4 } 2023 ippmMeasureBeginTime OBJECT-TYPE 2024 SYNTAX GMTTimeStamp 2025 MAX-ACCESS read-create 2026 STATUS current 2027 DESCRIPTION 2028 "Specifies the time at which the measure starts." 2029 ::= { ippmMeasureEntry 5 } 2031 ippmMeasureClockPeriodUnit OBJECT-TYPE 2032 SYNTAX TimeUnit 2033 MAX-ACCESS read-create 2034 STATUS current 2035 DESCRIPTION 2036 "Specifies the unit of the measure period." 2037 DEFVAL { second } 2038 ::= { ippmMeasureEntry 6 } 2040 ippmMeasureClockPeriod OBJECT-TYPE 2041 SYNTAX Integer32 2042 MAX-ACCESS read-create 2043 STATUS current 2044 DESCRIPTION 2045 "Specifies the amount of time between 2 measurement action 2046 intervals. The action is specific to the semantic of the measure. 2048 Network metrics: 2050 The ippmNetworkMeasureClockPattern transforms the flow of 2051 periodical instants as a flow of unpredictable instants of 2052 measurement packet emission. 2054 As the source and the sink share the definition of the clock of 2055 the measure, as the sending timestamp is part of the measurement 2056 packet, the sink have the information to verify that the stream 2057 of packets generated by the source respects the clock law. 2059 Aggregated metrics: 2061 They are performed periodically on a sequence of results of other 2062 measures. The period corresponds to the interval between two 2063 successive computations of the metric. The value of 2064 ippmHistoryTimestamp result of a aggregated metric computed 2065 corresponds to the value of the ippmHistoryTimestamp of the last 2066 metric result of the sequence used in to compute the aggregated 2067 metric." 2068 DEFVAL { 60 } 2069 ::= { ippmMeasureEntry 7 } 2071 ippmMeasureDurationUnit OBJECT-TYPE 2072 SYNTAX TimeUnit 2073 MAX-ACCESS read-create 2074 STATUS current 2075 DESCRIPTION 2076 "Specifies the unit of the measure duration." 2077 DEFVAL { second } 2078 ::= { ippmMeasureEntry 8 } 2080 ippmMeasureDuration OBJECT-TYPE 2081 SYNTAX Integer32 2082 MAX-ACCESS read-create 2083 STATUS current 2084 DESCRIPTION 2085 "Specifies the duration of the measure." 2086 DEFVAL { 120 } 2087 ::= { ippmMeasureEntry 9 } 2089 ippmMeasureHistorySize OBJECT-TYPE 2090 SYNTAX Integer32 2091 MAX-ACCESS read-create 2092 STATUS current 2093 DESCRIPTION 2094 "Specifies the maximum number of results saved for each metric of 2095 this measure. The history of each metric is managed as a circular 2096 table. The newest result overwrites the oldest one when the 2097 history granted to this metric measure is full. 2099 The management of the results may be optimized if synchronized 2100 with the reports steps of this measure. " 2101 DEFVAL { 120 } 2102 ::= { ippmMeasureEntry 10 } 2104 ippmMeasureStorageType OBJECT-TYPE 2106 SYNTAX StorageType 2107 MAX-ACCESS read-create 2108 STATUS current 2109 DESCRIPTION 2110 "This object defines whether this row and the measure controlled 2111 by this row are kept in volatile storage and lost upon reboot or 2112 if this row is backed up 2113 by non-volatile or permanent storage. 2114 Possible values are: other(1), volatile(2), nonVolatile(3), 2115 permanent(4), readOnly(5)" 2116 DEFVAL { nonVolatile } 2117 ::= { ippmMeasureEntry 11 } 2119 ippmMeasureStatus OBJECT-TYPE 2120 SYNTAX RowStatus 2121 MAX-ACCESS read-create 2122 STATUS current 2123 DESCRIPTION 2124 "The status of this table entry. Once the entry status is set to 2125 active, the associate entry cannot be modified." 2126 ::= { ippmMeasureEntry 12 } 2128 -- 2129 -- ippmHistory Group 2130 -- 2131 -- 2133 -- 2134 -- ippmHistoryTable 2135 -- 2137 ippmHistoryTable OBJECT-TYPE 2138 SYNTAX SEQUENCE OF IppmHistoryEntry 2139 MAX-ACCESS not-accessible 2140 STATUS current 2141 DESCRIPTION 2142 "The table of the results of the measures." 2143 ::= { ippmHistory 1 } 2145 ippmHistoryEntry OBJECT-TYPE 2146 SYNTAX IppmHistoryEntry 2147 MAX-ACCESS not-accessible 2148 STATUS current 2149 DESCRIPTION 2150 "An ippmHistoryEntry entry is one of the results of a measure 2151 identified by ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex 2152 and ippmHistoryIndex. 2154 In the index : 2156 + ippmMeasureOwner identifies the owner of the measure; 2158 + ippmMeasureIndex identifies the measure in the owner namespace; 2160 + ippmMetricIndex identifies the metric measured in 2161 ippmMetricTable; 2163 + ippmHistoryIndex is the local index of the result on the 2164 history table." 2165 INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex, 2166 ippmHistoryIndex } 2167 ::= { ippmHistoryTable 1 } 2169 IppmHistoryEntry ::= 2170 SEQUENCE { 2171 ippmHistoryIndex Integer32, 2172 ippmHistorySequence Integer32, 2173 ippmHistoryTimestamp GMTTimeStamp, 2174 ippmHistoryValue Integer32 2175 } 2177 ippmHistoryIndex OBJECT-TYPE 2178 SYNTAX Integer32 (1.. 65535) 2179 MAX-ACCESS not-accessible 2180 STATUS current 2181 DESCRIPTION 2182 " A local index that only identifies a result in the history 2183 table." 2184 ::= { ippmHistoryEntry 1 } 2186 ippmHistorySequence OBJECT-TYPE 2187 SYNTAX Integer32 (1.. 65535) 2188 MAX-ACCESS read-only 2189 STATUS current 2190 DESCRIPTION 2191 "ippmHistorySequence is the sequence index of the measurement 2192 results of the measure of a metric. 2194 Network metrics: 2195 It's the sequence index of a measurement packet. Typically, it 2196 identifies the order of the packet in the stream of packets sends 2197 by the source. 2199 Aggregated metrics: 2200 It is the sequence index of the aggregated metric results 2201 computed." 2202 ::= { ippmHistoryEntry 2 } 2203 ippmHistoryTimestamp OBJECT-TYPE 2204 SYNTAX GMTTimeStamp 2205 MAX-ACCESS read-only 2206 STATUS current 2207 DESCRIPTION 2208 "The instant of the measure of the result." 2209 ::= { ippmHistoryEntry 3 } 2211 ippmHistoryValue OBJECT-TYPE 2212 SYNTAX Integer32 2213 MAX-ACCESS read-only 2214 STATUS current 2215 DESCRIPTION 2216 "The value of the measure." 2217 ::= { ippmHistoryEntry 4 } 2219 ippmOnHistoryFullAction OBJECT-TYPE 2220 SYNTAX INTEGER { 2221 wrap(1), 2222 suspend(2), 2223 resume(3) 2224 } 2225 MAX-ACCESS read-write 2226 STATUS current 2227 DESCRIPTION 2228 "Action to take when the history log is full. The user may choose 2229 to either wrap, in which case the agent writes over existing 2230 records. The user may choose to suspend writing to the log in the 2231 event that he wishes to archive the data. The resume action 2232 causes the agent to begin to write in the history log, and 2233 assumes the data has been cleared." 2234 ::= { ippmHistory 2 } 2236 -- 2237 -- ippmNetworkMeasure Group 2238 -- 2240 -- 2241 -- 2242 -- ippmNetworkMeasureTable 2243 -- 2244 -- 2246 ippmNetworkMeasureTable OBJECT-TYPE 2247 SYNTAX SEQUENCE OF IppmNetworkMeasureEntry 2248 MAX-ACCESS not-accessible 2249 STATUS current 2250 DESCRIPTION 2251 "A entry is a measure which performs network measures and 2252 provides a flow of results. 2254 This table extends the ippmMeasureTable. 2256 It performs several metric measurements per packet exchange. Each 2257 step of a measure produces a singleton result per metric. The 2258 time of the measure and the value of the metric are saved in the 2259 ippmHistoryTable." 2260 ::= { ippmNetworkMeasure 1 } 2262 ippmNetworkMeasureEntry OBJECT-TYPE 2263 SYNTAX IppmNetworkMeasureEntry 2264 MAX-ACCESS not-accessible 2265 STATUS current 2266 DESCRIPTION 2267 " Typically the configuration operation sets both the values of 2268 the new ippmMeasureEntry and of the new IppmNetworkMeasureEntry. 2270 IppmNetworkMeasureTable is mandatory. 2272 IppmNetworkMeasureTable content is read only. It means that the 2273 measurement software handles the table internally. The setup of 2274 network is not permitted through the IPPM REPORTING MIB. OWAP 2275 provides a setup protocol to enable and teardown networks 2276 measures. 2278 The ippmMeasureMetrics is set to a list of metrics to be computed 2279 from the same raw packet exchange. Each step of measurement 2280 delivers a singleton per chosen metric. Results are timestamped 2281 and saved in the ippmHistoryTable. 2283 The ippmNetworkMeasureTable typical usage consists is providing 2284 network measure indexes to permits aggregated measure to perform 2285 aggregation on the results of network measures. 2286 An obvious usage of the ippmNetworkMeasureTable consists in the 2287 verification of the network measures states." 2288 INDEX { ippmMeasureOwner, ippmMeasureIndex } 2289 ::= { ippmNetworkMeasureTable 1 } 2291 IppmNetworkMeasureEntry ::= 2292 SEQUENCE { 2293 ippmNetworkMeasureSrcTypeP TypeP, 2294 ippmNetworkMeasureSrc TypePaddress, 2295 ippmNetworkMeasureDstTypeP TypeP, 2296 ippmNetworkMeasureDst TypePaddress, 2297 ippmNetworkMeasureClockPattern OCTET STRING, 2298 ippmNetworkMeasurePoissonRate Integer32, 2299 ippmNetworkMeasureTimeoutDelay Integer32, 2300 ippmNetworkMeasureL3PacketSize Integer32, 2301 ippmNetworkMeasureDataPattern OCTET STRING 2302 } 2304 ippmNetworkMeasureSrcTypeP OBJECT-TYPE 2305 SYNTAX TypeP 2306 MAX-ACCESS read-only 2307 STATUS current 2308 DESCRIPTION 2309 "Defines the type P of the source address of the packets sent by 2310 the measure." 2311 DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0 2312 ::= { ippmNetworkMeasureEntry 1 } 2314 ippmNetworkMeasureSrc OBJECT-TYPE 2315 SYNTAX TypePaddress 2316 MAX-ACCESS read-only 2317 STATUS current 2318 DESCRIPTION 2319 "Specifies the address of the source of the measure. 2320 It is represented as a list of parameters corresponding to those 2321 of the PROTOCOL IDENTIFIER sets in ippmNetworkMeasureSrcTypeP." 2322 ::= { ippmNetworkMeasureEntry 2} 2324 ippmNetworkMeasureDstTypeP OBJECT-TYPE 2325 SYNTAX TypeP 2326 MAX-ACCESS read-only 2327 STATUS current 2328 DESCRIPTION 2329 "Defines the type P of the destination address of the packets 2330 sent by the measure." 2331 ::= { ippmNetworkMeasureEntry 3 } 2333 ippmNetworkMeasureDst OBJECT-TYPE 2334 SYNTAX TypePaddress 2335 MAX-ACCESS read-only 2336 STATUS current 2337 DESCRIPTION 2338 "Specifies the address of the source of the measure. 2339 It is represented as a list of parameters corresponding to those 2340 of the PROTOCOL IDENTIFIER sets in ippmNetworkMeasureSrcTypeP." 2341 ::= { ippmNetworkMeasureEntry 4 } 2343 ippmNetworkMeasureClockPattern OBJECT-TYPE 2344 SYNTAX OCTET STRING 2345 MAX-ACCESS read-only 2346 STATUS current 2347 DESCRIPTION 2348 "This cyclic clock shapes the profile of the instants of 2349 measurement action provided by ippmMeasureClockPeriod according 2350 to an arbitrary distribution law. The clock resolution is 2351 ippmMeasureClockPeriod. The bits of the clock pattern set to the 2352 value 1 determine the valid instants of measurement action. A 2353 measure is to be processed if and only if the current bit value 2354 is 1. 2355 This pseudo-random clock pattern allows the configuration by the 2356 NMS of numerous kind of time sampling law such as periodic, 2357 pseudo random or Poisson. 2359 The source of the measure sends the stream of measurement packets 2360 synchronously with the stream of instants selected by the clock 2361 pattern sampling. 2363 ippmNetworkMeasureClockPattern can not be used conjointly with 2364 ippmNetworkMeasurePoissonRate." 2365 DEFVAL { "11111111" } 2366 -- 100% periodic 2367 ::= { ippmNetworkMeasureEntry 5 } 2369 ippmNetworkMeasurePoissonRate OBJECT-TYPE 2370 SYNTAX Integer32 2371 MAX-ACCESS read-only 2372 STATUS current 2373 DESCRIPTION 2374 "Indicates the average number of packets per seconds sent using a 2375 poisson law. 2377 ippmNetworkMeasurePoissonRate can not be used conjointly with 2378 ippmNetworkMeasureClockPattern." 2379 DEFVAL { 30 } 2380 ::= { ippmNetworkMeasureEntry 6 } 2382 ippmNetworkMeasureTimeoutDelay OBJECT-TYPE 2383 SYNTAX Integer32 2384 MAX-ACCESS read-only 2385 STATUS current 2386 -- UNITS "Milliseconds" 2387 DESCRIPTION 2388 "Specifies the delay after which the packet is considered lost by the 2389 sink." 2390 DEFVAL { 1 } 2391 ::= { ippmNetworkMeasureEntry 7 } 2393 ippmNetworkMeasureL3PacketSize OBJECT-TYPE 2394 SYNTAX Integer32 2395 MAX-ACCESS read-only 2396 STATUS current 2397 DESCRIPTION 2398 "Specifies the size of the packets sent at the last network layer 2399 in regards to the TypeP definition." 2400 DEFVAL { 64 } 2401 ::= { ippmNetworkMeasureEntry 8 } 2403 ippmNetworkMeasureDataPattern OBJECT-TYPE 2404 SYNTAX OCTET STRING 2405 MAX-ACCESS read-only 2406 STATUS current 2407 DESCRIPTION 2408 "The current field defines the round robin pattern used to fill 2409 the packet." 2410 DEFVAL { 'FF'H } 2411 ::= { ippmNetworkMeasureEntry 9 } 2413 -- 2414 -- 2415 -- ippmAggrMeasure Group 2416 -- 2417 -- 2418 -- 2419 -- 2420 -- ippmAggrMeasureTable 2421 -- 2422 -- 2424 ippmAggrMeasureTable OBJECT-TYPE 2425 SYNTAX SEQUENCE OF IppmAggrMeasureEntry 2426 MAX-ACCESS not-accessible 2427 STATUS current 2428 DESCRIPTION 2429 " This table extends the ippmMeasureTable. 2430 An aggregated measure summarizes the results of previous network 2431 or aggregated measures. The results may be saved in the 2432 ippmHistoryTable. 2434 Each step of the calculation for the measure produces a singleton 2435 result per metric." 2436 ::= { ippmAggrMeasure 1 } 2438 ippmAggrMeasureEntry OBJECT-TYPE 2439 SYNTAX IppmAggrMeasureEntry 2440 MAX-ACCESS not-accessible 2441 STATUS current 2442 DESCRIPTION 2443 "Typically the configuration operation sets both the values of 2444 the new ippmMeasureEntry and of the new IppmAggrMeasureEntry. 2446 ippmAggrMeasureTable is mandatory. 2448 ippmAggrMeasureTable content is read only. It means that the 2449 measure software handles the table internally. 2451 The ippmMeasureMetrics defines the metric to compute. 2452 The results of the measure to summarize are identified by: 2453 + ippmAggrMeasureHistoryOwner, 2454 + ippmAggrMeasureHistoryOwnerIndex and 2455 + ippmAggrMeasureHistoryMetric 2457 The aggregated task starts at ippmMeasureBeginTime and ends after 2458 ippmMeasureDuration. An aggregated result is performed and saved 2459 in the ippmHistoryTable for each ippmMeasureClockPeriod tick. " 2460 INDEX { ippmMeasureOwner, ippmMeasureIndex } 2461 ::= { ippmAggrMeasureTable 1 } 2463 IppmAggrMeasureEntry ::= 2464 SEQUENCE { 2465 ippmAggrMeasureHistoryOwner IppmOwnerString, 2466 ippmAggrMeasureHistoryOwnerIndex Integer32, 2467 ippmAggrMeasureHistoryMetric Integer32 2468 } 2470 ippmAggrMeasureHistoryOwner OBJECT-TYPE 2471 SYNTAX IppmOwnerString 2472 MAX-ACCESS read-create 2473 STATUS current 2474 DESCRIPTION 2475 "The owner of the measure to summarize. " 2476 ::= { ippmAggrMeasureEntry 1 } 2478 ippmAggrMeasureHistoryOwnerIndex OBJECT-TYPE 2479 SYNTAX Integer32 (1.. 65535) 2480 MAX-ACCESS read-create 2481 STATUS current 2482 DESCRIPTION 2483 "The owner index of the measure to summarize. " 2484 ::= { ippmAggrMeasureEntry 2 } 2486 ippmAggrMeasureHistoryMetric OBJECT-TYPE 2487 SYNTAX Integer32 2488 MAX-ACCESS read-create 2489 STATUS current 2490 DESCRIPTION 2491 "The metric of the measure to summarize. " 2492 ::= { ippmAggrMeasureEntry 3 } 2494 -- 2495 -- ippmReport Group 2496 -- 2498 -- 2499 -- 2500 -- ippmReportSetupTable 2501 -- 2502 -- 2504 ippmReportSetupTable OBJECT-TYPE 2505 SYNTAX SEQUENCE OF IppmReportSetupEntry 2506 MAX-ACCESS not-accessible 2507 STATUS current 2508 DESCRIPTION 2509 "The ippmReportSetupTable is a list of definition of reports. It 2510 defines the results of a network or aggregated measures that are 2511 to be reported. A report is saved in the ippmReportTable, or sent 2512 to an application using a SNMP Trap, a SNMP inform PDU, an email 2513 or a SMS. The reporting task is not intended to be a batch action 2514 processed at the end of the measure. It is coupled with threshold 2515 detections and event filtering to deliver application level 2516 events and data, while preserving scalability. 2518 It extends the definition of a measure: the definition of a 2519 measure may include the definition of a report." 2520 ::= { ippmReport 1 } 2522 ippmReportSetupEntry OBJECT-TYPE 2523 SYNTAX IppmReportSetupEntry 2524 MAX-ACCESS not-accessible 2525 STATUS current 2526 DESCRIPTION 2527 "The report applies to the results of the measure which is 2528 extended by the current report definition. 2530 Typically the creation of a report sets both the values of the 2531 new measure and those of the new IppmReportSetupEntry. 2532 The ippmReportSetupDefinition describes the data and the events 2533 to include in the report. The definition consists in a list of 2534 tasks to perform on the results of the measure. 2536 A report is associated to a network measure or to an aggregated 2537 measure. 2539 Note 1 : To associate a report to an existing measure the manager 2540 suspends the measure while setting the ippmMeasureStatus to 2541 'notInService'. Then he setups the report fields and activates 2542 the measure while setting the ippmMeasureStatus to 'active'. 2544 Note 2 : A report is tied to a measure. The period of the measure 2545 " 2546 INDEX { ippmMeasureOwner, ippmMeasureIndex } 2547 ::= { ippmReportSetupTable 1 } 2549 IppmReportSetupEntry ::= 2550 SEQUENCE { 2551 ippmReportSetupDefinition IppmReportDefinition, 2552 ippmReportSetupMetricThreshold Integer32, 2553 ippmReportSetupDurationThreshold Integer32, 2554 ippmReportSetupNMS SnmpAdminString, 2555 ippmReportSetupNotification OBJECT IDENTIFIER, 2556 ippmReportSetupStatus RowStatus 2557 } 2559 ippmReportSetupDefinition OBJECT-TYPE 2560 SYNTAX IppmReportDefinition 2561 MAX-ACCESS read-create 2562 STATUS current 2563 DESCRIPTION 2564 "The description of the events and actions that are used in the 2565 definition of the report. 2566 Send the report using the type of message selected by the bits 8 2567 to 12. The report consists of the results of the measure which 2568 have been saved in the ippmReportTable. If the 2569 onEventSendReport(7) bit is unset, the report is not saved. 2571 The message sent is a notification defined in the 2572 ippmNotifications node. The notification sent depends on the step 2573 of the measure: 2574 + Singleton events are sent using the notification 2575 ippmSingletonAlarm 2576 + Exceeded events durations are sent using the notification 2577 ippmEventsDurationExceededAlarm 2578 + A report of a cycle of measure is sent using the notification 2579 ippmCycleOfMeasureReport 2580 + A report of a complete measure is sent using the notification 2581 ippmCompletedMeasureReport 2583 Example 1: 2584 The report setup of an alarm to be sent to the owner in a SNMP 2585 Trap each time the two results are found on each side of the 2586 metric threshold value of 5: 2588 ippmReportSetupMetricThreshold 5 2589 ippmReportSetupDefinition { 2590 onSingleton(1), 2591 reportOnlyUptoDownMetricResults(4), 2592 inSNMPTrapPDU(8) 2593 } 2595 Example 2: 2597 The setup of a report to be sent to the owner in a SNMP 2598 informRequestPDU per measure cycle. It reports the two results 2599 found on each side of the metric threshold of 5: 2601 ippmReportSetupMetricThreshold 5 2602 ippmReportSetupDefinition { 2603 onMeasureCycle(2), 2604 reportOnlyUptoDownMetricResults(4), 2605 inInformRequestPDU(10), 2606 onReportDeliveryClearHistory(13) 2607 } 2609 Default report: 2610 The default report provides the control protocol with an implicit 2611 mechanism to forward the result of a cycle of measure to the 2612 owner of the measure while deleting the results corresponding to 2613 this cycle of measure from the ippmHistoryTable on reception of 2614 the response to the InformRequestPDU : 2615 ippmReportSetupDefinition { 2616 onMeasureCycle(2), 2617 inInformRequestPDU(10), 2618 onReportDeliveryClearHistory(13) 2619 } 2620 " 2621 DEFVAL { { onMeasureCycle, inInformRequestPDU, 2622 onReportDeliveryClearHistory} } 2623 ::= { ippmReportSetupEntry 1 } 2625 ippmReportSetupMetricThreshold OBJECT-TYPE 2626 SYNTAX Integer32 2627 MAX-ACCESS read-create 2628 STATUS current 2629 DESCRIPTION 2630 "An event is generated when the result of the measure exceeds the 2631 value of ippmReportSetupMetricThreshold. 2632 The threshold has the same unit as the metric. The metric unit is 2633 recorded in the object ippmMetricsUnit of this metric entry in 2634 the ippmMetricTable. 2635 " 2636 ::= { ippmReportSetupEntry 2 } 2638 ippmReportSetupDurationThreshold OBJECT-TYPE 2639 SYNTAX Integer32 2640 UNITS "Seconds" 2641 MAX-ACCESS read-create 2642 STATUS current 2643 DESCRIPTION 2644 "An event is generated when contiguous results of the measure are 2645 over the ippmReportSetupMetricThreshold, during 2646 ippmReportSetupDurationThreshold seconds. 2648 Performance: 2649 To improve the performance the ippmReportSetupDurationThreshold 2650 may have the same value as the ippmMeasurePeriod. 2651 The default value of ippmReportSetupDurationThreshold is 2652 ippmMeasurePeriod. That improves the performance because the 2653 threshold comparison is synchronized with the ippmMeasurePeriod 2654 aggregation cycle. That improves the performance because it 2655 synchronized the report exportation with the management of the 2656 history and report records of a measure." 2658 DEFVAL { 15 } 2659 ::= { ippmReportSetupEntry 3 } 2661 ippmReportSetupNMS OBJECT-TYPE 2662 SYNTAX SnmpAdminString 2663 MAX-ACCESS read-create 2664 STATUS current 2665 DESCRIPTION 2666 "The recipient of the report may be provided in the setup. By 2667 default the recipient of the report is the owner of the measure. 2668 Its addresses are recorded in the ippmOwnersTable. 2669 The type of ippmReportSetupNMS is not InetAddress because the 2670 report may be sent using SMS or fax. 2671 " 2672 ::= { ippmReportSetupEntry 4 } 2674 ippmReportSetupNotification OBJECT-TYPE 2675 SYNTAX OBJECT IDENTIFIER 2676 MAX-ACCESS read-create 2677 STATUS current 2678 DESCRIPTION 2679 " ippmReportSetupNotification identifies the notification used to 2680 send the report. The definition of the notification defines the 2681 content and the format of the report. " 2682 ::= { ippmReportSetupEntry 5 } 2684 ippmReportSetupStatus OBJECT-TYPE 2685 SYNTAX RowStatus 2686 MAX-ACCESS read-create 2687 STATUS current 2688 DESCRIPTION 2689 "The status of this table entry. " 2690 ::= { ippmReportSetupEntry 6 } 2692 -- 2693 -- ippmReportTable 2694 -- 2695 ippmReportTable OBJECT-TYPE 2696 SYNTAX SEQUENCE OF IppmReportEntry 2697 MAX-ACCESS not-accessible 2698 STATUS current 2699 DESCRIPTION 2700 "The ippmReportTable logs the results of the reports. The results 2701 consist of a subset of the results of a measure as described in 2702 the report definition. The activation of an up and down filtering 2703 in the report definition limits the results logged to those 2704 corresponding to major events. Otherwise, the ippmReportTable is 2705 identical to the ippmHistoryTable." 2707 ::= { ippmReport 2 } 2709 ippmReportEntry OBJECT-TYPE 2710 SYNTAX IppmReportEntry 2711 MAX-ACCESS not-accessible 2712 STATUS current 2713 DESCRIPTION 2714 "A report is a list of results of a measure. This sample is 2715 associated with the ippmReportSetupEntry which has set up the 2716 report. An ippmReportEntry entry is one of the results of a 2717 measure to report. 2719 An ippmReportEntry entry is one of the results of a measure 2720 identified by ippmReportOwner, ippmReportIndex, ippmReportIndex 2721 and ippmHistoryIndex. 2723 In the index: 2725 + ippmMeasureOwner identifies the owner of the measure; 2727 + ippmMeasureIndex identifies the measure in the owner namespace; 2729 + ippmMetricIndex identifies the metric measured in 2730 ippmMetricTable; 2732 + ippmReportIndex is the local index of the result on the report 2733 table." 2735 INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex, 2736 ippmReportIndex } 2737 ::= { ippmReportTable 1 } 2739 IppmReportEntry ::= 2740 SEQUENCE { 2741 ippmReportIndex Integer32, 2742 ippmReportSequence Integer32, 2743 ippmReportTimestamp GMTTimeStamp, 2744 ippmReportValue Integer32 2745 } 2747 ippmReportIndex OBJECT-TYPE 2748 SYNTAX Integer32 (1.. 65535) 2749 MAX-ACCESS not-accessible 2750 STATUS current 2751 DESCRIPTION 2752 "The local index of the result of a metric measure" 2753 ::= { ippmReportEntry 1 } 2755 ippmReportSequence OBJECT-TYPE 2756 SYNTAX Integer32 (1.. 65535) 2757 MAX-ACCESS read-only 2758 STATUS current 2759 DESCRIPTION 2761 " ippmReportSequence is the sequence index of the measurement 2762 results of the measure of a metric. 2764 Network metrics: 2766 It's the sequence index of a measurement packet. Typically, it 2767 identifies the order of the packet in the stream of packets sends 2768 by the source. 2770 Aggregated metrics: 2772 It is the sequence index of the aggregated metric results 2773 computed." 2774 ::= { ippmReportEntry 2 } 2776 ippmReportTimestamp OBJECT-TYPE 2777 SYNTAX GMTTimeStamp 2778 MAX-ACCESS read-only 2779 STATUS current 2780 DESCRIPTION 2781 "The instant of the measure of the result." 2782 ::= { ippmReportEntry 3 } 2784 ippmReportValue OBJECT-TYPE 2785 SYNTAX Integer32 2786 MAX-ACCESS read-only 2787 STATUS current 2788 DESCRIPTION 2789 "The value." 2790 ::= { ippmReportEntry 4 } 2791 ippmOnReportFullAction OBJECT-TYPE 2792 SYNTAX INTEGER { 2793 wrap(1), 2794 suspend(2), 2795 resume(3) 2796 } 2798 MAX-ACCESS read-write 2799 STATUS current 2800 DESCRIPTION 2801 "Action to take when the report log is full. The user may choose 2802 to either wrap, in which case the agent writes over existing 2803 records. The user may choose to suspend writing to the log in the 2804 event that he wishes to archive the data. The resume action 2805 causes the agent to begin to write in the report log, and assumes 2806 the data has been cleared." 2808 ::= { ippmReport 3 } 2810 -- 2811 -- IPPM Notifications 2812 -- 2814 ippmSingletonAlarm NOTIFICATION-TYPE 2815 OBJECTS { 2816 ippmMetricUnit, 2817 ippmReportTimestamp, 2818 ippmReportValue 2819 } 2820 STATUS current 2821 DESCRIPTION 2822 "A notification sent because 2 contiguous results are on opposite 2823 sides of the metric threshold value. 2825 The notification contains the instances of the ippmReportValue 2826 object that exceeded the threshold. 2827 The notification contains the instances of the 2828 ippmReportTimestamp identifying the time the event occurred." 2829 ::= { ippmNotifications 1 } 2831 ippmEventsDurationExceededAlarm NOTIFICATION-TYPE 2832 OBJECTS { 2833 ippmMetricUnit, 2834 ippmReportTimestamp, 2835 ippmReportValue 2836 } 2837 STATUS current 2838 DESCRIPTION 2839 "A notification sent when the duration of contiguous raising 2840 ippmReportSetupMetricThreshold exceeds the 2841 ippmReportSetupDurationThreshold value. 2843 The notification contains the instances of the ippmReportValue 2844 object that exceeded the threshold. 2846 The notification contains the instances of the 2847 ippmReportTimestamp identifying the time the event occurred." 2848 ::= { ippmNotifications 2 } 2850 ippmCycleOfMeasureReport NOTIFICATION-TYPE 2851 OBJECTS { 2852 ippmMetricUnit, 2853 ippmHistoryTimestamp, 2854 ippmHistoryValue 2855 } 2856 STATUS current 2857 DESCRIPTION 2858 "A notification sent when a measure cycle completes. 2860 The notification contains the instances of the ippmReportValue 2861 objects saved in the ippmReportTable for this measure cycle. The 2862 ippmHistoryTimestamp of the index identifies the time the 2863 measures where performed." 2864 ::= { ippmNotifications 3 } 2866 ippmCompletedMeasureReport NOTIFICATION-TYPE 2867 OBJECTS { 2868 ippmMetricUnit, 2869 ippmHistoryTimestamp, 2870 ippmHistoryValue 2871 } 2872 STATUS current 2873 DESCRIPTION 2874 "A notification sent when a measure completes. 2875 The index of the included ippmReportSetupDefinition object 2876 identifies the ippmMeasureEntry and the ippmResultSetupEntry that 2877 specified the report. 2879 The notification contains the instances of the ippmReportValue 2880 objects saved in the ippmReportTable for this measure cycle. The 2881 ippmHistoryTimestamp of the index identifies the time the 2882 measures where performed." 2883 ::= { ippmNotifications 4 } 2885 ippmHistoryLogFull NOTIFICATION-TYPE 2886 OBJECTS { 2887 ippmOnHistoryFullAction 2888 } 2889 STATUS current 2890 DESCRIPTION 2891 "A notification sent when the history log is full. It indicates 2892 what action is to be taken. If the action is wrap the agent will 2893 write over existing records in the beginning of the log file. If 2894 the action is suspend, the agent halts all recording of measures 2895 in the history table. If the action is resume, the agent begins 2896 writing measures again in the history log" 2897 ::= { ippmNotifications 5 } 2899 ippmReportLogFull NOTIFICATION-TYPE 2900 OBJECTS { 2901 ippmOnReportFullAction 2902 } 2903 STATUS current 2904 DESCRIPTION 2905 "A notification sent when the report log is full. It indicates 2906 what action is to be taken. If the action is wrap the agent will 2907 write over existing records in the beginning of the log file. If 2908 the action is suspend, the agent halts all recording of measures 2909 in the report table. If the action is resume, the agent begins 2910 writing measures again in the report log" 2911 ::= { ippmNotifications 6 } 2913 -- 2914 -- IPPM MIB Conformance statements 2915 -- 2917 ippmCompliances OBJECT IDENTIFIER ::={ ippmConformance 1 } 2919 ippmGroups OBJECT IDENTIFIER ::={ ippmConformance 2 } 2921 ippmProxyInterDomainCompliances MODULE-COMPLIANCE 2922 STATUS current 2923 DESCRIPTION 2924 "The compliance statement for SNMP entities which implement the 2925 IPPM MIB as a proxy in interdomain. The implementation of the 2926 VACM control is mandatory." 2927 MODULE -- this module 2928 MANDATORY-GROUPS { 2929 ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, 2930 ippmHistoryGroup, ippmAggrMeasureGroup, ippmReportGroup, 2931 ippmNotificationGroup 2932 } 2933 ::= { ippmCompliances 1 } 2935 ippmProxyCompliances MODULE-COMPLIANCE 2936 STATUS current 2937 DESCRIPTION 2938 "The compliance statement for SNMP entities which implement the 2939 IPPM MIB as a proxy." 2940 MODULE -- this module 2941 MANDATORY-GROUPS { 2942 ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, 2943 ippmHistoryGroup, ippmAggrMeasureGroup, ippmReportGroup, 2944 ippmNotificationGroup 2945 } 2946 GROUP ippmOwnersGroup 2947 DESCRIPTION 2948 "The ippmOwnersGroup is needed if VACM is not implemented." 2949 ::= { ippmCompliances 2 } 2951 ippmProbeCompliances MODULE-COMPLIANCE 2952 STATUS current 2953 DESCRIPTION 2954 "The compliance statement for SNMP entities which implement the 2955 IPPM MIB in a probe." 2956 MODULE -- this module 2957 MANDATORY-GROUPS { 2958 ippmSystemGroup, ippmMeasureGroup, ippmNetworkMeasureGroup, 2959 ippmHistoryGroup 2960 } 2961 ::= { ippmCompliances 3 } 2963 ippmSystemGroup OBJECT-GROUP 2964 OBJECTS { 2965 ippmSystemSynchronizationDesc, 2966 ippmSystemTime, 2967 ippmSystemSynchronizationType, 2968 ippmSystemClockResolution, 2969 ippmSystemCurrentSynchronization, 2970 ippmSynchronizationTime, 2971 ippmSynchronizationStratum, 2972 ippmSynchronizationResolution, 2973 ippmPointOfMeasureMgmtAddrType, 2974 ippmPointOfMeasureMgmtAddress, 2975 ippmPointOfMeasureTypePAddress, 2976 ippmPointOfMeasureAddress 2977 } 2978 STATUS current 2979 DESCRIPTION 2980 "The IPPM System Group" 2981 ::= { ippmGroups 1} 2983 ippmMeasureGroup OBJECT-GROUP 2984 OBJECTS { 2985 ippmMetricCapabilities, 2986 ippmMetricUnit, 2987 ippmMetricDescription, 2988 ippmMetricMaxHistorySize, 2989 ippmMeasureName, 2990 ippmMeasureMetrics, 2991 ippmMeasureBeginTime, 2992 ippmMeasureClockPeriodUnit, 2993 ippmMeasureClockPeriod, 2994 ippmMeasureDurationUnit, 2995 ippmMeasureDuration, 2996 ippmMeasureHistorySize, 2997 ippmMeasureStorageType, 2998 ippmMeasureStatus 2999 } 3000 STATUS current 3001 DESCRIPTION 3002 "The IPPM Measure Group" 3003 ::= { ippmGroups 2} 3005 ippmNetworkMeasureGroup OBJECT-GROUP 3006 OBJECTS { 3007 ippmNetworkMeasureSrcTypeP, 3008 ippmNetworkMeasureSrc, 3009 ippmNetworkMeasureDstTypeP, 3010 ippmNetworkMeasureDst, 3011 ippmNetworkMeasureClockPattern, 3012 ippmNetworkMeasurePoissonRate, 3013 ippmNetworkMeasureTimeoutDelay, 3014 ippmNetworkMeasureL3PacketSize, 3015 ippmNetworkMeasureDataPattern 3016 } 3017 STATUS current 3018 DESCRIPTION 3019 "The IPPM Network Measure Group" 3020 ::= { ippmGroups 3} 3022 ippmHistoryGroup OBJECT-GROUP 3023 OBJECTS { 3024 ippmHistorySequence, 3025 ippmHistoryTimestamp, 3026 ippmOnHistoryFullAction, 3027 ippmHistoryValue 3028 } 3029 STATUS current 3030 DESCRIPTION 3031 "The IPPM History Group" 3032 ::= { ippmGroups 4} 3034 ippmAggrMeasureGroup OBJECT-GROUP 3035 OBJECTS { 3036 ippmAggrMeasureHistoryOwner, 3037 ippmAggrMeasureHistoryOwnerIndex, 3038 ippmAggrMeasureHistoryMetric 3039 } 3040 STATUS current 3041 DESCRIPTION 3042 "The IPPM AggregatedMeasure Group" 3043 ::= { ippmGroups 5} 3045 ippmReportGroup OBJECT-GROUP 3046 OBJECTS { 3047 ippmReportSetupDefinition, 3048 ippmReportSetupMetricThreshold, 3049 ippmReportSetupDurationThreshold, 3050 ippmReportSetupNMS, 3051 ippmReportSetupNotification, 3052 ippmReportSetupStatus, 3053 ippmReportSequence, 3054 ippmReportTimestamp, 3055 ippmReportValue, 3056 ippmOnReportFullAction 3057 } 3058 STATUS current 3059 DESCRIPTION 3060 "The IPPM Report Group" 3061 ::= { ippmGroups 6} 3063 ippmOwnersGroup OBJECT-GROUP 3064 OBJECTS { 3065 ippmOwnersOwner, 3066 ippmOwnersGrantedMetrics, 3067 ippmOwnersGrantedRules, 3068 ippmOwnersIpAddress, 3069 ippmOwnersEmail, 3070 ippmOwnersSMS, 3071 ippmOwnersStatus, 3072 ippmOwnersIpAddressType, 3073 ippmResultSharingMeasureOwner, 3074 ippmResultSharingMeasureIndex, 3075 ippmResultSharingGrantedOwner, 3076 ippmResultSharingStatus 3077 } 3078 STATUS current 3079 DESCRIPTION 3080 "The IPPM Owners Group" 3081 ::= { ippmGroups 7} 3083 ippmNotificationGroup NOTIFICATION-GROUP 3084 NOTIFICATIONS { 3085 ippmSingletonAlarm, 3086 ippmCycleOfMeasureReport, 3087 ippmCompletedMeasureReport, 3088 ippmEventsDurationExceededAlarm, 3089 ippmHistoryLogFull, 3090 ippmReportLogFull 3091 } 3092 STATUS current 3093 DESCRIPTION 3094 "The IPPM Notification Group" 3095 ::= { ippmGroups 8} 3097 END 3099 9. Security Considerations 3101 9.1. Privacy 3103 The privacy concerns of network measurement are intrinsically limited 3104 by the active measurements. Unlike passive measurements, there can be 3105 no release of existing user data. 3107 9.2. Measurement aspects 3109 Conducting Internet measurements raises both security and privacy 3110 concerns. This memo does not specify an implementation of the 3111 metrics, so it does not directly affect the security of the Internet 3112 nor of applications that run on the Internet. However, 3113 implementations of these metrics must be mindful of security and 3114 privacy concerns. 3116 There are two types of security concerns: potential harm caused by 3117 the measurements, and potential harm to the measurements. The 3118 measurements could cause harm because they are active, and inject 3119 packets into the network. The measurement parameters MUST be 3120 carefully selected so that the measurements inject trivial amounts of 3121 additional traffic into the networks they measure. If they inject 3122 "too much" traffic, they can skew the results of the measurement, and 3123 in extreme cases cause congestion and denial of service. 3125 The measurements themselves could be harmed by routers giving 3126 measurement traffic a different priority than "normal" traffic, or by 3127 an attacker injecting artificial measurement traffic. If routers can 3128 recognize measurement traffic and treat it separately, the 3129 measurements will not reflect actual user traffic. If an attacker 3130 injects artificial traffic that is accepted as legitimate, the loss 3131 rate will be artificially lowered. Therefore, the measurement 3132 methodologies SHOULD include appropriate techniques to reduce the 3133 probability measurement traffic can be distinguished from "normal" 3134 traffic. 3136 Authentication techniques, such as digital signatures, may be used 3137 where appropriate to guard against injected traffic attacks. 3139 9.3. Management aspects 3141 There are a number of management objects defined in this MIB that 3142 have a MAX-ACCESS clause of read-write and/or read-only. Such objects 3143 may be considered sensitive or vulnerable in some network 3144 environments. The support for SET operations in a non-secure 3145 environment without proper protection can have a negative effect on 3146 network operations. 3148 SNMPv1 by itself is not a secure environment. Even if the network 3149 itself is secure (for example by using IPSec), even then, there is no 3150 control as to who on the secure network is allowed to access and 3151 GET/SET (read/change/create/delete) the objects in this MIB. 3153 It is recommended that the implementors consider the security 3154 features as provided by the SNMPv3 framework. Specifically, the use 3155 of the User-based Security Model RFC 2574 [18] and the View-based 3156 Access Control Model RFC 2575 [21] is recommended. 3158 It is then a customer/user responsibility to ensure that the SNMP 3159 entity giving access to an instance of this MIB, is properly 3160 configured to give access to the objects only to those principals 3161 (users) that have legitimate rights to indeed GET or SET 3162 (change/create/delete) them. 3164 10. Document management 3166 10.1. Open issues 3168 Describe incompatible bit combinations in IPPMreport and granted 3169 metric 3171 Run SMIlint. 3173 Discussion on the management of the history size. 3175 10.2. changes since release 00 3177 + Put in a description of the relationship of certain tables, 3178 particularly the measure/network measure/aggregated measure table. 3180 + The TC GMTTimeStamp is the common type to define timestamp objects. 3182 + ippmHisoryTable index simplified: ippmHistoryTimestamp replaced 3183 with ippmHistorySqceNdx in the index. 3185 + The MIB has been compiled using net-snmp. 3187 + Snmpadminstring replaces Displaystring. 3189 + IP addresses defined using INETaddresstype. 3191 + Sharing table is optional to permit the VACM framework to be used. 3193 + The description of the network measure table emphases that the set 3194 up of network measure is not permitted using SNMP. 3196 + The TC StandardMetrics is removed and replaced with the table 3197 ippmMetricsTable. 3199 + The table pointOfMeasureTable is added to describe multiples 3200 interfaces devices 3202 + 5 tables have been changed to read/create: ippmOwnersTable, 3203 ippmMeasureTable, ippmAggrMeasureTable, ippmResultSharingTable, and 3204 ippmReportSetupTable. 3206 + IppmHistoryTable and ippmReportTable index reviews: 3208 IppmHistorySqceNdx field added in the ippmHistoryTable. 3209 INDEX modified. IppmHistorySqceNdx replaces IppmHistoryTimemark. 3211 + IppmSystem group refurbished: 3212 IppmSystemTimer renamed ippmSystemTime. 3213 Current and last synch event concept generalized in the 3214 ippmSynchronizationTable. 3216 10.3. Changes since release 01 3218 + Document Format: 3219 Make use of the regular MIB object indentation. 3221 + Typos correction: ippmMeasureHystorySize and so on. 3223 + Time unit textual convention: 3224 Enumerations listed in description clauses (e.g. ms, us, ns may 3225 not be universally understood so explicitly named as millisecond, 3226 microsecond, nanosecond) 3228 + Clarify ClearHistory and ClearReport definition: 3229 OnReportDeliveryClearHistory and OnReportDeliveryClearReport 3230 options 3232 + Added scalars ippmOnReportFullAction and ippmOnHistoryFullAction: 3233 To take action when the tables are full. A scalar, which is read- 3234 write and indicates the action to be taken when the log is full. 3235 Options are: wrap, suspend, resume. Same was done for report 3236 group. 3238 + Conformance section: 3239 Added the MODULE-COMPLIANCE macro and the corresponding OBJECT- 3240 GROUPS instances. 3241 Added a compliance instances for proxy mode, proxy inter-domain 3242 mode and probe mode. 3244 + PointOfMeasure: 3245 Put in ippmPointOfMeasureMgmtAddrType-> InetAddressType with 3246 ippmPointOfMeasureMgmtAddress-> InetAddress. 3247 Changed point of measure address to be INET also. 3249 + Took out default point of measure address: 3250 Added OwnersIpAddressType to be in pair with OwnersIpAddress 3252 + Added ippmSynchronizationResolution in the ppmSynchronizationTable: 3253 It indicates the new time resolution (Henk request). 3255 + Added an object ippmReportSetupNotification in the report setup. 3257 + IppmHistoryIndex added in the history table: 3259 To differentiate the result index from the test packet order. 3261 + IppmReportIndex added in the report table: 3262 To differentiate the result index from the test packet order. 3264 + Smilint: with the option -s -l6: 3265 Name length exceeded 32 chars: 3266 Prefix: 3267 + ippmAggregatedMeasure -> ippmAggrMeasure; 3268 + IppmSystemSynchronizationDescription 3269 -> ippmSystemSynchronizationDescr; 3270 + IppmReportSetupEventsDurationThreshold 3271 -> ippmReportSetupDurationThreshold. 3273 + ippmNotifications identified under ippm 3275 + TC OwnerString replaced with IppmOwnerString to fix a warning 3276 of the key length; 3278 + Gain 0 error and warning ! 3280 + ippmAggrMeasureStatus removed: 3281 The status of the row is managed in the ippmMeasureTable 3283 + Notifications: 3284 definition clarified; 3285 ippmReportTimestamp added to notification 3286 ippmEventsDurationExceededAlarm, ippmSingletonAlarm, 3287 ippmCycleOfMeasureReport, ippmCompletedMeasureReport. 3289 + IppmNetworkMeasureEntry : 3290 ippmNetworkMeasurePoissonRate added as the average rates. 3292 + TypeP redefined as a SnmpAdminString instead of a raw OCTET STRING 3293 e.g: '080000080000000011020000'H -> "ip.ipip4". 3294 open issue: 3295 is there a need to indicate the number of parameters of the 3296 protocol identifier ? "ip.ipip4.2" or "ip.ipip4" ? 3298 + TypePaddress Textual convention created: 3299 Dst and Src value is a display string instead of a raw OCTET 3300 STRING. It is the list of parameters of a TypeP. 3301 e.g: 3302 Src address TypeP is "ip.ipip4": 128.2.6.7 in 192.168.1.1. 3303 Src value was '0A04C0A801010480020607'H. 3304 Src is now "192.168.1.1 128.2.6.7". 3306 open issue: 3308 is there any potential parameter with one or more space 3309 inside ? 3311 11. References 3313 [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 3314 9, RFC 2026, October 1996. 3316 [2] Mahdavi J. and V. Paxson, "IPPM Metrics for Measuring 3317 Connectivity", RFC 2678, September 1999. 3319 [3] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay 3320 Metric for IPPM", RFC 2679, September 1999. 3322 [4] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Packet 3323 Loss Metric for IPPM", RFC 2680, September 1999. 3325 [5]Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-trip Delay 3326 Metric for IPPM.", RFC 2681, September 1999. 3328 [6] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 3329 Describing SNMP Management Frameworks", RFC 2571, April 1999. 3331 [7] Rose, M., and K. McCloghrie, "Structure and Identification of 3332 Management Information for TCP/IP-based Internets", STD 16, RFC 3333 1155, May 1990. 3335 [8] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 3336 RFC 1212, March 1991. 3338 [9] M. Rose, "A Convention for Defining Traps for use with the SNMP", 3339 RFC 1215, March 1991. 3341 [10] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 3342 M., and S. Waldbusser, "Structure of Management Information 3343 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3345 [11] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 3346 M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, 3347 RFC 2579, April 1999. 3349 [12] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 3350 M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, 3351 RFC 2580, April 1999. 3353 [13] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 3354 Network Management Protocol", STD 15, RFC 1157, May 1990. 3356 [14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3357 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 3359 [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3360 "Transport Mappings for Version 2 of the Simple Network Management 3361 Protocol (SNMPv2)", RFC 1906, January 1996. 3363 [16]Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 3364 Processing and Dispatching for the Simple Network Management 3365 Protocol (SNMP)", RFC 2572, April 1999. 3367 [17] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 3368 for version 3 of the Simple Network Management Protocol (SNMPv3)", 3369 RFC 2574, April 1999. 3371 [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 3372 Operations for Version 2 of the Simple Network Management Protocol 3373 (SNMPv2)", RFC 1905, January 1996. 3375 [19] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 3376 2573, April 1999. 3378 [20] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-basedAccess 3379 Control Model (VACM) for the Simple Network Management Protocol 3380 (SNMP)", RFC 2575, April 1999. 3382 [21] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction 3383 to Version 3 of the Internet-standard Network Management 3384 Framework", RFC 2570, April 1999. 3386 12. Acknowledgments 3388 A Kerbe. 3390 13. Authors Addresses 3392 Emile STEPHAN 3393 France Telecom R & D 3394 2 avenue Pierre Marzin 3395 F-22307 Lannion cedex 3396 Phone: (+ 33) 2 96 05 11 11 3397 Email: emile.stephan@francetelecom.com 3399 Jessie Jewitt 3400 France Telecom R & D 3401 801 Gateway Blvd. Suit 500 3402 South San Francisco, CA 94080 3403 Tel : 1 650 875-1524 3404 Email : jessie.jewitt@francetelecom.com 3406 Full Copyright Statement 3408 "Copyright (C) The Internet Society (2001). All Rights Reserved. 3410 This document and translations of it may be copied and furnished to 3411 others, and derivative works that comment on or otherwise explain it 3412 or assist its implementation may be prepared, copied, published and 3413 distributed, in whole or in part, without restriction of any kind, 3414 provided that the above copyright notice and this paragraph are 3415 included on all such copies and derivative works. However, this 3416 document itself may not be modified in any way, such as by removing 3417 the copyright notice or references to the Internet Society or other 3418 Internet organizations, except as needed for the purpose of 3419 developing Internet standards in which case the procedures for 3420 copyrights defined in the Internet Standards process must be 3421 followed, or as required to translate it into languages other than 3422 English. 3424 The limited permissions granted above are perpetual and will not be 3425 revoked by the Internet Society or its successors or assigns. 3427 This document and the information contained herein is provided on an 3428 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3429 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3430 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3431 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3432 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.