idnits 2.17.1 draft-boucadair-ipte-acct-pib-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: ---------------------------------------------------------------------------- == There is 1 instance of lines with non-ascii characters in the document. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 9 instances of too long lines in the document, the longest one being 62 characters in excess of 72. ** The abstract seems to contain references ([2]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 20 has weird spacing: '...me. It is i...' == Line 23 has weird spacing: '... The list ...' == Line 31 has weird spacing: '... This docum...' == Line 59 has weird spacing: '...Traffic engin...' == Line 68 has weird spacing: '...ncludes routi...' == (10 more instances...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2003) is 7621 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-04) exists of draft-ietf-rap-feedback-frwk-03 == Outdated reference: A later version (-03) exists of draft-tequila-sls-02 -- Unexpected draft version: The latest known version of draft-jacquenet-ip-te-pib is -02, but you're referring to -03. == Outdated reference: A later version (-06) exists of draft-ietf-rap-feedback-fr-pib-04 -- No information found for draft-jacquenet-qos-nrli - is the name correct? Summary: 5 errors (**), 0 flaws (~~), 12 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Boucadair 3 Internet Draft France Telecom R&D 4 Document: draft-boucadair-ipte-acct-pib-02.txt June 2003 5 Category: Experimental 7 An IP Traffic Engineering PIB for Accounting purposes 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC 2026 [1]. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that other 17 groups may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress". 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt. 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 This document defines a set of IP Traffic Engineering Policy 32 Provisioning Classes (PRCs) for accounting usage within the context 33 of a COPS-based policy enforcement scheme. The purpose of those PRCs 34 is to provide information exploitable by the IP Traffic Engineering 35 decision-making process. Those PRCs are intended for use by the 36 reporting process of the IP TE Client-Type [2]. 38 Table of Contents 40 1. Introduction................................................2 41 2. Conventions used in this document...........................3 42 3. Changes since last version..................................3 43 4. Accounting and Traffic Engineering..........................3 44 4.1. Introduction................................................3 45 4.2. The IP TE Selection Tables..................................4 46 4.3. The IP TE Accounting Usage Tables...........................4 47 4.4. PIB overview................................................5 48 4.5. The relation of the Accounting PIB with external PIB 49 modules...................................................5 51 5. IP TE Usage PIB.............................................5 52 6. Security Considerations....................................17 53 7. References.................................................17 54 8. Acknowledgments............................................18 55 9. Author's Addresses.........................................18 57 1. Introduction 59 Traffic engineering is one of the possible means for solving 60 congestion problems and permitting efficient use of the network 61 resources. Indeed, several tools have been proposed to achieve this 62 goal. Nevertheless, only few solutions introduce a high level of 63 automation for the allocation of resources and the configuration 64 operations. 66 The design of an IP Traffic Engineering (IP TE) policy implies the 67 manipulation of a large amount of configuration information that 68 includes routing considerations, traffic forecast, available 69 resources, etc. These parameters are provisioned as configuration 70 information to the network devices by means of a COPS-based 71 communication scheme, thanks to the use of a specific client-type 72 [2]. But remains the choice of the appropriate parameters to meet 73 network constraints as well as Quality Of Service (QOS) requirements, 74 and also to observe the impact of such choice on the stability of the 75 network. 77 From this standpoint, several methods can be adopted: either use 78 statistical data based on mathematical models, or data resulting of 79 measurements. The advantage of the second method is that it allows 80 for real time statistics. 82 Therefore, the actual enforcement of a traffic engineering policy 83 requires a feedback mechanism not only to qualify how efficient such 84 enforcement is, but also the impact the future decisions made by the 85 Policy Decision Point (PDP) and installed by the PDP at the Policy 86 Enforcement Point (PEP)-embedded devices. 88 Within the context of this document, the data recorded, monitored 89 and/or reported by the PEP are the results of the activation of 90 dynamic routing processes (e.g. Open Shortest Path First (OSPF) and 91 Border Gateway Protocol version 4 (BGP)). 93 We propose in this document to define a set of IP TE accounting usage 94 Policy Rule Classes (PRC) that will be monitored, recorded and/or 95 reported by the PEP. Those PRCs complement the PRC classes that have 96 been defined in the Framework of COPS-PR PIB for Policy Usage [3]. 98 This document is organised as follows: 100 - Section 4 shows the use of accounting mode within a TE context. 102 - Section 5 presents the IP TE Usage PIB. 104 2. Conventions used in this document 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in RFC-2119 [4]. 110 3. Changes since last version 112 - The introduction has been reworded 113 - The references section has been updated 114 - Modification of section 4 116 4. Accounting and Traffic Engineering 117 4.1. Introduction 119 The actual enforcement of an IP TE policy is conditioned by the 120 manipulation of information such as traffic forecast (according to 121 customers' requests, for example [5]), and traffic load calculation 122 (see fig.1). Within the context of a COPS architecture, the 123 qualification of a policy's efficiency could be based upon the 124 accounting mode. 126 [6] defines the capability to report information to the PDP. Several 127 types of reports are defined: success, failure and accounting. A 128 framework of the use of the accounting mode is introduced in [3]. 130 +-----------------+ 131 | Other | 132 | external system | 133 +-----------------+ 134 ^ 135 | +-----------------+ 136 | | TE | 137 | | Forecast Block | 138 | +-----------------+ 139 | ^ +------------------+ 140 | | | PDP | 141 | | | Decision-making | 142 | | +--------/\--------+ 143 | | +--------\/--------+ 144 | | | | 145 | | | PDP | 146 | | | | 147 | | +---------------- --+ 148 +--------------------------+ | | ^ 149 | PEP | | | | 150 | +-------------------+ | | | | 151 | | IP TE Client-Type | | | | | 152 | | +--------------+ | |<------+ | | 153 | | |Report Process| | |<-------------------------+ | 154 | | |-Monitoring | | |<---------------------------------- + 155 | | |-Recording | | | IP TE REPORT 156 | | |-Reporting | | | 157 | | +--------------+ | | 158 | +-------------------+ | 159 +--------------------------+ 160 Fig.1: IP TE Reporting Mechanism 162 According to Fig.1, the report sent by the IP TE client type is 163 received by the PDP. 165 The IP TE report classes are instantiated as multiple Provisioning 166 Instance (PRI) instances, each of which being identified by 167 PRovisioning Instance iDentifier (PRID). These classes contain 168 attributes that actually describe the accounting IP TE-related 169 information collected in the network. 171 4.2. The IP TE Selection Tables 173 The documents [7], [8] and [9] define IP Traffic Engineering Policy 174 Information Base (IP TE PIB). The IP TE PIB could be organized into 175 the following provisioning classes: 177 1. The Forwarding classes: the information contained in these classes 178 is meant to provide a detailed description of the traffic- 179 engineered routes. Only one table is defined: the IP TE Route 180 table, which describes the information related to TE routes that 181 have been installed by the routers in their FIBs. 183 2. The Metrics classes: the information stored in the tables included 184 in this class is meant to provide the description of the metric 185 values that will be taken into account by intra- and inter-domain 186 routing protocols for the computation and the selection of 187 traffic-engineered routes. 189 3. The Statistics classes: the information contained in these classes 190 is meant to provide statistics on the enforcement of the TE 191 policies. 193 These tables are used as selection tables. 195 4.3. The IP TE Accounting Usage Tables 197 Within the context of [10], three policies are defined: 198 - The selection criteria policy: defines the conditions used by PEP 199 to monitor and record a usage policy. 200 - The usage policy: defines what attributes are monitored and/or 201 recorded by the PEP. 203 - The linkage policy: provides a linkage for the selection and usage 204 policies. 206 As mentioned above, the tables defined in the IP TE PIB are used as 207 the Selection policies and we introduced in the following Section 4 208 the Usage classes. 210 In addition, the IP TE Selection Usage Combination Capability Table 211 contains objects pointing to the IP TE Usage tables, IP TE Selection 212 tables and Threshold tables. 214 4.4. PIB overview 216 The PIB defined within the context of IP traffic engineering for 217 accounting purposes has the goal to complete the whole COPS TE 218 reporting machinery. This PIB contains the following tables: 220 - ospfTeRouterUsageTable: this class defines the usage attributes to 221 be reported, and which are related to the router 222 identified by the Router-Id. 223 - ospfTeUsageTable : this class defines the usage attributes to use 224 for OSPF TE purposes. 225 - isisTeUsageTable : this class defines the usage attributes to use 226 for IS-IS TE purposes. 227 - bgpTeTable : this table contains a set of accounting 228 information related to the activation of BGP 229 process enabling exchange of QOS information. 230 - ospfTeThresholdTable: this class defines the threshold attributes 231 corresponding to OSPF TE usage attributes 232 specified in ospfTeUsageTable. 233 - isisTeThresholdTable: this class defines the threshold attributes 234 corresponding to IS-IS TE usage attributes 235 specified in isisTeUsageTable. 236 - bgpTeThresholdTable: this class defines the threshold attributes 237 corresponding to BGP usage attributes specified 238 in bgpTeUsageTable. 240 4.5. The relation of the Accounting PIB with external PIB modules 242 In the actual stage of the IPTE PIB design effort, several PIB 243 modules have been proposed to the IETF, mainly [8],[9] and [12]. 245 The accounting PIB could impact these modules by providing additional 246 input to the process of configuration of the aforementioned modules. 248 5. IP TE Usage PIB 250 -- 251 -- The PIB defined within the context of IP traffic engineering 252 -- for accounting purposes has the goal to complete the whole 253 -- COPS TE reporting machinery. 255 -- Data contained in this PIB aren�t stabilized yet and will be 256 -- modified and updated as necessary. 257 -- 259 IPTE-ACCOUNTING-PIB PIB-DEFINITIONS ::= BEGIN 261 IMPORTS 262 ExtUTCTime, Unsigned32, Unsigned64, 263 Integer32, MODULE-IDENTITY, OBJECT-TYPE 264 FROM COPS-PR-SPPI 265 TruthValue, TEXTUAL-CONVENTION 266 FROM SNMPv2-TC 267 PolicyInstanceId, PolicyReferenceId 268 FROM COPS-PR-SPPI-TC; 269 RoleCombination 270 FROM POLICY-DEVICE-AUX-MIB; 271 Counter64 272 FROM SNMPv2-SMI; 274 ipTeAccountingPib MODULE-IDENTITY 276 SUBJECT-CATEGORIES {tbd} 277 LAST-UPDATED "200201250900Z" 278 ORGANIZATION "France Telecom R&D" 279 CONTACT-INFO " 280 Mohamed Boucadair 281 Adresse: 42, rue des Coutures 282 BP 6243 283 14066 Caen Cedex 284 Phone: +33 2 31 75 92 31 285 Email: Mohamed.Boucadair@francetelecom.com" 287 DESCRIPTION 288 "The PIB module that contains classes describing the 289 parameters to be monitored, recorded and/or reported 290 by the PEP for Traffic Engineering accounting 291 purposes." 293 ::= {tbd} 295 -- 296 -- The ipTe Accounting Class 297 -- 299 ipTeAccountingClasses 300 OBJECT IDENTIFIER ::= { ipTeAccountingPib 1 } 302 -- 303 -- The MPLS TE Accounting Class 304 -- 305 -- This class defines tables related to MPLS TE 306 -- To be done in next version of this draft. 308 lspTeAccountingClasses 309 OBJECT IDENTIFIER ::= { ipTeAccountingPib 2 } 311 -- 312 -- ospfTeRouterUsageTable 313 -- 315 ospfTeRouterUsageTable OBJECT-TYPE 317 SYNTAX SEQUENCE OF ospfTeRouterUsageEntry 318 PIB-ACCESS report-only 319 STATUS current 320 DESCRIPTION 321 "This class defines the usage attributes to be 322 reported, and which are related to the router 323 identified by the Router-Id." 325 ::= { ipTeAccountingClasses 1} 327 ospfTeRouterUsageEntry OBJECT-TYPE 329 SYNTAX ospfTeUsageRouterEntry 330 STATUS current 331 DESCRIPTION 332 "An entry for the ospfTeRouterUsageTable." 334 PIB-INDEX { ospfTeRouterUsagePrid} 335 UNIQUENESS { ospfTeRouterUsageLinkPrid, 336 ospfTeUsageIfActif} 338 ::= {ospfTeRouterUsageTable 1} 340 ospfTeRouterUsageEntry ::= SEQUENCE { 341 ospfTeRouterUsagePrid InstanceID, 342 ospfTeRouterUsageLinkPrid Prid, 343 ospfTeRouterUsageIfActif Counter64 } 345 ospfTeRouterUsagePrid OBJECT-TYPE 347 SYNTAX Prid 348 STATUS current 349 DESCRIPTION 350 "An integer index that uniquely identifies this 351 instance of the ospfTeRouterUsage class." 353 ::= { ospfTeRouterUsageEntry 1 } 355 ospfTeRouterUsageLinkPrid OBJECT-TYPE 356 SYNTAX Prid 357 STATUS current 358 DESCRIPTION 359 "The PRID of the Linkage policy instance used to refer 360 this usage policy instance." 362 ::= { ospfTeRouterUsageEntry 2 } 364 ospfTeRouterUsageIfActif OBJECT-TYPE 366 SYNTAX Counter64 367 STATUS current 368 DESCRIPTION 369 "The number of interfaces that participate to an OSPF- 370 TE route computation in the router identified by 371 Router-ID." 373 ::= { ospfTeRouterUsageEntry 3 } 375 -- 376 -- ospfTeUsageTable 377 -- 379 ospfTeUsageTable OBJECT-TYPE 381 SYNTAX SEQUENCE OF ospfTeUsageEntry 382 PIB-ACCESS report-only 383 STATUS current 384 DESCRIPTION 385 "This class defines the usage attributes to use for 386 OSPF TE purposes." 388 ::= { ipTeAccountingClasses 2 } 390 ospfTeUsageEntry OBJECT-TYPE 392 SYNTAX ospfTeUsageEntry 393 STATUS current 394 DESCRIPTION 395 "An entry for the ospfTeUsageTable." 397 PIB-INDEX { ospfTeUsagePrid} 398 UNIQUENESS { ospfTeUsageLinkPrid, 399 OspfTeUsageLinkDelay } 401 ::= {ospfTeUsageTable 1 } 403 ospfTeUsageEntry ::= SEQUENCE { ospfTeUsagePrid InstanceID, 404 ospfTeUsageLinkPrid Prid, 406 ospfTeUsageLinkDelay Unsigned32 } 408 ospfTeUsagePrid OBJECT-TYPE 410 SYNTAX Prid 411 STATUS current 412 DESCRIPTION 413 "An integer index that uniquely identifies this 414 instance of the ospfTeUsage class." 416 ::= { ospfTeUsageEntry 1 } 418 ospfTeUsageLinkPrid OBJECT-TYPE 420 SYNTAX Prid 421 STATUS current 422 DESCRIPTION 423 "The PRID of the Linkage policy instance used to refer 424 this usage policy instance." 426 ::= { ospfTeUsageEntry 2 } 428 ospfTeUsageLinkDelay OBJECT-TYPE 430 SYNTAX Unsigned32 431 STATUS current 432 DESCRIPTION 433 "The one-way delay that has been observed on this 434 route." 436 ::= { ospfTeUsageEntry 3 } 438 -- 439 -- isisTeUsageTable 440 -- 442 isisTeUsageTable OBJECT-TYPE 444 SYNTAX SEQUENCE OF isisTeUsageEntry 445 PIB-ACCESS report-only 446 STATUS current 447 DESCRIPTION 448 "This class defines the usage attributes to use for 449 IS-IS TE purposes." 451 ::= { ipTeAccountingClasses 3 } 453 isisTeUsageEntry OBJECT-TYPE 455 SYNTAX isisTeUsageEntry 456 STATUS current 457 DESCRIPTION 458 "An entry for the isisTeUsageTable." 460 PIB-INDEX { isisTeUsagePrid} 461 UNIQUENESS { isisTeUsageLinkPrid, 462 isisTeUsageLinkDelay } 464 ::= {isisTeUsageTable 1 } 466 isisTeUsageEntry ::= SEQUENCE { 467 isisTeUsagePrid InstanceID, 468 isisTeUsageLinkPrid Prid, 469 isisTeUsageLinkDelay Unsigned32 } 471 isisTeUsagePrid OBJECT-TYPE 473 SYNTAX Prid 474 STATUS current 475 DESCRIPTION 476 "An integer index that uniquely identifies this 477 instance of the isisTeUsage class." 479 ::= { isisTeUsageEntry 1 } 481 isisTeUsageLinkPrid OBJECT-TYPE 483 SYNTAX Prid 484 STATUS current 485 DESCRIPTION 486 "The PRID of the Linkage policy instance used to refer 487 this usage policy instance." 489 ::= { isisTeUsageEntry 2 } 491 isisTeUsageLinkDelay OBJECT-TYPE 493 SYNTAX Unsigned32 494 STATUS current 495 DESCRIPTION 496 "The one-way delay that has been observed on this 497 route." 499 ::= { isisTeUsageEntry 3 } 501 -- 502 -- bgpTeUsageTable 503 -- 505 bgpTeTable OBJECT-TYPE 506 SYNTAX SEQUENCE OF bgpTeUsageEntry 507 PIB-ACCESS report-only 508 STATUS current 509 DESCRIPTION 510 "This table contains a set of accounting information 511 related to the activation of BGP process enabling 512 exchange of QOS information." 514 ::= { ipTeAccountingClasses 4 } 516 bgpTeUsageEntry OBJECT-TYPE 518 SYNTAX bgpTeUsageEntry 519 STATUS current 520 DESCRIPTION 521 "An entry to bgpTeUsage Class." 523 PIB-INDEX { bgpTeUsagePrid } 524 UNIQUENESS { bgpTeUsageLinkPrid, 525 bgpTeUsageActIf, 526 bgpTeUsageOneWayDelay } 528 ::= { bgpTeUsageTable 1 } 530 bgpTeUsageEntry ::= SEQUENCE { 531 bgpTeUsagePrid InstanceId, 532 bgpTeUsageLinkPrid Prid, 533 bgpTeUsageActIf Counter64, 534 bgpTeUsageOneWayDelay Unsigned32 } 536 bgpTeUsagePrid OBJECT-TYPE 538 SYNTAX InstanceId 539 STATUS current 540 DESCRIPTION 541 "An integer index that uniquely identifies this 542 instance of the bgpTeUsage class." 544 ::= { bgpTeUsageEntry 1 } 546 bgpTeUsageLinkPrid OBJECT-TYPE 548 SYNTAX Prid 549 STATUS current 550 DESCRIPTION 551 "The PRID of the Linkage policy instance used to base 552 this usage policy instance upon." 554 ::= { bgpTeUsageEntry 2 } 556 bgpTeUsageActIf OBJECT-TYPE 558 SYNTAX Counter64 559 STATUS current 560 DESCRIPTION 561 "Specifies the number of interfaces that participate 562 to the BGP route computation process." 564 ::= { bgpTeUsageEntry 3 } 566 bgpTeUsageOneWayDelay OBJECT-TYPE 568 SYNTAX Unsigned32 569 STATUS current 570 DESCRIPTION 571 "Specifies the one-way delay that has been observed on 572 this route." 574 ::= { bgpTeUsageEntry 4 } 576 -- 577 -- The Threshold class that accompanies the OSPF and BGP usage 578 -- tables 579 -- 580 -- 581 -- OSPF Threshold attributes 582 -- 584 ospfTeThresholdTable OBJECT-TYPE 586 SYNTAX SEQUENCE OF ospfThresholdEntry 587 PIB-ACCESS Install 588 STATUS current 589 DESCRIPTION 590 "This class defines the threshold attributes 591 corresponding to OSPF TE usage attributes specified in 592 ospfTeUsageTable." 594 ::= { ipTeAccountingClasses 5 } 596 ospfTeThresholdEntry OBJECT-TYPE 598 SYNTAX ospfTeThresholdEntry 599 STATUS current 600 DESCRIPTION 601 "Defines the attributes to hold threshold values." 603 PIB-INDEX { ospfTeThresholdId } 605 ::= { ospfTeThresholdId 1 } 607 ospfTeThresholdEntry::= SEQUENCE { 608 ospfTeThresholdId InstanceID, 609 ospfTeThresholdBwThresholds Integer64, 610 ospfTeThresholdRsvBwThresholds Integer64 } 612 ospfTeThresholdId OBJECT-TYPE 614 SYNTAX InstanceId 615 STATUS current 616 DESCRIPTION 617 "Arbitrary integer index that uniquely identifies an 618 instance of the class." 620 ::= { ospfTeThresholdEntry 1 } 622 ospfTeThresholdBwThresholds OBJECT-TYPE 624 SYNTAX Integer64 625 STATUS current 626 DESCRIPTION 627 "The threshold the used bandwidth on the link 628 shouldn't exceed." 630 ::= { ospfTeThresholdEntry 2 } 632 ospfTeThresholdRsvBwThresholds OBJECT-TYPE 634 SYNTAX Integer64 635 STATUS current 636 DESCRIPTION 637 "The threshold the reserved bandwidth on the link 638 shouldn't exceed." 640 ::= { ospfTeThresholdEntry 3 } 642 -- 643 -- ISIS Threshold attributes 644 -- 646 isisTeThresholdTable OBJECT-TYPE 648 SYNTAX SEQUENCE OF isisThresholdEntry 649 PIB-ACCESS Install 650 STATUS current 651 DESCRIPTION 652 "This class defines the threshold attributes 653 corresponding to ISIS TE usage attributes specified in 654 isisTeUsageTable." 656 ::= { ipTeAccountingClasses 6 } 658 isisTeThresholdEntry OBJECT-TYPE 660 SYNTAX isisTeThresholdEntry 661 STATUS current 662 DESCRIPTION 663 "Defines the attributes to hold threshold values." 665 PIB-INDEX { isisTeThresholdId } 667 ::= { isisTeThresholdId 1 } 669 isisTeThresholdEntry::= SEQUENCE { 670 isisTeThresholdId InstanceID, 671 isisTeThresholdBwThresholds Integer64, 672 isisTeThresholdRsvBwThresholds Integer64 } 674 isisTeThresholdId OBJECT-TYPE 676 SYNTAX InstanceId 677 STATUS current 678 DESCRIPTION 679 "Arbitrary integer index that uniquely identifies an 680 instance of the class." 682 ::= { isisTeThresholdEntry 1 } 684 isisTeThresholdBwThresholds OBJECT-TYPE 685 SYNTAX Integer64 686 STATUS current 687 DESCRIPTION 688 "The threshold the used bandwidth on the link 689 shouldn't exceed." 691 ::= { isisTeThresholdEntry 2 } 693 isisTeThresholdRsvBwThresholds OBJECT-TYPE 695 SYNTAX Integer64 696 STATUS current 697 DESCRIPTION 698 "The threshold the reserved bandwidth on the link 699 shouldn't exceed." 701 ::= { isisTeThresholdEntry 3 } 703 -- 704 -- BGP Threshold attributes 705 -- 707 bgpTeThresholdTable OBJECT-TYPE 709 SYNTAX SEQUENCE OF bgpThresholdEntry 710 PIB-ACCESS Install 711 STATUS current 712 DESCRIPTION 713 "This class defines the threshold attributes 714 corresponding to BGP usage attributes specified in 715 bgpTeUsageTable." 717 ::= { ipTeAccountingClasses 7 } 719 bgpTeThresholdEntry OBJECT-TYPE 721 SYNTAX bgpTeThresholdEntry 722 STATUS current 723 DESCRIPTION 724 "Defines the attributes to hold threshold values." 726 PIB-INDEX { bgpTeThresholdPrid } 728 ::= { bgpTeThresholdId 1 } 730 bgpTeThresholdEntry ::= SEQUENCE { 731 bgpTeThresholdId InstanceID, 732 bgpTeThresholdNlriAddress InetAddress, 733 bgpTeThresholdNextHopAddress InetAddress, 734 bgpTeThresholdOneWayDelayThreshold Integer64, 735 bgpTeThresholdInterPacketDelayThreshold Integer64, 736 bgpTeThresholdLossRateThreshold Integer64 } 738 bgpTeThresholdId OBJECT-TYPE 740 SYNTAX InstanceId 741 STATUS current 742 DESCRIPTION 743 "Arbitrary integer index that uniquely identifies an 744 instance of the class." 746 ::= { bgpTeThresholdEntry 1 } 748 bgpTeThresholdNlriAddress OBJECT-TYPE 750 SYNTAX InetAddress 751 STATUS current 752 DESCRIPTION 753 "The IP address to match against the NLRI field of 754 QOS_NLRI attribute of the BGP4 UPDATE message 755 introduced in [11]." 757 ::= { bgpTeThresholdEntry 2 } 759 bgpTeThresholdNextHopAddress OBJECT-TYPE 761 SYNTAX InetAddress 762 STATUS current 763 DESCRIPTION 764 "The address of the next router." 766 ::= { bgpTeThresholdEntry 3 } 768 bgpTeThresholdOneWayDelayThreshold OBJECT-TYPE 770 SYNTAX Integer64 771 STATUS current 772 DESCRIPTION 773 "The threshold of the one-way delay, that will trigger 774 a report in the next reporting interval when 775 exceeded." 777 ::= { bgpTeThresholdEntry 4 } 779 bgpTeThresholdInterPacketDelayThreshold OBJECT-TYPE 781 SYNTAX Integer64 782 STATUS current 783 DESCRIPTION 784 "The threshold of the inter-packet delay variation, 785 that will trigger a report in the next reporting 786 interval, when exceeded." 788 ::= { bgpTeThresholdEntry 5 } 790 bgpTeThresholdLossRateThreshold OBJECT-TYPE 792 SYNTAX Integer64 793 STATUS current 794 DESCRIPTION 795 "The threshold, in terms of loss rate, that will 796 trigger a report in the next reporting interval, when 797 exceeded." 799 ::= { bgpTeThresholdEntry 6 } 801 END 803 6. Security Considerations 805 Data manipulated within the context of IP TE accounting could be used 806 by the IP TE decision-making processes, but only authorized COPS-PR 807 communications can take place. Therefore, this draft does not 808 introduce any additional security issues other than those that have 809 been identified in the COPS-PR specification [12]. 811 Nevertheless, the activation of an integrity mechanism is recommended 812 for external systems making use of the TE accounting data. 814 7. References 816 [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 817 9, RFC 2026, October 1996. 818 [2] Jacquenet, C., "An IP Traffic Engineering COPS Client-type", 819 draft jacquenet-ip-te-cops-04.txt, Work in Progress, December 820 2002. 822 [3] Rawlins, D., Kulkarni, A., Bokaemper, M., Ho Chan, K., "Framework 823 of COPS-PR Policy Usage Feedback", draft-ietf-rap-feedback-frwk- 824 03.txt, October 2002. 825 [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement 826 Levels", BCP 14, RFC 2119, March 1997 827 [5] Goderis, D., T'Joens, Y., Jacquenet, C., Memenios, G., Pavlou, 828 G., Egan, R., Griffin, D., Georgatsos, P., Georgiadis, 829 L.,"Specification of a Service Level Specification (SLS) 830 Template", draft-tequila-sls-02.txt, Work in Progress, February 831 2002. 832 [6] Boyle, J., Cohen, R., Durham, D., Herzog, S., Raja, R., Sastry, 833 A., "The COPS (Common Open Policy Service) Protocol", RFC 2748, 834 January 2000. 835 [7] Boucadair, M., Jacquenet, C., "An IP Traffic Engineering Policy 836 Information Base", draft-jacquenet-ip-te-pib-03.txt, Work in 837 Progress, December 2002. 838 [8] Boucadair, M., Jacquenet, C., "IGP Policy Information Base for TE 839 purposes", Work in Progress. 840 [9] Boucadair, M., Jacquenet, C., "BGP Policy Information Base for 841 QoS purposes", Work in Progress. 842 [10] Rawlins, D., Kulkarni, A., Bokaemper, M., Ho Chan, K. " 843 Framework Policy Information Base for Usage Feedback ", draft- 844 ietf-rap-feedback-fr-pib-04.txt, November 2002. 845 [11] Jacquenet, C., "Providing Quality of Service Indication by the 846 BGP-4 Protocol: the QOS_NLRI Attribute", draft-jacquenet-qos-nrli- 847 04.txt, Work in Progress, March 2002. 848 [12] Ho Chan, K., Durham, D., Gai, S., Herzog, S., McLoghrie, K., 849 Reichmeyer, F., Seligson, J., Smith, A., Yavatkar, R., "COPS Usage 850 for Policy Provisioning (COPS-PR)", RFC 3084, March 2001. 851 [12] Boucadair, M., Jacquenet, C., "An IP Forwarding PIB", Work in 852 Progress. 854 8. Acknowledgments 856 The author would like to thank M. Jacquenet for his remarks and 857 suggestions. 859 9. Author's Addresses 861 Mohamed Boucadair 862 France Telecom R & D 863 DMI/SIR 864 42, rue des Coutures 865 BP 6243 866 14066 Caen Cedex 4 867 France 868 Phone: +33 2 31 75 92 31 869 Email: mohamed.boucadair@rd.francetelecom.com 871 Full Copyright Statement 873 "Copyright (C) The Internet Society (2003). All Rights Reserved. 875 This document and translations of it may be copied and furnished to 876 others, and derivative works that comment on or otherwise explain it 877 or assist its implementation may be prepared, copied, published and 878 distributed, in whole or in part, without restriction of any kind, 879 provided that the above copyright notice and this paragraph are 880 included on all such copies and derivative works. However, this 881 document itself may not be modified in any way, such as by removing 882 the copyright notice or references to the Internet Society or other 883 Internet organizations, except as needed for the purpose of 884 developing Internet standards in which case the procedures for 885 copyrights defined in the Internet Standards process must be 886 followed, or as required to translate it into languages other than 887 English. 889 The limited permissions granted above are perpetual and will not be 890 revoked by the Internet Society or its successors or assigns. 892 This document and the information contained herein is provided on an 893 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 894 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 895 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 896 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 897 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.