idnits 2.17.1 draft-ietf-rap-rsvppcc-pib-00.txt: -(60): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1104): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1113): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1244): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1493): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1508): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(1596): 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 63 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 367 has weird spacing: '... the feedba...' == Line 725 has weird spacing: '...applied to In...' == Line 1090 has weird spacing: '...be used by th...' == Line 1507 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 (November 14, 2001) is 8199 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 1543, but no explicit reference was found in the text == Unused Reference: 'SPPI' is defined on line 1547, but no explicit reference was found in the text == Unused Reference: '2750' is defined on line 1560, but no explicit reference was found in the text == Unused Reference: '2751' is defined on line 1563, but no explicit reference was found in the text == Unused Reference: '2872' is defined on line 1573, 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-00 -- 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: May 2002 Lei Yao 3 File: draft-ietf-rap-rsvppcc-pib-00.txt Richard McClain 4 WorldCom 5 Amol Kulkarni 6 Intel 8 RSVP Policy Control Criteria PIB 10 November 14, 2001 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.5 Integrated Services over Differentiated Services Policy Tables.7 64 3.5.1 Intsrv to Diffserv Interworking Function Table...............7 65 3.5.2 Admission Control virtual Pool Table.........................7 66 3.5.3 Edge Point Identification Table..............................7 67 3.5 Policy Control Criteria Usage Tables...........................7 68 3.5.1 Policy Control Criteria Allocated Table......................7 69 3.5.2 Policy Control Criteria Session Stats Table..................7 70 3.6 Example........................................................8 71 4 The RSVP Policy Control Criteria PIB Module......................8 72 5 Security Considerations.........................................30 73 6 Acknowledgements................................................30 74 7 Authors Addresses...............................................31 75 8 References......................................................31 77 1. Introduction 79 The RSVP Policy Control Criteria PIB defines the policy criteria used 80 to authorize an RSVP reservation request. The policy criteria defined 81 by this PIB are enforced by the RSVP enabled Policy Enforcement Point 82 (PEP). These are provisioned by the Policy Decision Point (PDP) 83 rather than outsourced to the PDP. 85 Policy control is an important processing component described in RSVP 86 [2205]. While admission control evaluates the resources available at 87 the RSVP enabled interface, it does not determine if the requested 88 reservation is allowed. Policy control determines whether the policy 89 is allowed (or authorized.) It may base the decision on multiple 90 factors including application identification, policy authentication 91 preemption rules and service level agreements. 93 Two basic models are defined for prescribing policy to a network 94 enforcement device using COPS [2748]. First, there is an outsourcing 95 mechanism for policy control where the network device requests a 96 policy decision from an external policy server[2749]. This mechanism 97 can be used in conjunction with a local decision policy scheme that 98 outsources information to the PDP for confirmation of the locally 99 made decision [2753]. There also exists a policy configuration 100 mechanism that does not require the network device to outsource all 101 policy decisions. The device is provisioned with decision policy 102 using Policy Information Bases (PIB) that define the policies to be 103 enforced by the PEP. [3084.] 105 Currently there is no PIB defining RSVP policy control criteria to be 106 conveyed by the provisioning model. Provisioned policy control 107 criteria are useful in topologies where large numbers of signaling 108 flows are transiting a set of well know boundary devices. The sheer 109 volume and nature of the application generating RSVP signals (such as 110 with VoIP) may make outsourcing policy impractical at some boundary 111 devices. The use of local policy control criteria is an attractive 112 alternative to going off-board to another policy device for all PATH 113 and RESV messages and their associated contexts (Incoming / 114 Allocation / Outgoing), which reduces the response time of policy 115 control, the amount of policy control traffic on the network, and 116 overall QoS setup time for the application. 118 Reliance on a network operator to manually provision the policy 119 criteria locally per device is not a scalable solution. It is labor- 120 intensive, time-consuming as well as error prone and it limits the 121 flexibility of policy control. The automated provisioning of RSVP 122 criteria by the PDP expands the uses of QoS reservation policy to 123 dynamic, high volume QoS sensitive applications. 125 2 General Concepts 127 2.1 Overview 128 This document defines a RSVP Policy Control Criteria PIB. The RSVP 129 Policy Control Criteria PIB provides the policy classes describing 130 the criteria for RSVP policy control to the PEP so it does not need 131 to outsource decisions for all RSVP signals. 133 Together with the PIB defined in this document, COPS-PR is used to 134 push RSVP related policy control criteria from a PDP to a PEP. Thus 135 the RSVP policy control criteria are installed on the PEP a priori of 136 the affected RSVP signals and enables making policy control decisions 137 for the RSVP messages locally at the PEP. 139 The use of provisioned policy criteria does not prohibit the 140 outsourcing of policy decisions. The outsourcing and provisioned 141 policy approaches may be used in combination with each other as 142 defined by the following three processing models: 143 - Make local decisions AND outsource each request to the PDP for 144 confirmation as described in [2753]. 145 - Make local decisions and outsource ONLY IF no relevant local 146 policy is found. 147 - Take local decisions only. Do not outsource. 149 Feedback must be provided to the PDP about the usage of policy at the 150 PEP. The PEP monitors, tracks and provides periodic accounting type 151 reports to the PDP. 153 2.2 Normal Operation 155 When a PEP is initialized, a COPS session connection is established 156 for SUBJECT_CATEGORY RSVP-PCC between the PEP and PDP. The PEP issues 157 the request for initial configuration describing its basic PIB policy 158 capabilities per [POLFRWK.] The policy classes supported by the PEP 159 are indicated with the PRCSupportTable instances. The PEP also 160 describes the policy model capability associated with that interface 161 using an instance of the RSVPPccCapTable. 163 The Policy Decision Point determines the appropriate policy 164 information to supply the PEP and responds with a decision install. 165 The PEP confirms the success or failure of the configuration decision 166 with a report. 168 The failover operation of the PEP and PDP is described in [3084.] 170 2.3 RSVP Policy Processing Models with local policy criteria 172 The policy control processing follows one of three possible models: 174 - The first model is the LDP model described in [2753]. The installed 175 policy criteria are used to make a Local Decision. If the local 176 policy approves the reservation request the RSVP message continues 177 its normal processing. The LDP then confirms the decision with the 178 PDP by issuing a request with the LPDP Decision Object. The PDP then 179 issues a final decision, which is enforced by the PEP. The 180 outsourcing of the request to the PDP is accomplished via the COPS- 181 RSVP connection [2753.] 183 - The second model is where the PEP performs policy control by 184 approving a reservation request based on installed policy criteria. 185 In the event that no policy exists for the reservation request, the 186 PEP then outsources the request to the PDP. The PDP then decides to 187 approve or deny the request [2749]. In other words, when a PEP 188 receives a RSVP message, it first queries Local RSVP policy control 189 criteria. If no policy exists for the request the PEP uses COPS-RSVP 190 to query the PDP for outsourcing policy decisions. Note that the PEP 191 may send periodic reports to the PDP informing it of factors that 192 affect decision-making at the PDP e.g. the resource usage etc. In the 193 case that a request is outsourced to a PDP, all pending allocation 194 usage reports should be sent prior to issuing the request. This helps 195 the PDP maintain an accurate picture of resource availability at the 196 PEP while making decisions. 198 - The third model is where the PEP relies entirely upon the 199 provisioned policy control criteria for its policy control decision- 200 making. If no policies are found for a policy request of a RSVP 201 session, the RSVP session should be rejected. No COPS-RSVP connection 202 between the PEP and PDP is required in this third model when the 203 policy control criteria is local and there is no outsourcing 204 operation. 206 2.4 Session Classification and Reservation Styles 208 The IP filters, frwkIPFilterTable, described in [POLFRWK] are used to 209 associate the authorization (or enforcement) policy with a RSVP 210 session. These filter instances provide the ability to identify the 211 flow 5-tuple: source address, source port, destination address, 212 destination port and protocol id. The RSVP Sender_Template Class, 213 FilterSpec Class and Session Class can be classified using the 214 frwkIPFilterTable. The 5-tuple filter instances may be defined using 215 a wildcard value for the attribute, which accommodates classification 216 policies for the RSVP Fixed Filter, Shared Explicit and Wildcard 217 reservation styles. The frwkIPFilterTable attribute, frwkIPFilterDSCP 218 attribute should contain a wildcard value and must be ignored with 219 regards to the authorization policy. 221 3 PIB Summary 223 The PIB defines the policy control criteria using several types of 224 Policy Rule Classes (PRC). These are the PCC capability policy, the 225 PCC mode policy, filter policy, authorization policies, Intsrv over 226 Diffserv policies, linkage policy and usage policy. The PCC 227 capability specifies the local policy models that the device 228 supports. The PCC mode defines the local policy model that the PDP is 229 directing the PEP to use. The filter policy identifies the flows that 230 have authorization policy. The authorization policy defines the 231 enforcement rules. The Intsrv over Diffserv policies define the 232 interworking rules. The linkage policy associates the filter policy 233 with an authorization policy. The usage policy provides feedback to 234 the PDP according to what the PEP has monitored and recorded via an 235 accounting type report. 237 3.1 Capabilities Table - policyControlCapsTable 239 This table provides a single instance describing the RSVP local 240 decision policy models or modes that the PEP is capable of 241 supporting. The three modes have been previously described in section 242 2.3. 244 3.2 Policy Mode Table � pccModeTable 245 This table contains a single instance that specifies the RSVP local 246 decision policy model that the PDP is directing the PEP to use. This 247 mode must be compatible with the capabilities indicated by the PEP. 249 3.3 PCC Linkage Table - pccLinkTable 251 This table defines the association between the filter policy and the 252 authorization policy. The PCC Linkage Class references the filter 253 PRID as well as the PRID of the authorization policy class. It links 254 the two instances. (The PRID is the Object Identifier constructed 255 with the PRC and the instance id as the last sub-identifier.) Note 256 that the same filter may have multiple authorization policies. For 257 example a filter may have a Traffic Specifier policy, a Rate 258 Specifier policy and Preemption policy that should be used as policy 259 criteria for determining if the flow is allowed. 261 There is future work needed to explore the optimization of the 262 association of filters with authorization policies. 264 3.4 Authorization Policy Tables 266 The Authorization tables contain the enforcement policy classes that 267 determine whether the RSVP reservation is allowed. These policy 268 classes describe the Integrated Services Controlled Load and 269 Guaranteed Services, [2210,2211,2212,2215], the identity 270 authorization user and authorization application policies [2752], and 271 the preemption policies [2751.] The policy classes included in this 272 group are: 274 3.4.1 Traffic Specifier (Tspec) Policies Table 276 Identifies the Integrated Service type and defines the transmission 277 rate of the traffic flow with that Integrated Service type. 279 3.4.2 RSPEC Limits Table 281 Defines the requested service rate from the network related with 282 Guaranteed Services. 284 3.4.3 Identification Authentication Data Policy Elements Table 285 Defines means to securely identify the owner or application making 286 the reservation request. 288 3.4.4 Priority Preemption Policy Elements Table 290 Defines the relative order of importance of the requested flow and 291 permits the preemption of lesser important flows to allow higher 292 priority flows admission. 294 3.5 Integrated Services over Differentiated Services Policy Tables 296 These tables describe the interworking rules for Integrated Services 297 over Diffserv Services. The interworking provisioning rules are based 298 on the model where Intsrv is in the control plane and Diffserv is in 299 the data plane as introduced in [2998] and then further discussed in 300 [EdgeAdmCtl] 302 3.5.1 Intsrv to Diffserv Interworking Function Table 304 This table defines the specific attributes used for the interworking 305 between the RSVP process in the control plane and the Differentiated 306 Services in the data plane. This is used by the Packet Classification 307 and Packet Schedule process for classifying and marking the traffic 308 flow with the appropriate Differentiated Service Code Point and 309 policing the flow. . 311 3.5.2 Admission Control Virtual Pool Table 313 This table defines the virtual pool that is mapped to the 314 Differentiated Services resource allocated to Intsrv traffic. It 315 specifies the Intsrv Service Type, maximum capacity available to the 316 Intsrv admission control process, reservation acceptance status and 317 the associated boundary router logical interface if applicable. 319 3.5.3 Edge Point Identification Table 321 This table is used to identify the receiver domain. The entries 322 define the addresses that are receivers with respect to the router. 323 Admission control performs the upstream resource check when the RSVP 324 Session Object matches one of these address ranges. 326 3.5 Policy Control Criteria Usage Tables 328 3.5.1 Policy Control Criteria Allocated Table 330 This usage table records the traffic specifications allocated to a 331 successful session and provides feedback to the PDP via the 332 accounting type report. 334 3.5.2 Policy Control Criteria Session Stats Table 336 The usage table records the start time and end time of a session. The 337 start time is based on the successful allocation of the resources for 338 a reservation and the end time is associated with the termination of 339 the session and its policy. 341 3.5.3 Virtual Pool Usage Table 343 The virtual pool usage table tracks the current total of resources 344 consumed by the Intsrv flows for a given virtual pool. 346 3.6 Example 348 Authorization policies are defined in terms of TRAFFIC SPECIFIER and 349 RSPEC characteristics as well as Integrated Services type i.e. 350 Controlled Load or Guaranteed Services. Additional criteria such as 351 Policy Authentication and Priority Preemption can also be specified. 353 An example policy control criteria scenario is as follows. The 354 SenderTemplate and Filterspec are compared against the policy control 355 criteria filters by the PEP. The filter is associated with a set of 356 authorization rules with the linkage policies. For example, policy 357 control criteria could establish authorization for the Gold and 358 Silver VoIP services. The Gold VoIP could be defined as allowing a 359 guaranteed service request, within a traffic specifier and rspec 360 limit, with a high preemption priority and high preemption defending 361 priority. A Silver VoIP could be defined as granting a controlled 362 load service request, within a traffic specifier and rspec limit, 363 with a moderate preemption priority and low preemption defending 364 priority. The PEP records the traffic specifications requested by the 365 session and the session statistics. It reports these back to the PDP 366 on a periodic basis determined by the accounting interval defined in 367 the feedback linkage policy [FEEDBKFRPIB]. 369 4 The RSVP Policy Control Criteria PIB Module 371 RSVP-PCC-PIB PIB-DEFINITIONS ::= BEGIN 373 IMPORTS 374 Unsigned32, Unsigned64, Integer32, MODULE-IDENTITY 375 FROM COPS-PR-SPPI 376 InstanceID, ReferenceID, Prid, TagID 377 FROM COPS-PR-SPPI-TC 378 InetAddress, InetAddressType 379 FROM SNMPv2-TC 380 Role, RoleCombination 381 FROM POLICY-DEVICE-AUX-MIB 382 OBJECT-GROUP 383 FROM SNMPv2-CONF 384 MessageSize, BitRate, BurstSize 385 FROM INTEGRATED-SERVICES-MIB 386 FrwkIpFilterTable 387 FROM FRAMEWORK-PIB; 389 RsvpPccPib MODULE-IDENTITY SUBJECT-CATEGORY { RSVP-PCC(tbd) } 390 LAST-UPDATED "200011131600Z" 391 ORGANIZATION "IETF-RAP-WG" 392 CONTACT-INFO " 393 Diana Rawlins 394 901 International Parkway 395 Richardson, TX 75081 396 Email: Diana.Rawlins@wcom.com 397 Phone +1 972 729 1044 399 Lei Yao 400 22001 Loudoun County Parkway 401 Ashburn, VA 20147 402 Email: Lei.yao@wcom.com 403 Phone: +1 703 886 1830 405 Richard McClain 406 901 International Parkway 407 Richardson, TX 75081 408 Email: Richard.McClain@wcom.com 409 Phone: +1 972 729 1094 411 Amol Kulkarni 412 JF3-206 413 2111 NE 25th Ave 414 Hillsboro, Oregon 97124 415 Email: amol.kulkarni@intel.com 416 Phone: +1 503 712 1168 " 418 DESCRIPTION 419 "A PIB module containing the policy control 420 classes that are required for support of 421 pushing policy control from the PDP to PEPs." 423 ::= { tbd } 425 -- 426 -- The root OID for PRCs in the RSVP Policy Control Criteria PIB 427 -- 429 rsvpPccBaseClasses 430 OBJECT IDENTIFIER ::= { RsvpPccPib 1 } 432 -- 433 -- Textual Conventions 434 -- 436 -- 437 -- Policy Control Capabilities Table 438 -- 440 policyControlCapsTable OBJECT-TYPE 441 SYNTAX SEQUENCE OF PolicyControlCapsEntry 442 PIB-ACCESS notify, 3 443 STATUS current 444 DESCRIPTION 445 " The policy control capability in terms of the policy 446 control mode supported by the device." 448 ::= { rsvpPccBaseClasses 1 } 450 policyControlCapsEntry OBJECT-TYPE 451 SYNTAX PolicyControlCapsEntry 452 STATUS current 453 DESCRIPTION 454 " The instance defining the policy control mode." 456 PIB-INDEX { policyControlCapsPccId } 458 ::= { policyControlCapsTable 1 } 460 PolicyControlCapsEntry ::= SEQUENCE { 461 policyControlCapsPccId InstanceId, 462 policyControlCapsMode BITS 463 } 465 policyControlCapsPccId OBJECT-TYPE 466 SYNTAX InstanceId 467 STATUS current 468 DESCRIPTION 469 "An arbitrary integer index that uniquely identifies 470 an instance of the PolicyControlCaps class." 472 ::= { policyControlCapsEntry 1 } 474 policyControlCapsMode OBJECT-TYPE 475 SYNTAX BITS { 476 CONFIRM_ALL(0), 477 LOCAL_IF_AVAILABLE(1), 478 LOCAL_ONLY(2) 479 } 480 STATUS current 481 DESCRIPTION 482 "The policy control criteria mode of the device. The 483 device may support any combination of modes. 484 The valid bit values are: 485 (0)Local Decision Policy which makes decision and 486 then outsources confirmation to the PDP 487 (1)local control and if no policy control criteria 488 is available locally, then outsource decision to PDP 489 (2)local policy control only." 491 ::= { policyControlCapsEntry 2} 493 -- 494 -- Policy Control Criteria Mode Table 495 -- 497 pccModeTable OBJECT-TYPE 499 SYNTAX SEQUENCE OF PccModeEntry 500 PIB-ACCESS notify,3 501 STATUS current 502 DESCRIPTION 503 " The policy control mode designated by the PDP." 505 ::= { rsvpPccBaseClasses 2 } 507 pccModeEntry OBJECT-TYPE 508 SYNTAX PccModeEntry 509 STATUS current 510 DESCRIPTION 511 " The instance defining the PDP designated mode of 512 policy control." 514 PIB-INDEX { pccModeId } 516 ::= { pccModeTable 1 } 518 PccModeEntry ::= SEQUENCE { 519 pccModeId InstanceId, 520 pccModeMode INTEGER 521 } 523 pccModeId OBJECT-TYPE 524 SYNTAX InstanceId 525 STATUS current 526 DESCRIPTION 527 "An arbitrary integer index that uniquely identifies 528 an instance of the pccModeTable class." 530 ::= { pccModeEntry 1 } 532 pccModeMode OBJECT-TYPE 533 SYNTAX INTEGER { 534 CONFIRM_ALL(1), 535 LOCAL_IF_AVAILABLE(2), 536 LOCAL_ONLY(3) 537 } 538 STATUS current 539 DESCRIPTION 540 "The policy criteria control mode to be used by the 541 device. 542 The valid enumeration values are: 543 (1)Local Decision Policy which makes decision and 544 then outsources confirmation to the PDP 545 (2)local control and if no policy control criteria 546 is available locally, then outsource decision to PDP 547 (3)local policy control only." 549 ::= { pccModeEntry 2} 551 -- 552 -- Policy Control Criteria Linkage Table 553 -- 555 pccLinkTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF PccLinkEntry 557 PIB-ACCESS install-notify, 4 558 STATUS current 559 DESCRIPTION 560 " This table defines the association between 561 the filter, frwkIpFilterTable instance and 562 the authorization policy instance" 564 ::= { rsvpPccBaseClasses 3 } 566 pccLinkEntry OBJECT-TYPE 567 SYNTAX PccLinkEntry 568 STATUS current 569 DESCRIPTION 570 " An entry links the filter and the authorization 571 policy." 573 PIB-INDEX { pccLinkPccId } 574 UNIQUENESS { 575 pccLinkFilterRefId, 576 pccLinkPolicyPrid } 578 ::= { pccLinkTable 1 } 580 PccLinkEntry::= SEQUENCE { 581 pccLinkPccId InstanceId, 582 pccLinkFilterRefId ReferenceId, 583 pccLinkPolicyPrid Prid 584 } 586 pccLinkPccId OBJECT-TYPE 587 SYNTAX InstanceId 588 STATUS current 589 DESCRIPTION 590 " An arbitrary integer index that uniquely 591 identifies an instance of the PccLink class. " 593 ::= { pccLinkEntry 1 } 595 pccLinkFilterRefId OBJECT-TYPE 596 SYNTAX ReferenceId 597 STATUS current 598 DESCRIPTION 599 " References an instance of FrwkIPFilterTable. " 600 ::= { pccLinkEntry 2 } 602 pccLinkPolicy OBJECT-TYPE 603 SYNTAX Prid 604 STATUS current 605 DESCRIPTION 606 " Specifies the specific PRID of the PRC and instance of 607 authorization policy associated with this filter." 609 ::= { pccLinkEntry 3 } 611 -- 612 -- Traffic Specifier Policies Table 613 -- 615 trafficSpecifierPolicyTable OBJECT-TYPE 616 SYNTAX SEQUENCE OF TrafficSpecifierPolicyEntry 617 PIB-ACCESS install-notify, 7 618 STATUS current 619 DESCRIPTION 620 "This table defines the Traffic specifier policy control 621 characteristics that can be used to determine 622 SENDER_TSPEC, Controlled-Load or Guaranteed Services 623 policies." 625 ::= { rsvpPccBaseClasses 4 } 627 trafficSpecifierPolicyEntry OBJECT-TYPE 628 SYNTAX TrafficSpecifierPolicyEntry 629 STATUS current 630 DESCRIPTION 631 " An entry describes a specific limits for a T-SPEC 632 policy. " 634 PIB-INDEX { trafficSpecifierPolicyId } 635 UNIQUENESS {trafficSpecifierPolicyIntService, 636 trafficSpecifierPolicyBucketRate, 637 trafficSpecifierPolicyBucketSize, 638 trafficSpecifierPolicyPeakRate, 639 trafficSpecifierPolicyMinPolicedUnit, 640 trafficSpecifierPolicyMaxPacketSize } 642 ::= { trafficSpecifierPoliciesTable 1 } 644 TrafficSpecifierPolicyEntry ::= SEQUENCE { 645 trafficSpecifierPolicyId InstanceId, 646 trafficSpecifierPolicyIntService Integer32, 647 trafficSpecifierPolicyBucketRate BitRate, 648 trafficSpecifierPolicyBucketSize Unsigned32, 649 trafficSpecifierPolicyPeakRate BurstRate, 650 trafficSpecifierPolicyMinPolicedUnit MessageSize, 651 trafficSpecifierPolicyMaxPacketSize MessageSize 653 } 655 trafficSpecifierPolicyId OBJECT-TYPE 656 SYNTAX InstanceId 657 STATUS current 658 DESCRIPTION 659 "An arbitrary integer index that uniquely identifies an 660 instance of the TrafficSpecifierPolicy class." 662 ::= { trafficSpecifierPolicyEntry 1 } 664 trafficSpecifierPolicyIntService OBJECT-TYPE 665 SYNTAX Integer32 666 STATUS current 667 DESCRIPTION 668 " The traffic specifier policy is applied 669 to the flow of this Integrated Service type.� 670 ::= { pccDiffservMarkerEntry 2 } 672 trafficSpecifierPolicyBucketRate OBJECT-TYPE 673 SYNTAX BitRate 674 STATUS current 675 DESCRIPTION 676 " 'r' bytes per second, the token bucket rate. " 678 ::= { trafficSpecifierPolicyEntry 3 } 680 trafficSpecifierPolicyBucketSize OBJECT-TYPE 681 SYNTAX Unsigned32 682 STATUS current 683 DESCRIPTION 684 " 'b' bucket depth in bytes, the token bucket size. " 686 ::= { trafficSpecifierPolicyEntry 4 } 688 trafficSpecifierPolicyPeakRate OBJECT-TYPE 689 SYNTAX BurstSize 690 STATUS current 691 DESCRIPTION 692 " 'p' peak traffic data rate in bytes. " 694 ::= { trafficSpecifierPolicyEntry 5 } 696 trafficSpecifierPolicyMinPolicedUnit OBJECT-TYPE 697 SYNTAX MessageSize 698 STATUS current 699 DESCRIPTION 700 " 'm' minimum policed unit: size in bytes 701 of application data and all IP and greater 702 level (UDP, RTP, TCP, etc.) headers. " 704 ::= { trafficSpecifierPolicyEntry 6 } 706 trafficSpecifierPolicyMaxPacketSize OBJECT-TYPE 707 SYNTAX MessageSize 708 STATUS current 709 DESCRIPTION 710 " 'M' maximum packet size: biggest packet 711 that conforms to traffic specification. " 713 ::= { trafficSpecifierPolicyEntry 7 } 715 -- 716 -- RSPEC Limits Table 717 -- 719 rspecLimitsTable OBJECT-TYPE 720 SYNTAX SEQUENCE OF RspecLimitsEntry 721 PIB-ACCESS install-notify, 4 722 STATUS current 723 DESCRIPTION 724 "This table defines the RSPEC policy control 725 characteristics that are applied to Integrated 726 Services Guaranteed Service." 728 ::= { rsvpPccBaseClasses 5 } 730 rspecLimitsEntry OBJECT-TYPE 731 SYNTAX RspecLimitsEntry 732 STATUS current 733 DESCRIPTION 734 " An entry that defines specific Rate and Slack 735 limits for a Guaranteed Service resource request " 737 EXTENDS { trafficSpecifierPolicyTable } 738 UNIQUENESS { rspecLimitRate, 739 rspecLimitsSlackTerm } 741 ::= { rspecLimitsTable 1 } 743 RspecLimitsEntry ::= SEQUENCE { 744 RspecLimitsId InstanceId, 745 rspecLimitsRate BitRate, 746 rspecLimitsSlackTerm Unsigned32 747 } 749 rspecLimitsId OBJECT-TYPE 750 SYNTAX InstanceId 751 STATUS current 752 DESCRIPTION 753 "An arbitrary integer index that uniquely identifies an 754 instance of the rspecLimits class." 756 ::= { rspecLimitsEntry 1 } 758 rspecLimitsRate OBJECT-TYPE 759 SYNTAX BitRate 760 STATUS current 761 DESCRIPTION 762 " 'R' - Rate. Must be greater than or equal to 'r', rate 763 for the flow " 765 ::= { rspecLimitsEntry 2 } 767 rspecLimitsSlackTerm OBJECT-TYPE 768 SYNTAX Unsigned32 769 STATUS current 770 DESCRIPTION 771 " 'S' - Slack Term. Defines in microseconds the 772 difference between desired delay and the delay 773 attained with the reservation level of R" 775 ::= { rspecLimitsEntry 3 } 777 -- 778 -- Authentication Data Policy Element Table 779 -- 781 authDataPolicyElementTable OBJECT-TYPE 782 SYNTAX SEQUENCE OF AuthDataPolicyElementEntry 783 PIB-ACCESS install-notify, 6 784 STATUS current 785 DESCRIPTION 786 "This table specifies policy control to identify and 787 authenticate the owner making resource request." 789 ::= { rsvpPccBaseClasses 6 } 791 authDataPolicyElementEntry OBJECT-TYPE 792 SYNTAX AuthDataPolicyElementEntry 793 STATUS current 794 DESCRIPTION 795 " An entry defines the specific authentication 796 identify used to grant permission for the 797 reservation request." 799 PIB-INDEX { authDataPolicyElementPccId } 800 UNIQUENESS { 801 authDataPolicyElementPolicySetId, 802 authDataPolicyElementPolicyIdentity, 803 authDataPolicyElementPolicyAuthAttrType, 804 authDataPolicyElementPolicyAuthAttrSubType 805 } 807 ::= { authDataPolicyElementTable 1 } 809 AuthDataPolicyElementEntry::= SEQUENCE { 810 AuthDataPolicyElementPccId InstanceID, 811 AuthDataPolicyElementPolicySetId TagID, 812 authDataPolicyElementPolicyIdentity INTEGER, 813 authDataPolicyElementPolicyAuthAttrType INTEGER, 814 authDataPolicyElementPolicyAuthAttrSubType INTEGER 815 } 817 authDataPolicyElementPccId OBJECT-TYPE 818 SYNTAX InstanceID 819 STATUS current 820 DESCRIPTION 821 "An arbitrary integer index that uniquely identifies 822 an instance of the AuthDataPolicyElement class." 824 ::= { authDataPolicyElementEntry 1 } 826 authDataPolicyElementPolicySetId OBJECT-TYPE 827 SYNTAX TagID 828 STATUS current 829 DESCRIPTION 830 " This associates a set of authentication attributes." 832 ::= { authDataPolicyElementEntry 2 } 834 authDataPolicyElementPolicyIdentity OBJECT-TYPE 835 SYNTAX INTEGER{ 836 AUTH_USER(1), 837 AUTH_APP(2) 838 } 839 STATUS current 840 DESCRIPTION 841 " Identifies the Policy Set Element via enumeration 842 values: 843 (2) AUTH_USER 844 (3) AUTH_APP " 846 ::= { authDataPolicyElementEntry 3 } 848 authDataPolicyElementPolicyAuthAttrType OBJECT-TYPE 849 SYNTAX INTEGER { 850 POLICY_LOCATOR(1), 851 CREDENTIAL(2), 852 DIGITAL_SIGNATURE(3), 853 POLICY_ERROR_object(4) 854 } 855 STATUS current 856 DESCRIPTION 857 " Enumeration values: 858 (1) POLICY_LOCATOR (valid for both AUTH_USER and 859 AUTH_APP) 860 (2) CREDENTIAL (valid for both AUTH_USER and 861 AUTH_APP) 862 (3) DIGITAL_SIGNATURE 863 (4) POLICY_ERROR_OBJECT " 865 ::= { authDataPolicyElementEntry 4 } 867 authDataPolicyElementPolicyAuthAttrSubType OBJECT-TYPE 868 SYNTAX INTEGER { 869 NO_TYPE(0), 870 ASCII_DN(1), 871 UNICODE_DN(2), 872 ASCII_DN_ENCRYPT(3), 873 UNICODE_DN_ENCRYPT(4), 874 ASCII_ID(5), 875 UNICODE_ID(6), 876 KERBEROS_TKT(7), 877 X509_CERT(8), 878 PGP_CERT(9), 879 NO_MORE_INFO(10), 880 UNSUPPORTED_CRED_TYPE(11), 881 INSUFFICIENT_PRIVS(12), 882 EXPIRED_CREDENTIAL(13), 883 IDENTITY_CHANGED(14) 884 } 885 STATUS current 886 DESCRIPTION 887 " For POLICY_LOCATOR valid enumeration values are: 888 (1) ASCII_DN (valid for both AUTH_USER and 889 AUTH_APP) 890 (2) UNICODE_DN (valid for both AUTH_USER and 891 AUTH_APP) 892 (3) ASCII_DN_ENCRYPT 893 (4) UNICODE_DN_ENCRYPT 895 For CREDENTIAL valid enumeration values are: 896 (5) ASCII_ID (valid for both AUTH_USER and 897 AUTH_APP) 899 (6) UNICODE_ID (valid for both AUTH_USER and 900 AUTH_APP) 901 (7) KERBEROS_TKT 902 (8) X509_V3_CERT 903 (9) PGP_CERT 905 For DIGITAL_SIGNATURE: 906 Sub-Type set to 0 908 For POLICY_ERROR_OBJECT valid enumeration values are: 909 (10) ERROR_NO_MORE_INFO 910 (11) UNSUPPORTED_CREDENTIAL_TYPE 911 (12) INSUFFICIENT_PRIVILEGES 912 (13) EXPIRED_CREDENTIAL 913 (14) IDENTITY_CHANGED " 915 ::= { authDataPolicyElementEntry 5 } 917 -- 918 -- Priority Preemption Policy Element Table 919 -- 921 priorityPreemptionPolicyElementTable OBJECT-TYPE 922 SYNTAX SEQUENCE OF PriorityPreemptionPolicyElementEntry 923 PIB-ACCESS install-notify,5 924 STATUS current 925 DESCRIPTION 926 "This table defines policy control for priority 927 preemption." 929 ::= { rsvpPccBaseClasses 7 } 931 priorityPreemptionPolicyElementEntry OBJECT-TYPE 932 SYNTAX PriorityPreemptionPolicyElementEntry 933 STATUS current 934 DESCRIPTION 935 " An entry defines the specific preemption priority to 936 admit the flow and the defending priority. " 938 PIB-INDEX { priorityPreemptionPolicyElementPccId } 939 UNIQUENESS { 940 priorityPreemptionPolicyElementMergeStrategy, 941 priorityPreemptionPolicyElementPreemptionPriority, 942 priorityPreemptionPolicyElementDefendingPriority 943 } 945 ::= { priorityPreemptionPolicyElementTable 1 } 947 PriorityPreemptionPolicyElementEntry ::= SEQUENCE { 948 priorityPreemptionPolicyElementPccId InstanceId, 949 priorityPreemptionPolicyElementMergeStrategy INTEGER, 950 priorityPreemptionPolicyElementPreemptionPriority INTEGER, 951 priorityPreemptionPolicyElementDefendingPriority INTEGER 952 } 954 priorityPreemptionPolicyElementPccId OBJECT-TYPE 955 SYNTAX InstanceId 956 STATUS current 957 DESCRIPTION 958 "An arbitrary integer index that uniquely identifies 959 an instance of the PriorityPreemptionPolicyElement 960 class." 962 ::= { priorityPreemptionPolicyElementEntry 1 } 964 priorityPreemptionPolicyElementMergeStrategy OBJECT-TYPE 965 SYNTAX INTEGER { 966 HIGHEST_QOS(1), 967 HIGHEST_PRIORITY(2), 968 ERROR_ON_MERGE(3) 969 } 970 STATUS current 971 DESCRIPTION 972 " Defines the merging strategy for the flow. The 973 Enum values are: 974 (1) take priority of highest QoS 975 (2) take highest priority 976 (3) force an error on heterogeneous merge" 978 ::= { priorityPreemptionPolicyElementEntry 2 } 980 priorityPreemptionPolicyElementPreemptionPriority OBJECT-TYPE 981 SYNTAX INTEGER 982 STATUS current 983 DESCRIPTION 984 " Defines the value of the new reservation that is 985 compared against the defending priorities of existing 986 flows. A higher value represents a higher priority." 988 ::= { priorityPreemptionPolicyElementEntry 3 } 990 priorityPreemptionPolicyElementDefendingPriority OBJECT-TYPE 991 SYNTAX INTEGER 992 STATUS current 993 DESCRIPTION 994 " The value defined for an existing flow to defend its 995 priority against a new reservation seeking admission. 996 The higher value represents higher priority." 998 ::= { priorityPreemptionPolicyElementEntry 4 } 1000 -- 1001 --Intsrv to Diffserv Interworking Function Table 1002 -- 1004 pccIwfTable OBJECT TYPE 1005 SYNTAX SEQUENCE OF PccIwfEntry 1006 PIB-ACCESS Install 1007 STATUS current 1008 DESCRIPTION 1009 �This table defines the attributes used for the 1010 interworking between the RSVP process in the 1011 control plane and Differentiated Services in the 1012 data plane.� 1014 ::= {rsvpPccBaseClasses 8} 1016 pccIwfEntry OBJECT TYPE 1017 SYNTAX PccIwfEntry 1018 STATUS current 1019 DESCRIPTION 1020 �Defines the attributes for Intsrv and Diffserv 1021 interworking.� 1022 PIB-INDEX {pccIwfId} 1024 ::= {pccIwfTable 1} 1026 PccIwfEntry ::= SEQUENCE { 1027 pccIwfId InstanceID, 1028 pccIwfIntSrvClass Integer 32, 1029 pccIwfDSCP Integer 32, 1030 pccIwfOutOfProfile Integer 32, 1031 pccIwfRemarkvalue Integer 32, 1032 pccIwfScheduler Integer 32 1033 } 1035 pccIwfId OBJECT-TYPE 1036 SYNTAX InstanceId 1037 STATUS current 1038 DESCRIPTION 1039 �This is the unique identifier of the iwfTable 1040 entry.� 1041 ::= { pccIwfEntry 1} 1043 pccIwfIntSrvClass OBJECT-TYPE 1044 SYNTAX Integer 32 1045 STATUS current 1046 DESCRIPTION 1047 �The value of the Intsrv Class associated with 1048 the attributes of this specific interworking function 1049 entry. It must have a corresponding bit set in 1050 pccACPoolISClass.� 1051 ::= { pccIwfEntry 2} 1053 pccIwfDSCP OBJECT-TYPE 1054 SYNTAX Integer 32 1055 STATUS current 1056 DESCRIPTION 1057 �The Value of the DSCP to assign the data stream 1058 for the session with the IntSrv class type 1059 matching the value of the pccIwfIntSrvClass. 1060 Value range is 0 � 63.� 1061 ::= { pccIwfEntry 3} 1063 pccIwfOutOfProfile 1064 SYNTAX Integer 32 1065 STATUS current 1066 DESCRIPTION 1067 �This indicates the behavior when the data stream 1068 is out of profile. This value overrides any other 1069 configured profile such as that defined in the 1070 MeterTableEntry. The value of 0 indicates that 1071 this attribute is ignored for this entry. A value 1072 of 1 indications the out of profile packet is 1073 dropped. A value of 2 indicates the out of profile 1074 packet DSCP is remarked with the value 1075 pccIwfRemarkValue.� 1076 ::= {pccIwfEntry 4} 1077 pccIwfRemark 1078 SYNTAX Integer 32 1079 STATUS current 1080 DESCRIPTION 1081 �This is the value of the DSCP to remark an out of 1082 profile packet. This value is only used if the 1083 pccIwfOutOfProfile has a value of 2.� 1084 ::= {pccIwfEntry 5} 1085 pccIwfScheduler 1086 SYNTAX Integer 32 1087 STATUS current 1088 DESCRIPTION 1089 �This is the value that identifies the scheduler 1090 to be used by the data streams of sessions with an 1091 IntSrv class matching the value of the attribute 1092 pccIwfIntSrClass.� 1093 ::= {pccIwfEntry 5} 1095 -- 1096 --Admission Control Virtual Pool Table 1097 -- 1099 pccACVirPoolTable OBJECT TYPE 1100 SYNTAX SEQUENCE OF PccACVirPoolEntry 1101 PIB-ACCESS Install 1102 STATUS current 1103 DESCRIPTION 1104 �This table defines the virtual pool used by the RSVP 1105 process during admission contro. � 1107 ::= {rsvpPccBaseClasses 9} 1109 pccACVirPoolEntry OBJECT TYPE 1110 SYNTAX PccACVirPoolEntry 1111 STATUS current 1112 DESCRIPTION 1113 �Defines the attributes for the Intsrv virtual pool.� 1114 PIB-INDEX {pccACVirPoolId} 1116 ::= {pccACVirPoolTable 1} 1118 PccACVirPoolEntry ::= SEQUENCE { 1119 pccACVirPoolId InstanceID, 1120 pccACVirPoolInterface SNMP string, 1121 pccACVirPoolDirection Integer32, 1122 pccACVirPoolIntSrvClass BITS, 1123 pccACVirPoolMaxAbsRate Unsigned32, 1124 pccACVirPoolAcceptResv Integer32 1125 } 1127 pccACVirPoolId OBJECT-TYPE 1128 SYNTAX InstanceId 1129 STATUS current 1130 DESCRIPTION 1131 �This is the unique identifier of the pccACVirPool 1132 entry.� 1133 ::= { pccACVirPoolEntry 1} 1135 pccACVirPoolInterface OBJECT-TYPE 1136 SYNTAX SNMP string 1137 STATUS current 1138 DESCRIPTION 1139 �The SNMP string identifies the logical interface 1140 associated with the Admission Control Virtual 1141 Pool entry.� 1142 ::= { pccACVirPoolEntry 2} 1144 pccACVirPoolDirection OBJECT-TYPE 1145 SYNTAX Integer32 1146 STATUS current 1147 DESCRIPTION 1148 �This attribute indicates the relationship of the 1149 traffic stream to the interface. The traffic 1150 stream is either inbound (1) or outbound (2). An 1151 upstream virtual pool has an inbound Direction 1152 and a downstream virtual pool has a Direction of 1153 outbound.� 1154 ::= { pccACVirPoolEntry 3} 1156 pccACVirPoolIntSrvClass OBJECT-TYPE 1157 SYNTAX BITS 1158 STATUS current 1159 DESCRIPTION 1160 �The bit string indicates the IntSrv class or 1161 classes that have resources allocated from this 1162 virtual pool by admission control. 1163 Value range is 0 � 63.� 1164 ::= { pccACVirPoolEntry 4} 1166 pccACVirPoolMaxAbsRate 1167 SYNTAX Unsigned32 1168 STATUS current 1169 DESCRIPTION 1170 �This is the maximum absolute rate in kilobits 1171 that this pool may allocate to the IntSrv 1172 sessions defined by the 1173 pccACVirtPoolIntSrvClass.� 1174 ::= {pccACVirPoolEntry 5} 1176 pccACVirPoolAcceptResv 1177 SYNTAX Integer 32 1178 STATUS current 1179 DESCRIPTION 1180 �This value indicates whether the RSVP admission 1181 control is to accept RSVP RESV request for the 1182 IntSrv flows belonging to the IntSrv classes 1183 defined by pccACVirPoolIntSrvClass.� 1184 ::= {pccACVirPoolEntry 6} 1186 -- 1187 --Edge Point Identification Table 1188 -- 1190 pccEdgeTable OBJECT TYPE 1191 SYNTAX SEQUENCE OF PccEdgeEntry 1192 PIB-ACCESS Install 1193 STATUS current 1194 DESCRIPTION 1195 �This table defines the attributes used to identify 1196 the receiver domain. Admission control performs the 1197 upstream resource check when the RSVP Session Object 1198 matches one of the entries in this table.� 1200 ::= {rsvpPccBaseClasses 10} 1202 pccEdgeEntry OBJECT TYPE 1203 SYNTAX PccEdgeEntry 1204 STATUS current 1205 DESCRIPTION 1206 �Defines the attributes for identifying the 1207 receiver domain edge that invokes upstream 1208 Admission control in addition to downstream 1209 Admission control.� 1210 PIB-INDEX {pccEdgeId} 1212 ::= {pccEdgeTable 1} 1214 PccEdgeEntry ::= SEQUENCE { 1215 pccEdgeId InstanceID, 1216 pccAddrType INET Address Type, 1217 pccEdgeAddr INET Address, 1218 pccEdgeMask Unsigned 32, 1219 } 1221 pccEdgeId OBJECT-TYPE 1222 SYNTAX InstanceId 1223 STATUS current 1224 DESCRIPTION 1225 �This is the unique identifier of the pccEdgeTable 1226 entry.� 1227 ::= { pccEdgeEntry 1} 1229 pccEdgeAddrType OBJECT-TYPE 1230 SYNTAX INET Address 1231 STATUS current 1232 DESCRIPTION 1233 �This is the enumerated value specifying the type 1234 of address (IPv4 or Ipv6) as defined in RFC 2851.� 1235 ::= { pccEdgeEntry 2} 1237 pccEdgeAddr OBJECT-TYPE 1238 SYNTAX INET Address 1239 STATUS current 1240 DESCRIPTION 1241 �When the value of this address matches the RSVP 1242 Session Object Destination Address, it indicates 1243 a that the session receiver is downstream and that 1244 the upstream admission control should be performed.� 1245 ::= { pccEdgeEntry 3} 1247 pccEdgeAddrMask OBJECT-TYPE 1248 SYNTAX unsigned 32 1249 STATUS current 1250 DESCRIPTION 1251 �The length of the mask for matching th eaddress.� 1252 ::= { pccEdgeEntry 4} 1254 -- 1255 -- The Policy Control Criteria Session Statistics usage 1256 -- 1258 pccSessionStatsUsageTable OBJECT-TYPE 1259 SYNTAX SEQUENCE OF PccSessionStatsUsageEntry 1260 PIB-ACCESS report 1261 STATUS current 1262 DESCRIPTION 1263 "This class defines the session statistics. It contains 1264 the PRID of the linkage instance associating the 1265 selection criteria instance with the usage instance." 1267 ::= {rsvpPccBaseClasses 11} 1269 pccSessionStatsUsageEntry OBJECT-TYPE 1270 SYNTAX PccSessionStatsUsageEntry 1271 STATUS current 1272 DESCRIPTION 1273 "Defines the attributes the PEP is to monitor, 1274 record and report." 1275 PIB-INDEX {pccSessionStatsUsageId} 1277 ::= {pccSessionStatsUsageTable 1} 1279 PccSessionStatsUsageEntry ::= SEQUENCE { 1280 pccSessionStatsUsageId InstanceID, 1281 pccSessionStatsUsageStart ExtUTCTime, 1282 pccSessionStatsUsageEnd ExtUTCTime 1283 } 1285 pccSessionStatsUsageId OBJECT-TYPE 1286 SYNTAX InstanceId 1287 STATUS current 1288 DESCRIPTION 1289 "An arbitrary integer index that uniquely identifies an 1290 instance of the pccSessionStatsUsage class." 1292 ::= { pccSessionStatsUsageEntry 1 } 1294 pccSessionStatsUsageStart OBJECT-TYPE 1295 SYNTAX ExtUTCTime 1296 STATUS current 1297 DESCRIPTION 1298 "The timestamp when the reservation was successfully 1299 allocated." 1301 ::= { pccSessionStatsUsageEntry 2} 1303 pccSessionStatsUsageEnd OBJECT-TYPE 1304 SYNTAX ExtUTCTime 1305 STATUS current 1306 DESCRIPTION 1307 "The timestamp when the reservation was ended. This 1308 could be due to reservation tear down, an error or 1309 time out condition" 1311 ::= { pccSessionSatsUsageEntry 3} 1313 -- The Policy Control Criteria Allocated Usage Table 1314 -- 1316 pccAllocatedUsageTable OBJECT-TYPE 1317 SYNTAX SEQUENCE OF PccAllocatedUsageEntry 1318 PIB-ACCESS report 1319 STATUS current 1320 DESCRIPTION 1321 "This class records the traffic specification allocated 1322 to a session. It contains the PRID of the linkage 1323 instance associating the selection criteria instance 1324 with the usage instance." 1326 ::= {rsvpPccBaseClasses 12} 1328 pccAllocatedUsageEntry OBJECT-TYPE 1329 SYNTAX PccAllocatedUsageEntry 1330 STATUS current 1331 DESCRIPTION 1332 "Defines the attributes the PEP is to monitor, record 1333 and report." 1334 PIB-INDEX {pccAllocatedUsageId} 1336 ::= { pccAllocatedUsageTable 1} 1338 PccAllocatedUsageEntry ::= SEQUENCE { 1339 pccAllocatedUsageId InstanceId, 1340 pccAllocatedIntsrvClass Integer32, 1341 pccAllocatedUsageBucketRate BitRate, 1342 pccAllocatedUsageBucketSize Unsigned32, 1343 pccAllocatedUsagePeakRate BurstRate, 1344 pccAllocatedUsageMinPolicedUnit MessageSize, 1345 pccAllocatedUsageMaxPacketSize MessageSize 1346 pccAllocatedUsageLimitsRate BitRate, 1347 pccAllocatedUsageSlackTerm Unsigned32 1348 } 1350 pccAllocatedUsageId OBJECT-TYPE 1351 SYNTAX InstanceId 1352 STATUS current 1353 DESCRIPTION 1354 "An arbitrary integer index that uniquely identifies an 1355 instance of the PpcAllocatedUsage class." 1357 ::= { pccAllocatedUsageEntry 1 } 1359 pccAllocatedIntsrvClass OBJECT-TYPE 1360 SYNTAX Integer32 1361 STATUS current 1362 DESCRIPTION 1363 �The Intsrv Class associated with the session.� 1365 ::= { pccAllocatedUsageEntry 2 } 1367 pccAllocatedUsageBucketRate OBJECT-TYPE 1368 SYNTAX BitRate 1369 STATUS current 1370 DESCRIPTION 1371 " 'r' bytes per second, the token bucket rate. " 1373 ::= { pccAllocatedUsageEntry 3 } 1375 pccAllocatedUsageBucketSize OBJECT-TYPE 1376 SYNTAX Unsigned32 1377 STATUS current 1378 DESCRIPTION 1379 " 'b' bucket depth in bytes, the token bucket size. " 1381 ::= { pccAllocatedUsageEntry 4 } 1383 pccAllocatedUsagePeakRate OBJECT-TYPE 1384 SYNTAX BurstSize 1385 STATUS current 1386 DESCRIPTION 1387 " 'p' peak traffic data rate in bytes. " 1389 ::= { pccAllocatedUsageEntry 5 } 1391 pccAllocatedUsageMinPolicedUnit OBJECT-TYPE 1392 SYNTAX MessageSize 1393 STATUS current 1394 DESCRIPTION 1395 " 'm' minimum policed unit - size in bytes of 1396 application data and all IP and greater level (UDP, 1397 RTP, TCP, etc.) headers. " 1399 ::= { pccAllocatedUsageEntry 6 } 1401 pccAllocatedUsageMaxPacketSize OBJECT-TYPE 1402 SYNTAX MessageSize 1403 STATUS current 1404 DESCRIPTION 1405 " 'M' maximum packet size - biggest packet that conforms 1406 to traffic specification. " 1407 ::= { pccAllocatedUsageEntry 7 } 1409 pccAllocatedUsageLimitsRate OBJECT-TYPE 1410 SYNTAX BitRate 1411 STATUS current 1412 DESCRIPTION 1413 " Limit Rate. Must be greater than or equal to rate for 1414 the flow " 1416 ::= { pccAllocatedUsageEntry 8 } 1418 pccAllocatedUsageSlackTerm OBJECT-TYPE 1419 SYNTAX Unsigned32 1420 STATUS current 1421 DESCRIPTION 1422 " 'S' - Slack Term. Defines in microseconds the 1423 difference between desired delay and the delay 1424 attained with the reservation level of R" 1426 ::= { pccAllocatedUsageEntry 9 } 1428 -- 1429 --Virtual Pool Usage Table 1430 -- 1432 pccPoolUsageTable OBJECT TYPE 1433 SYNTAX SEQUENCE OF PccPoolUsageEntry 1434 PIB-ACCESS Install 1435 STATUS current 1436 DESCRIPTION 1437 �This table tracks and reports the current total 1438 of resources consumed by Intsrv flows for a 1439 specific virtual pool.� 1441 ::= {rsvpPccBaseClasses 13} 1443 pccPoolUsageEntry OBJECT TYPE 1444 SYNTAX PcPoolUsageEntry 1445 STATUS current 1446 DESCRIPTION 1447 �Defines the attributes for tracking the current 1448 total of resources used by Intsrv flows for a 1449 virtual pool.� 1450 PIB-INDEX {pccPoolUsageId} 1452 ::= {pccPoolUsageTable 1} 1454 PccPoolUsageEntry ::= SEQUENCE { 1455 pccPoolUsageId InstanceID, 1456 pccPoolUsagePoolId PRID, 1457 pccPoolUsageAbsRateInUse Unsigned32 1458 } 1460 pccPoolUsageId OBJECT-TYPE 1461 SYNTAX InstanceId 1462 STATUS current 1463 DESCRIPTION 1464 �This is the unique identifier of the 1465 pccPoolUsage Table entry.� 1466 ::= { pcPoolUsageEntry 1} 1468 pccPoolUsagePoolId OBJECT-TYPE 1469 SYNTAX PRID 1470 STATUS current 1471 DESCRIPTION 1472 �This is the prid of the pccACVirPoolTable entry 1473 that is being tracked.� 1474 ::= { pcPoolUsageEntry 2} 1476 pccPoolUsageAbsRateInUse OBJECT-TYPE 1477 SYNTAX Unsigned32 1478 STATUS current 1479 DESCRIPTION 1480 �This is the current total of resources used 1481 by Intsrv flows for the virtual pool identified 1482 by the pccPoolUsagePoolId.� 1483 ::= { pccPoolUsageEntry 3} 1485 pccPoolUsgeAbsRateInUseThreshold OBJECT-TYPE 1486 SYNTAX Unsigned32 1487 STATUS current 1488 DESCRIPTION 1489 � This value is associated with the 1490 pccPoolUsageAbsRateInUse and defines the feedback 1491 threshold for this usage that results in the 1492 instance being reported to the PDP. This value is 1493 only used if the linkage entry is set to threshold� 1494 ::= { pccPoolUsageEntry 4 } 1496 END 1498 5 Security Considerations 1500 "..The use of IPSEC between the PDP and the PEP, as described in 1501 [2748], provides the necessary protection against security threats. 1502 However, even if the network itself is secure, there is no control as 1503 to who on the secure network is allowed to "Install/Notify" 1504 (read/change/create/delete) the PRIs in this PIB. It is then a 1505 customer/user responsibility to ensure that the PEP/PDP giving access 1506 to an instance of this PIB, is properly configured to give access to 1507 the PRIs only to those principals (users) that have legitimate 1508 rights to indeed "Install" or "Notify" (change/create/ delete) them�" 1509 [POLFRWK] 1511 6 Acknowledgements 1512 The authors would like to thank Russell Fenger of Intel for his 1513 contribution to this document. 1515 7 Authors Addresses 1517 Diana Rawlins 1518 901 International Parkway 1519 Richardson, TX 75081 1520 Diana.Rawlins@wcom.com 1522 Lei Yao 1523 22001 Loudoun County Parkway 1524 Ashburn, VA 20147 1525 Lei.yao@wcom.com 1527 Richard McClain 1528 901 International Parkway 1529 Richardson, TX 75081 1530 Richard.McClain@wcom.com 1532 Amol Kulkarni 1533 JF3-206 1534 2111 NE 25th Ave 1535 Hillsboro, Oregon 97124 1536 amol.kulkarni@intel.com 1538 8 References 1539 [2748] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., 1540 and A. Sastry, "The COPS (Common Open Policy Service) Protocol" 1541 RFC 2748, January 2000. 1543 [3084] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. 1544 Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for 1545 Policy Provisioning," RFC 3084, March 2001. 1547 [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning 1548 Information," draft-ietf-rap-sppi-02.txt, October 2000. 1550 [POLFRWK] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, 1551 A. Smith, F. Reichmeyer "Framework Policy Information Base", 1553 [FEEDBKFRPIB] D. Rawlins, A. Kulkarni, K. Chan, D. Dutt, " 1554 Framework of COPS-PR Policy Information Base for Accounting 1555 Usage", draft-ietf-rap-feedback-fr-pib-01.txt, November 2001 1557 [2749] Herzog, S., Boyle J., Cohen, R., Durham, D., Rajan, R., 1558 Sastry, A., "COPS usage for RSVP" RFC 2749, January 2000 1560 [2750] Herzog, S., "COPS Extensions for Policy Control" RFC 2750, 1561 January 2000. 1563 [2751] Herzog, S., "Signal Priority Preemption Policy Element" RFC 1564 2751, January 2000. 1566 [2752] Yadav, S., Yavatkar, R., Pabbati, R., Ford, P., Moore, T. 1567 Herzog, S. "Identity Representation for RSVP" RFC 2752, January 1568 2000. 1570 [2753] Yavatkar, R., Pendarakis, D., Guerin, R., "A Framework for 1571 Policy-based Admission Control" RFC 2753, January 2000. 1573 [2872] Bernet, Y., Pabbati, R., "Application and Sub Application 1574 Identity Policy Element for Use with RSVP" RFC 2872, June 2000. 1576 [2205] Braden, R., Zhang, L., Berson, S., Herzog, S., Jamin, S., 1577 "Resource ReSerVation Protocol (RSVP)" RFC2205, September 1997. 1579 [2210] Wroclawski, J., "The Use of RSVP with IETF Integrated 1580 Services", RFC2210, September 1997. 1582 [2211] Wroclawski, J., "Specification of the Controlled-Load 1583 Network Element Service", RFC2211, September 1997. 1585 [2212] Shenker, S., Partridge, C., Guerin, R., "Specification of 1586 Guaranteed Quality of Service", RFC2212, September 1997. 1588 [2215] Shenker, S., Wroclawski, J.," General Characterization 1589 Parameters for Integrated Service Network Elements", RFC2215, 1590 September 1997. 1592 [2998] Bernet, Y., et al, �Integrated Services over Diffserv 1593 Networks�, RFC 2998, November 2000. 1595 [EdgeAdmCtl] D. Rawlins, L. Yao, D. McDysan, �Edge Based Admission 1596 Control with Class Based Resource Management�, draft-rawlins-admctl- 1597 ds-mgt-00.txt, November 2001.