idnits 2.17.1 draft-ietf-rap-feedback-fr-pib-01.txt: -(831): 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 7 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 ([COPS-PR], [COPS]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 502 has weird spacing: '... usage monit...' == Line 715 has weird spacing: '...ination with ...' -- 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 20, 2001) is 8192 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 43, but not defined == Missing Reference: 'COPS-PR' is mentioned on line 154, but not defined == Unused Reference: 'FEEDBACKfWK' is defined on line 1313, but no explicit reference was found in the text == Unused Reference: '3084' is defined on line 1321, but no explicit reference was found in the text == Outdated reference: A later version (-04) exists of draft-ietf-rap-feedback-frwk-01 ** Downref: Normative reference to an Informational draft: draft-ietf-rap-feedback-frwk (ref. 'FEEDBACKfWK') ** Downref: Normative reference to an Historic RFC: RFC 3084 ** Downref: Normative reference to an Historic RFC: RFC 3159 (ref. 'SPPI') == Outdated reference: A later version (-09) exists of draft-ietf-diffserv-pib-05 ** Downref: Normative reference to an Historic draft: draft-ietf-diffserv-pib (ref. 'DIFFSERV-PIB') == Outdated reference: A later version (-09) exists of draft-ietf-rap-frameworkpib-06 ** Downref: Normative reference to an Historic draft: draft-ietf-rap-frameworkpib (ref. 'FR-PIB') Summary: 9 errors (**), 0 flaws (~~), 11 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Diana Rawlins 3 Expiration: May 2002 WorldCom 4 File: draft-ietf-rap-feedback-fr-pib-01.txt Amol Kulkarni 5 Intel 6 Kwok Ho Chan 7 Nortel Networks 8 Martin Bokaemper 9 Unisphere Networks 10 Dinesh Dutt 11 Cisco 13 Framework of COPS-PR Policy Information Base for Policy Usage 14 Feedback 16 Last Updated November 20, 2001 18 Status of this Memo 19 This document is an Internet-Draft and is in full conformance with 20 all provisions of Section 10 of RFC2026. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six 28 months and may be updated, replaced, or obsoleted by other 29 documents at any time. It is inappropriate to use Internet-Drafts 30 as reference material or to cite them other than as "work in 31 progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 Conventions used in this document 40 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 41 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 42 in this document are to be interpreted as described in [RFC-2119]. 44 Abstract 45 Currently there are no policy classes defined for the PEP to convey 46 provisioned policy usage feedback to the PDP. The purpose of this 47 document is to define the policy usage feedback framework PIB that 48 specifies the policy classes common for COPS feedback reports. The 49 basic operation and objects for reporting usage information are 50 defined in [COPS]. A specific clientSI feedback object named REPORT 51 is defined in [COPS-PR]. A framework for approaching solicited and 52 periodic usage feedback is described in [COPS-FEED-FRWK.]This 53 document defines the policy classes for a feedback framework Policy 54 information base (PIB). 56 Table of Contents 58 1 Introduction.....................................................3 59 2 General Concepts.................................................3 60 2.1 Selection, Usage and Linkage Policies..........................3 61 2.2 Normal Operations..............................................4 62 2.2.1 Connection Establishment and Initial Configuration Request...4 63 2.2.2 Unsolicited Reports - Periodic Reporting.....................5 64 2.2.3 Unsolicited Reports - Reporting Conditions...................5 65 2.2.4 Solicited Reports............................................5 66 2.2.5 Resuming and Suspending Periodic Feedback Reporting..........6 67 2.2.6 Failover.....................................................6 68 3 Summary of the Feedback Framework Policy Information Base........6 69 3.1 SPPI ACCESS clause report-only.................................6 70 3.2 Feedback Groups and PRCs.......................................7 71 3.2.1 Feedback Action Table........................................7 72 3.2.2 Feedback List Table..........................................8 73 3.2.3 The Feedback Selection Usage Combination Capability Table....8 74 3.2.4 The Feedback Report Linkage Table............................8 75 3.2.7 The Feedback Traffic Statistics Threshold Table..............9 76 3.2.8 The SetWatchPoint Table......................................9 77 3.2.9 Feedback DPE Selection Criteria Table........................9 78 3.2.10 Feedback DPE Selection Query Table..........................9 79 4 The Feedback Framework PIB Module...............................10 80 5 Security Considerations.........................................25 81 6 Acknowledgements................................................25 82 7 Authors' Addresses..............................................26 83 8 References......................................................26 85 1 Introduction 87 The Framework of COPS-PR Usage Feedback describes the overall 88 approach to policy usage monitoring and reporting. This document 89 defines the specific Policy Information Base (PIB) framework for 90 policy usage feedback. The policy classes for monitoring and 91 reporting policy usage feedback as well as policy classes for 92 controlling reporting intervals, suspension, resumption and 93 solicitation are also defined. 95 2 General Concepts 97 2.1 Selection, Usage and Linkage Policies 99 There are three basic types of policy used to define what the PEP is 100 to monitor, record and report. These are the selection criteria 101 policy, the usage policy and the feedback report linkage policy. 103 The selection criteria policy is installed by the PDP. It defines the 104 conditions used by the PEP to monitor and record a usage policy. 105 Generally, the selection criterion is an existing PRC such as the 106 qosClfrElementEntry. This PRC is useful for specifying conditions on 107 which to base usage - i.e. count the number of packets received for 108 this classified flow. 110 The usage policy defines what attributes are monitored and recorded 111 by the PEP. These policies have an ACCESS clause of Report. 112 Generally, the usage policies specify counts related to a specific 113 action such as a packet being dropped. The feedback framework PIB 114 defines one usage policy class, frwkFeedbackTrafficUsage. It counts 115 packets and bytes. Usage PRCs may be generic, collecting basic 116 statistics, or they may be specific to a particular usage. The PDP 117 decides which PRC(s) best suit(s) its requirements. The PEP may 118 support only one usage PRC, in which case all statistics are gathered 119 using instances of that PRC. Alternatively, the PEP may support 120 multiple usage PRCs. The PDP then decides which PRC to associate with 121 a particular selection criterion. 123 A usage policy and selection policy are tightly associated with one 124 another. A third policy is used to associate, or link, the selection 125 and usage policies. The frwkFeedbackLinkTable performs this linking 126 of the selection and usage policies. The feedback report linkage 127 permits the same selection criteria instance to be re-used for 128 various usage policies. The feedback type report linkage references 129 the selection criteria instance as well as defines the policy class 130 of the usage PRC. As noted above, the selection criteria policy may 131 be used for enforcement policies as well as usage policies. This is 132 the case with qosClfrElementEntry. 134 ----------------- ------------------ ----------------- 135 | | | | | | 136 | Select Criteria | |Linkage Instance | |Usage Instance | 137 | | |-instance ID | |- instance ID | 138 | -instance ID |<--|-PRID of selection|--->|- PRID of Linkage| 139 | -conditions... | |-PRC of usage | |- counts... | 140 | | | | | | 141 ----------------- ------------------ ----------------- 143 Figure 1 145 Figure 1 illustrates the relationship between a selection criteria, 146 linkage and usage policies. 148 The PDP is not aware of the instance identifier of the usage policy 149 when installing the selection criteria and feedback report linkage 150 policies. The usage policy is instantiated on the PEP by the 151 installation of a feedback report linkage and the PEP designates the 152 instance identifier. The usage policy class always contains an 153 attribute of type Prid which contains the value of the associated 154 feedback report linkage PRID [COPS-PR] installed by the PDP. Note 155 that the Prid type is a textual convention for an object identifier 156 that is the PRC of the table used for the feedback report linkage 157 (was - selection criteria) and where the last sub-identifier is an 158 instance ID of the feedback report linkage. 160 2.2 Normal Operations 162 2.2.1 Connection Establishment and Initial Configuration Request 164 The Accounting Timer object in the Connection Accept message contains 165 the minimum number of seconds between reporting intervals as 166 described in [COPS] and [COPS-FEEDBACK-FRWK.] This is used as the 167 basic unit of measurement in defining intervals for specific usage 168 policies with the frwkFeedbackLinkInterval attribute. 170 The PEP notifies the PDP of the selection criteria policy classes and 171 usage policy classes it supports during the initial request for 172 configuration data using the frwkPRCSupportTable entries [FR-PIB]. 173 The PEP also indicates whether it supports the frwkFeedbackLinkTable 174 as well. 176 The PDP responds to the initial request for configuration with a 177 DECISION that installs policies. The PDP may also specify maximum 178 reporting intervals associated with each of the usage policies. This 179 is done with the frwkFeedbackLinkInterval attribute in the 180 frwkFeedbackLinkTable instance. It may also specify reporting 181 thresholds by including an instance of a threshold class (e.g. 182 frwkFeedbackTrafficThresholdTable) in the decision. The PEP monitors 183 and records the usage per the conditions defined by its associated 184 selection criteria policy. Periodically the PEP reports the usage 185 with an feedback type REPORT or provides a REPORT when solicited by 186 the PDP. The PDP solicits usage feedback with the 187 frwkFeedbackActionIndicator attribute of the frwkFeedbackActionTable. 189 2.2.2 Unsolicited Reports - Periodic Reporting 191 Reporting may be periodic in nature and unsolicited. The intervals 192 at which the unsolicited reports are provided by the PEP are defined 193 in the specific Linkage policies. The defined intervals are based on 194 the number of seconds specified by the PDP in the ACCT Timer value. 195 The PDP may specify that the periodic unsolicited report is to only 196 occur if a threshold is reached and/or if the usage value has 197 changed from the previous reporting interval. 199 There are cases when the PEP must supply unsolicited feedback 200 reports that may not fall on an interval boundary. The PEP MUST 201 provide an unsolicited REPORT containing all defined usages 202 instances just prior to the PEP issuing a Delete Request State and 203 just prior to the PEP de-activating a PIB instance context. 205 2.2.3 Unsolicited Reports - Reporting Conditions 207 Periodic unsolicited reports for individual linkage objects can be 208 suppressed by specifying additional conditions. Supported conditions 209 are: 210 ChangeOnly 211 If this flag is set in the frwkFeedbackUsageLinkFlags field, 212 the associated usage instance is only included in a periodic 213 unsolicited report if its value changed since the last 214 unsolicited report. 216 Threshold 217 If this flag is set in the frwkFeedbackUsageLinkFlags field, 218 the associated usage instance is only included in a periodic 219 unsolicited report, if the threshold condition referenced in 220 the frwkLinkThreshold field evaluates successfully for the 221 associated usage instance. 223 Both conditions can be combined in one frwkFeedbackLinkUsage object. 224 In this case both conditions need to succeed for the usage instance 225 to be reported. 227 Unsolicited reports triggered by a Delete Request State or the 228 deactivation of a PIB instance are not subject to these conditions - 229 all usage objects must be included in these cases. 231 2.2.4 Solicited Reports 233 The PDP may solicit policy usage feedback by issuing an unsolicited 234 Decision containing the frwkFeedbackActionIndicator set to SOLICIT 235 USAGE REPORT NOW. The PEP is to provide a solicited REPORT feedback 236 containing usage feedback. The PEP shall continue to provide 237 periodic feedback as well at the specified intervals established at 238 client connection acceptance. 239 The reporting conditions (ChangeOnly and Threshold) do not affect 240 solicited reports - all requested usage instances must be included. 242 2.2.5 Resuming and Suspending Periodic Feedback Reporting 244 The PDP may suspend usage monitoring and tracking at the PEP with the 245 frwkFeedbackActionIndicator set to SUSPEND USAGE MONITORING AND 246 REPORTS. The PEP must stop tracking usage information and must not 247 issue any feedback reports. The PDP may only suspend feedback 248 reporting by setting the ActionIndicator to SUSPEND REPORTS ONLY. The 249 PEP must cease sending unsolicited reports but is to continue 250 monitoring and tracking usage. The PDP may resume the sending of 251 feedback reports and may resume usage monitoring by setting the 252 ActionIndicator to RESUME USAGE AND REPORTING. 254 The PDP may suspend or resume for all usage instances or the PDP may 255 specify one or more instances that are to be suspended or resumed. 256 The frwkFeedbackActionList contains a tag identifier that references 257 a list of one or more frwkFeedbackActionListTable entries. 259 The PDP may halt usage monitoring, tracking and reporting of usage 260 policies by removing the associated Linkage entry. 262 2.2.6 Failover 264 In the event the connection is lost between the PEP and PDP, the PEP 265 continues to track usage information as long as it continues to 266 operate with the installed policy. When the locally installed policy 267 at the PEP expires, the usage policy data also expires. 269 Upon successful reconnection where the PEP is still caching policy, 270 the PDP indicates to the PEP that the PEP may resume sending of the 271 feedback type report messages. The PDP does this deterministically. 272 It issues an unsolicited decision containing the 273 frwkFeedbackResumeIndicator set to resume reporting. The PEP should 274 resume reporting at the next appropriate feedback interval 275 established upon the acceptance of the re-connection. The PDP is 276 aware of the request state Handle(s) and the supported PRCs either 277 through the state synchronization mechanism or because the PDP 278 considers itself synchronized with the PEP upon reconnection. 280 3 Summary of the Feedback Framework Policy Information Base 282 3.1 SPPI ACCESS clause report-only 284 The selection criteria and linkage policy classes follow the 285 definitions specified by [SPPI]. This structure specifies well- 286 defined policy classes and their instances residing in a common, 287 virtual repository [FR-PIB]. The additional PIB-ACCESS clause 288 attribute of "report-only" denotes the usage policy class reported by 289 the PEP. 291 3.2 Feedback Groups and PRCs 293 It is useful to define reporting intervals, and suspend, resume, and 294 solicit characteristics as well as the common usage and selection 295 criteria polices. These policy classes are common to account type 296 reporting for various technologies and apply to ALL SUBJECT- 297 CATEGORIES. The policy classes are divided into three new groups, 298 namely, The Feedback Report Group, The Feedback Usage Group and The 299 Feedback Selection Group. 301 The policy classes in the Feedback Report Group are: 303 1) Feedback Action Table 304 2) Feedback Action List Table 305 3) Feedback Selection Usage Combination Capability Table 306 4) Feedback Linkage Table 308 The policy classes in the Feedback Usage Group are: 309 1) Feedback Traffic Statistics Usage Table 310 2) Feedback Interface Traffic Statistics Usage Table 311 3) Feedback Traffic Statistics Threshold Table 313 The policy classes in the Feedback Selection Group are: 314 1) SetWatchPoint Table 315 2) Feedback DPE Selection Criteria Table 316 3) Feedback DPE Selection Query Table 317 4) Feedback DPE Interface Usage Table 319 3.2.1 Feedback Action Table 321 The Feedback Action Table contains the attributes that specify 322 action that the PEP is to take regarding policy usage, monitoring 323 and tracking. The PDP may suspend usage monitoring and periodic 324 reporting, suspend periodic reporting only, resume usage and 325 periodic reporting or solicit immediate reporting. The action may 326 affect all feedback policies or be associated with one or more 327 policy instances. 329 The Feedback Action Indicator defines the action. The Feedback 330 Specific PRI indicates whether the action applies to all of the 331 usage policies or to a list. The Feedback List ID is the identifier 332 of the list of Linkage policy instances to which the action is to be 333 applied. 335 The PDP can solicit the PEP for immediate usage feedback. The PEP 336 shall respond with a solicited report containing the usage feedback. 338 The PDP can direct the resumption of usage monitoring and reporting 339 per the defined intervals. For example, the PEP may have re- 340 connected to a PDP and has cached usage policies. The PDP indicates 341 to the PEP to resume usage tracking and monitoring and to send all 342 the cached usage policy. The PEP shall respond at the next 343 appropriate interval with an unsolicited report containing the usage 344 feedback. 346 The PDP can suspend the monitoring of usage policy. The PEP 347 maintains the current usage that has been monitored but discontinues 348 any further monitoring until the PDP directs the PEP to resume 349 monitoring in a subsequent Decision. 351 The PDP can also suspend just the reporting of usage, but not 352 interrupt the monitoring and tracking of usage. The PEP shall 353 discontinue sending Report messages with usage feedback until the 354 PDP directs the PEP to resume. The PEP then begins reporting the 355 usage feedback at the next interval. 357 3.2.2 Feedback List Table 359 This table contains a list of PRIDs of the linkage table for which 360 the PDP wants feedback reports. The value is referenced by an 361 attribute in the Feedback Resume Table. There may be one or more 362 instances associated with a specific list identifier defined by the 363 Feedback Action List ID. 365 3.2.3 The Feedback Selection Usage Combination Capability Table 367 This table defines the valid selection criteria PRC, and usage PRC 368 and threshold PRC combinations supported. 370 3.2.4 The Feedback Report Linkage Table 372 This table links the selection criteria instance with the usage 373 instance. It specifies the PRID of the selection criteria and the PRC 374 of the usage instance. This table permits the reuse of a selection 375 criteria instance for multiple usage policies. 377 The linkage table also permits the definition of a maximum reporting 378 interval to use when issuing the feedback type reports for the usage 379 instance. This interval is defined in units of the Accounting Timer 380 Interval specified in the client accept message. A value of 0 in this 381 attribute indicates that the usage policy must be solicited. 383 3.2.5 The Feedback Traffic Statistics Usage Table 385 This table describes the packet counts, byte counts, last timestamp 386 when a packet was received and the PRID of the associated Feedback 387 Report Linkage instance. The count and timestamp information is 388 monitored and recorded by the PEP and supplied to the PDP with the 389 feedback type report message within the maximum interval specified. 391 3.2.6 The Feedback Interface Traffic Statistics Usage Table 393 This table is similar to the table described above, except that it 394 includes an additional reference to an interface. This table should 395 be used with a selection criteria that matches an element that is 396 assigned to multiple interfaces. The interface field can be used to 397 associate the instances of this table with the specific element�s 398 assignment. 400 3.2.7 The Feedback Traffic Statistics Threshold Table 402 This table is used to provide threshold values for the attributes 403 described in the above usage tables. 405 3.2.8 The SetWatchPoint Table 407 This table defines a selection criteria policy that identifies the 408 enforcement policy processing point at which the associated usage 409 policy is to be monitored. This is useful in the data path models 410 where re-use of the enforcement policy occurs and is implemented in 411 a linked fashion. For example, it may be useful to monitor and 412 feedback the packet usage at a specific dropper enforcement policy 413 in the DiffServ PIB. 415 3.2.9 Feedback DPE Selection Criteria Table 417 This table is an example of a Selection Criteria PRC that references 418 a specific instance of a shared object. 419 It is based on the popular model of a data path consisting of 420 multiple linked data path elements (DPEs). 421 A single data path can be assigned to multiple interfaces by a 422 single entry in the Data Path Table [DIFFSERV-PIB], elements within 423 this data path however can collect usage information for each 424 assignment individually. 426 Instances of this class allow the PDP to select a specific 427 assignment of a data path element to be selected for usage 428 reporting. This is achieved by the combination of references to a 429 Data Path Entry, a Data Path Element and the Interface. 430 It is expected to be used in combination with the 431 FrwkFeedbackTrafficUsage PRC. 433 3.2.10 Feedback DPE Selection Query Table 435 This Selection Criteria PRC is similar to the DPE Selection Criteria 436 Table, however it is missing the reference to a specific interface. 437 This means an instance of this class can select multiple assignments 438 of a data path element for usage collection. Each selected 439 assignment of the DPE creates its own usage instance. 440 This selection criteria PRC is expected to be used together with a 441 usage PRC that includes the a reference to an interface, so the 442 results can be assigned uniquely. 444 3.2.11 Feedback DPE Interface Usage Table 446 The DPE Interface Usage class is an extension of the generic Traffic 447 Usage class that also includes a reference to a frwkIfRoleComboEntry 448 that represents the interface, this instance is associated with. 450 4 The Feedback Framework PIB Module 452 FEEDBACK-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN 454 IMPORTS 455 ExtUTCTime, Unsigned32, Unsigned64, 456 Integer32, MODULE-IDENTITY, OBJECT-TYPE 457 FROM COPS-PR-SPPI 458 TruthValue, TEXTUAL-CONVENTION 459 FROM SNMPv2-TC 460 PolicyInstanceId, PolicyReferenceId 461 FROM COPS-PR-SPPI-TC; 462 RoleCombination 463 FROM FRAMEWORK-ROLE-PIB; 464 Counter64 465 FROM SNMPv2-SMI; 467 feedbackPolFrameworkPib MODULE-IDENTITY 468 SUBJECT-CATEGORIES { all } 469 LAST-UPDATED "200011171000Z" 470 ORGANIZATION "IETF RAP WG" 471 CONTACT-INFO " 472 Diana Rawlins 473 WorldCom 474 901 International Parkway 475 Richardson, TX 75081 476 Phone: 972 729 1044 477 Email: diana.rawlins@wcom.com 479 Amol Kulkarni 480 JF3-206 481 2111 NE 25th Ave 482 Hillsboro, Oregon 97124 483 Phone: 503-712-1168 484 Email: amol.kulkarni@intel.com 486 Kwok Ho Chan 487 Nortel Networks, Inc. 488 600 Technology Park Drive 489 Billerica, MA 01821 USA 490 Phone: 978-288-8175 491 Email: khchan@nortelnetworks.com 492 Martin Bokaemper 493 Unisphere Networks 494 700 Silver Seven Road 495 Kanata, ON, K2V 1C3, Canada 496 Phone: 613-591-2735 497 Email: mbokaemper@unispherenetworks.com" 499 DESCRIPTION 500 "The PIB module containing the base set of policy rule 501 classes that are required for support of all policy 502 usage monitoring, tracking and reporting policies" 504 ::= { tbd } 505 -- 506 -- The feedback report group 507 -- 509 frwkFeedbackGroupClasses 510 OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 1 } 512 -- 513 -- Feedback Action Table 514 -- 516 frwkFeedbackActionTable OBJECT-TYPE 517 SYNTAX SEQUENCE OF FrwkFeedbackActionEntry 518 PIB-ACCESS install 519 STATUS current 520 DESCRIPTION 521 "This class contains a single PRI that indicates 522 that the PEP is to resume the sending of 523 feedback type reports." 525 ::= { frwkFeedbackGroupClasses 1} 527 frwkFeedbackActionEntry OBJECT-TYPE 528 SYNTAX FrwkFeedbackActionEntry 529 STATUS current 530 DESCRIPTION 531 "An instance of this class can indicates a action 532 the PEP is to take regarding the usage policies." 533 PIB-INDEX { frwkFeedbackActionId} 535 ::= { frwkFeedbackActionTable 1} 537 FrwkFeedbackActionEntry ::= SEQUENCE { 538 frwkFeedbackActionId InstanceId, 539 frwkFeedbackActionIndicator INTEGER, 540 frwkFeedbackActionSpecificPri INTEGER, 541 frwkFeedbackActionList TagReference 542 } 544 frwkFeedbackActionId OBJECT-TYPE 545 SYNTAX InstanceID 546 STATUS current 547 DESCRIPTION 548 " An arbitrary integer index that uniquely identifies an 549 instance of the frwkFeedbackActionTable class." 551 ::= { frwkFeedbackActionEntry 1} 553 frwkFeedbackActionIndicator OBJECT-TYPE 554 SYNTAX INTEGER { 555 SUSPEND USAGE MONITORING_AND_REPORTS(0) 556 SUSPEND_REPORTS_ONLY(1) 557 RESUME_USAGE AND REPORTING(2) 558 SOLICIT USAGE REPORT NOW(3) 559 } 560 STATUS current 561 DESCRIPTION 562 "The value indicates if the PEP is to send cached 563 usage policies via feedback type report messages. 564 The enumeration values are: 565 (0) SUSPEND USAGE MONITORING_AND_REPORTS 566 (1) SUSPEND_REPORTS_ONLY 567 (2) RESUME_USAGE AND REPORTING 568 (3) SOLICIT USAGE REPORT NOW " 570 ::= { frwkFeedbackActionEntry 2 } 572 frwkFeedbackActionSpecificPri OBJECT-TYPE 573 SYNTAX TruthValue 574 STATUS current 575 DESCRIPTION 576 "A value of 0 indicates that the 577 frwkFeedbackActionListId attribute should be 578 ignored, and the action applied to all policies. A 579 value of 1 indicates that the action entry has a 580 specific list of policies to which it is to be 581 applied." 582 ::= { frwkFeedbackActionEntry 3} 584 frwkFeedbackActionList OBJECT-TYPE 585 SYNTAX TagReference 586 STATUS current 587 DESCRIPTION 588 "Identifies a list of 589 frwkFeedbackActionListTable instances 590 associated with the action described by 591 this instance" 592 ::= { frwkFeedbackActionEntry 4} 594 -- 595 -- Feedback Action List Table 596 -- 597 frwkFeedbackActionListTable OBJECT-TYPE 598 SYNTAX SEQUENCE OF FrwkFeedbackActionListEntry 599 PIB-ACCESS install 600 STATUS current 601 DESCRIPTION 602 "This class contains the PRIDs of the 603 linkage instance which are to be impacted by 604 the frwkFeedbackActionIndicator for this 605 list." 606 ::= { frwkFeedbackGroupClasses 2} 608 frwkFeedbackActionListEntry OBJECT-TYPE 609 SYNTAX FrwkFeedbackActionListEntry 610 STATUS current 611 DESCRIPTION 612 "This class identifies a set of linkage instances 613 for which the PDP is suspending, resuming or 614 soliciting usage feedback." 616 PIB-INDEX {frwkFeedbackActionListId } 617 UNIQUENESS { frwkFeedbackActionListGroup, 618 frwkFeedbackActionListPRID 619 } 620 ::= { frwkFeedbackActionListTable 1} 622 FrwkFeedbackActionListEntry::= SEQUENCE { 623 frwkFeedbackActionListId InstanceID, 624 frwkFeedbackActionListGroup TagId, 625 frwkFeedbackActionListPRID Prid 626 } 628 frwkFeedbackActionListId OBJECT-TYPE 629 SYNTAX InstanceId 630 STATUS current 631 DESCRIPTION 632 "Arbitrary integer index that uniquely 633 identifies an instance of the class." 635 ::= { frwkFeedbackActionListEntry 1 } 637 frwkFeedbackActionListListGroup OBJECT-TYPE 638 SYNTAX TagId 639 STATUS current 640 DESCRIPTION 641 "Represents the binding between the Action 642 table entry and the Action List table entries" 643 ::= { frwkFeedbackActionListEntry 2 } 645 frwkFeedbackActionListPRID OBJECT-TYPE 646 SYNTAX Prid 647 STATUS current 648 DESCRIPTION 649 "The PRID of the linkage instance(s) belonging 650 to the list of instances identified by the 651 list id upon which the suspend, resume or 652 solicit action is directed." 654 ::= { frwkFeedbackActionListEntry 3 } 656 -- 657 -- The Feedback Selection Usage Combination Capability Table 658 -- 660 frwkFeedbackSelUsageComboCapsTable OBJECT-TYPE 661 SYNTAX SEQENCE OF FrwkFeedbackSelUsageComboCapsEntry 662 PIB-ACCESS notify 663 STATUS current 664 DESCRIPTION 665 "This table defines the valid combinations of the 666 selection criteria PRCs, the usage PRCs and the 667 threshold PRCs that the PEP supports." 668 ::= { frwkFeedbackGroupClasses 3} 670 frwkFeedbackSelUsageComboCapsEntry OBJECT-TYPE 671 SYNTAX FrwkFeedbackSelUsageComboCapsEntry 672 STATUS current 673 DESCRIPTION 674 "The attributes of this class identify valid 675 combinations of selection criteria, usage and 676 threshold PRCs for feedback supported by the PEP 677 device." 678 PIB-INDEX {frwkFeedbackActionLinkId} 679 UNIQUENESS { frwkFeedbacSelUsageComboCapId, 680 frwkFeedbackSelUsageComboCapSelection, 681 frwkFeedbackSelUsageComboCapUsage, 682 frwkFeedbackSelUsageComboCapThreshold 683 } 684 ::= {frwkFeedbackSelUsageComboTable 1} 686 FrwkFeedbackSelUsageComboCapsEntry ::= SEQUENCE { 687 frwkFeedbackSelUsageComboCapId InstanceID, 688 frwkFeedbackSelUsageComboCapSelection OBJECT IDENTIFIER, 689 frwkFeedbackSelUsageComboCapUsage OBJECT IDENTIFIER, 690 frwkFeedbackSelUsageComboCapThreshold OBJECT IDENTIFIER 691 } 693 frwkFeedbackSelUsageComboCapId OBJECT-TYPE 694 SYNTAX InstanceID 695 STATUS current 696 DESCRIPTION 697 " An arbitrary integer index that uniquely identifies an 698 instance of the frwkFeedbackSelUsageComboCapsEntry 699 class." 700 ::= { frwkFeedbackSelUsageComboCapsEntry 1} 702 frwkFeedbackSelUsageComboCapSelection OBJECT-TYPE 703 SYNTAX OBJECT IDENTIFIER 704 STATUS current 705 DESCRIPTION 706 "The PRC of the selection class that is supported by 707 the device in the combination defined by this instance." 708 ::= { frwkFeedbackSelUsageComboCapsEntry 2} 710 frwkFeedbackSelUsageComboCapUsage OBJECT-TYPE 711 SYNTAX OBJECT IDENTIFIER 712 STATUS current 713 DESCRIPTION 714 "The PRC of the usage policy class that is supported by 715 the device in combination with the selection PRC and the 716 threshold PRC defined in this instance." 717 ::= { frwkFeedbackSelUsageComboCapsEntry 3} 719 frwkFeedbackSelUsageComboCapThreshold OBJECT-TYPE 720 SYNTAX OBJECT IDENTIFIER 721 STATUS current 722 DESCRIPTION 723 "The PRC of the threshold class that is supported by 724 the device in the combination defined by this instance." 725 ::= { frwkFeedbackSelUsageComboCapsEntry 2} 727 -- 728 -- The Feedback Report Linkage Table 729 -- 731 frwkFeedbackLinkTable OBJECT-TYPE 732 SYNTAX SEQUENCE OF FrwkFeedbackLinkEntry 733 PIB-ACCESS Install 734 STATUS current 735 DESCRIPTION 736 "This class associates the selection criteria with the 737 usage policy. It also permit the defining of the max 738 interval used for reporting the usage instance." 740 ::= { frwkFeedbackGroupClasses 4} 742 frwkFeedbackLinkEntry OBJECT-TYPE 743 SYNTAX FrwkFeedbackLinkEntry 744 STATUS current 745 DESCRIPTION 746 "This class associates the selection criteria with the 747 usage policy. It also permits the defining of the max 748 interval used for reporting the usage instance." 749 PIB-INDEX {frwkFeedbackActionLinkId} 750 UNIQUENESS { frwkFeedbackLinkId, 751 frwkFeedbackLinkSel, 752 frwkFeedbackLinkUsage } 754 ::= {frwkFeedbackLinkTable 1} 756 FrwkFeedbackLinkEntry ::= SEQUENCE { 757 frwkFeedbackLinkId InstanceID, 758 frwkFeedbackLinkSel Prid, 759 frwkFeedbackLinkUsage OBJECT IDENTIFIER, 760 frwkFeedbackLinkInterval Integer32, 761 frwkFeedbackLinkThreshold Prid, 762 frwkFeedbackLinkFlags BITS 763 } 765 frwkFeedbackLinkId OBJECT-TYPE 766 SYNTAX InstanceID 767 STATUS current 768 DESCRIPTION 769 " An arbitrary integer index that uniquely identifies an 770 instance of the frwkFeedbackLinkTable class." 771 ::= { frwkFeedbackLinkEntry 1} 773 frwkFeedbackLinkSel OBJECT-TYPE 774 SYNTAX Prid 775 STATUS current 776 DESCRIPTION 777 "The PRID of the selection criteria instance that 778 defines the conditions to use by the PEP for 779 monitoring the usage." 781 ::= { frwkFeedbackLinkEntry 2} 783 frwkFeedbackLinkUsage OBJECT-TYPE 784 SYNTAX OBJECT IDENTIFIER 785 STATUS current 786 DESCRIPTION 787 "The PRC of the usage policy class that the PEP uses to 788 monitor, record and report." 790 ::= { frwkFeedbackLinkEntry 3} 792 frwkFeedbackLinkInterval OBJECT-TYPE 793 SYNTAX Integer32 794 STATUS current 795 DESCRIPTION 796 "Maximum interval in units of the value of the 797 Accounting Timer specified by the PDP in the client 798 accept message. A frwkFeedbackLinkInterval of 1 is 799 equal to the value of the Accounting Timer. This value 800 must be 1 or greater. " 802 ::= { frwkFeedbackLinkEntry 4} 804 frwkFeedbackLinkThreshold OBJECT-TYPE 805 SYNTAX Prid 806 STATUS current 807 DESCRIPTION 808 "The PRID of the threshold class instance. This 809 instance specifies the threshold values for the usage 810 policy." 811 ::= { frwkFeedbackLinkEntry 5} 813 frwkFeedbackLinkFlags OBJECT-TYPE 814 SYNTAX BITS { 815 periodic(0), 816 threshold(1), 817 changeOnly(2), 818 } 819 STATUS current 820 DESCRIPTION 821 "This value indicates the reporting basis of the usage 822 policy. The feed back may be generated on demand, on a 823 periodic basis regardless of a change in value from the 824 previous report, on a periodic basis if a change in 825 value has occurred, or the usage is reported when an 826 identified threshold value in the usage instance has 827 been reached. 828 If the �periodic� flag is set, the PEP will provide 829 unsolicited reports at the rate specified in 830 frwkFeedbackLinkInterval. 831 If the �periodic� flag is not set, reports will only be 832 generated when solicited by the PDP. 833 The �threshold� and �changeOnly� flags make the 834 periodic reports conditional - these flags only make 835 sense in combination with the �periodic� flag." 837 ::= { frwkFeedbackLinkEntry 6} 839 -- 840 -- All actual usage classes are in the separate 841 -- FrwkFeedbackUsageClasses group 842 -- 844 FrwkFeedbackUsageClasses 845 OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 2 } 847 -- 848 -- The generic traffic (byte & packet count) usage class 849 -- 851 frwkFeedbackTrafficUsageTable OBJECT-TYPE 852 SYNTAX SEQUENCE OF FrwkFeedbackTrafficUsageEntry 853 PIB-ACCESS report-only 854 STATUS current 855 DESCRIPTION 856 "This class defines the usage attributes that the PEP 857 is to monitor for plain traffic handling elements 858 like filters. All packets and the bytes contained in 859 these packets are counted. It also contains the PRID 860 of the linkage instance associating the selection 861 criteria instance with the usage instance." 863 ::= { frwkFeedbackUsageClasses 1} 865 frwkFeedbackTrafficUsageEntry OBJECT-TYPE 866 SYNTAX FrwkFeedbackTrafficUsageEntry 867 STATUS current 868 DESCRIPTION 869 "Defines the attributes the PEP is to monitor, 870 record and report." 871 PIB-INDEX {frwkFeedbackTrafficUsageId} 872 UNIQUENESS { frwkFeedbackTrafficUsageLinkPRID } 874 ::= {frwkFeedbackTrafficUsageTable 1} 876 FrwkFeedbackTrafficUsageEntry ::= SEQUENCE { 877 FrwkFeedbackTrafficUsageId InstanceID, 878 frwkFeedbackTrafficUsageLinkPRID Prid, 879 frwkFeedbackTrafficUsagePacketCount Counter64, 880 frwkFeedbackTrafficUsageByteCount Counter64 882 } 884 frwkFeedbackTrafficUsageId OBJECT-TYPE 885 SYNTAX InstanceId 886 STATUS current 887 DESCRIPTION 888 "Arbitrary integer index that uniquely identifies 889 an instance of the class." 890 ::= { frwkFeedbackTrafficUsageEntry 1 } 892 frwkFeedbackTrafficUsageLinkPRID OBJECT-TYPE 893 SYNTAX Prid 894 STATUS current 895 DESCRIPTION 896 "The PRID of the Linkage policy instance used to base 897 this usage policy instance upon." 899 ::= { frwkFeedbackTrafficUsageEntry 2 } 901 frwkFeedbackTrafficUsagePacketCount OBJECT-TYPE 902 SYNTAX Counter64 903 STATUS current 904 DESCRIPTION 905 "The count of packets handled by the associated 906 element during the reporting interval." 908 ::= {frwkFeedbackTrafficUsageEntry 3} 910 frwkFeedbackTrafficUsageByteCount OBJECT-TYPE 911 SYNTAX Counter64 912 STATUS current 913 DESCRIPTION 914 "The byte count of packets handled by the associated 915 element." 916 ::= { frwkFeedbackTrafficUsageEntry 4} 918 -- 919 -- The traffic usage class, qualified for an interface 920 -- 922 frwkFeedbackIfTrafficUsageTable OBJECT-TYPE 923 SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficUsageEntry 924 PIB-ACCESS report-only 925 STATUS current 926 DESCRIPTION 927 "A usage PRC similar to the basic TrafficUsage class 928 that also contains a reference to an interface. This 929 class should be used with a selection criteria that 930 matches an element that is assigned to multiple 931 interfaces. The interface field can be used to 932 associate the instances of this class with the specific 933 element�s assignment." 934 ::= { frwkFeedbackUsageClasses 2 } 936 frwkFeedbackIfTrafficUsageEntry OBJECT-TYPE 937 SYNTAX FrwkFeedbackIfTrafficUsageEntry 938 STATUS current 939 DESCRIPTION 940 "Defines the attributes the PEP is to monitor, 941 record and report." 942 PIB-INDEX {frwkFeedbackIfTrafficUsageId} 943 UNIQUENESS { frwkFeedbackIfTrafficUsageLinkPRID, 944 frwkFeedbackIfTrafficUsageInterface } 946 ::= {frwkFeedbackTrafficUsageTable 1} 948 FrwkFeedbackIfTrafficUsageEntry ::= SEQUENCE { 949 FrwkFeedbackIfTrafficUsageId InstanceID, 950 frwkFeedbackIfTrafficUsageLinkPRID Prid, 951 frwkFeedbackIfTrafficUsageInterface Prid, 952 frwkFeedbackIfTrafficUsagePacketCount Counter64, 953 frwkFeedbackIfTrafficUsageByteCount Counter64 955 } 957 frwkFeedbackIfTrafficUsageId OBJECT-TYPE 958 SYNTAX InstanceId 959 STATUS current 960 DESCRIPTION 961 "Arbitrary integer index that uniquely identifies 962 an instance of the class." 963 ::= { frwkFeedbackIfTrafficUsageEntry 1 } 965 frwkFeedbackIfTrafficUsageLinkPRID OBJECT-TYPE 966 SYNTAX Prid 967 STATUS current 968 DESCRIPTION 969 "The PRID of the Linkage policy instance used to base 970 this usage policy instance upon." 971 ::= { frwkFeedbackIfTrafficUsageEntry 2 } 973 frwkFeedbackIfTrafficUsageInterface OBJECT-TYPE 974 SYNTAX Prid 975 STATUS current 976 DESCRIPTION 977 "The PRID of a frwkIfRoleCombo instance, uniquely 978 identifying a specific interface." 979 ::= { frwkFeedbackIfTrafficUsageEntry 3 } 981 frwkFeedbackIfTrafficUsagePacketCount OBJECT-TYPE 982 SYNTAX Counter64 983 STATUS current 984 DESCRIPTION 985 "The count of packets handled by the associated element 986 during the reporting interval." 987 ::= { frwkFeedbackIfTrafficUsageEntry 4 } 989 frwkFeedbackIfTrafficUsageByteCount OBJECT-TYPE 990 SYNTAX Counter64 991 STATUS current 992 DESCRIPTION 993 "The byte count of packets 994 handled by the associated element." 995 ::= { frwkFeedbackIfTrafficUsageEntry 5 } 997 -- 998 -- The Threshold class that accompanies the above Usage PRCs 999 -- 1001 frwkFeedbackTrafficThresholdTable OBJECT-TYPE 1002 SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresholdEntry 1003 PIB-ACCESS Install 1004 STATUS current 1005 DESCRIPTION 1006 "This class defines the threshold attributes 1007 corresponding to usage attributes specified in 1008 frwkFeedbackTrafficUsageTable, 1009 frwkFeedbackIfTrafficUsageTable and other similar 1010 usage classes. 1011 The usage object is considered to match the threshold 1012 condition if the following expression evaluates to 1013 �TRUE�: 1014 { 1015 byteCond = (ByteThreshold != NULL) ? 1016 (ByteThreshold > ByteCounter) : FALSE; 1017 packetCond (PacketThreshold != NULL) ? 1018 (PacketThreshold > PacketCounter) : FALSE; 1019 return ( byteCond || packetCond ); 1020 }" 1022 ::= { frwkFeedbackUsageClasses 3} 1024 frwkFeedbackTrafficThresholdEntry OBJECT-TYPE 1025 SYNTAX FrwkFeedbackTrafficThresholdEntry 1026 STATUS current 1027 DESCRIPTION 1028 "Defines the attributes to hold threshold values." 1029 PIB-INDEX {frwkFeedbackTrafficThresholdId} 1031 ::= {frwkFeedbackTrafficThresholdTable 1} 1033 FrwkFeedbackTrafficThresholdEntry ::= SEQUENCE { 1034 FrwkFeedbackTrafficThresholdId InstanceID, 1035 frwkFeedbackTrafficThresholdPacketThreshold Integer64, 1036 frwkFeedbackTrafficThresholdByteThreshold Integer64 1037 } 1039 frwkFeedbackIfTrafficThresholdId OBJECT-TYPE 1040 SYNTAX InstanceId 1041 STATUS current 1042 DESCRIPTION 1043 "Arbitrary integer index that uniquely identifies 1044 an instance of the class." 1045 ::= { frwkFeedbackIfTrafficThresholdEntry 1 } 1047 frwkFeedbackIfTrafficThresholdPacketThreshold OBJECT-TYPE 1048 SYNTAX Integer64 1049 STATUS current 1050 DESCRIPTION 1051 "The threshold, in terms of packets, that must be 1052 exceeded to trigger a report in the next 1053 reporting interval." 1054 ::= { frwkFeedbackIfTrafficThresholdEntry 2 } 1056 frwkFeedbackIfTrafficThresholdByteThreshold OBJECT-TYPE 1057 SYNTAX Integer64 1058 STATUS current 1059 DESCRIPTION 1060 "The threshold, in terms of bytes, that must be 1061 exceeded to trigger a report in the next 1062 reporting interval." 1063 ::= { frwkFeedbackIfTrafficThresholdEntry 3 } 1065 -- 1066 -- All Selection classes are in the separate 1067 -- FrwkFeedbackSelectionClasses group 1068 -- 1070 FrwkFeedbackSelectionClasses 1071 OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 3 } 1073 -- 1074 -- The Set WatchPoint Table 1075 -- 1077 frwkFeedbackSetWatchPointTable OBJECT-TYPE 1078 SYNTAX SEQUENCE OF FrwkFeedbackSetWatchPointEntry 1079 PIB-ACCESS Install 1080 STATUS current 1081 DESCRIPTION 1082 "This class defines a selection criteria that 1083 identifies a specific processing point to watch 1084 for the desired usage. This selection criteria 1085 may be useful in PIBs that are designed using a 1086 datapath approach where the policies are linked 1087 and can be reused within the PIB." 1089 ::= { frwkFeedbackSelectionClasses 1} 1091 frwkFeedbackSetWatchPointEntry OBJECT-TYPE 1092 SYNTAX FrwkFeedbackSetWatchPointEntry 1093 STATUS current 1094 DESCRIPTION 1095 "Defines the attributes the of the selection 1096 criteria identifying a specific policy 1097 where to monitor the associated usage." 1098 PIB-INDEX { frwkFeedbackSetWatchPointId } 1100 ::= {frwkFeedbackSetWatchPointTable 1} 1102 FrwkFeedbackSetWatchPointEntry ::= SEQUENCE { 1103 frwkFeedbackSetWatchPointId InstanceID, 1104 frwkFeedbackSetWatchPointPolicyPRID Prid, 1106 } 1108 frwkFeedbackSetWatchPointId OBJECT-TYPE 1109 SYNTAX InstanceId 1110 STATUS current 1111 DESCRIPTION 1112 "Arbitrary integer index that uniquely identifies 1113 an instance of the class." 1114 ::= { frwkFeedbackSetWatchPointEntry 1 } 1116 frwkFeedbackSetWatchPointPolicyPRID OBJECT-TYPE 1117 SYNTAX Prid 1118 STATUS current 1119 DESCRIPTION 1120 "The PRID of the enforcement policy instance where 1121 the associated usage is to be monitored." 1123 ::= { frwkFeedbackSetWatchPointEntry 2 } 1125 -- 1126 -- DPE Selection Class 1127 -- 1129 frwkFeedbackDPESelectionTable OBJECT-TYPE 1130 SYNTAX SEQUENCE OF frwkFeedbackDPESelectionEntry 1131 PIB-ACCESS Install 1132 STATUS current 1133 DESCRIPTION 1134 "This class defines a selection criteria that 1135 identifies a specific data path element to collect 1136 usage information" 1138 ::= { frwkFeedbackSelectionClasses 2} 1140 frwkFeedbackDPESelectionEntry OBJECT-TYPE 1141 SYNTAX frwkFeedbackDPESelecyionEntry 1142 STATUS current 1143 DESCRIPTION 1144 "Defines the attributes the of the selection 1145 criteria identifying a specific policy 1146 where to monitor the associated usage." 1147 PIB-INDEX { frwkFeedbackDPESelectionId } 1148 UNIQUENESS { frwkFeedbackDPESelectionDataPathElement, 1149 frwkFeedbackDPESelectionInterface, 1150 frwkFeedbackDPESelectionIfDirection } 1152 ::= {frwkFeedbackDPESelectionTable 1} 1154 frwkFeedbackDPESelectionEntry ::= SEQUENCE { 1155 frwkFeedbackDPESelectionId InstanceId, 1156 frwkFeedbackDPESelectionDataPathElement Prid, 1157 frwkFeedbackDPESelectionInterface Prid, 1158 frwkFeedbackDPESelectionIfDirection IfDirection 1159 } 1161 frwkFeedbackDPESelectionId OBJECT-TYPE 1162 SYNTAX InstanceId 1163 STATUS current 1164 DESCRIPTION 1165 "Arbitrary integer index that uniquely identifies 1166 an instance of the class." 1167 ::= { frwkFeedbackDPESelectionEntry 1 } 1169 frwkFeedbackDPESelectionDataPathElement OBJECT-TYPE 1170 SYNTAX Prid 1171 STATUS current 1172 DESCRIPTION 1173 "The PRID of the element in the data path that we 1174 want to collect usage information from. This element 1175 must be part of the data path assigned to the 1176 interface/direction combination referenced in this 1177 object." 1178 ::= { frwkFeedbackDPESelectionEntry 2 } 1180 frwkFeedbackDPESelectionInterface OBJECT-TYPE 1181 SYNTAX Prid 1182 STATUS current 1183 DESCRIPTION 1184 "The PRID of a frwkIfRoleCombo instance, uniquely 1185 identifying a specific interface" 1186 ::= { frwkFeedbackDPESelectionEntry 3 } 1188 frwkFeedbackDPESelectionIfDirection OBJECT-TYPE 1189 SYNTAX IfDirection 1190 STATUS current 1191 DESCRIPTION 1192 "The direction (ingress/egress) that to which the DPE 1193 is attached that we want to match." 1194 ::= { frwkFeedbackDPESelectionEntry 4 } 1196 -- 1197 -- DPE Selection Query Class 1198 -- 1200 frwkFeedbackDPESelectionQueryTable OBJECT-TYPE 1201 SYNTAX SEQUENCE OF frwkFeedbackDPESelectionQueryEntry 1202 PIB-ACCESS Install 1203 STATUS current 1204 DESCRIPTION 1205 "This class defines a selection criteria that 1206 identifies a set of assignments of a data path element 1207 based on an entry in the Data Path Table 1208 Each matched assignment will collect and report usage 1209 independently, so this selection criteria should be 1210 combined with a Usage PRC that includes an interface 1211 reference." 1213 ::= { frwkFeedbackSelectionClasses 3} 1215 frwkFeedbackDPESelectionQueryEntry OBJECT-TYPE 1216 SYNTAX frwkFeedbackDPESelectionQueryEntry 1217 STATUS current 1218 DESCRIPTION 1219 "Defines the attributes the of the selection 1220 criteria identifying a specific policy 1221 where to monitor the associated usage." 1222 PIB-INDEX { frwkFeedbackDPESelectionQueryId } 1223 UNIQUENESS { frwkFeedbackDPESelectionQueryDataPath, 1224 FrwkFeedbackDPESelectionQueryDataPathElement } 1226 ::= {frwkFeedbackDPESelectionQueryTable 1} 1228 frwkFeedbackDPESelectionQueryEntry ::= SEQUENCE { 1229 frwkFeedbackDPESelectionQueryId InstanceId, 1230 frwkFeedbackDPESelectionQueryDataPath Prid, 1231 frwkFeedbackDPESelectionQueryDataPathElement Prid 1232 } 1234 frwkFeedbackDPESelectionQueryId OBJECT-TYPE 1235 SYNTAX InstanceId 1236 STATUS current 1237 DESCRIPTION 1238 "Arbitrary integer index that uniquely identifies 1239 an instance of the class." 1240 ::= { frwkFeedbackDPESelectionQueryEntry 1 } 1242 frwkFeedbackDPESelectionQueryDataPath OBJECT-TYPE 1243 SYNTAX Prid 1244 STATUS current 1245 DESCRIPTION 1246 "The PRID of a Data Path instance, identifying a 1247 group of data path assignments." 1248 ::= { frwkFeedbackDPESelectionQueryEntry 2 } 1250 frwkFeedbackDPESelectionQueryDataPathElement OBJECT-TYPE 1251 SYNTAX Prid 1252 STATUS current 1253 DESCRIPTION 1254 "The PRID of the element in the data path that we 1255 want to collect usage information from. This element 1256 must be part of the data path referenced from the 1257 frwkFeedbackDPESelectionQueryDataPath field." 1258 ::= { frwkFeedbackDPESelectionQueryEntry 3 } 1260 END 1262 5 Security Considerations 1264 The feedback information is sensitive and requires that authorized 1265 messaging occur between the PEP and the PDP. This protection can 1266 be accomplished with IPSEC between the PEP and the PDP or using 1267 the security mechanisms described in the base COPS protocol. 1269 6 Acknowledgements 1270 The authors would like to thank Dave Durham and Russell Fenger of 1271 Intel and John K. Gallant of WorldCom for their contribution to 1272 this document. 1274 7 Authors' Addresses 1276 Diana Rawlins 1277 WorldCom 1278 901 International Parkway 1279 Richardson, Texas 75081 1280 Phone: 972-729-1044 1281 Email: Diana.Rawlins@wcom.com 1283 Amol Kulkarni 1284 JF3-206 1285 2111 NE 25th Ave 1286 Hillsboro, Oregon 97124 1287 Phone: 503-712-1168 1288 Email: amol.kulkarni@intel.com 1290 Kwok Ho Chan 1291 Nortel Networks, Inc. 1292 600 Technology Park Drive 1293 Billerica, MA 01821 USA 1294 Phone: 978-288-8175 1295 Email: khchan@nortelnetworks.com 1297 Martin Bokaemper 1298 Unisphere Networks 1299 700 Silver Seven Road 1300 Kanata, ON, K2V 1C3, Canada 1301 Phone: 613-591-2735 1302 Email: mbokaemper@unispherenetworks.com 1304 Dinesh G Dutt 1305 Cisco Systems, Inc. 1306 170 Tasman Dr. 1307 San Jose, CA 95134-1706 1308 Phone: 408-527-0955 1309 Email: ddutt@cisco.com 1311 8 References 1313 [FEEDBACKfWK] Rawlins, D., Kulkarni, A., "Framework of COPS-PR 1314 Policy Usage Feedback", draft-ietf-rap-feedback-frwk-01.txt, 1315 November 2001. 1317 [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., 1318 and A. Sastry, "The COPS (Common Open Policy Service) Protocol" 1319 RFC 2748, January 2000. 1321 [3084] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. 1322 Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for 1323 Policy Provisioning," RFC 3084, May 2001. 1325 [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning 1326 Information," RFC 3159, August 2001. 1328 [DIFFSERV-PIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K., 1329 Hahn, S., Bell, C., Smith, A. and Reichmeyer, A. "Differentiated 1330 Services Quality of Service Policy Information Base", draft-ietf- 1331 diffserv-pib-05.txt, November 2001 1333 [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A. 1334 Smith, F. Reichmeyer "Framework Policy Information Base", draft- 1335 ietf-rap-frameworkpib-06.txt, November 2001