idnits 2.17.1 draft-boucadair-ipte-acct-pib-01.txt: -(240): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page == 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 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: ' 6. 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.) ** The document seems to lack an Authors' Addresses Section. ** There are 305 instances of too long lines in the document, the longest one being 107 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [1]), 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 56 has weird spacing: '...Traffic engin...' == Line 65 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 (December 2002) is 7801 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- -- Missing reference section? '1' on line 800 looks like a reference -- Missing reference section? '2' on line 802 looks like a reference -- Missing reference section? '3' on line 805 looks like a reference -- Missing reference section? '4' on line 808 looks like a reference -- Missing reference section? '5' on line 810 looks like a reference -- Missing reference section? '6' on line 815 looks like a reference -- Missing reference section? '7' on line 819 looks like a reference -- Missing reference section? '8' on line 822 looks like a reference -- Missing reference section? '9' on line 824 looks like a reference -- Missing reference section? '10' on line 826 looks like a reference -- Missing reference section? '11' on line 829 looks like a reference -- Missing reference section? '12' on line 832 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 9 warnings (==), 14 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-01.txt December 2002 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............................45 47 4.4. PIB overview..................................................5 48 5. IP TE Usage PIB.................................................5 49 6. Security Considerations........................................17 50 7. References.....................................................17 51 8. Acknowledgments................................................18 52 9. Author's Addresses.............................................18 54 1. Introduction 56 Traffic engineering is one of the possible means for solving 57 congestion problems and permitting efficient use of the network 58 resources. Indeed, several tools have been proposed to achieve this 59 goal. Nevertheless, only few solutions introduce a high level of 60 automation for the allocation of resources and the configuration 61 operations. 63 The design of an IP Traffic Engineering (IP TE) policy implies the 64 manipulation of a large amount of configuration information that 65 includes routing considerations, traffic forecast, available 66 resources, etc. These parameters are provisioned as configuration 67 information to the network devices by means of a COPS-based 68 communication scheme, thanks to the use of a specific client-type 69 [2]. But remains the choice of the appropriate parameters to meet 70 network constraints as well as Quality Of Service (QOS) requirements, 71 and also to observe the impact of such choice on the stability of the 72 network. 74 From this standpoint, several methods can be adopted: either use 75 statistical data based on mathematical models, or data resulting of 76 measurements. The advantage of the second method is that it allows 77 for real time statistics. 79 Therefore, the actual enforcement of a traffic engineering policy 80 requires a feedback mechanism not only to qualify how efficient such 81 enforcement is, but also the impact the future decisions made by the 82 Policy Decision Point (PDP) and installed by the PDP at the Policy 83 Enforcement Point (PEP)-embedded devices. 85 Within the context of this document, the data recorded, monitored 86 and/or reported by the PEP are the results of the activation of 87 dynamic routing processes (e.g. Open Shortest Path First (OSPF) and 88 Border Gateway Protocol version 4 (BGP)). 90 We propose in this document to define a set of IP TE accounting usage 91 Policy Rule Classes (PRC) that will be monitored, recorded and/or 92 reported by the PEP. Those PRCs complement the PRC classes that have 93 been defined in the Framework of COPS-PR PIB for Policy Usage [3]. 95 This document is organised as follows: 97 - Section 4 shows the use of accounting mode within a TE context. 98 - Section 5 presents the IP TE Usage PIB. 100 2. Conventions used in this document 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC-2119 [4]. 106 3. Changes since last version 108 - The introduction has been reworded 109 - Updating the PIB by introducing IS-IS related information 110 - The references section has been updated 112 4. Accounting and Traffic Engineering 113 4.1. Introduction 115 The actual enforcement of an IP TE policy is conditioned by the 116 manipulation of information such as traffic forecast (according to 117 customers' requests, for example [5]), and traffic load calculation 118 (see fig.1). Within the context of a COPS architecture, the 119 qualification of a policy's efficiency could be based upon the 120 accounting mode. 122 [6] defines the capability to report information to the PDP. Several 123 types of reports are defined: success, failure and accounting. A 124 framework of the use of the accounting mode is introduced in [3]. 126 +-----------------+ 127 | Other | 128 | external system | 129 +-----------------+ 130 ^ 131 | +-----------------+ 132 | | TE | 133 | | Forecast Block | 134 | +-----------------+ 135 | ^ +------------------+ 136 | | | PDP | 137 | | | Decision-making | 138 | | +--------/\--------+ 139 | | +--------\/--------+ 140 | | | | 141 | | | PDP | 142 | | | | 143 | | +---------------- --+ 144 +--------------------------+ | | ^ 145 | PEP | | | | 146 | +-------------------+ | | | | 147 | | IP TE Client-Type | | | | | 148 | | +--------------+ | |<------+ | | 149 | | |Report Process| | |<-------------------------+ | 150 | | |-Monitoring | | |<---------------------------------- + 151 | | |-Recording | | | IP TE REPORT 152 | | |-Reporting | | | 153 | | +--------------+ | | 154 | +-------------------+ | 155 +--------------------------+ 156 Fig.1: IP TE Reporting Mechanism 158 According to Fig.1, the report sent by the IP TE client type is 159 received by the PDP. 161 The IP TE report classes are instantiated as multiple Provisioning 162 Instance (PRI) instances, each of which being identified by 163 PRovisioning Instance iDentifier (PRID). These classes contain 164 attributes that actually describe the accounting IP TE-related 165 information collected in the network. 167 4.2. The IP TE Selection Tables 169 The documents [7], [8] and [9] define IP Traffic Engineering Policy 170 Information Base (IP TE PIB). The IP TE PIB could be organized into 171 the following provisioning classes: 173 1. The Forwarding classes: the information contained in these classes 174 is meant to provide a detailed description of the traffic- 175 engineered routes. Only one table is defined: the IP TE Route 176 table, which describes the information related to TE routes that 177 have been installed by the routers in their FIBs. 179 2. The Metrics classes: the information stored in the tables included 180 in this class is meant to provide the description of the metric 181 values that will be taken into account by intra- and inter-domain 182 routing protocols for the computation and the selection of 183 traffic-engineered routes. 185 3. The Statistics classes: the information contained in these classes 186 is meant to provide statistics on the enforcement of the TE 187 policies. 189 These tables are used as selection tables. 191 4.3. The IP TE Accounting Usage Tables 193 Within the context of [10], three policies are defined: 194 - The selection criteria policy: defines the conditions used by PEP 195 to monitor and record a usage policy. 196 - The usage policy: defines what attributes are monitored and/or 197 recorded by the PEP. 198 - The linkage policy: provides a linkage for the selection and usage 199 policies. 201 As mentioned above, the tables defined in the IP TE PIB are used as 202 the Selection policies and we introduced in the following Section 4 203 the Usage classes. 205 In addition, the IP TE Selection Usage Combination Capability Table 206 contains objects pointing to the IP TE Usage tables, IP TE Selection 207 tables and Threshold tables. 209 4.4. PIB overview 211 The PIB defined within the context of IP traffic engineering for 212 accounting purposes has the goal to complete the whole COPS TE 213 reporting machinery. This PIB contains the following tables: 215 - ospfTeRouterUsageTable: this class defines the usage attributes to 216 be reported, and which are related to the router 217 identified by the Router-Id. 218 - ospfTeUsageTable : this class defines the usage attributes to use 219 for OSPF TE purposes. 220 - isisTeUsageTable : this class defines the usage attributes to use 221 for IS-IS TE purposes. 222 - bgpTeTable : this table contains a set of accounting 223 information related to the activation of BGP 224 process enabling exchange of QOS information. 225 - ospfTeThresholdTable: this class defines the threshold attributes 226 corresponding to OSPF TE usage attributes 227 specified in ospfTeUsageTable. 228 - isisTeThresholdTable: this class defines the threshold attributes 229 corresponding to IS-IS TE usage attributes 230 specified in isisTeUsageTable. 231 - bgpTeThresholdTable: this class defines the threshold attributes 232 corresponding to BGP usage attributes specified 233 in bgpTeUsageTable. 234 5. IP TE Usage PIB 236 -- 237 -- The PIB defined within the context of IP traffic engineering 238 -- for accounting purposes has the goal to complete the whole 239 -- COPS TE reporting machinery. 240 -- Data contained in this PIB aren�t stabilized yet and will be 241 -- modified and updated as necessary. 242 -- 244 IPTE-ACCOUNTING-PIB PIB-DEFINITIONS ::= BEGIN 246 IMPORTS 247 ExtUTCTime, Unsigned32, Unsigned64, 248 Integer32, MODULE-IDENTITY, OBJECT-TYPE 249 FROM COPS-PR-SPPI 250 TruthValue, TEXTUAL-CONVENTION 251 FROM SNMPv2-TC 252 PolicyInstanceId, PolicyReferenceId 253 FROM COPS-PR-SPPI-TC; 254 RoleCombination 255 FROM POLICY-DEVICE-AUX-MIB; 256 Counter64 257 FROM SNMPv2-SMI; 259 ipTeAccountingPib MODULE-IDENTITY 261 SUBJECT-CATEGORIES {tbd} 262 LAST-UPDATED "200201250900Z" 263 ORGANIZATION "France Telecom R&D" 264 CONTACT-INFO " 265 Mohamed Boucadair 266 Adresse: 42, rue des Coutures 267 BP 6243 268 14066 Caen Cedex 269 Phone: +33 2 31 75 92 31 270 Email: Mohamed.Boucadair@francetelecom.com" 272 DESCRIPTION 273 "The PIB module that contains classes describing the 274 parameters to be monitored, recorded and/or reported 275 by the PEP for Traffic Engineering accounting 276 purposes." 278 ::= {tbd} 280 -- 281 -- The ipTe Accounting Class 282 -- 284 ipTeAccountingClasses 285 OBJECT IDENTIFIER ::= { ipTeAccountingPib 1 } 287 -- 288 -- The MPLS TE Accounting Class 289 -- 290 -- This class defines tables related to MPLS TE 291 -- To be done in next version of this draft. 293 lspTeAccountingClasses 294 OBJECT IDENTIFIER ::= { ipTeAccountingPib 2 } 296 -- 297 -- ospfTeRouterUsageTable 298 -- 300 ospfTeRouterUsageTable OBJECT-TYPE 301 SYNTAX SEQUENCE OF ospfTeRouterUsageEntry 302 PIB-ACCESS report-only 303 STATUS current 304 DESCRIPTION 305 "This class defines the usage attributes to be 306 reported, and which are related to the router 307 identified by the Router-Id." 309 ::= { ipTeAccountingClasses 1} 311 ospfTeRouterUsageEntry OBJECT-TYPE 313 SYNTAX ospfTeUsageRouterEntry 314 STATUS current 315 DESCRIPTION 316 "An entry for the ospfTeRouterUsageTable." 318 PIB-INDEX { ospfTeRouterUsagePrid} 319 UNIQUENESS { ospfTeRouterUsageLinkPrid, 320 ospfTeUsageIfActif} 322 ::= {ospfTeRouterUsageTable 1} 324 ospfTeRouterUsageEntry ::= SEQUENCE { 325 ospfTeRouterUsagePrid InstanceID, 326 ospfTeRouterUsageLinkPrid Prid, 327 ospfTeRouterUsageIfActif Counter64 } 329 ospfTeRouterUsagePrid OBJECT-TYPE 331 SYNTAX Prid 332 STATUS current 333 DESCRIPTION 334 "An integer index that uniquely identifies this 335 instance of the ospfTeRouterUsage class." 337 ::= { ospfTeRouterUsageEntry 1 } 339 ospfTeRouterUsageLinkPrid OBJECT-TYPE 341 SYNTAX Prid 342 STATUS current 343 DESCRIPTION 344 "The PRID of the Linkage policy instance used to refer 345 this usage policy instance." 347 ::= { ospfTeRouterUsageEntry 2 } 349 ospfTeRouterUsageIfActif OBJECT-TYPE 350 SYNTAX Counter64 351 STATUS current 352 DESCRIPTION 353 "The number of interfaces that participate to an OSPF- 354 TE route computation in the router identified by 355 Router-ID." 357 ::= { ospfTeRouterUsageEntry 3 } 359 -- 360 -- ospfTeUsageTable 361 -- 363 ospfTeUsageTable OBJECT-TYPE 365 SYNTAX SEQUENCE OF ospfTeUsageEntry 366 PIB-ACCESS report-only 367 STATUS current 368 DESCRIPTION 369 "This class defines the usage attributes to use for 370 OSPF TE purposes." 372 ::= { ipTeAccountingClasses 2 } 374 ospfTeUsageEntry OBJECT-TYPE 376 SYNTAX ospfTeUsageEntry 377 STATUS current 378 DESCRIPTION 379 "An entry for the ospfTeUsageTable." 381 PIB-INDEX { ospfTeUsagePrid} 382 UNIQUENESS { ospfTeUsageLinkPrid, 383 OspfTeUsageLinkDelay } 385 ::= {ospfTeUsageTable 1 } 387 ospfTeUsageEntry ::= SEQUENCE { ospfTeUsagePrid InstanceID, 388 ospfTeUsageLinkPrid Prid, 389 ospfTeUsageLinkDelay Unsigned32 } 391 ospfTeUsagePrid OBJECT-TYPE 393 SYNTAX Prid 394 STATUS current 395 DESCRIPTION 396 "An integer index that uniquely identifies this 397 instance of the ospfTeUsage class." 399 ::= { ospfTeUsageEntry 1 } 401 ospfTeUsageLinkPrid OBJECT-TYPE 403 SYNTAX Prid 404 STATUS current 405 DESCRIPTION 406 "The PRID of the Linkage policy instance used to refer 407 this usage policy instance." 409 ::= { ospfTeUsageEntry 2 } 411 ospfTeUsageLinkDelay OBJECT-TYPE 413 SYNTAX Unsigned32 414 STATUS current 415 DESCRIPTION 416 "The one-way delay that has been observed on this 417 route." 419 ::= { ospfTeUsageEntry 3 } 421 -- 422 -- isisTeUsageTable 423 -- 425 isisTeUsageTable OBJECT-TYPE 427 SYNTAX SEQUENCE OF isisTeUsageEntry 428 PIB-ACCESS report-only 429 STATUS current 430 DESCRIPTION 431 "This class defines the usage attributes to use for 432 IS-IS TE purposes." 434 ::= { ipTeAccountingClasses 3 } 436 isisTeUsageEntry OBJECT-TYPE 438 SYNTAX isisTeUsageEntry 439 STATUS current 440 DESCRIPTION 441 "An entry for the isisTeUsageTable." 443 PIB-INDEX { isisTeUsagePrid} 444 UNIQUENESS { isisTeUsageLinkPrid, 445 isisTeUsageLinkDelay } 447 ::= {isisTeUsageTable 1 } 449 isisTeUsageEntry ::= SEQUENCE { 450 isisTeUsagePrid InstanceID, 451 isisTeUsageLinkPrid Prid, 452 isisTeUsageLinkDelay Unsigned32 } 454 isisTeUsagePrid OBJECT-TYPE 456 SYNTAX Prid 457 STATUS current 458 DESCRIPTION 459 "An integer index that uniquely identifies this 460 instance of the isisTeUsage class." 462 ::= { isisTeUsageEntry 1 } 464 isisTeUsageLinkPrid OBJECT-TYPE 466 SYNTAX Prid 467 STATUS current 468 DESCRIPTION 469 "The PRID of the Linkage policy instance used to refer 470 this usage policy instance." 472 ::= { isisTeUsageEntry 2 } 474 isisTeUsageLinkDelay OBJECT-TYPE 476 SYNTAX Unsigned32 477 STATUS current 478 DESCRIPTION 479 "The one-way delay that has been observed on this 480 route." 482 ::= { isisTeUsageEntry 3 } 484 -- 485 -- bgpTeUsageTable 486 -- 488 bgpTeTable OBJECT-TYPE 490 SYNTAX SEQUENCE OF bgpTeUsageEntry 491 PIB-ACCESS report-only 492 STATUS current 493 DESCRIPTION 494 "This table contains a set of accounting information 495 related to the activation of BGP process enabling 496 exchange of QOS information." 498 ::= { ipTeAccountingClasses 4 } 500 bgpTeUsageEntry OBJECT-TYPE 501 SYNTAX bgpTeUsageEntry 502 STATUS current 503 DESCRIPTION 504 "An entry to bgpTeUsage Class." 506 PIB-INDEX { bgpTeUsagePrid } 507 UNIQUENESS { bgpTeUsageLinkPrid, 508 bgpTeUsageActIf, 509 bgpTeUsageOneWayDelay } 511 ::= { bgpTeUsageTable 1 } 513 bgpTeUsageEntry ::= SEQUENCE { 514 bgpTeUsagePrid InstanceId, 515 bgpTeUsageLinkPrid Prid, 516 bgpTeUsageActIf Counter64, 517 bgpTeUsageOneWayDelay Unsigned32 } 519 bgpTeUsagePrid OBJECT-TYPE 521 SYNTAX InstanceId 522 STATUS current 523 DESCRIPTION 524 "An integer index that uniquely identifies this 525 instance of the bgpTeUsage class." 527 ::= { bgpTeUsageEntry 1 } 529 bgpTeUsageLinkPrid OBJECT-TYPE 531 SYNTAX Prid 532 STATUS current 533 DESCRIPTION 534 "The PRID of the Linkage policy instance used to base 535 this usage policy instance upon." 537 ::= { bgpTeUsageEntry 2 } 539 bgpTeUsageActIf OBJECT-TYPE 541 SYNTAX Counter64 542 STATUS current 543 DESCRIPTION 544 "Specifies the number of interfaces that participate 545 to the BGP route computation process." 547 ::= { bgpTeUsageEntry 3 } 549 bgpTeUsageOneWayDelay OBJECT-TYPE 551 SYNTAX Unsigned32 552 STATUS current 553 DESCRIPTION 554 "Specifies the one-way delay that has been observed on 555 this route." 557 ::= { bgpTeUsageEntry 4 } 559 -- 560 -- The Threshold class that accompanies the OSPF and BGP usage 561 -- tables 562 -- 563 -- 564 -- OSPF Threshold attributes 565 -- 567 ospfTeThresholdTable OBJECT-TYPE 569 SYNTAX SEQUENCE OF ospfThresholdEntry 570 PIB-ACCESS Install 571 STATUS current 572 DESCRIPTION 573 "This class defines the threshold attributes 574 corresponding to OSPF TE usage attributes specified in 575 ospfTeUsageTable." 577 ::= { ipTeAccountingClasses 5 } 579 ospfTeThresholdEntry OBJECT-TYPE 581 SYNTAX ospfTeThresholdEntry 582 STATUS current 583 DESCRIPTION 584 "Defines the attributes to hold threshold values." 586 PIB-INDEX { ospfTeThresholdId } 588 ::= { ospfTeThresholdId 1 } 590 ospfTeThresholdEntry::= SEQUENCE { 591 ospfTeThresholdId InstanceID, 592 ospfTeThresholdBwThresholds Integer64, 593 ospfTeThresholdRsvBwThresholds Integer64 } 595 ospfTeThresholdId OBJECT-TYPE 597 SYNTAX InstanceId 598 STATUS current 599 DESCRIPTION 600 "Arbitrary integer index that uniquely identifies an 601 instance of the class." 603 ::= { ospfTeThresholdEntry 1 } 605 ospfTeThresholdBwThresholds OBJECT-TYPE 607 SYNTAX Integer64 608 STATUS current 609 DESCRIPTION 610 "The threshold the used bandwidth on the link 611 shouldn't exceed." 613 ::= { ospfTeThresholdEntry 2 } 615 ospfTeThresholdRsvBwThresholds OBJECT-TYPE 617 SYNTAX Integer64 618 STATUS current 619 DESCRIPTION 620 "The threshold the reserved bandwidth on the link 621 shouldn't exceed." 623 ::= { ospfTeThresholdEntry 3 } 625 -- 626 -- ISIS Threshold attributes 627 -- 629 isisTeThresholdTable OBJECT-TYPE 631 SYNTAX SEQUENCE OF isisThresholdEntry 632 PIB-ACCESS Install 633 STATUS current 634 DESCRIPTION 635 "This class defines the threshold attributes 636 corresponding to ISIS TE usage attributes specified in 637 isisTeUsageTable." 639 ::= { ipTeAccountingClasses 6 } 641 isisTeThresholdEntry OBJECT-TYPE 643 SYNTAX isisTeThresholdEntry 644 STATUS current 645 DESCRIPTION 646 "Defines the attributes to hold threshold values." 648 PIB-INDEX { isisTeThresholdId } 650 ::= { isisTeThresholdId 1 } 652 isisTeThresholdEntry::= SEQUENCE { 653 isisTeThresholdId InstanceID, 654 isisTeThresholdBwThresholds Integer64, 655 isisTeThresholdRsvBwThresholds Integer64 } 657 isisTeThresholdId OBJECT-TYPE 659 SYNTAX InstanceId 660 STATUS current 661 DESCRIPTION 662 "Arbitrary integer index that uniquely identifies an 663 instance of the class." 665 ::= { isisTeThresholdEntry 1 } 667 isisTeThresholdBwThresholds OBJECT-TYPE 669 SYNTAX Integer64 670 STATUS current 671 DESCRIPTION 672 "The threshold the used bandwidth on the link 673 shouldn't exceed." 675 ::= { isisTeThresholdEntry 2 } 677 isisTeThresholdRsvBwThresholds OBJECT-TYPE 679 SYNTAX Integer64 680 STATUS current 681 DESCRIPTION 682 "The threshold the reserved bandwidth on the link 683 shouldn't exceed." 685 ::= { isisTeThresholdEntry 3 } 687 -- 688 -- BGP Threshold attributes 689 -- 691 bgpTeThresholdTable OBJECT-TYPE 693 SYNTAX SEQUENCE OF bgpThresholdEntry 694 PIB-ACCESS Install 695 STATUS current 696 DESCRIPTION 697 "This class defines the threshold attributes 698 corresponding to BGP usage attributes specified in 699 bgpTeUsageTable." 701 ::= { ipTeAccountingClasses 7 } 703 bgpTeThresholdEntry OBJECT-TYPE 705 SYNTAX bgpTeThresholdEntry 706 STATUS current 707 DESCRIPTION 708 "Defines the attributes to hold threshold values." 710 PIB-INDEX { bgpTeThresholdPrid } 712 ::= { bgpTeThresholdId 1 } 714 bgpTeThresholdEntry ::= SEQUENCE { 715 bgpTeThresholdId InstanceID, 716 bgpTeThresholdNlriAddress InetAddress, 717 bgpTeThresholdNextHopAddress InetAddress, 718 bgpTeThresholdOneWayDelayThreshold Integer64, 719 bgpTeThresholdInterPacketDelayThreshold Integer64, 720 bgpTeThresholdLossRateThreshold Integer64 } 722 bgpTeThresholdId OBJECT-TYPE 724 SYNTAX InstanceId 725 STATUS current 726 DESCRIPTION 727 "Arbitrary integer index that uniquely identifies an 728 instance of the class." 730 ::= { bgpTeThresholdEntry 1 } 732 bgpTeThresholdNlriAddress OBJECT-TYPE 734 SYNTAX InetAddress 735 STATUS current 736 DESCRIPTION 737 "The IP address to match against the NLRI field of 738 QOS_NLRI attribute of the BGP4 UPDATE message 739 introduced in [11]." 741 ::= { bgpTeThresholdEntry 2 } 743 bgpTeThresholdNextHopAddress OBJECT-TYPE 745 SYNTAX InetAddress 746 STATUS current 747 DESCRIPTION 748 "The address of the next router." 750 ::= { bgpTeThresholdEntry 3 } 752 bgpTeThresholdOneWayDelayThreshold OBJECT-TYPE 754 SYNTAX Integer64 755 STATUS current 756 DESCRIPTION 757 "The threshold of the one-way delay, that will trigger 758 a report in the next reporting interval when 759 exceeded." 761 ::= { bgpTeThresholdEntry 4 } 763 bgpTeThresholdInterPacketDelayThreshold OBJECT-TYPE 765 SYNTAX Integer64 766 STATUS current 767 DESCRIPTION 768 "The threshold of the inter-packet delay variation, 769 that will trigger a report in the next reporting 770 interval, when exceeded." 772 ::= { bgpTeThresholdEntry 5 } 774 bgpTeThresholdLossRateThreshold OBJECT-TYPE 776 SYNTAX Integer64 777 STATUS current 778 DESCRIPTION 779 "The threshold, in terms of loss rate, that will 780 trigger a report in the next reporting interval, when 781 exceeded." 783 ::= { bgpTeThresholdEntry 6 } 785 END 787 6. Security Considerations 789 Data manipulated within the context of IP TE accounting could be used 790 by the IP TE decision-making processes, but only authorized COPS-PR 791 communications can take place. Therefore, this draft does not 792 introduce any additional security issues other than those that have 793 been identified in the COPS-PR specification [12]. 795 Nevertheless, the activation of an integrity mechanism is recommended 796 for external systems making use of the TE accounting data. 798 7. References 800 [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 801 9, RFC 2026, October 1996. 802 [2] Jacquenet, C., "An IP Traffic Engineering COPS Client-type", 803 draft jacquenet-ip-te-cops-04.txt, Work in Progress, December 804 2002. 805 [3] Rawlins, D., Kulkarni, A., Bokaemper, M., Ho Chan, K., "Framework 806 of COPS-PR Policy Usage Feedback", draft-ietf-rap-feedback-frwk- 807 03.txt, October 2002. 808 [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement 809 Levels", BCP 14, RFC 2119, March 1997 810 [5] Goderis, D., T'Joens, Y., Jacquenet, C., Memenios, G., Pavlou, 811 G., Egan, R., Griffin, D., Georgatsos, P., Georgiadis, 812 L.,"Specification of a Service Level Specification (SLS) 813 Template", draft-tequila-sls-02.txt, Work in Progress, February 814 2002. 815 [6] Boyle, J., Cohen, R., Durham, D., Herzog, S., Raja, R., Sastry, 816 A., "The COPS (Common Open Policy Service) Protocol", RFC 2748, 817 January 2000. 819 [7] Boucadair, M., Jacquenet, C., "An IP Traffic Engineering Policy 820 Information Base", draft-jacquenet-ip-te-pib-03.txt, Work in 821 Progress, December 2002. 822 [8] Boucadair, M., Jacquenet, C., "IGP Policy Information Base for TE 823 purposes", Work in Progress, December 2002. 824 [9] Boucadair, M., Jacquenet, C., "BGP Policy Information Base for 825 QoS purposes", Work in Progress, December 2002. 826 [10] Rawlins, D., Kulkarni, A., Bokaemper, M., Ho Chan, K. " 827 Framework Policy Information Base for Usage Feedback ", draft- 828 ietf-rap-feedback-fr-pib-04.txt, November 2002. 829 [11] Jacquenet, C., "Providing Quality of Service Indication by the 830 BGP-4 Protocol: the QOS_NLRI Attribute", draft-jacquenet-qos-nrli- 831 04.txt, Work in Progress, March 2002. 832 [12] Ho Chan, K., Durham, D., Gai, S., Herzog, S., McLoghrie, K., 833 Reichmeyer, F., Seligson, J., Smith, A., Yavatkar, R., "COPS Usage 834 for Policy Provisioning (COPS-PR)", RFC 3084, March 2001. 836 8. Acknowledgments 838 The author would like to thank M. Jacquenet for his remarks and 839 suggestions. 841 9. Author's Addresses 843 Mohamed Boucadair 844 France Telecom R & D 845 DMI/SIR 846 42, rue des Coutures 847 BP 6243 848 14066 Caen Cedex 4 849 France 850 Phone: +33 2 31 75 92 31 851 Email: mohamed.boucadair@rd.francetelecom.com 853 Full Copyright Statement 855 "Copyright (C) The Internet Society (2002). All Rights Reserved. 857 This document and translations of it may be copied and furnished to 858 others, and derivative works that comment on or otherwise explain it 859 or assist its implementation may be prepared, copied, published and 860 distributed, in whole or in part, without restriction of any kind, 861 provided that the above copyright notice and this paragraph are 862 included on all such copies and derivative works. However, this 863 document itself may not be modified in any way, such as by removing 864 the copyright notice or references to the Internet Society or other 865 Internet organizations, except as needed for the purpose of 866 developing Internet standards in which case the procedures for 867 copyrights defined in the Internet Standards process must be 868 followed, or as required to translate it into languages other than 869 English. 871 The limited permissions granted above are perpetual and will not be 872 revoked by the Internet Society or its successors or assigns. 874 This document and the information contained herein is provided on an 875 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 876 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 877 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 878 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 879 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.