idnits 2.17.1 draft-ietf-rap-rsvppcc-pib-01.txt: -(60): 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: ---------------------------------------------------------------------------- == There are 4 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([2749]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The "Author's Address" (or "Authors' Addresses") section title is misspelled. == Line 372 has weird spacing: '... the feedba...' == Line 729 has weird spacing: '...applied to In...' == Line 1086 has weird spacing: '...be used by th...' == Line 1525 has weird spacing: '...at have legi...' == 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 (March 1, 2002) is 8064 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC-2119' is mentioned on line 38, but not defined == Unused Reference: '3084' is defined on line 1561, but no explicit reference was found in the text == Unused Reference: 'SPPI' is defined on line 1565, but no explicit reference was found in the text == Unused Reference: '2750' is defined on line 1578, but no explicit reference was found in the text == Unused Reference: '2751' is defined on line 1581, but no explicit reference was found in the text == Unused Reference: '2872' is defined on line 1591, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 3084 == Outdated reference: A later version (-07) exists of draft-ietf-rap-sppi-02 ** Downref: Normative reference to an Historic draft: draft-ietf-rap-sppi (ref. 'SPPI') -- Possible downref: Non-RFC (?) normative reference: ref. 'POLFRWK' == Outdated reference: A later version (-06) exists of draft-ietf-rap-feedback-fr-pib-01 ** Downref: Normative reference to an Historic draft: draft-ietf-rap-feedback-fr-pib (ref. 'FEEDBKFRPIB') ** Obsolete normative reference: RFC 2751 (Obsoleted by RFC 3181) ** Obsolete normative reference: RFC 2752 (Obsoleted by RFC 3182) ** Downref: Normative reference to an Informational RFC: RFC 2753 ** Downref: Normative reference to an Informational RFC: RFC 2998 == Outdated reference: A later version (-03) exists of draft-rawlins-admctl-ds-mgt-01 -- Possible downref: Normative reference to a draft: ref. 'EdgeAdmCtl' Summary: 11 errors (**), 0 flaws (~~), 17 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Diana Rawlins 2 Expiration: September 2002 Lei Yao 3 File: draft-ietf-rap-rsvppcc-pib-01.txt Richard McClain 4 WorldCom 5 Amol Kulkarni 6 Intel 8 RSVP Policy Control Criteria PIB 10 March 1, 2002 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other documents 24 at any time. It is inappropriate to use Internet-Drafts as 25 reference material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Conventions used in this document 35 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 36 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 37 this document are to be interpreted as described in [RFC-2119]. 39 Abstract 41 This draft describes the use of COPS-PR for support of a PDP 42 provisioning a PEP with RSVP policy control criteria and defines a 43 RSVP policy control criteria PIB for this purpose. The RSVPCC-PIB 44 described in the document is provided for definition of policies that 45 are currently defined by the outsourcing model [2749]. It is designed 46 to be scalable and flexible as well as extensible for accommodating 47 future policy criteria. 49 Table Of Contents 51 Abstract...........................................................1 52 1. Introduction....................................................3 53 2 General Concepts.................................................3 54 2.1 Overview.......................................................3 55 2.2 Normal Operation...............................................4 56 2.3 RSVP Policy Processing Models with local policy criteria.......4 57 2.4 Session Classification and Reservation Styles..................5 58 3 PIB Summary......................................................5 59 3.1 Capabilities Table - policyControlCapsTable....................6 60 3.2 Policy Mode Table � pccModeTable...............................6 61 3.3 PCC Linkage Table - pccLinkTable..............................6 62 3.4 Authorization Policy Tables....................................6 63 3.4.1 Traffic Specifier (Tspec) Policies Table.....................6 64 3.4.2 RSPEC Limits Table...........................................6 65 3.4.3 Identification Authentication Data Policy Elements Table.....6 66 3.4.4 Priority Preemption Policy Elements Table....................7 67 3.5 Integrated Services over Differentiated Services Policy Tables.7 68 3.5.1 Intsrv to Diffserv Interworking Function Table...............7 69 3.5.2 Admission Control Virtual Pool Table.........................7 70 3.5.3 Edge Point Identification Table..............................7 71 3.5 Policy Control Criteria Usage Tables...........................7 72 3.5.1 Policy Control Criteria Allocated Table......................7 73 3.5.2 Policy Control Criteria Session Stats Table..................7 74 3.5.3 Virtual Pool Usage Table.....................................8 75 3.6 Example........................................................8 76 4 The RSVP Policy Control Criteria PIB Module......................8 77 5 Security Considerations.........................................30 78 6 Acknowledgements................................................31 79 7 Authors Addresses...............................................31 80 8 References......................................................31 82 1. Introduction 84 The RSVP Policy Control Criteria PIB defines the policy criteria used 85 to authorize an RSVP reservation request. The policy criteria defined 86 by this PIB are enforced by the RSVP enabled Policy Enforcement Point 87 (PEP). These are provisioned by the Policy Decision Point (PDP) 88 rather than outsourced to the PDP. 90 Policy control is an important processing component described in RSVP 91 [2205]. While admission control evaluates the resources available at 92 the RSVP enabled interface, it does not determine if the requested 93 reservation is allowed. Policy control determines whether the policy 94 is allowed (or authorized.) It may base the decision on multiple 95 factors including application identification, policy authentication 96 preemption rules and service level agreements. 98 Two basic models are defined for prescribing policy to a network 99 enforcement device using COPS [2748]. First, there is an outsourcing 100 mechanism for policy control where the network device requests a 101 policy decision from an external policy server[2749]. This mechanism 102 can be used in conjunction with a local decision policy scheme that 103 outsources information to the PDP for confirmation of the locally 104 made decision [2753]. There also exists a policy configuration 105 mechanism that does not require the network device to outsource all 106 policy decisions. The device is provisioned with decision policy 107 using Policy Information Bases (PIB) that define the policies to be 108 enforced by the PEP. [3084.] 110 Currently there is no PIB defining RSVP policy control criteria to be 111 conveyed by the provisioning model. Provisioned policy control 112 criteria are useful in topologies where large numbers of signaling 113 flows are transiting a set of well know boundary devices. The sheer 114 volume and nature of the application generating RSVP signals (such as 115 with VoIP) may make outsourcing policy impractical at some boundary 116 devices. The use of local policy control criteria is an attractive 117 alternative to going off-board to another policy device for all PATH 118 and RESV messages and their associated contexts (Incoming / 119 Allocation / Outgoing), which reduces the response time of policy 120 control, the amount of policy control traffic on the network, and 121 overall QoS setup time for the application. 123 Reliance on a network operator to manually provision the policy 124 criteria locally per device is not a scalable solution. It is labor- 125 intensive, time-consuming as well as error prone and it limits the 126 flexibility of policy control. The automated provisioning of RSVP 127 criteria by the PDP expands the uses of QoS reservation policy to 128 dynamic, high volume QoS sensitive applications. 130 2 General Concepts 132 2.1 Overview 133 This document defines a RSVP Policy Control Criteria PIB. The RSVP 134 Policy Control Criteria PIB provides the policy classes describing 135 the criteria for RSVP policy control to the PEP so it does not need 136 to outsource decisions for all RSVP signals. 138 Together with the PIB defined in this document, COPS-PR is used to 139 push RSVP related policy control criteria from a PDP to a PEP. Thus 140 the RSVP policy control criteria are installed on the PEP a priori of 141 the affected RSVP signals and enables making policy control decisions 142 for the RSVP messages locally at the PEP. 144 The use of provisioned policy criteria does not prohibit the 145 outsourcing of policy decisions. The outsourcing and provisioned 146 policy approaches may be used in combination with each other as 147 defined by the following three processing models: 148 - Make local decisions AND outsource each request to the PDP for 149 confirmation as described in [2753]. 150 - Make local decisions and outsource ONLY IF no relevant local 151 policy is found. 152 - Take local decisions only. Do not outsource. 154 Feedback must be provided to the PDP about the usage of policy at the 155 PEP. The PEP monitors, tracks and provides periodic accounting type 156 reports to the PDP. 158 2.2 Normal Operation 160 When a PEP is initialized, a COPS session connection is established 161 for SUBJECT_CATEGORY RSVP-PCC between the PEP and PDP. The PEP issues 162 the request for initial configuration describing its basic PIB policy 163 capabilities per [POLFRWK.] The policy classes supported by the PEP 164 are indicated with the PRCSupportTable instances. The PEP also 165 describes the policy model capability associated with that interface 166 using an instance of the RSVPPccCapTable. 168 The Policy Decision Point determines the appropriate policy 169 information to supply the PEP and responds with a decision install. 170 The PEP confirms the success or failure of the configuration decision 171 with a report. 173 The failover operation of the PEP and PDP is described in [3084.] 175 2.3 RSVP Policy Processing Models with local policy criteria 177 The policy control processing follows one of three possible models: 179 - The first model is the LDP model described in [2753]. The installed 180 policy criteria are used to make a Local Decision. If the local 181 policy approves the reservation request the RSVP message continues 182 its normal processing. The LDP then confirms the decision with the 183 PDP by issuing a request with the LPDP Decision Object. The PDP then 184 issues a final decision, which is enforced by the PEP. The 185 outsourcing of the request to the PDP is accomplished via the COPS- 186 RSVP connection [2753.] 188 - The second model is where the PEP performs policy control by 189 approving a reservation request based on installed policy criteria. 190 In the event that no policy exists for the reservation request, the 191 PEP then outsources the request to the PDP. The PDP then decides to 192 approve or deny the request [2749]. In other words, when a PEP 193 receives a RSVP message, it first queries Local RSVP policy control 194 criteria. If no policy exists for the request the PEP uses COPS-RSVP 195 to query the PDP for outsourcing policy decisions. Note that the PEP 196 may send periodic reports to the PDP informing it of factors that 197 affect decision-making at the PDP e.g. the resource usage etc. In the 198 case that a request is outsourced to a PDP, all pending allocation 199 usage reports should be sent prior to issuing the request. This helps 200 the PDP maintain an accurate picture of resource availability at the 201 PEP while making decisions. 203 - The third model is where the PEP relies entirely upon the 204 provisioned policy control criteria for its policy control decision- 205 making. If no policies are found for a policy request of a RSVP 206 session, the RSVP session should be rejected. No COPS-RSVP connection 207 between the PEP and PDP is required in this third model when the 208 policy control criteria is local and there is no outsourcing 209 operation. 211 2.4 Session Classification and Reservation Styles 213 The IP filters, frwkIPFilterTable, described in [POLFRWK] are used to 214 associate the authorization (or enforcement) policy with a RSVP 215 session. These filter instances provide the ability to identify the 216 flow 5-tuple: source address, source port, destination address, 217 destination port and protocol id. The RSVP Sender_Template Class, 218 FilterSpec Class and Session Class can be classified using the 219 frwkIPFilterTable. The 5-tuple filter instances may be defined using 220 a wildcard value for the attribute, which accommodates classification 221 policies for the RSVP Fixed Filter, Shared Explicit and Wildcard 222 reservation styles. The frwkIPFilterTable attribute, frwkIPFilterDSCP 223 attribute should contain a wildcard value and must be ignored with 224 regards to the authorization policy. 226 3 PIB Summary 228 The PIB defines the policy control criteria using several types of 229 Policy Rule Classes (PRC). These are the PCC capability policy, the 230 PCC mode policy, filter policy, authorization policies, Intsrv over 231 Diffserv policies, linkage policy and usage policy. The PCC 232 capability specifies the local policy models that the device 233 supports. The PCC mode defines the local policy model that the PDP is 234 directing the PEP to use. The filter policy identifies the flows that 235 have authorization policy. The authorization policy defines the 236 enforcement rules. The Intsrv over Diffserv policies define the 237 interworking rules. The linkage policy associates the filter policy 238 with an authorization policy. The usage policy provides feedback to 239 the PDP according to what the PEP has monitored and recorded via an 240 accounting type report. 242 3.1 Capabilities Table - policyControlCapsTable 244 This table provides a single instance describing the RSVP local 245 decision policy models or modes that the PEP is capable of 246 supporting. The three modes have been previously described in section 247 2.3. 249 3.2 Policy Mode Table � pccModeTable 250 This table contains a single instance that specifies the RSVP local 251 decision policy model that the PDP is directing the PEP to use. This 252 mode must be compatible with the capabilities indicated by the PEP. 254 3.3 PCC Linkage Table - pccLinkTable 256 This table defines the association between the filter policy and the 257 authorization policy. The PCC Linkage Class references the filter 258 PRID as well as the PRID of the authorization policy class. It links 259 the two instances. (The PRID is the Object Identifier constructed 260 with the PRC and the instance id as the last sub-identifier.) Note 261 that the same filter may have multiple authorization policies. For 262 example a filter may have a Traffic Specifier policy, a Rate 263 Specifier policy and Preemption policy that should be used as policy 264 criteria for determining if the flow is allowed. 266 There is future work needed to explore the optimization of the 267 association of filters with authorization policies. 269 3.4 Authorization Policy Tables 271 The Authorization tables contain the enforcement policy classes that 272 determine whether the RSVP reservation is allowed. These policy 273 classes describe the Integrated Services Controlled Load and 274 Guaranteed Services, [2210,2211,2212,2215], the identity 275 authorization user and authorization application policies [2752], and 276 the preemption policies [2751.] The policy classes included in this 277 group are: 279 3.4.1 Traffic Specifier (Tspec) Policies Table 281 Identifies the Integrated Service type and defines the transmission 282 rate of the traffic flow with that Integrated Service type. 284 3.4.2 RSPEC Limits Table 286 Defines the requested service rate from the network related with 287 Guaranteed Services. 289 3.4.3 Identification Authentication Data Policy Elements Table 290 Defines means to securely identify the owner or application making 291 the reservation request. 293 3.4.4 Priority Preemption Policy Elements Table 295 Defines the relative order of importance of the requested flow and 296 permits the preemption of lesser important flows to allow higher 297 priority flows admission. 299 3.5 Integrated Services over Differentiated Services Policy Tables 301 These tables describe the interworking rules for Integrated Services 302 over Diffserv Services. The interworking provisioning rules are based 303 on the model where Intsrv is in the control plane and Diffserv is in 304 the data plane as introduced in [2998] and then further discussed in 305 [EdgeAdmCtl] 307 3.5.1 Intsrv to Diffserv Interworking Function Table 309 This table defines the specific attributes used for the interworking 310 between the RSVP process in the control plane and the Differentiated 311 Services in the data plane. This is used by the Packet Classification 312 and Packet Schedule process for classifying and marking the traffic 313 flow with the appropriate Differentiated Service Code Point and 314 policing the flow. 316 3.5.2 Admission Control Virtual Pool Table 318 This table defines the virtual pool that is mapped to the 319 Differentiated Services resource allocated to Intsrv traffic. It 320 specifies the Intsrv Service Type, maximum capacity available to the 321 Intsrv admission control process, reservation acceptance status and 322 the associated boundary router logical interface if applicable. 324 3.5.3 Edge Point Identification Table 326 This table is used to identify the receiver domain. The entries 327 define the addresses that are receivers with respect to the router. 328 Admission control performs the upstream resource check when the RSVP 329 Session Object matches one of these address ranges. 331 3.5 Policy Control Criteria Usage Tables 333 3.5.1 Policy Control Criteria Allocated Table 335 This usage table records the traffic specifications allocated to a 336 successful session and provides feedback to the PDP via the 337 accounting type report. 339 3.5.2 Policy Control Criteria Session Stats Table 341 The usage table records the start time and end time of a session. The 342 start time is based on the successful allocation of the resources for 343 a reservation and the end time is associated with the termination of 344 the session and its policy. 346 3.5.3 Virtual Pool Usage Table 348 The virtual pool usage table tracks the current total of resources 349 consumed by the Intsrv flows for a given virtual pool. 351 3.6 Example 353 Authorization policies are defined in terms of TRAFFIC SPECIFIER and 354 RSPEC characteristics as well as Integrated Services type i.e. 355 Controlled Load or Guaranteed Services. Additional criteria such as 356 Policy Authentication and Priority Preemption can also be specified. 358 An example policy control criteria scenario is as follows. The 359 SenderTemplate and Filterspec are compared against the policy control 360 criteria filters by the PEP. The filter is associated with a set of 361 authorization rules with the linkage policies. For example, policy 362 control criteria could establish authorization for the Gold and 363 Silver VoIP services. The Gold VoIP could be defined as allowing a 364 guaranteed service request, within a traffic specifier and rspec 365 limit, with a high preemption priority and high preemption defending 366 priority. A Silver VoIP could be defined as granting a controlled 367 load service request, within a traffic specifier and rspec limit, 368 with a moderate preemption priority and low preemption defending 369 priority. The PEP records the traffic specifications requested by the 370 session and the session statistics. It reports these back to the PDP 371 on a periodic basis determined by the accounting interval defined in 372 the feedback linkage policy [FEEDBKFRPIB]. 374 4 The RSVP Policy Control Criteria PIB Module 376 RSVP-PCC-PIB PIB-DEFINITIONS ::= BEGIN 378 IMPORTS 379 Unsigned32, Unsigned64, 380 Integer32, MODULE-IDENTITY 381 FROM COPS-PR-SPPI 382 InstanceId, ReferenceId, Prid, TagId 383 FROM COPS-PR-SPPI-TC 384 InetAddress, InetAddressType 385 FROM SNMPv2-TC 386 MessageSize, BitRate, BurstSize 387 FROM INTEGRATED-SERVICES-MIB 388 FrwkIpFilterTable 389 FROM FRAMEWORK-PIB; 391 RsvpPccPib MODULE-IDENTITY 392 SUBJECT-CATEGORIES { all } 393 LAST-UPDATED "200011131600Z" 394 ORGANIZATION "IETF-RAP-WG" 395 CONTACT-INFO " 396 Diana Rawlins 397 901 International Parkway 398 Richardson, TX 75081 399 Email: Diana.Rawlins@wcom.com 400 Phone +1 972 729 1044 402 Lei Yao 403 22001 Loudoun County Parkway 404 Ashburn, VA 20147 405 Email: Lei.yao@wcom.com 406 Phone: +1 703 886 1830 408 Richard McClain 409 901 International Parkway 410 Richardson, TX 75081 411 Email: Richard.McClain@wcom.com 412 Phone: +1 972 729 1094 414 Amol Kulkarni 415 JF3-206 416 2111 NE 25th Ave 417 Hillsboro, Oregon 97124 418 Email: amol.kulkarni@intel.com 419 Phone: +1 503 712 1168 " 421 DESCRIPTION 422 "A PIB module containing the policy control 423 classes that are required for support of 424 pushing policy control from the PDP to PEPs." 426 ::= { pib xx } -- xx to be assigned by IANA 428 -- 429 -- The root OID for PRCs in the RSVP Policy Control Criteria PIB 430 -- 432 rsvpPccBaseClasses 433 OBJECT IDENTIFIER ::= { RsvpPccPib 1 } 435 -- 436 -- Textual Conventions 437 -- 439 -- 440 -- Policy Control Capabilities Table 441 -- 443 policyControlCapsTable OBJECT-TYPE 444 SYNTAX SEQUENCE OF PolicyControlCapsEntry 445 PIB-ACCESS notify, 3 446 STATUS current 447 DESCRIPTION 448 " The policy control capability in terms of the policy 449 control mode supported by the device." 451 ::= { rsvpPccBaseClasses 1 } 453 policyControlCapsEntry OBJECT-TYPE 454 SYNTAX PolicyControlCapsEntry 455 STATUS current 456 DESCRIPTION 457 " The instance defining the policy control mode." 459 PIB-INDEX { policyControlCapsPccId } 461 ::= { policyControlCapsTable 1 } 463 PolicyControlCapsEntry ::= SEQUENCE { 464 policyControlCapsPccId InstanceId, 465 policyControlCapsMode BITS 466 } 468 policyControlCapsPccId OBJECT-TYPE 469 SYNTAX InstanceId 470 STATUS current 471 DESCRIPTION 472 "An arbitrary integer index that uniquely identifies 473 an instance of the PolicyControlCaps class." 475 ::= { policyControlCapsEntry 1 } 477 policyControlCapsMode OBJECT-TYPE 478 SYNTAX BITS { 479 CONFIRM_ALL(0), 480 LOCAL_IF_AVAILABLE(1), 481 LOCAL_ONLY(2) 482 } 483 STATUS current 484 DESCRIPTION 485 "The policy control criteria mode of the device. The 486 device may support any combination of modes. 487 The valid bit values are: 488 (0)Local Decision Policy which makes decision and 489 then outsources confirmation to the PDP 490 (1)local control and if no policy control criteria 491 is available locally, then outsource decision to PDP 492 (2)local policy control only." 494 ::= { policyControlCapsEntry 2} 496 -- 497 -- Policy Control Criteria Mode Table 498 -- 499 pccModeTable OBJECT-TYPE 501 SYNTAX SEQUENCE OF PccModeEntry 502 PIB-ACCESS notify,3 503 STATUS current 504 DESCRIPTION 505 " The policy control mode designated by the PDP." 507 ::= { rsvpPccBaseClasses 2 } 509 pccModeEntry OBJECT-TYPE 510 SYNTAX PccModeEntry 511 STATUS current 512 DESCRIPTION 513 " The instance defining the PDP designated mode of 514 policy control." 516 PIB-INDEX { pccModeId } 518 ::= { pccModeTable 1 } 520 PccModeEntry ::= SEQUENCE { 521 pccModeId InstanceId, 522 pccModeMode INTEGER 523 } 525 pccModeId OBJECT-TYPE 526 SYNTAX InstanceId 527 STATUS current 528 DESCRIPTION 529 "An arbitrary integer index that uniquely identifies an 530 instance of the pccModeTable class." 532 ::= { pccModeEntry 1 } 534 pccModeMode OBJECT-TYPE 535 SYNTAX INTEGER { 536 CONFIRM_ALL(1), 537 LOCAL_IF_AVAILABLE(2), 538 LOCAL_ONLY(3) 539 } 540 STATUS current 541 DESCRIPTION 542 "The policy criteria control mode to be used by the 543 device. 544 The valid enumeration values are: 545 (1)Local Decision Policy which makes decision and 546 then outsources confirmation to the PDP 547 (2)local control and if no policy control criteria 548 is available locally, then outsource decision to PDP 549 (3)local policy control only." 551 ::= { pccModeEntry 2} 553 -- 554 -- Policy Control Criteria Linkage Table 555 -- 557 pccLinkTable OBJECT-TYPE 558 SYNTAX SEQUENCE OF PccLinkEntry 559 PIB-ACCESS install-notify, 4 560 STATUS current 561 DESCRIPTION 562 " This table defines the association between 563 the filter, frwkIpFilterTable instance and 564 the authorization policy instance" 566 ::= { rsvpPccBaseClasses 3 } 568 pccLinkEntry OBJECT-TYPE 569 SYNTAX PccLinkEntry 570 STATUS current 571 DESCRIPTION 572 " An entry links the filter and the authorization 573 policy." 575 PIB-INDEX { pccLinkPccId } 576 UNIQUENESS { 577 pccLinkFilterRefId, 578 pccLinkPolicyPrid } 580 ::= { pccLinkTable 1 } 582 PccLinkEntry::= SEQUENCE { 583 pccLinkPccId InstanceId, 584 pccLinkFilterRefId ReferenceId, 585 pccLinkPolicyPrid Prid 586 } 588 pccLinkPccId OBJECT-TYPE 589 SYNTAX InstanceId 590 STATUS current 591 DESCRIPTION 592 " An arbitrary integer index that uniquely 593 identifies an instance of the PccLink class. " 595 ::= { pccLinkEntry 1 } 597 pccLinkFilterRefId OBJECT-TYPE 598 SYNTAX ReferenceId 599 PIB-REFERENCES { frwkIpFilterEntry } 601 STATUS current 602 DESCRIPTION 603 " References an instance of FrwkIPFilterTable. " 604 ::= { pccLinkEntry 2 } 606 pccLinkPolicyPrid OBJECT-TYPE 607 SYNTAX Prid 608 STATUS current 609 DESCRIPTION 610 " Specifies the specific PRID of the PRC and instance 611 of authorization policy associated with this filter." 613 ::= { pccLinkEntry 3 } 615 -- 616 -- Traffic Specifier Policies Table 617 -- 619 trafficSpecifierPolicyTable OBJECT-TYPE 620 SYNTAX SEQUENCE OF TrafficSpecifierPolicyEntry 621 PIB-ACCESS install-notify, 7 622 STATUS current 623 DESCRIPTION 624 "This table defines the Traffic specifier policy 625 control characteristics that can be used to determine 626 SENDER_TSPEC, Controlled-Load or Guaranteed Services 627 policies." 629 ::= { rsvpPccBaseClasses 4 } 631 trafficSpecifierPolicyEntry OBJECT-TYPE 632 SYNTAX TrafficSpecifierPolicyEntry 633 STATUS current 634 DESCRIPTION 635 " An entry describes a specific limits for a T-SPEC 636 policy. " 638 PIB-INDEX { trafficSpecifierPolicyId } 639 UNIQUENESS {trafficSpecifierPolicyIntService, 640 trafficSpecifierPolicyBucketRate, 641 trafficSpecifierPolicyBucketSize, 642 trafficSpecifierPolicyPeakRate, 643 trafficSpecifierPolicyMinPolicedUnit, 644 trafficSpecifierPolicyMaxPacketSize } 646 ::= { trafficSpecifierPolicyTable 1 } 648 TrafficSpecifierPolicyEntry ::= SEQUENCE { 649 trafficSpecifierPolicyId InstanceId, 650 trafficSpecifierPolicyIntService Integer32, 651 trafficSpecifierPolicyBucketRate BitRate, 652 trafficSpecifierPolicyBucketSize Unsigned32, 653 trafficSpecifierPolicyPeakRate BurstSize, 654 trafficSpecifierPolicyMinPolicedUnit MessageSize, 655 trafficSpecifierPolicyMaxPacketSize MessageSize 657 } 659 trafficSpecifierPolicyId OBJECT-TYPE 660 SYNTAX InstanceId 661 STATUS current 662 DESCRIPTION 663 "An arbitrary integer index that uniquely identifies an 664 instance of the TrafficSpecifierPolicy class." 666 ::= { trafficSpecifierPolicyEntry 1 } 668 trafficSpecifierPolicyIntService OBJECT-TYPE 669 SYNTAX Integer32 670 STATUS current 671 DESCRIPTION 672 " The traffic specifier policy is applied 673 to the flow of this Integrated Service type." 674 ::= { trafficSpecifierPolicyEntry 2 } 676 trafficSpecifierPolicyBucketRate OBJECT-TYPE 677 SYNTAX BitRate 678 STATUS current 679 DESCRIPTION 680 " 'r' bytes per second, the token bucket rate. " 682 ::= { trafficSpecifierPolicyEntry 3 } 684 trafficSpecifierPolicyBucketSize OBJECT-TYPE 685 SYNTAX Unsigned32 686 STATUS current 687 DESCRIPTION 688 " 'b' bucket depth in bytes, the token bucket size. " 690 ::= { trafficSpecifierPolicyEntry 4 } 692 trafficSpecifierPolicyPeakRate OBJECT-TYPE 693 SYNTAX BurstSize 694 STATUS current 695 DESCRIPTION 696 " 'p' peak traffic data rate in bytes. " 698 ::= { trafficSpecifierPolicyEntry 5 } 700 trafficSpecifierPolicyMinPolicedUnit OBJECT-TYPE 701 SYNTAX MessageSize 702 STATUS current 703 DESCRIPTION 704 " 'm' minimum policed unit: size in bytes 705 of application data and all IP and greater 706 level (UDP, RTP, TCP, etc.) headers. " 708 ::= { trafficSpecifierPolicyEntry 6 } 710 trafficSpecifierPolicyMaxPacketSize OBJECT-TYPE 711 SYNTAX MessageSize 712 STATUS current 713 DESCRIPTION 714 " 'M' maximum packet size: biggest packet 715 that conforms to traffic specification. " 717 ::= { trafficSpecifierPolicyEntry 7 } 719 -- 720 -- RSPEC Limits Table 721 -- 723 rspecLimitsTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF RspecLimitsEntry 725 PIB-ACCESS install-notify, 4 726 STATUS current 727 DESCRIPTION 728 "This table defines the RSPEC policy control 729 characteristics that are applied to Integrated 730 Services Guaranteed Service." 732 ::= { rsvpPccBaseClasses 5 } 734 rspecLimitsEntry OBJECT-TYPE 735 SYNTAX RspecLimitsEntry 736 STATUS current 737 DESCRIPTION 738 " An entry that defines specific Rate and Slack 739 limits for a Guaranteed Service resource request " 741 EXTENDS { trafficSpecifierPolicyEntry } 742 UNIQUENESS { rspecLimitsRate, 743 rspecLimitsSlackTerm } 745 ::= { rspecLimitsTable 1 } 747 RspecLimitsEntry ::= SEQUENCE { 748 rspecLimitsRate BitRate, 749 rspecLimitsSlackTerm Unsigned32 751 } 753 rspecLimitsRate OBJECT-TYPE 754 SYNTAX BitRate 755 STATUS current 756 DESCRIPTION 757 " 'R' - Rate. Must be greater than or equal to 'r', 758 rate for the flow " 760 ::= { rspecLimitsEntry 1 } 762 rspecLimitsSlackTerm OBJECT-TYPE 763 SYNTAX Unsigned32 764 STATUS current 765 DESCRIPTION 766 " 'S' - Slack Term. Defines in microseconds the 767 difference between desired delay and the delay 768 attained with the reservation level of R" 770 ::= { rspecLimitsEntry 2 } 772 -- 773 -- Authentication Data Policy Element Table 774 -- 776 authDataPolicyElementTable OBJECT-TYPE 777 SYNTAX SEQUENCE OF AuthDataPolicyElementEntry 778 PIB-ACCESS install-notify, 6 779 STATUS current 780 DESCRIPTION 781 "This table specifies policy control to identify and 782 authenticate the owner making resource request." 784 ::= { rsvpPccBaseClasses 6 } 786 authDataPolicyElementEntry OBJECT-TYPE 787 SYNTAX AuthDataPolicyElementEntry 788 STATUS current 789 DESCRIPTION 790 " An entry defines the specific authentication 791 identify used to grant permission for the 792 reservation request." 794 PIB-INDEX { authDataPolicyElementPccId } 795 UNIQUENESS { 796 authDataPolicyElementPolicySetId, 797 authDataPolicyElementPolicyIdentity, 798 authDataPolicyElementPolicyAuthAttrType, 799 authDataPolicyElementPolicyAuthAttrSubType 800 } 802 ::= { authDataPolicyElementTable 1 } 804 AuthDataPolicyElementEntry::= SEQUENCE { 805 authDataPolicyElementPccId InstanceId, 806 authDataPolicyElementPolicySetId TagId, 807 authDataPolicyElementPolicyIdentity INTEGER, 808 authDataPolicyElementPolicyAuthAttrType INTEGER, 809 authDataPolicyElementPolicyAuthAttrSubType INTEGER 810 } 812 authDataPolicyElementPccId OBJECT-TYPE 813 SYNTAX InstanceId 814 STATUS current 815 DESCRIPTION 816 "An arbitrary integer index that uniquely identifies 817 an instance of the AuthDataPolicyElement class." 819 ::= { authDataPolicyElementEntry 1 } 821 authDataPolicyElementPolicySetId OBJECT-TYPE 822 SYNTAX TagId 823 STATUS current 824 DESCRIPTION 825 " This associates a set of authentication attributes." 827 ::= { authDataPolicyElementEntry 2 } 829 authDataPolicyElementPolicyIdentity OBJECT-TYPE 830 SYNTAX INTEGER{ 831 AUTH_USER(1), 832 AUTH_APP(2) 833 } 834 STATUS current 835 DESCRIPTION 836 " Identifies the Policy Set Element via enumeration 837 values: 838 (2) AUTH_USER 839 (3) AUTH_APP " 841 ::= { authDataPolicyElementEntry 3 } 843 authDataPolicyElementPolicyAuthAttrType OBJECT-TYPE 844 SYNTAX INTEGER { 845 POLICY_LOCATOR(1), 846 CREDENTIAL(2), 847 DIGITAL_SIGNATURE(3), 848 POLICY_ERROR_object(4) 849 } 850 STATUS current 851 DESCRIPTION 852 " Enumeration values: 853 (1) POLICY_LOCATOR (valid for both AUTH_USER and 854 AUTH_APP) 855 (2) CREDENTIAL (valid for both AUTH_USER and 856 AUTH_APP) 857 (3) DIGITAL_SIGNATURE 858 (4) POLICY_ERROR_OBJECT " 860 ::= { authDataPolicyElementEntry 4 } 862 authDataPolicyElementPolicyAuthAttrSubType OBJECT-TYPE 863 SYNTAX INTEGER { 864 NO_TYPE(0), 865 ASCII_DN(1), 866 UNICODE_DN(2), 867 ASCII_DN_ENCRYPT(3), 868 UNICODE_DN_ENCRYPT(4), 869 ASCII_ID(5), 870 UNICODE_ID(6), 871 KERBEROS_TKT(7), 872 X509_CERT(8), 873 PGP_CERT(9), 874 NO_MORE_INFO(10), 875 UNSUPPORTED_CRED_TYPE(11), 876 INSUFFICIENT_PRIVS(12), 877 EXPIRED_CREDENTIAL(13), 878 IDENTITY_CHANGED(14) 879 } 880 STATUS current 881 DESCRIPTION 882 " For POLICY_LOCATOR valid enumeration values are: 883 (1) ASCII_DN (valid for both AUTH_USER and 884 AUTH_APP) 885 (2) UNICODE_DN (valid for both AUTH_USER and 886 AUTH_APP) 887 (3) ASCII_DN_ENCRYPT 888 (4) UNICODE_DN_ENCRYPT 890 For CREDENTIAL valid enumeration values are: 891 (5) ASCII_ID (valid for both AUTH_USER and 892 AUTH_APP) 893 (6) UNICODE_ID (valid for both AUTH_USER and 894 AUTH_APP) 895 (7) KERBEROS_TKT 896 (8) X509_V3_CERT 897 (9) PGP_CERT 899 For DIGITAL_SIGNATURE: 900 Sub-Type set to 0 902 For POLICY_ERROR_OBJECT valid enumeration values are: 903 (10) ERROR_NO_MORE_INFO 904 (11) UNSUPPORTED_CREDENTIAL_TYPE 905 (12) INSUFFICIENT_PRIVILEGES 906 (13) EXPIRED_CREDENTIAL 907 (14) IDENTITY_CHANGED " 909 ::= { authDataPolicyElementEntry 5 } 911 -- 912 -- Priority Preemption Policy Element Table 913 -- 915 priorityPreemptionPolicyElementTable OBJECT-TYPE 916 SYNTAX SEQUENCE OF PriorityPreemptionPolicyElementEntry 917 PIB-ACCESS install-notify,5 918 STATUS current 919 DESCRIPTION 920 "This table defines policy control for priority 921 preemption." 923 ::= { rsvpPccBaseClasses 7 } 925 priorityPreemptionPolicyElementEntry OBJECT-TYPE 926 SYNTAX PriorityPreemptionPolicyElementEntry 927 STATUS current 928 DESCRIPTION 929 " An entry defines the specific preemption priority to 930 admit the flow and the defending priority. " 932 PIB-INDEX { priorityPreemptionPolicyElementPccId } 933 UNIQUENESS { 934 priorityPreemptionPolicyElementMergeStrategy, 935 priorityPreemptionPolicyElementPreemptionPriority, 936 priorityPreemptionPolicyElementDefendingPriority 937 } 939 ::= { priorityPreemptionPolicyElementTable 1 } 941 PriorityPreemptionPolicyElementEntry ::= SEQUENCE { 942 priorityPreemptionPolicyElementPccId InstanceId, 943 priorityPreemptionPolicyElementMergeStrategy INTEGER, 944 priorityPreemptionPolicyElementPreemptionPriority INTEGER, 945 priorityPreemptionPolicyElementDefendingPriority INTEGER 946 } 948 priorityPreemptionPolicyElementPccId OBJECT-TYPE 949 SYNTAX InstanceId 950 STATUS current 951 DESCRIPTION 952 "An arbitrary integer index that uniquely identifies 953 an instance of the PriorityPreemptionPolicyElement 954 class." 956 ::= { priorityPreemptionPolicyElementEntry 1 } 958 priorityPreemptionPolicyElementMergeStrategy OBJECT-TYPE 959 SYNTAX INTEGER { 960 HIGHEST_QOS(1), 961 HIGHEST_PRIORITY(2), 962 ERROR_ON_MERGE(3) 963 } 964 STATUS current 965 DESCRIPTION 966 " Defines the merging strategy for the flow. The 967 Enum values are: 968 (1) take priority of highest QoS 969 (2) take highest priority 970 (3) force an error on heterogeneous merge" 972 ::= { priorityPreemptionPolicyElementEntry 2 } 974 priorityPreemptionPolicyElementPreemptionPriority OBJECT-TYPE 975 SYNTAX INTEGER 976 STATUS current 977 DESCRIPTION 978 " Defines the value of the new reservation that is 979 compared against the defending priorities of existing 980 flows. A higher value represents a higher priority." 982 ::= { priorityPreemptionPolicyElementEntry 3 } 984 priorityPreemptionPolicyElementDefendingPriority OBJECT-TYPE 985 SYNTAX INTEGER 986 STATUS current 987 DESCRIPTION 988 " The value defined for an existing flow to defend its 989 priority against a new reservation seeking admission. 990 The higher value represents higher priority." 992 ::= { priorityPreemptionPolicyElementEntry 4 } 994 -- 995 --Intsrv to Diffserv Interworking Function Table 996 -- 998 pccIwfTable OBJECT-TYPE 999 SYNTAX SEQUENCE OF PccIwfEntry 1000 PIB-ACCESS Install 1001 STATUS current 1002 DESCRIPTION 1003 "This table defines the attributes used for the 1004 interworking between the RSVP process in the 1005 control plane and Differentiated Services in the 1006 data plane." 1008 ::= {rsvpPccBaseClasses 8} 1010 pccIwfEntry OBJECT-TYPE 1011 SYNTAX PccIwfEntry 1012 STATUS current 1013 DESCRIPTION 1014 "Defines the attributes for Intsrv and Diffserv 1015 interworking." 1016 PIB-INDEX {pccIwfId} 1018 ::= {pccIwfTable 1} 1020 PccIwfEntry ::= SEQUENCE { 1021 pccIwfId InstanceId, 1022 pccIwfIntSrvClass Integer32, 1023 pccIwfDSCP Integer32, 1024 pccIwfOutOfProfile Integer32, 1025 pccIwfRemarkvalue Integer32, 1026 pccIwfScheduler Integer32 1027 } 1029 pccIwfId OBJECT-TYPE 1030 SYNTAX InstanceId 1031 STATUS current 1032 DESCRIPTION 1033 "This is the unique identifier of the iwfTable 1034 entry." 1035 ::= { pccIwfEntry 1} 1037 pccIwfIntSrvClass OBJECT-TYPE 1038 SYNTAX Integer32 1039 STATUS current 1040 DESCRIPTION 1041 "The value of the Intsrv Class associated with 1042 the attributes of this specific interworking function 1043 entry. It must have a corresponding bit set in 1044 pccACPoolISClass." 1045 ::= { pccIwfEntry 2} 1047 pccIwfDSCP OBJECT-TYPE 1048 SYNTAX Integer32 1049 STATUS current 1050 DESCRIPTION 1051 "The Value of the DSCP to assign the data stream 1052 for the session with the IntSrv class type 1053 matching the value of the pccIwfIntSrvClass. 1054 Value range is 0 � 63." 1055 ::= { pccIwfEntry 3} 1057 pccIwfOutOfProfile OBJECT-TYPE 1058 SYNTAX Integer32 1059 STATUS current 1060 DESCRIPTION 1061 "This indicates the behavior when the data stream 1062 is out of profile. This value overrides any other 1063 configured profile such as that defined in the 1064 MeterTableEntry. The value of 0 indicates that 1065 this attribute is ignored for this entry. A value 1066 of 1 indications the out of profile packet is 1067 dropped. A value of 2 indicates the out of profile 1068 packet DSCP is remarked with the value 1069 pccIwfRemarkValue." 1070 ::= {pccIwfEntry 4} 1072 pccIwfRemarkvalue OBJECT-TYPE 1073 SYNTAX Integer32 1074 STATUS current 1075 DESCRIPTION 1076 "This is the value of the DSCP to remark an out of 1077 profile packet. This value is only used if the 1078 pccIwfOutOfProfile has a value of 2." 1079 ::= {pccIwfEntry 5} 1081 pccIwfScheduler OBJECT-TYPE 1082 SYNTAX Integer32 1083 STATUS current 1084 DESCRIPTION 1085 "This is the value that identifies the scheduler 1086 to be used by the data streams of sessions with an 1087 IntSrv class matching the value of the attribute 1088 pccIwfIntSrClass." 1089 ::= {pccIwfEntry 6} 1091 -- 1092 --Admission Control Virtual Pool Table 1093 -- 1095 pccACVirPoolTable OBJECT-TYPE 1096 SYNTAX SEQUENCE OF PccACVirPoolEntry 1097 PIB-ACCESS Install 1098 STATUS current 1099 DESCRIPTION 1100 "This table defines the virtual pool used by the RSVP 1101 process during admission control." 1103 ::= {rsvpPccBaseClasses 9} 1105 pccACVirPoolEntry OBJECT-TYPE 1106 SYNTAX PccACVirPoolEntry 1107 STATUS current 1108 DESCRIPTION 1109 "Defines the attributes for the Intsrv virtual pool." 1110 PIB-INDEX {pccACVirPoolId} 1112 ::= {pccACVirPoolTable 1} 1114 PccACVirPoolEntry ::= SEQUENCE { 1115 pccACVirPoolId InstanceId, 1116 pccACVirPoolInterface SnmpAdminString, 1117 pccACVirPoolDirection Integer32, 1118 pccACVirPoolIntSrvClass BITS, 1119 pccACVirPoolMaxAbsRate Unsigned32, 1120 pccACVirPoolAcceptResv Integer32 1121 } 1123 pccACVirPoolId OBJECT-TYPE 1124 SYNTAX InstanceId 1125 STATUS current 1126 DESCRIPTION 1127 "This is the unique identifier of the pccACVirPool 1128 entry." 1129 ::= { pccACVirPoolEntry 1} 1131 pccACVirPoolInterface OBJECT-TYPE 1132 SYNTAX SnmpAdminString 1133 STATUS current 1134 DESCRIPTION 1135 "The SnmpAdminString identifies the logical interface 1136 associated with the Admission Control Virtual 1137 Pool entry." 1138 ::= { pccACVirPoolEntry 2} 1140 pccACVirPoolDirection OBJECT-TYPE 1141 SYNTAX Integer32 1142 STATUS current 1143 DESCRIPTION 1144 "This attribute indicates the relationship of the 1145 traffic stream to the interface. The traffic 1146 stream is either inbound (1) or outbound (2). An 1147 upstream virtual pool has an inbound Direction 1148 and a downstream virtual pool has a Direction of 1149 outbound." 1150 ::= { pccACVirPoolEntry 3} 1152 pccACVirPoolIntSrvClass OBJECT-TYPE 1153 SYNTAX BITS 1154 STATUS current 1155 DESCRIPTION 1156 "The bit string indicates the IntSrv class or 1157 classes that have resources allocated from this 1158 virtual pool by admission control. 1159 Value range is 0 � 63." 1160 ::= { pccACVirPoolEntry 4} 1162 pccACVirPoolMaxAbsRate OBJECT-TYPE 1163 SYNTAX Unsigned32 1164 STATUS current 1165 DESCRIPTION 1166 "This is the maximum absolute rate in kilobits 1167 that this pool may allocate to the IntSrv 1168 sessions defined by the 1169 pccACVirtPoolIntSrvClass." 1170 ::= {pccACVirPoolEntry 5} 1172 pccACVirPoolAcceptResv OBJECT-TYPE 1173 SYNTAX Integer32 1174 STATUS current 1175 DESCRIPTION 1176 "This value indicates whether the RSVP admission 1177 control is to accept RSVP RESV request for the 1178 IntSrv flows belonging to the IntSrv classes 1179 defined by pccACVirPoolIntSrvClass." 1180 ::= {pccACVirPoolEntry 6} 1182 -- 1183 --Edge Point Identification Table 1184 -- 1186 pccEdgeTable OBJECT-TYPE 1187 SYNTAX SEQUENCE OF PccEdgeEntry 1188 PIB-ACCESS Install 1189 STATUS current 1190 DESCRIPTION 1191 "This table defines the attributes used to identify 1192 the receiver domain. Admission control performs the 1193 upstream resource check when the RSVP Session Object 1194 matches one of the entries in this table." 1196 ::= {rsvpPccBaseClasses 10} 1198 pccEdgeEntry OBJECT-TYPE 1199 SYNTAX PccEdgeEntry 1200 STATUS current 1201 DESCRIPTION 1202 "Defines the attributes for identifying the 1203 receiver domain edge that invokes upstream 1204 Admission control in addition to downstream 1205 Admission control." 1206 PIB-INDEX {pccEdgeId} 1208 ::= {pccEdgeTable 1} 1210 PccEdgeEntry ::= SEQUENCE { 1211 pccEdgeId InstanceId, 1212 pccEdgeAddrType InetAddressType, 1213 pccEdgeAddr InetAddress, 1214 pccEdgeAddrMask Unsigned32 1215 } 1217 pccEdgeId OBJECT-TYPE 1218 SYNTAX InstanceId 1219 STATUS current 1220 DESCRIPTION 1221 "This is the unique identifier of the pccEdgeTable 1222 entry." 1223 ::= { pccEdgeEntry 1} 1225 pccEdgeAddrType OBJECT-TYPE 1226 SYNTAX InetAddressType 1227 STATUS current 1228 DESCRIPTION 1229 "This is the enumerated value specifying the type 1230 of address (IPv4 or Ipv6) as defined in RFC 2851." 1231 ::= { pccEdgeEntry 2} 1233 pccEdgeAddr OBJECT-TYPE 1234 SYNTAX InetAddress 1235 STATUS current 1236 DESCRIPTION 1237 "When the value of this address matches the RSVP 1238 Session Object Destination Address, it indicates 1239 a that the session receiver is downstream and that 1240 the upstream admission control should be performed." 1241 ::= { pccEdgeEntry 3} 1243 pccEdgeAddrMask OBJECT-TYPE 1244 SYNTAX unsigned32 1245 STATUS current 1246 DESCRIPTION 1247 "The length of the mask for matching the address." 1248 ::= { pccEdgeEntry 4} 1250 -- 1251 -- The Policy Control Criteria Session Statistics usage 1252 -- 1254 pccSessionStatsUsageTable OBJECT-TYPE 1255 SYNTAX SEQUENCE OF PccSessionStatsUsageEntry 1256 PIB-ACCESS report-only 1257 STATUS current 1258 DESCRIPTION 1259 "This class defines the session statistics. It 1260 contains the PRID of the linkage instance associating 1261 the selection criteria instance with the usage 1262 instance." 1264 ::= {rsvpPccBaseClasses 11} 1266 pccSessionStatsUsageEntry OBJECT-TYPE 1267 SYNTAX PccSessionStatsUsageEntry 1268 STATUS current 1269 DESCRIPTION 1270 "Defines the attributes the PEP is to monitor, 1271 record and report." 1272 PIB-INDEX {pccSessionStatsUsageId} 1274 ::= {pccSessionStatsUsageTable 1} 1276 PccSessionStatsUsageEntry ::= SEQUENCE { 1277 pccSessionStatsUsageId InstanceId, 1278 pccSessionStatsUsageLinkId ReferenceId, 1279 pccSessionStatsUsageStart ExtUTCTime, 1280 pccSessionStatsUsageEnd ExtUTCTime 1281 } 1283 pccSessionStatsUsageId OBJECT-TYPE 1284 SYNTAX InstanceId 1285 STATUS current 1286 DESCRIPTION 1287 "An arbitrary integer index that uniquely identifies an 1288 instance of the pccSessionStatsUsage class." 1290 ::= { pccSessionStatsUsageEntry 1 } 1292 pccSessionStatsUsageLinkId OBJECT-TYPE 1293 SYNTAX ReferenceId 1294 PIB-REFERENCES { frwkFeedbackLinkEntry } 1295 STATUS current 1296 DESCRIPTION 1297 "Points to the instance of the Linkage table in the 1298 Framework Feedback PIB, due to which this PRI was 1299 created." 1300 ::= { pccSessionStatsUsageEntry 2 } 1302 pccSessionStatsUsageStart OBJECT-TYPE 1303 SYNTAX ExtUTCTime 1304 STATUS current 1305 DESCRIPTION 1306 "The timestamp when the reservation was successfully 1307 allocated." 1309 ::= { pccSessionStatsUsageEntry 3} 1311 pccSessionStatsUsageEnd OBJECT-TYPE 1312 SYNTAX ExtUTCTime 1313 STATUS current 1314 DESCRIPTION 1315 "The timestamp when the reservation was ended. This 1316 could be due to reservation tear down, an error or 1317 time out condition" 1319 ::= {pccSessionStatsUsageEntry 4} 1321 -- The Policy Control Criteria Allocated Usage Table 1322 -- 1324 pccAllocatedUsageTable OBJECT-TYPE 1325 SYNTAX SEQUENCE OF PccAllocatedUsageEntry 1326 PIB-ACCESS report-only 1327 STATUS current 1328 DESCRIPTION 1329 "This class records the traffic specification 1330 allocated to a session. It contains the PRID of the 1331 linkage instance associating the selection criteria 1332 instance with the usage instance." 1334 ::= {rsvpPccBaseClasses 12} 1336 pccAllocatedUsageEntry OBJECT-TYPE 1337 SYNTAX PccAllocatedUsageEntry 1338 STATUS current 1339 DESCRIPTION 1340 "Defines the attributes the PEP is to monitor, record 1341 and report." 1342 PIB-INDEX {pccAllocatedUsageId} 1344 ::= { pccAllocatedUsageTable 1} 1346 PccAllocatedUsageEntry ::= SEQUENCE { 1347 pccAllocatedUsageId InstanceId, 1348 pccAllocatedUsageLinkId ReferenceId, 1349 pccAllocatedUsageIntsrvClass Integer32, 1350 pccAllocatedUsageBucketRate BitRate, 1351 pccAllocatedUsageBucketSize Unsigned32, 1352 pccAllocatedUsagePeakRate BurstSize, 1353 pccAllocatedUsageMinPolicedUnit MessageSize, 1354 pccAllocatedUsageMaxPacketSize MessageSize, 1355 pccAllocatedUsageLimitsRate BitRate, 1356 pccAllocatedUsageSlackTerm Unsigned32 1357 } 1359 pccAllocatedUsageId OBJECT-TYPE 1360 SYNTAX InstanceId 1361 STATUS current 1362 DESCRIPTION 1363 "An arbitrary integer index that uniquely identifies an 1364 instance of the PpcAllocatedUsage class." 1366 ::= { pccAllocatedUsageEntry 1 } 1368 pccAllocatedUsageLinkId OBJECT-TYPE 1369 SYNTAX ReferenceId 1370 PIB-REFERENCES { frwkFeedbackLinkEntry } 1371 STATUS current 1372 DESCRIPTION 1373 "Points to the instance of the Linkage table in the 1374 Framework Feedback PIB, due to which this PRI was 1375 created." 1376 ::= { pccAllocatedUsageEntry 2 } 1378 pccAllocatedUsageIntsrvClass OBJECT-TYPE 1379 SYNTAX Integer32 1380 STATUS current 1381 DESCRIPTION 1382 "The Intsrv Class associated with the session." 1383 ::= { pccAllocatedUsageEntry 3 } 1385 pccAllocatedUsageBucketRate OBJECT-TYPE 1386 SYNTAX BitRate 1387 STATUS current 1388 DESCRIPTION 1389 " 'r' bytes per second, the token bucket rate. " 1391 ::= { pccAllocatedUsageEntry 4 } 1393 pccAllocatedUsageBucketSize OBJECT-TYPE 1394 SYNTAX Unsigned32 1395 STATUS current 1396 DESCRIPTION 1397 " 'b' bucket depth in bytes, the token bucket size. " 1399 ::= { pccAllocatedUsageEntry 5 } 1401 pccAllocatedUsagePeakRate OBJECT-TYPE 1402 SYNTAX BurstSize 1403 STATUS current 1404 DESCRIPTION 1405 " 'p' peak traffic data rate in bytes. " 1407 ::= { pccAllocatedUsageEntry 6 } 1409 pccAllocatedUsageMinPolicedUnit OBJECT-TYPE 1410 SYNTAX MessageSize 1411 STATUS current 1412 DESCRIPTION 1413 " 'm' minimum policed unit - size in bytes of 1414 application data and all IP and greater level (UDP, 1415 RTP, TCP, etc.) headers. " 1417 ::= { pccAllocatedUsageEntry 7 } 1419 pccAllocatedUsageMaxPacketSize OBJECT-TYPE 1420 SYNTAX MessageSize 1421 STATUS current 1422 DESCRIPTION 1423 " 'M' maximum packet size - biggest packet that 1424 conforms to traffic specification. " 1425 ::= { pccAllocatedUsageEntry 8 } 1427 pccAllocatedUsageLimitsRate OBJECT-TYPE 1428 SYNTAX BitRate 1429 STATUS current 1430 DESCRIPTION 1431 " Limit Rate. Must be greater than or equal to rate for 1432 the flow " 1434 ::= { pccAllocatedUsageEntry 9 } 1436 pccAllocatedUsageSlackTerm OBJECT-TYPE 1437 SYNTAX Unsigned32 1438 STATUS current 1439 DESCRIPTION 1440 " 'S' - Slack Term. Defines in microseconds the 1441 difference between desired delay and the delay 1442 attained with the reservation level of R" 1444 ::= { pccAllocatedUsageEntry 10 } 1446 -- 1447 --Virtual Pool Usage Table 1448 -- 1450 pccPoolUsageTable OBJECT-TYPE 1451 SYNTAX SEQUENCE OF PccPoolUsageEntry 1452 PIB-ACCESS Install 1453 STATUS current 1454 DESCRIPTION 1455 "This table tracks and reports the current total 1456 of resources consumed by Intsrv flows for a 1457 specific virtual pool." 1459 ::= {rsvpPccBaseClasses 13} 1461 pccPoolUsageEntry OBJECT-TYPE 1462 SYNTAX PccPoolUsageEntry 1463 STATUS current 1464 DESCRIPTION 1465 "Defines the attributes for tracking the current 1466 total of resources used by Intsrv flows for a 1467 virtual pool." 1468 PIB-INDEX {pccPoolUsageId} 1470 ::= {pccPoolUsageTable 1} 1472 PccPoolUsageEntry ::= SEQUENCE { 1473 pccPoolUsageId InstanceId, 1474 pccPoolUsagePoolId Prid, 1475 pccPoolUsageAbsRateInUse Unsigned32, 1476 pccPoolUsageAbsRateInUseThreshold Unsigned32 1477 } 1479 pccPoolUsageId OBJECT-TYPE 1480 SYNTAX InstanceId 1481 STATUS current 1482 DESCRIPTION 1483 "This is the unique identifier of the 1484 pccPoolUsage Table entry." 1485 ::= { pccPoolUsageEntry 1} 1487 pccPoolUsagePoolId OBJECT-TYPE 1488 SYNTAX Prid 1489 STATUS current 1490 DESCRIPTION 1491 "This is the prid of the pccACVirPoolTable entry 1492 that is being tracked." 1493 ::= { pccPoolUsageEntry 2} 1495 pccPoolUsageAbsRateInUse OBJECT-TYPE 1496 SYNTAX Unsigned32 1497 STATUS current 1498 DESCRIPTION 1499 "This is the current total of resources used 1500 by Intsrv flows for the virtual pool identified 1501 by the pccPoolUsagePoolId." 1502 ::= { pccPoolUsageEntry 3} 1504 pccPoolUsageAbsRateInUseThreshold OBJECT-TYPE 1505 SYNTAX Unsigned32 1506 STATUS current 1507 DESCRIPTION 1508 " This value is associated with the 1509 pccPoolUsageAbsRateInUse and defines the feedback 1510 threshold for this usage that results in the 1511 instance being reported to the PDP. This value is 1512 only used if the linkage entry is set to threshold" 1513 ::= { pccPoolUsageEntry 4 } 1515 END 1517 5 Security Considerations 1518 "..The use of IPSEC between the PDP and the PEP, as described in 1519 [2748], provides the necessary protection against security threats. 1520 However, even if the network itself is secure, there is no control as 1521 to who on the secure network is allowed to "Install/Notify" 1522 (read/change/create/delete) the PRIs in this PIB. It is then a 1523 customer/user responsibility to ensure that the PEP/PDP giving access 1524 to an instance of this PIB, is properly configured to give access to 1525 the PRIs only to those principals (users) that have legitimate 1526 rights to indeed "Install" or "Notify" (change/create/ delete) them" 1527 [POLFRWK] 1529 6 Acknowledgements 1530 The authors would like to thank Russell Fenger of Intel for his 1531 contribution to this document. 1533 7 Authors Addresses 1535 Diana Rawlins 1536 901 International Parkway 1537 Richardson, TX 75081 1538 Diana.Rawlins@wcom.com 1540 Lei Yao 1541 22001 Loudoun County Parkway 1542 Ashburn, VA 20147 1543 Lei.yao@wcom.com 1545 Richard McClain 1546 901 International Parkway 1547 Richardson, TX 75081 1548 Richard.McClain@wcom.com 1550 Amol Kulkarni 1551 JF3-206 1552 2111 NE 25th Ave 1553 Hillsboro, Oregon 97124 1554 amol.kulkarni@intel.com 1556 8 References 1557 [2748] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., 1558 and A. Sastry, "The COPS (Common Open Policy Service) Protocol" 1559 RFC 2748, January 2000. 1561 [3084] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. 1562 Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for 1563 Policy Provisioning," RFC 3084, March 2001. 1565 [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning 1566 Information," draft-ietf-rap-sppi-02.txt, October 2000. 1568 [POLFRWK] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, 1569 A. Smith, F. Reichmeyer "Framework Policy Information Base", 1571 [FEEDBKFRPIB] D. Rawlins, A. Kulkarni, K. Chan, D. Dutt, " 1572 Framework of COPS-PR Policy Information Base for Accounting 1573 Usage", draft-ietf-rap-feedback-fr-pib-01.txt, November 2001 1575 [2749] Herzog, S., Boyle J., Cohen, R., Durham, D., Rajan, R., 1576 Sastry, A., "COPS usage for RSVP" RFC 2749, January 2000 1578 [2750] Herzog, S., "COPS Extensions for Policy Control" RFC 2750, 1579 January 2000. 1581 [2751] Herzog, S., "Signal Priority Preemption Policy Element" RFC 1582 2751, January 2000. 1584 [2752] Yadav, S., Yavatkar, R., Pabbati, R., Ford, P., Moore, T. 1585 Herzog, S. "Identity Representation for RSVP" RFC 2752, January 1586 2000. 1588 [2753] Yavatkar, R., Pendarakis, D., Guerin, R., "A Framework for 1589 Policy-based Admission Control" RFC 2753, January 2000. 1591 [2872] Bernet, Y., Pabbati, R., "Application and Sub Application 1592 Identity Policy Element for Use with RSVP" RFC 2872, June 2000. 1594 [2205] Braden, R., Zhang, L., Berson, S., Herzog, S., Jamin, S., 1595 "Resource ReSerVation Protocol (RSVP)" RFC2205, September 1997. 1597 [2210] Wroclawski, J., "The Use of RSVP with IETF Integrated 1598 Services", RFC2210, September 1997. 1600 [2211] Wroclawski, J., "Specification of the Controlled-Load 1601 Network Element Service", RFC2211, September 1997. 1603 [2212] Shenker, S., Partridge, C., Guerin, R., "Specification of 1604 Guaranteed Quality of Service", RFC2212, September 1997. 1606 [2215] Shenker, S., Wroclawski, J.," General Characterization 1607 Parameters for Integrated Service Network Elements", RFC2215, 1608 September 1997. 1610 [2998] Bernet, Y., et al, "Integrated Services over Diffserv 1611 Networks", RFC 2998, November 2000. 1613 [EdgeAdmCtl] D. Rawlins, L. Yao, D. McDysan, "Edge Based Admission 1614 Control with Class Based Resource Management", draft-rawlins-admctl- 1615 ds-mgt-01.txt, February 2002.