idnits 2.17.1 draft-boucadair-ipte-acct-pib-00.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 page length should not exceed 58 lines per page, but there was 7 longer pages, the longest (page 3) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 16 pages 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 16 instances of too long lines in the document, the longest one being 35 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 684 has weird spacing: '...tion by the...' == 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 2002) is 7987 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-02 == Outdated reference: A later version (-03) exists of draft-tequila-sls-02 == Outdated reference: A later version (-04) exists of draft-ietf-rap-feedback-frwk-02 -- Duplicate reference: draft-ietf-rap-feedback-frwk, mentioned in '8', was also mentioned in '3'. -- No information found for draft-jacquenet-qos-nrli - is the name correct? Summary: 5 errors (**), 0 flaws (~~), 8 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-00.txt June 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...........................2 42 3. Accounting and Traffic Engineering..........................3 43 3.1. Introduction................................................3 44 3.2. The IP TE Selection Tables..................................4 45 3.3. The IP TE Accounting Usage Tables...........................4 46 3.4. PIB overview................................................5 47 4. IP TE Usage PIB.............................................5 48 5. Security Considerations....................................14 49 6. References.................................................14 50 7. Acknowledgments............................................15 51 8. Author's Addresses.........................................15 53 1. Introduction 55 Traffic engineering is one of the possible means for solving 56 congestion problems and permitting efficient use of the network 57 resources. The design of an IP Traffic Engineering (IP TE) policy 58 implies the manipulation of a large amount of configuration 59 information that includes routing considerations, traffic forecast, 60 available resources, etc. 62 These parameters are provisioned as configuration information to the 63 network devices by means of a COPS-based communication scheme, thanks 64 to the use of a specific client-type. But remains the choice of the 65 appropriate parameters to meet network constraints as well as Quality 66 Of Service (QOS) requirements, and also to observe the impact of such 67 choice on the stability of the network. 69 From this standpoint, several methods can be adopted: either use 70 statistical data based on mathematical models, or data resulting of 71 measurements. The advantage of the second method is that it allows 72 for real time statistics. 74 Therefore, the actual enforcement of a traffic engineering policy 75 requires a feedback mechanism not only to qualify how efficient such 76 enforcement is, but also the impact the future decisions made by the 77 Policy Decision Point (PDP) and installed by the PDP at the Policy 78 Enforcement Point (PEP)-embedded devices. 80 Within the context of this document, the data recorded, monitored 81 and/or reported by the PEP are the results of the activation of 82 dynamic routing processes (e.g. Open Shortest Path First (OSPF) and 83 Border Gateway Protocol version 4 (BGP)). 85 We propose in this document to define a set of IP TE accounting usage 86 Policy Rule Classes (PRC) that will be monitored, recorded and/or 87 reported by the PEP. Those PRCs complement the PRC classes that have 88 been defined in the Framework of COPS-PR PIB for Policy Usage [3]. 90 This document is organised as follows: 92 - Section 3 shows the use of accounting mode within a TE context. 93 - Section 4 presents the IP TE Usage PIB. 95 2. Conventions used in this document 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC-2119 [4]. 100 3. Accounting and Traffic Engineering 101 3.1. Introduction 103 The actual enforcement of an IP TE policy is conditioned by the 104 manipulation of information such as traffic forecast (according to 105 customers' requests, for example [5]), and traffic load calculation 106 (see fig.1). Within the context of a COPS architecture, the 107 qualification of a policy's efficiency could be based upon the 108 accounting mode. 110 [6] defines the capability to report information to the PDP. Several 111 types of reports are defined: success, failure and accounting. A 112 framework of the use of the accounting mode is introduced in [3]. 114 +-----------------+ 115 | Other | 116 | external system | 117 +-----------------+ 118 ^ 119 | +-----------------+ 120 | | TE | 121 | | Forecast Block | 122 | +-----------------+ 123 | ^ +------------------+ 124 | | | PDP | 125 | | | Decision-making | 126 | | +--------/\--------+ 127 | | +--------\/--------+ 128 | | | | 129 | | | PDP | 130 | | | | 131 | | +------------------+ 132 +--------------------------+ | | ^ 133 | PEP | | | | 134 | +-------------------+ | | | | 135 | | IP TE Client-Type | | | | | 136 | | +--------------+ | |<----+ | | 137 | | |Report Process| | |<--------------------+ | 138 | | |-Monitoring | | |<----------------------------+ 139 | | |-Recording | | | IP TE REPORT 140 | | |-Reporting | | | 141 | | +--------------+ | | 142 | +-------------------+ | 143 +--------------------------+ 144 Fig.1: IP TE Reporting Mechanism 146 According to Fig.1, the report sent by the IP TE client type is 147 received by the PDP. 149 The IP TE report classes are instantiated as multiple Provisioning 150 Instance (PRI) instances, each of which being identified by 151 PRovisioning Instance iDentifier (PRID). These classes contain 152 attributes that actually describe the accounting IP TE-related 153 information collected in the network. 155 3.2. The IP TE Selection Tables 157 The document [7] defines an IP Traffic Engineering Policy Information 158 Base (IP TE PIB). The IP TE PIB is organized into the following 159 provisioning classes: 161 1. The Forwarding classes (ipTeFwClasses): the information contained 162 in these classes is meant to provide a detailed description of the 163 traffic-engineered routes. Only one table is defined: the IP TE 164 Route table, which describes the information related to TE routes 165 that have been installed by the routers in their FIBs. 167 2. The Metrics classes (ipTeMetricsClasses): the information stored 168 in the tables included in this class is meant to provide the 169 description of the metric values that will be taken into account 170 by intra- and inter-domain routing protocols for the computation 171 and the selection of traffic-engineered routes. 173 3. The Statistics classes (ipTeStatsClasses): the information 174 contained in these classes is meant to provide statistics on the 175 enforcement of the TE policies. 177 These tables are used as selection tables. 179 3.3. The IP TE Accounting Usage Tables 181 Within the context of [8], three policies are defined: 182 - The selection criteria policy: defines the conditions used by PEP 183 to monitor and record a usage policy. 184 - The usage policy: defines what attributes are monitored and/or 185 recorded by the PEP. 186 - The linkage policy: provides a linkage for the selection and usage 187 policies. 189 As mentioned above, the tables defined in the IP TE PIB are used as 190 the Selection policies and we introduced in the following Section 4 191 the Usage classes. 193 In addition, the IP TE Selection Usage Combination Capability Table 194 contains objects pointing to the IP TE Usage tables, IP TE Selection 195 tables and Threshold tables. 197 3.4. PIB overview 199 The PIB defined within the context of IP traffic engineering for 200 accounting purposes has the goal to complete the whole COPS TE 201 reporting machinery. This PIB contains the following tables: 203 - ospfTeRouterUsageTable : this class defines the usage 204 attributes to be reported, and which are related 205 to the router identified by the Router-Id. 206 - ospfTeUsageTable : this class defines the usage attributes to use 207 for OSPF TE purposes. 208 - bgpTeTable : this table contains a set of accounting 209 information related to the activation of BGP 210 process enabling exchange of QOS information. 211 - ospfTeThresholdTable: this class defines the threshold attributes 212 corresponding to OSPF TE usage attributes 213 specified in ospfTeUsageTable. 214 - bgpTeThresholdTable: this class defines the threshold attributes 215 corresponding to BGP usage attributes specified 216 in bgpTeUsageTable. 217 4. IP TE Usage PIB 219 -- 220 -- The PIB defined within the context of IP traffic engineering 221 -- for accounting purposes has the goal to complete the whole 222 -- COPS TE reporting machinery. 223 -- Data contained in this PIB aren't stabilized yet and will be 224 -- modified and updated as necessary. 225 -- 227 IPTE-ACCOUNTING-PIB PIB-DEFINITIONS ::= BEGIN 229 IMPORTS 230 ExtUTCTime, Unsigned32, Unsigned64, 231 Integer32, MODULE-IDENTITY, OBJECT-TYPE 232 FROM COPS-PR-SPPI 233 TruthValue, TEXTUAL-CONVENTION 234 FROM SNMPv2-TC 235 PolicyInstanceId, PolicyReferenceId 236 FROM COPS-PR-SPPI-TC; 237 RoleCombination 238 FROM POLICY-DEVICE-AUX-MIB; 239 Counter64 240 FROM SNMPv2-SMI; 242 ipTeAccountingPib MODULE-IDENTITY 244 SUBJECT-CATEGORIES {tbd} 245 LAST-UPDATED "200201250900Z" 246 ORGANIZATION "France Telecom R&D" 247 CONTACT-INFO " 248 Mohamed Boucadair 249 Adresse: 42, rue des Coutures 250 BP 6243 251 14066 Caen Cedex 252 Phone: +33 2 31 75 92 31 253 Email: Mohamed.Boucadair@francetelecom.com" 255 DESCRIPTION 256 "The PIB module that contains classes describing the 257 parameters to be monitored, recorded and/or reported 258 by the PEP for Traffic Engineering accounting 259 purposes." 261 ::= {tbd} 263 -- 264 -- The ipTe Accounting Class 265 -- 267 ipTeAccountingClasses 268 OBJECT IDENTIFIER ::= { ipTeAccountingPib 1 } 270 -- 271 -- The MPLS TE Accounting Class 272 -- 273 -- This class defines tables related to MPLS TE 274 -- To be done in next version of this draft. 276 lspTeAccountingClasses 277 OBJECT IDENTIFIER ::= { ipTeAccountingPib 2 } 279 -- 280 -- ospfTeRouterUsageTable 281 -- 283 ospfTeRouterUsageTable OBJECT-TYPE 285 SYNTAX SEQUENCE OF ospfTeRouterUsageEntry 286 PIB-ACCESS report-only 287 STATUS current 288 DESCRIPTION 289 "This class defines the usage attributes to be 290 reported, and which are related to the router 291 identified by the Router-Id." 293 ::= { ipTeAccountingClasses 1} 295 ospfTeRouterUsageEntry OBJECT-TYPE 296 SYNTAX ospfTeUsageRouterEntry 297 STATUS current 298 DESCRIPTION 299 "An entry for the ospfTeRouterUsageTable." 301 PIB-INDEX { ospfTeRouterUsagePrid} 302 UNIQUENESS { ospfTeRouterUsageLinkPrid, 303 ospfTeUsageIfActif} 305 ::= {ospfTeRouterUsageTable 1} 307 ospfTeRouterUsageEntry ::= SEQUENCE { 308 ospfTeRouterUsagePrid InstanceID, 309 ospfTeRouterUsageLinkPrid Prid, 310 ospfTeRouterUsageIfActif Counter64 } 312 ospfTeRouterUsagePrid OBJECT-TYPE 314 SYNTAX Prid 315 STATUS current 316 DESCRIPTION 317 "An integer index that uniquely identifies this 318 instance of the ospfTeRouterUsage class." 320 ::= { ospfTeRouterUsageEntry 1 } 322 ospfTeRouterUsageLinkPrid OBJECT-TYPE 324 SYNTAX Prid 325 STATUS current 326 DESCRIPTION 327 "The PRID of the Linkage policy instance used to refer 328 this usage policy instance." 330 ::= { ospfTeRouterUsageEntry 2 } 332 ospfTeRouterUsageIfActif OBJECT-TYPE 334 SYNTAX Counter64 335 STATUS current 336 DESCRIPTION 337 "The number of interfaces that participate to an OSPF- 338 TE route computation in the router identified by 339 Router-ID." 341 ::= { ospfTeRouterUsageEntry 3 } 343 -- 344 -- ospfTeUsageTable 345 -- 346 ospfTeUsageTable OBJECT-TYPE 348 SYNTAX SEQUENCE OF ospfTeUsageEntry 349 PIB-ACCESS report-only 350 STATUS current 351 DESCRIPTION 352 "This class defines the usage attributes to use for 353 OSPF TE purposes." 355 ::= { ipTeAccountingClasses 1 } 357 ospfTeUsageEntry OBJECT-TYPE 359 SYNTAX ospfTeUsageEntry 360 STATUS current 361 DESCRIPTION 362 "An entry for the ospfTeUsageTable." 364 PIB-INDEX { ospfTeUsagePrid} 365 UNIQUENESS { ospfTeUsageLinkPrid, 366 OspfTeUsageLinkDelay } 368 ::= {ospfTeUsageTable 1 } 370 ospfTeUsageEntry ::= SEQUENCE { ospfTeUsagePrid 371 InstanceID, 372 ospfTeUsageLinkPrid Prid, 373 ospfTeUsageLinkDelay Unsigned32 } 375 ospfTeUsagePrid OBJECT-TYPE 377 SYNTAX Prid 378 STATUS current 379 DESCRIPTION 380 "An integer index that uniquely identifies this 381 instance of the ospfTeUsage class." 383 ::= { ospfTeUsageEntry 1 } 385 ospfTeUsageLinkPrid OBJECT-TYPE 387 SYNTAX Prid 388 STATUS current 389 DESCRIPTION 390 "The PRID of the Linkage policy instance used to refer 391 this usage policy instance." 393 ::= { ospfTeUsageEntry 2 } 395 ospfTeUsageLinkDelay OBJECT-TYPE 396 SYNTAX Unsigned32 397 STATUS current 398 DESCRIPTION 399 "The one-way delay that has been observed on this 400 route." 402 ::= { ospfTeUsageEntry 3 } 404 -- 405 -- bgpTeUsageTable 406 -- 408 bgpTeTable OBJECT-TYPE 410 SYNTAX SEQUENCE OF bgpTeUsageEntry 411 PIB-ACCESS report-only 412 STATUS current 413 DESCRIPTION 414 "This table contains a set of accounting information 415 related to the activation of BGP process enabling 416 exchange of QOS information." 418 ::= { ipTeAccountingClasses 2 } 420 bgpTeUsageEntry OBJECT-TYPE 422 SYNTAX bgpTeUsageEntry 423 STATUS current 424 DESCRIPTION 425 "An entry to bgpTeUsage Class." 427 PIB-INDEX { bgpTeUsagePrid } 428 UNIQUENESS { bgpTeUsageLinkPrid, 429 bgpTeUsageActIf, 430 bgpTeUsageOneWayDelay } 432 ::= { bgpTeUsageTable 1 } 434 bgpTeUsageEntry ::= SEQUENCE { 435 bgpTeUsagePrid InstanceId, 436 bgpTeUsageLinkPrid Prid, 437 bgpTeUsageActIf Counter64, 438 bgpTeUsageOneWayDelay Unsigned32 } 440 bgpTeUsagePrid OBJECT-TYPE 442 SYNTAX InstanceId 443 STATUS current 444 DESCRIPTION 445 "An integer index that uniquely identifies this 446 instance of the bgpTeUsage class." 448 ::= { bgpTeUsageEntry 1 } 450 bgpTeUsageLinkPrid OBJECT-TYPE 452 SYNTAX Prid 453 STATUS current 454 DESCRIPTION 455 "The PRID of the Linkage policy instance used to base 456 this usage policy instance upon." 458 ::= { bgpTeUsageEntry 2 } 460 bgpTeUsageActIf OBJECT-TYPE 462 SYNTAX Counter64 463 STATUS current 464 DESCRIPTION 465 "Specifies the number of interfaces that participate 466 to the BGP route computation process." 468 ::= { bgpTeUsageEntry 3 } 470 bgpTeUsageOneWayDelay OBJECT-TYPE 472 SYNTAX Unsigned32 473 STATUS current 474 DESCRIPTION 475 "Specifies the one-way delay that has been observed on 476 this route." 478 ::= { bgpTeUsageEntry 4 } 480 -- 481 -- The Threshold class that accompanies the OSPF and BGP usage 482 -- tables 483 -- 484 -- 485 -- OSPF Threshold attributes 486 -- 488 ospfTeThresholdTable OBJECT-TYPE 490 SYNTAX SEQUENCE OF ospfThresholdEntry 491 PIB-ACCESS Install 492 STATUS current 493 DESCRIPTION 494 "This class defines the threshold attributes 495 corresponding to OSPF TE usage attributes specified in 496 ospfTeUsageTable." 498 ::= { ipTeAccountingClasses 3 } 500 ospfTeThresholdEntry OBJECT-TYPE 502 SYNTAX ospfTeThresholdEntry 503 STATUS current 504 DESCRIPTION 505 "Defines the attributes to hold threshold values." 507 PIB-INDEX { ospfTeThresholdId } 509 ::= { ospfTeThresholdId 1 } 511 ospfTeThresholdEntry::= SEQUENCE { 512 ospfTeThresholdId InstanceID, 513 ospfTeThresholdBwThresholds Integer64, 514 ospfTeThresholdRsvBwThresholds Integer64 } 516 ospfTeThresholdId OBJECT-TYPE 518 SYNTAX InstanceId 519 STATUS current 520 DESCRIPTION 521 "Arbitrary integer index that uniquely identifies an 522 instance of the class." 524 ::= { ospfTeThresholdEntry 1 } 526 ospfTeThresholdBwThresholds OBJECT-TYPE 528 SYNTAX Integer64 529 STATUS current 530 DESCRIPTION 531 "The threshold the used bandwidth on the link 532 shouldn't exceed." 534 ::= { ospfTeThresholdEntry 2 } 536 ospfTeThresholdRsvBwThresholds OBJECT-TYPE 538 SYNTAX Integer64 539 STATUS current 540 DESCRIPTION 541 "The threshold the reserved bandwidth on the link 542 shouldn't exceed." 544 ::= { ospfTeThresholdEntry 3 } 546 -- 547 -- BGP Threshold attributes 548 -- 550 bgpTeThresholdTable OBJECT-TYPE 552 SYNTAX SEQUENCE OF bgpThresholdEntry 553 PIB-ACCESS Install 554 STATUS current 555 DESCRIPTION 556 "This class defines the threshold attributes 557 corresponding to BGP usage attributes specified in 558 bgpTeUsageTable." 560 ::= { ipTeAccountingClasses 4 } 562 bgpTeThresholdEntry OBJECT-TYPE 564 SYNTAX bgpTeThresholdEntry 565 STATUS current 566 DESCRIPTION 567 "Defines the attributes to hold threshold values." 569 PIB-INDEX { bgpTeThresholdPrid } 571 ::= { bgpTeThresholdId 1 } 573 bgpTeThresholdEntry ::= SEQUENCE { 574 bgpTeThresholdId InstanceID, 575 bgpTeThresholdNlriAddress InetAddress, 576 bgpTeThresholdNextHopAddress InetAddress, 577 bgpTeThresholdOneWayDelayThreshold Integer64, 578 bgpTeThresholdInterPacketDelayThreshold Integer64, 580 bgpTeThresholdLossRateThreshold Integer64 } 582 bgpTeThresholdId OBJECT-TYPE 584 SYNTAX InstanceId 585 STATUS current 586 DESCRIPTION 587 "Arbitrary integer index that uniquely identifies an 588 instance of the class." 590 ::= { bgpTeThresholdEntry 1 } 592 bgpTeThresholdNlriAddress OBJECT-TYPE 594 SYNTAX InetAddress 595 STATUS current 596 DESCRIPTION 597 "The IP address to match against the NLRI field of 598 QOS_NLRI attribute of the BGP4 UPDATE message 599 introduced in [9]." 601 ::= { bgpTeThresholdEntry 2 } 603 bgpTeThresholdNextHopAddress OBJECT-TYPE 605 SYNTAX InetAddress 606 STATUS current 607 DESCRIPTION 608 "The address of the next router." 610 ::= { bgpTeThresholdEntry 3 } 612 bgpTeThresholdOneWayDelayThreshold OBJECT-TYPE 614 SYNTAX Integer64 615 STATUS current 616 DESCRIPTION 617 "The threshold of the one-way delay, that will trigger 618 a report in the next reporting interval when 619 exceeded." 621 ::= { bgpTeThresholdEntry 4 } 623 bgpTeThresholdInterPacketDelayThreshold OBJECT-TYPE 625 SYNTAX Integer64 626 STATUS current 627 DESCRIPTION 628 "The threshold of the inter-packet delay variation, 629 that will trigger a report in the next reporting 630 interval, when exceeded." 632 ::= { bgpTeThresholdEntry 5 } 634 bgpTeThresholdLossRateThreshold OBJECT-TYPE 636 SYNTAX Integer64 637 STATUS current 638 DESCRIPTION 639 "The threshold, in terms of loss rate, that will 640 trigger a report in the next reporting interval, when 641 exceeded." 643 ::= { bgpTeThresholdEntry 6 } 645 END 647 5. Security Considerations 649 Data manipulated within the context of IP TE accounting could be used 650 by the IP TE decision-making processes, but only authorized COPS-PR 651 communications can take place. Therefore, this draft does not 652 introduce any additional security issues other than those that have 653 been identified in the COPS-PR specification [10]. 655 Nevertheless, the activation of an integrity mechanism is recommended 656 for external systems making use of the TE accounting data. 658 6. References 660 [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 661 9, RFC 2026, October 1996. 662 [2] Jacquenet, C., "An IP Traffic Engineering COPS Client-type", 663 draft jacquenet-ip-te-cops-03.txt, Work in Progress, June 2002. 664 [3] Rawlins, D., Kulkarni, A., Bokaemper, M., Ho Chan, K., "Framework 665 of COPS-PR Policy Usage Feedback", draft-ietf-rap-feedback-frwk- 666 02.txt, March 2002. 667 [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement 668 Levels", BCP 14, RFC 2119, March 1997 670 [5] Goderis, D., T'Joens, Y., Jacquenet, C., Memenios, G., Pavlou, 671 G., Egan, R., Griffin, D., Georgatsos, P., Georgiadis, 672 L.,"Specification of a Service Level Specification (SLS) 673 Template", draft-tequila-sls-02.txt, Work in Progress, February 674 2002. 675 [6] Boyle, J., Cohen, R., Durham, D., Herzog, S., Raja, R., Sastry, 676 A., "The COPS (Common Open Policy Service) Protocol", RFC 2748, 677 January 2000. 678 [7] Boucadair, M., Jacquenet, C., "An IP Traffic Engineering Policy 679 Information Base", draft-jacquenet-ip-te-pib-02.txt, Work in 680 Progress, June 2002. 681 [8] Rawlins, D., Kulkarni, A., Bokaemper, M., Ho Chan, K. "Framework 682 of COPS-PR Policy Usage Feedback", draft-ietf-rap-feedback-frwk- 683 02.txt, March 2002. 684 [9] Jacquenet, C., "Providing Quality of Service Indication by the 685 BGP-4 Protocol: the QOS_NLRI Attribute", draft-jacquenet-qos-nrli- 686 04.txt, Work in Progress, March 2002. 687 [10] Ho Chan, K., Durham, D., Gai, S., Herzog, S., McLoghrie, K., 688 Reichmeyer, F., Seligson, J., Smith, A., Yavatkar, R., "COPS Usage 689 for Policy Provisioning (COPS-PR)", RFC 3084, March 2001. 691 7. Acknowledgments 693 The author would like to thank M. Jacquenet for his remarks and 694 suggestions. 696 8. Author's Addresses 698 Mohamed Boucadair 699 France Telecom R & D 700 DMI/SIR 701 42, rue des Coutures 702 BP 6243 703 14066 Caen Cedex 4 704 France 705 Phone: +33 2 31 75 92 31 706 Email: mohamed.boucadair@rd.francetelecom.com 708 Full Copyright Statement 710 "Copyright (C) The Internet Society (2002). All Rights Reserved. 712 This document and translations of it may be copied and furnished to 713 others, and derivative works that comment on or otherwise explain it 714 or assist its implementation may be prepared, copied, published and 715 distributed, in whole or in part, without restriction of any kind, 716 provided that the above copyright notice and this paragraph are 717 included on all such copies and derivative works. However, this 718 document itself may not be modified in any way, such as by removing 719 the copyright notice or references to the Internet Society or other 720 Internet organizations, except as needed for the purpose of 721 developing Internet standards in which case the procedures for 722 copyrights defined in the Internet Standards process must be 723 followed, or as required to translate it into languages other than 724 English. 726 The limited permissions granted above are perpetual and will not be 727 revoked by the Internet Society or its successors or assigns. 729 This document and the information contained herein is provided on an 730 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 731 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 732 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 733 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 734 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.