idnits 2.17.1 draft-ietf-rap-feedback-fr-pib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 5 longer pages, the longest (page 31) being 64 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 538 has weird spacing: '... usage monit...' == Line 1535 has weird spacing: '...for the purpo...' -- 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 2, 2002) is 7845 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 56, but not defined == Unused Reference: 'COPS-TLS' is defined on line 1515, but no explicit reference was found in the text == Unused Reference: 'DIFFSERV-PIB' is defined on line 1518, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 3084 (ref. 'COPS-PR') ** Downref: Normative reference to an Historic RFC: RFC 3159 (ref. 'SPPI') -- Possible downref: Non-RFC (?) normative reference: ref. 'FR-PIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'FEEDBACKfWK' == Outdated reference: A later version (-11) exists of draft-ietf-rap-cops-tls-04 Summary: 3 errors (**), 0 flaws (~~), 9 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Diana Rawlins 3 Expiration: May 2003 WorldCom 4 File: draft-ietf-rap-feedback-fr-pib-04.txt Amol Kulkarni 5 Intel 6 Kwok Ho Chan 7 Nortel Networks 8 Martin Bokaemper 9 Juniper Networks 10 Dinesh Dutt 11 Cisco 13 Framework Policy Information Base for Usage Feedback 15 Last Updated November 2, 2002 17 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC2026. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other 28 documents at any time. It is inappropriate to use Internet-Drafts 29 as reference material or to cite them other than as "work in 30 progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 Abstract 40 This document describes a Policy Information Base (PIB) to control 41 policy usage collection and reporting in a device. 43 The provisioning classes specified here allow a Policy Decision 44 Point (PDP) to select which policy objects should collect usage 45 information, what information should be collected and when it 46 should be reported. 48 This PIB requires the presence of other PIBs (defined elsewhere) 49 that provide the policy objects that usage information is collected 50 from. 52 Conventions used in this document 53 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 54 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 55 in this document are to be interpreted as described in [RFC-2119]. 57 Table of Contents 59 1 Introduction.....................................................3 60 2 General Concepts.................................................3 61 2.1 Selection, Usage and Linkage Policies..........................3 62 2.2 Normal Operations..............................................4 63 2.2.1 Connection Establishment and Initial Configuration Request...4 64 2.2.2 Unsolicited Reports - Periodic Reporting.....................5 65 2.2.3 Unsolicited Reports - Reporting Conditions...................5 66 2.2.4 Solicited Reports............................................5 67 2.2.5 Resuming and Suspending Periodic Feedback Reporting..........6 68 2.2.6 Failover.....................................................6 69 2.3 Usage Policy and Under-specified Selection Criteria............6 70 3 Summary of the Feedback Framework Policy Information Base........7 71 3.1 SPPI ACCESS clause report-only.................................7 72 3.2 Usage32 and Usage64 textual conventions........................7 73 3.3 Feedback Groups and PRCs.......................................8 74 3.3.1 Feedback Action..............................................8 75 3.3.2 Feedback Action List.........................................9 76 3.3.3 Feedback Linkage Capability..................................9 77 3.3.4 Feedback Linkage.............................................9 78 3.3.5 Feedback Traffic Statistics Threshold.......................10 79 4 The Feedback Framework PIB Module...............................10 80 6 IANA Considerations.............................................29 81 7 Acknowledgements................................................29 82 8 Authors' Addresses..............................................29 83 9 References......................................................30 84 9.1 Normative References..........................................30 85 9.2 Informational References......................................30 86 10 Copyright......................................................30 87 1 Introduction 89 The Framework of COPS-PR Usage Feedback describes the overall 90 approach to policy usage monitoring and reporting. This document 91 defines the specific Policy Information Base (PIB) framework for 92 policy usage feedback. The policy classes for monitoring and 93 reporting policy usage feedback as well as policy classes for 94 controlling reporting intervals, suspension, resumption and 95 solicitation are defined. 97 2 General Concepts 99 2.1 Selection, Usage and Linkage Policies 101 There are three basic types of policy used to define what the PEP is 102 to monitor, record and report. These are the selection criteria 103 policy, the usage policy and the feedback report linkage policy. 105 The selection criteria policy is installed by the PDP. It defines the 106 conditions used by the PEP to monitor and record a usage policy. The 107 selection criteria policy may only be used for defining usage 108 feedback selection criteria. However, the more general case is that a 109 policy that already exists for policy enforcement may also be used 110 for specifying feedback usage selection criteria. An example of this 111 is the frwkRoleCombo instance, which may be used in defining QoS 112 enforcement policies but may also be used to specify conditions on 113 which to base usage - i.e. count the number of packets meeting the 114 criterion of an interface capability set name and role combination. 116 The usage policy defines what attributes are recorded by the PEP. 117 These policies have an ACCESS clause of 'report-only'. Generally, the 118 usage policies specify counts related to a specific action such as a 119 packet being dropped. The feedback framework PIB defines two usage 120 policy classes, frwkFeedbackTraffic and frwkFeedbackIfTraffic. Usage 121 PRCs may be generic, collecting basic statistics, or they may be 122 specific to a particular usage. The PDP decides which PRC(s) best 123 suit(s) its requirements. The PEP may support only one usage feedback 124 PRC, in which case all statistics are gathered using instances of 125 that PRC. Alternatively, the PEP may support multiple usage feedback 126 PRCs. The PDP then decides which PRC to associate with a particular 127 selection criterion. 129 A usage feedback policy and selection policy are tightly associated 130 with one another. A third policy, the frwkFeedbackLinkTable, is used 131 to associate, or provide a linkage for the selection and usage 132 policies. The frwkFeedbackLinkTable also specifies when to report the 133 usage feedback. The frwkFeedbackLinkTable entry permits the same 134 selection criteria instance to be re-used for various usage feedback 135 policies. The frwkFeedbackLinkTable contains the value of the 136 selection criteria instance as well as the value of the usage 137 feedback PRC. 139 ----------------- ------------------ ----------------- 140 | | | | | | 141 | Select Criteria | |Linkage Instance | |Usage Instance | 142 | | |-instance ID | |- instance ID | 143 | -instance ID |<--|-PRID of selection|--->|- PRID of Linkage| 144 | -conditions... | |-PRC of usage | |- counts... | 145 | | | | | | 146 ----------------- ------------------ ----------------- 148 Figure 1 150 Figure 1 illustrates the relationship between the selection criteria, 151 linkage and usage policies. 153 The PDP is not aware of the instance identifier of the usage feedback 154 policy when installing the selection criteria and feedback linkage 155 policies. The usage feedback policy is instantiated on the PEP by the 156 installation of a feedback report linkage and the PEP designates the 157 instance identifier. The usage feedback policy class always contains 158 an attribute of type ReferenceId that contains the instance value of 159 the associated frwkFeedbackLinkTable instance installed by the PDP. 160 An example of this is the attribute frwkFeedbackTrafficLinkRef 162 2.2 Normal Operations 164 2.2.1 Connection Establishment and Initial Configuration Request 166 The Accounting Timer object in the COPS Connection Accept message 167 contains the minimum number of seconds between reporting intervals as 168 described in [COPS] and [FEEDBACKfWK]. This is used as the basic unit 169 of measurement in defining intervals for specific usage policies with 170 the frwkFeedbackLinkInterval attribute. 172 The PEP notifies the PDP of the selection criteria policy classes and 173 usage policy classes it supports during the initial request for 174 configuration data using frwkPRCSupport instances [FR-PIB]. The PEP 175 also indicates whether it supports the frwkFeedbackLinkTable as well. 177 The PDP responds to the initial request for configuration with a 178 DECISION that installs policies. The PDP may also specify maximum 179 reporting intervals associated with each of the usage policies. This 180 is done with the frwkFeedbackLinkInterval attribute in the 181 frwkFeedbackLink class. It may also specify reporting thresholds by 182 including an instance of a threshold class (e.g. 183 frwkFeedbackTrafficThreshold) in the decision. The PEP monitors and 184 records the usage per the conditions defined by its associated 185 selection criteria policy. Periodically the PEP reports the usage 186 with a REPORT message or provides a REPORT when solicited by the PDP. 187 The PDP solicits usage feedback with the frwkFeedbackActionIndicator 188 attribute of the frwkFeedbackAction class. 190 2.2.2 Unsolicited Reports - Periodic Reporting 192 Reporting may be periodic in nature and unsolicited. The intervals 193 at which the unsolicited reports are provided by the PEP are defined 194 in the specific Linkage policies. The defined intervals are based on 195 the number of seconds specified by the PDP in the ACCT Timer value. 196 The PDP may specify that the associated usage instance be included 197 in a periodic unsolicited report only if the threshold is reached 198 and/or if the usage value has changed from the previous reporting 199 interval. 201 There are cases when the PEP must supply unsolicited feedback 202 reports that may not fall on an interval boundary. The PEP MUST 203 provide an unsolicited REPORT containing all defined usage instances 204 just prior to the PEP issuing a Delete Request State and just prior 205 to the PEP de-activating a PIB instance context. 207 2.2.3 Unsolicited Reports - Reporting Conditions 209 Periodic unsolicited reports for individual usage feedback instances 210 can be suppressed by specifying additional conditions in the 211 frwkFeedbackLink instances. Supported conditions are: 212 ChangeOnly 213 If this flag is set in the frwkFeedbackLinkFlags attribute, the 214 associated usage instance is only included in a periodic 215 unsolicited report if its value changed since the last 216 unsolicited report. 218 Threshold 219 If this flag is set in the frwkFeedbackLinkFlags attribute, the 220 associated usage instance is only included in a periodic 221 unsolicited report, if the threshold condition referenced in 222 the frwkLinkThreshold field evaluates successfully for the 223 associated usage instance. 225 Both conditions can be combined in one frwkFeedbackLinkUsage object. 226 In this case both conditions need to succeed for the usage instance 227 to be reported. 229 Unsolicited reports triggered by a Delete Request State or the 230 deactivation of a PIB instance are not subject to these conditions - 231 all usage objects must be included in these cases. 233 2.2.4 Solicited Reports 235 The PDP may solicit policy usage feedback by issuing an unsolicited 236 Decision containing the frwkFeedbackActionIndicator set to 237 'solicitReport'. The PEP is to provide a solicited REPORT feedback 238 containing usage feedback. The PEP shall continue to provide 239 periodic feedback as well at the specified intervals established at 240 client connection acceptance. 242 The reporting conditions (ChangeOnly and Threshold) do not affect 243 solicited reports - all requested usage instances must be included. 245 2.2.5 Resuming and Suspending Periodic Feedback Reporting 247 The PDP may suspend usage monitoring and tracking at the PEP with the 248 frwkFeedbackActionIndicator set to 'suspendMonitoringAndReports'. The 249 PEP must stop tracking usage information and must not issue any 250 feedback reports. The PDP may only suspend feedback reporting by 251 setting the ActionIndicator to 'suspendReports'. The PEP must cease 252 sending unsolicited reports but is to continue monitoring and 253 tracking usage. The PDP may resume the sending of feedback reports 254 and may resume usage monitoring by setting the ActionIndicator to 255 'resume'. 257 The PDP may suspend or resume all usage instances or the PDP may 258 specify one or more instances that are to be suspended or resumed. 259 The frwkFeedbackActionList attribute contains a tag identifier that 260 references a list of one or more frwkFeedbackActionList instances. 262 The PDP may halt usage monitoring, tracking and reporting of usage 263 policies by removing the associated Linkage entry. 265 2.2.6 Failover 267 In the event the connection is lost between the PEP and PDP, the PEP 268 continues to track usage information as long as it continues to 269 operate with the installed policy. When the locally installed policy 270 at the PEP expires, the usage policy data also expires. 272 Upon successful reconnection where the PEP is still caching policy, 273 the PDP indicates to the PEP that the PEP may resume sending of the 274 COPS accounting type report messages. The PDP does this by issuing an 275 unsolicited decision containing the frwkFeedbackResumeIndicator set 276 to 'resume'. The PEP should resume reporting at the next appropriate 277 feedback interval established upon the acceptance of the re- 278 connection. The PDP is aware of the request state Handle(s) and the 279 supported PRCs either through the state synchronization mechanism or 280 because the PDP considers itself synchronized with the PEP upon 281 reconnection. 283 2.3 Usage Policy and Under-specified Selection Criteria 285 Some of the usage policy objects created in the PEP with COPS-PR can 286 be used by the PEP multiple times - they effectively act as 287 templates for the objects created by the PEP. COPS-PR only has the 288 identity (OID) of the object that is shared between all the 289 assignments the PEP created, however it is desirable to collect 290 usage information for each of the derived objects individually. 292 This capability is achieved in the feedback framework PIB by 293 distributing additional information to qualify a specific assignment 294 of an object between the selection criteria PRC and the feedback 295 usage PRC. 297 A selection criteria PRC that refers to a shared object but contains 298 no qualifying information selects all of the object's assignments. 299 Such a selection criteria PRC SHOULD be combined with a feedback 300 usage PRC that includes all the necessary information to identify a 301 specific assignment - a single selection criteria policy can then 302 result in the generation of many feedback usage objects, one for 303 each derived object. 305 If the selection criteria PRC contains all the required qualifying 306 attributes for a specific assignment, it is combined with a feedback 307 usage PRC that only contains the desired metrics but no additional 308 attributes. 310 Example: 312 A frwkRoleCombo instance may be used as a selection criteria, 313 identifying a set of interfaces through their the role 314 combination and capability set. If it is desired to get per- 315 interface traffic statistics, the usage PRC has to include an 316 additional attribute to qualify the specific interface. 318 This could be achieved by linking the frwkFeedbackIfTraffic class 319 with a frwkRoleCombo instance in a frwkFeedbackLink instance. 320 Multiple frwkFeedbackIfTraffic instances will be created by the 321 PEP, one for each interface selected by the frwkRoleCombo 322 instance. The frwkFeedbackIfTraffic class contains the 323 frwkFeedbackIfTrafficIfIndex attribute that allows the PDP to 324 identify each interface's individual counters when the PEP 325 reports the frwkFeedbackIfTraffic instances. 327 If traffic usage collection is only desired for an individual 328 interface, a selection criteria should be used that qualifies the 329 interface completely, for example a frwkIfRoleCombo instance. 330 In this case it can be linked to the usage class that has no 331 additional qualifying attributes, frwkFeedbackTraffic. 333 3 Summary of the Feedback Framework Policy Information Base 335 3.1 SPPI ACCESS clause report-only 337 The selection criteria and linkage policy classes follow the 338 definitions specified by [SPPI]. This structure specifies well- 339 defined policy classes and their instances residing in a common, 340 virtual repository [FR-PIB]. The additional PIB-ACCESS clause 341 attribute of "report-only" denotes the usage policy class reported by 342 the PEP. 344 3.2 Usage32 and Usage64 textual conventions 345 The SPPI does not support the Counter32/64 textual conventions (TC) 346 of SNMP - for feedback collection two similar textual conventions 347 have been defined in this PIB: Usage32 and Usage64. 349 In addition to the differential functionality of 'Counter', where 350 only the difference between two samples generally carries 351 information, a single value of a 'Usage' attribute usually provides 352 absolute information, since 353 - its initial value is known (0) 354 - no wrap-around events should occur 355 - the time or event when the initial value was set should be 356 available directly or indirectly from other objects. 358 When 'Usage' attributes are defined in a PRC, events that could 359 cause a reset of the attribute to it's initial value should be 360 defined in the description as well as the mechanism that allows the 361 PDP to detect the time of the last reset. 363 No usual COPS activity however should cause the reset of a Usage 364 attribute. In the case of a suspension of monitoring activity 365 (frwkFeedbackActionIndicator set to 'suspendMonitoringAndReports'), 366 'Usage' attributes should keep their values and continue counting 367 after monitoring is resumed. 369 3.3 Feedback Groups and PRCs 371 These policy classes defined in this PIB are common to account type 372 reporting for various technologies and apply to ALL SUBJECT- 373 CATEGORIES. The policy classes are divided into three new groups, 374 namely, The Feedback Report Group, The Feedback Usage Group and The 375 Feedback Selection Group. 377 The policy classes in the Feedback Report Group are: 378 - Feedback Action 379 - Feedback Action List 380 - Feedback Selection Usage Combination Capability 381 - Feedback Linkage 382 - Feedback Traffic Statistics Threshold 384 The policy classes in the Feedback Usage Group are: 385 - Feedback Traffic 386 - Feedback Interface Traffic 388 The policy class in the Feedback Selection Group is: 389 - Feedback RoleCombo Filter Selection 391 3.3.1 Feedback Action 393 The Feedback Action class contains the attributes that specify 394 action that the PEP is to take regarding policy usage, monitoring 395 and tracking. The PDP may suspend usage monitoring and periodic 396 reporting, suspend periodic reporting only, resume usage and 397 periodic reporting or solicit immediate reporting. The action may 398 affect all feedback policies or be associated with one or more 399 frwkFeedbackLink instances. 401 The frwkFeedbackActionIndicator attribute defines the action. The 402 frwkFeedbackActionPri attribute indicates whether the action applies 403 to all of the usage policies or to a list. The 404 frwkFeedbackActionList attribute is the identifier of the list of 405 Linkage policy instances to which the action is to be applied. 407 The PDP can solicit the PEP for immediate usage feedback. The PEP 408 shall respond with a solicited report containing the usage feedback. 410 The PDP can direct the resumption of usage monitoring and reporting 411 per the defined intervals. For example, the PEP may have re- 412 connected to a PDP and has cached usage policies. The PDP indicates 413 to the PEP to resume usage tracking and monitoring and to send all 414 the cached usage policy. The PEP shall respond at the next 415 appropriate interval with an unsolicited report containing the usage 416 feedback. 418 The PDP can suspend the monitoring of usage policy. The PEP 419 maintains the current usage that has been monitored but discontinues 420 any further monitoring until the PDP directs the PEP to resume 421 monitoring in a subsequent Decision. 423 The PDP can also suspend just the reporting of usage, but not 424 interrupt the monitoring and tracking of usage. The PEP shall 425 discontinue sending Report messages with usage feedback until the 426 PDP directs the PEP to resume. The PEP then begins reporting the 427 usage feedback at the next interval. 429 3.3.2 Feedback Action List 431 This class defines sets of linkage instances that can be referred to 432 from the frwkFeedbackActionList attribute. 434 3.3.3 Feedback Linkage Capability 436 This class defines the valid selection criteria PRC, usage PRC and 437 threshold PRC combinations supported by the PEP. 439 3.3.4 Feedback Linkage 441 This class links the selection criteria instance with the usage 442 class. This table permits the reuse of a selection criteria instance 443 for multiple usage policies. 445 The linkage table also permits the definition of a maximum reporting 446 interval to use when issuing the COPS accounting type reports for the 447 usage instance. A value of 0 in this attribute indicates that the 448 usage policy must be solicited. 450 3.3.5 Feedback Traffic Statistics Threshold 452 This class is used to provide threshold values for the attributes 453 described in the traffic usage classes below. 455 3.3.6 Feedback Traffic 457 This class includes the packet counts, byte counts and a reference to 458 the associated Linkage instance. 460 3.3.7 Feedback Interface Traffic 462 This class is similar to the previous Feedback Traffic class, except 463 that it includes an additional reference to an interface index. This 464 class should be used with a selection criteria instance that matches 465 an element that is assigned to multiple interfaces. The interface 466 field can be used to associate the instances of this table with the 467 specific element's assignment. 469 3.3.8 Feedback RoleCombo Filter Selection 471 This class is used as selection criteria based on role combination, 472 capability set and a filter instance. 474 4 The Feedback Framework PIB Module 476 FEEDBACK-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN 478 IMPORTS 479 pib, Unsigned32, Unsigned64, Integer32, 480 MODULE-IDENTITY, OBJECT-TYPE, MODULE-COMPLIANCE, OBJECT-GROUP 481 FROM COPS-PR-SPPI 482 TruthValue, TEXTUAL-CONVENTION 483 FROM SNMPv2-TC 484 InstanceId, ReferenceId, Prid, 485 TagId, TagReferenceId 486 FROM COPS-PR-SPPI-TC 487 PrcIdentifierOid, PrcIdentifierOidOrZero 488 FROM FRAMEWORK-TC-PIB 489 frwkRoleComboEntry 490 FROM FRAMEWORK-PIB 491 InterfaceIndex 492 FROM IF-MIB; 493 frwkFeedbackPib MODULE-IDENTITY 494 SUBJECT-CATEGORIES { all } 495 LAST-UPDATED "200210281000Z" 496 ORGANIZATION "IETF RAP WG" 497 CONTACT-INFO "IETF RAP WG 498 Email: rap@ops.ietf.org 500 Diana Rawlins 501 WorldCom 502 901 International Parkway 503 Richardson, TX 75081 504 Phone: 972 729 1044 505 Email: diana.rawlins@wcom.com 507 Amol Kulkarni 508 JF3-206 509 2111 NE 25th Ave 510 Hillsboro, Oregon 97124 511 Phone: 503-712-1168 512 Email: amol.kulkarni@intel.com 514 Kwok Ho Chan 515 Nortel Networks. 516 600 Technology Park Drive 517 Billerica, MA 01821 USA 518 Phone: 978-288-8175 519 Email: khchan@nortelnetworks.com 521 Martin Bokaemper 522 Juniper Networks 523 700 Silver Seven Road 524 Kanata, ON, K2V 1C3, Canada 525 Phone: 613-591-2735 526 Email: mbokaemper@juniper.net 528 Dinesh G Dutt 529 Cisco Systems, Inc. 530 170 Tasman Dr. 531 San Jose, CA 95134-1706 532 Phone: 408-527-0955 533 Email: ddutt@cisco.com" 535 DESCRIPTION 536 "The PIB module containing the base set of policy rule 537 classes that are required for support of all policy 538 usage monitoring, tracking and reporting policies" 539 REVISION "200210280000Z" 540 DESCRIPTION 541 "Initial version, published in RFC xxxx." 542 -- xxxx to be assigned by RFC editor 544 ::= { pib xx } -- xx will be assigned by IANA, according 545 -- to RFC 3159 (IANA considerations) 546 -- 547 -- Textual Conventions 548 -- 550 Usage32 ::= TEXTUAL-CONVENTION 551 STATUS current 552 DESCRIPTION 553 "The Usage32 type represents a non-negative integer 554 which monotonically increases. 555 Usage32 initial value is 0 and the object-type using 556 Usage32 needs to specify when it is initialized. 558 The Usage32 type is intended to reflect the absolute 559 number of counted events, so that even a new PDP 560 after a COPS reconnect can use the value directly. 562 If there is the possibility that the maximum Usage32 563 value of 2^32-1 is exceeded during the lifetime 564 of the Usage32 object, the larger Usage64 type 565 should be used. 567 If conditions other than the reset of the COPS 568 subsystem exist that disrupt the monotonic 569 characteristics of Usage32, these conditions and a 570 method how to detect their presence should be 571 specified in the description of the object-type using 572 Usage32 or its enclosing object-types (e.g. the 573 Entry or Table object-type of the Usage32 574 object-type). 576 Whenever the monotonic increase of Usage32 is violated, 577 it should be reset to 0 and the fact that this occurred 578 should be indicated through an appropriate mechanism, 579 for example a corresponding object of type TimeStamp 580 or TimeAndDate." 581 SYNTAX Unsigned32 583 Usage64 ::= TEXTUAL-CONVENTION 584 STATUS current 585 DESCRIPTION 586 "The Usage64 type represents a non-negative integer 587 which monotonically increases. 588 Usage64 initial value is 0 and the object-type using 589 Usage64 needs to specify when it is initialized. 591 The Usage64 type is intended to reflect the absolute 592 number of counted events, so that even a new PDP 593 after a COPS reconnect can use the value directly. 595 The lifetime of the Usage64 object should be defined 596 in a way that ensures the maximum Usage64 value of 597 2^64-1 is never exceeded. 599 If conditions other than the reset of the COPS 600 subsystem exist that disrupt the monotonic 601 characteristics of Usage64, these conditions and a 602 method how to detect their presence should be 603 specified in the description of the object-type using 604 Usage64 or its enclosing object-types (e.g. the 605 Entry or Table object-type of the Usage64 606 object-type). 608 Whenever the monotonic increase of Usage64 is violated, 609 it should be reset to 0 and the fact that this occurred 610 should be indicated through an appropriate mechanism, 611 for example a corresponding object of type TimeStamp 612 or TimeAndDate." 613 SYNTAX Unsigned64 615 -- 616 -- The feedback report group 617 -- 619 frwkFeedbackGroupClasses 620 OBJECT IDENTIFIER ::= { frwkFeedbackPib 1 } 622 -- 623 -- Feedback Action Table 624 -- 626 frwkFeedbackActionTable OBJECT-TYPE 627 SYNTAX SEQUENCE OF FrwkFeedbackActionEntry 628 PIB-ACCESS install 629 STATUS current 630 DESCRIPTION 631 "This class represents commands that the PDP sends to 632 suspend, resume or solicit collection or reporting of 633 usage data." 635 ::= { frwkFeedbackGroupClasses 1} 637 frwkFeedbackActionEntry OBJECT-TYPE 638 SYNTAX FrwkFeedbackActionEntry 639 STATUS current 640 DESCRIPTION 641 "Each frwkFeedbackActionEntry represents a command from 642 the PDP. FrwkFeedbackActionIndicator specifies the 643 command itself while frwkFeedbackActionSpecificPri 644 indicates if all frwkFeedbackLink objects in the system 645 are affected by the command, or just the set that is 646 referenced by frwkFeedbackActionList." 647 PIB-INDEX { frwkFeedbackActionId} 649 ::= { frwkFeedbackActionTable 1} 650 FrwkFeedbackActionEntry ::= SEQUENCE { 651 frwkFeedbackActionId InstanceId, 652 frwkFeedbackActionIndicator INTEGER, 653 frwkFeedbackActionSpecificPri TruthValue, 654 frwkFeedbackActionList TagReferenceId 655 } 657 frwkFeedbackActionId OBJECT-TYPE 658 SYNTAX InstanceId 659 STATUS current 660 DESCRIPTION 661 "An arbitrary integer index that uniquely identifies an 662 instance of the frwkFeedbackAction class." 664 ::= { frwkFeedbackActionEntry 1} 666 frwkFeedbackActionIndicator OBJECT-TYPE 667 SYNTAX INTEGER { 668 suspendMonitoringAndReports(0), 669 suspendReports(1), 670 resume(2), 671 solicitReport(3) 672 } 673 STATUS current 674 DESCRIPTION 675 "The value indicates if the PEP is to send cached 676 usage policies via COPS accounting type report 677 messages. 678 The enumeration values are: 679 (0) suspendMonitoringAndReports 680 (1) suspendReports 681 (2) resume 682 (3) solicitReport " 684 ::= { frwkFeedbackActionEntry 2 } 686 frwkFeedbackActionSpecificPri OBJECT-TYPE 687 SYNTAX TruthValue 688 STATUS current 689 DESCRIPTION 690 "A value of 0 indicates that the 691 frwkFeedbackActionList attribute should be ignored, 692 and the action applied to all policies. A value of 693 1 indicates that the action entry has a specific 694 list of policies to which it is to be applied." 695 ::= { frwkFeedbackActionEntry 3} 697 frwkFeedbackActionList OBJECT-TYPE 698 SYNTAX TagReferenceId 699 PIB-TAG { frwkFeedbackActionListTag } 700 STATUS current 701 DESCRIPTION 702 "Identifies a set of frwkFeedbackActionList 703 instances that this action should affect." 704 ::= { frwkFeedbackActionEntry 4} 706 -- 707 -- Feedback Action List Table 708 -- 710 frwkFeedbackActionListTable OBJECT-TYPE 711 SYNTAX SEQUENCE OF FrwkFeedbackActionListEntry 712 PIB-ACCESS install 713 STATUS current 714 DESCRIPTION 715 "This class defines groups of linkage instances. 716 Groups can be referenced by commands sent by the 717 PDP in a frwkFeedbackActionEntry -in this case the 718 command affects all linkage instances that are part 719 of the group." 720 ::= { frwkFeedbackGroupClasses 2} 722 frwkFeedbackActionListEntry OBJECT-TYPE 723 SYNTAX FrwkFeedbackActionListEntry 724 STATUS current 725 DESCRIPTION 726 "Each instance associates a linkage instance with a 727 specific ActionListGroup." 729 PIB-INDEX {frwkFeedbackActionListId } 730 UNIQUENESS { frwkFeedbackActionListTag, 731 frwkFeedbackActionListRefID 732 } 733 ::= { frwkFeedbackActionListTable 1} 735 FrwkFeedbackActionListEntry::= SEQUENCE { 736 frwkFeedbackActionListId InstanceId, 737 frwkFeedbackActionListTag TagId, 738 frwkFeedbackActionListRefID ReferenceId 739 } 741 frwkFeedbackActionListId OBJECT-TYPE 742 SYNTAX InstanceId 743 STATUS current 744 DESCRIPTION 745 "Arbitrary integer index that uniquely 746 identifies an instance of the class." 748 ::= { frwkFeedbackActionListEntry 1 } 750 frwkFeedbackActionListTag OBJECT-TYPE 751 SYNTAX TagId 752 STATUS current 753 DESCRIPTION 754 "Represents the binding between the Action 755 table entry and the Action List table entries" 756 ::= { frwkFeedbackActionListEntry 2 } 758 frwkFeedbackActionListRefID OBJECT-TYPE 759 SYNTAX ReferenceId 760 PIB-REFERENCES { frwkFeedbackLinkEntry } 761 STATUS current 762 DESCRIPTION 763 "The ReferenceID of the linkage instance(s) 764 belonging to the list of instances identified 765 by the list id upon which the suspend, resume 766 or solicit action is directed." 768 ::= { frwkFeedbackActionListEntry 3 } 770 -- 771 -- The Feedback Link Capability Table 772 -- 774 frwkFeedbackLinkCapsTable OBJECT-TYPE 775 SYNTAX SEQUENCE OF FrwkFeedbackLinkCapsEntry 776 PIB-ACCESS notify 777 STATUS current 778 DESCRIPTION 779 "Instances of the frwkFeedbackLink class reference 780 instances of selection and threshold classes and a 781 usage class. 782 This class allows the PEP to communicate valid 783 combinations of these three classes to the PDP." 784 ::= { frwkFeedbackGroupClasses 3} 786 frwkFeedbackLinkCapsEntry OBJECT-TYPE 787 SYNTAX FrwkFeedbackLinkCapsEntry 788 STATUS current 789 DESCRIPTION 790 "The attributes of this class identify valid 791 combinations of selection criteria, usage and 792 threshold classes for feedback." 793 PIB-INDEX { frwkFeedbackLinkCapsId } 794 UNIQUENESS { 795 frwkFeedbackLinkCapsSelection, 796 frwkFeedbackLinkCapsUsage, 797 frwkFeedbackLinkCapsThreshold 798 } 799 ::= {frwkFeedbackLinkCapsTable 1} 801 FrwkFeedbackLinkCapsEntry ::= SEQUENCE { 802 frwkFeedbackLinkCapsId InstanceId, 803 frwkFeedbackLinkCapsSelection PrcIdentifierOid, 804 frwkFeedbackLinkCapsUsage PrcIdentifierOid, 805 frwkFeedbackLinkCapsThreshold PrcIdentifierOidOrZero 806 } 807 frwkFeedbackLinkCapsId OBJECT-TYPE 808 SYNTAX InstanceId 809 STATUS current 810 DESCRIPTION 811 "An arbitrary integer index that uniquely identifies an 812 instance of the frwkFeedbackLinkCaps class." 813 ::= { frwkFeedbackLinkCapsEntry 1} 815 frwkFeedbackLinkCapsSelection OBJECT-TYPE 816 SYNTAX PrcIdentifierOid 817 STATUS current 818 DESCRIPTION 819 "The identifier of a class that is supported by the 820 device for feedback selection in combination with the 821 usage and threshold classes referenced in this 822 instance." 823 ::= { frwkFeedbackLinkCapsEntry 2} 825 frwkFeedbackLinkCapsUsage OBJECT-TYPE 826 SYNTAX PrcIdentifierOid 827 STATUS current 828 DESCRIPTION 829 "The identifier of the usage class that is supported by 830 the PEP in combination with the selection and threshold 831 classes referenced in this instance." 832 ::= { frwkFeedbackLinkCapsEntry 3} 834 frwkFeedbackLinkCapsThreshold OBJECT-TYPE 835 SYNTAX PrcIdentifierOidOrZero 836 STATUS current 837 DESCRIPTION 838 "The identifier of the threshold class that is 839 supported by the PEP in combination with the selection 840 and usage classes referenced in this instance. 841 0.0 is used if this combination does not allow a 842 threshold." 843 ::= { frwkFeedbackLinkCapsEntry 4} 845 -- 846 -- The Feedback Report Linkage Table 847 -- 849 frwkFeedbackLinkTable OBJECT-TYPE 850 SYNTAX SEQUENCE OF FrwkFeedbackLinkEntry 851 PIB-ACCESS install 852 STATUS current 853 DESCRIPTION 854 "This class associates the selection criteria with the 855 usage policy. It also permits the defining of the max 856 interval used for reporting the usage instance." 857 ::= { frwkFeedbackGroupClasses 4} 859 frwkFeedbackLinkEntry OBJECT-TYPE 860 SYNTAX FrwkFeedbackLinkEntry 861 STATUS current 862 DESCRIPTION 863 "This class associates the selection criteria with the 864 usage policy. It also permits the defining of the max 865 interval used for reporting the usage instance." 866 PIB-INDEX { frwkFeedbackLinkId } 867 UNIQUENESS {frwkFeedbackLinkSel, 868 frwkFeedbackLinkUsage } 869 ::= {frwkFeedbackLinkTable 1} 871 FrwkFeedbackLinkEntry ::= SEQUENCE { 872 frwkFeedbackLinkId InstanceId, 873 frwkFeedbackLinkSel Prid, 874 frwkFeedbackLinkUsage PrcIdentifierOid, 875 frwkFeedbackLinkInterval Integer32, 876 frwkFeedbackLinkThreshold Prid, 877 frwkFeedbackLinkFlags BITS 878 } 880 frwkFeedbackLinkId OBJECT-TYPE 881 SYNTAX InstanceId 882 STATUS current 883 DESCRIPTION 884 " An arbitrary integer index that uniquely identifies an 885 instance of the frwkFeedbackLinkTable class." 886 ::= { frwkFeedbackLinkEntry 1} 888 frwkFeedbackLinkSel OBJECT-TYPE 889 SYNTAX Prid 890 STATUS current 891 DESCRIPTION 892 "The PRID of the Policy Class instance as the monitoring 893 point, or the PRID of the selection criteria instance that 894 defines the conditions for monitoring, to be use by the 895 PEP for usage reporting." 897 ::= { frwkFeedbackLinkEntry 2} 899 frwkFeedbackLinkUsage OBJECT-TYPE 900 SYNTAX PrcIdentifierOid 901 STATUS current 902 DESCRIPTION 903 "The identifier of the usage class that the PEP uses to 904 monitor, record and report." 906 ::= { frwkFeedbackLinkEntry 3} 908 frwkFeedbackLinkInterval OBJECT-TYPE 909 SYNTAX Integer32 910 STATUS current 911 DESCRIPTION 912 "Maximum interval in units of the value of the 913 Accounting Timer specified by the PDP in the client 914 accept message. A frwkFeedbackLinkInterval of 1 is 915 equal to the value of the Accounting Timer. This value 916 must be 1 or greater. " 918 ::= { frwkFeedbackLinkEntry 4} 920 frwkFeedbackLinkThreshold OBJECT-TYPE 921 SYNTAX Prid 922 STATUS current 923 DESCRIPTION 924 "The PRID of a threshold class instance. This instance 925 specifies the threshold values for the usage policy." 926 ::= { frwkFeedbackLinkEntry 5} 928 frwkFeedbackLinkFlags OBJECT-TYPE 929 SYNTAX BITS { 930 periodic(0), 931 threshold(1), 932 changeOnly(2) 933 } 934 STATUS current 935 DESCRIPTION 936 "This value indicates the reporting basis of the usage 937 policy. The feed back may be generated on demand, on a 938 periodic basis regardless of a change in value from the 939 previous report, on a periodic basis if a change in 940 value has occurred, or the usage is reported when an 941 identified threshold value in the usage instance has 942 been reached. 943 If the 'periodic' flag is set, the PEP will provide 944 unsolicited reports at the rate specified in 945 frwkFeedbackLinkInterval. 946 If the 'periodic' flag is not set, reports will only be 947 generated when solicited by the PDP. 948 The 'threshold' and 'changeOnly' flags make the 949 periodic reports conditional - these flags only make 950 sense in combination with the 'periodic' flag." 952 ::= { frwkFeedbackLinkEntry 6} 954 -- 955 -- The Threshold class that accompanies the above Usage PRCs 956 -- 958 frwkFeedbackTrafficThresTable OBJECT-TYPE 959 SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresEntry 960 PIB-ACCESS install 961 STATUS current 962 DESCRIPTION 963 "This class defines the threshold attributes 964 corresponding to usage attributes specified in 965 frwkFeedbackTrafficTable, frwkFeedbackIfTrafficTable 966 and other similar usage classes. 968 The usage object is considered to match the threshold 969 condition if at least one of the packet or byte 970 threshold conditions match. 972 The byte and packet thresholds are considered to 973 match, if the threshold is present (not ASN1 NULL) 974 and the corresponding usage value exceeds the 975 threshold." 977 ::= { frwkFeedbackGroupClasses 5} 979 frwkFeedbackTrafficThresEntry OBJECT-TYPE 980 SYNTAX FrwkFeedbackTrafficThresEntry 981 STATUS current 982 DESCRIPTION 983 "Defines the attributes to hold threshold values." 984 PIB-INDEX {frwkFeedbackTrafficThresId} 986 ::= {frwkFeedbackTrafficThresTable 1} 988 FrwkFeedbackTrafficThresEntry ::= SEQUENCE { 989 frwkFeedbackTrafficThresId InstanceId, 990 frwkFeedbackTrafficThresPackets Unsigned64, 991 frwkFeedbackTrafficThresBytes Unsigned64 992 } 994 frwkFeedbackTrafficThresId OBJECT-TYPE 995 SYNTAX InstanceId 996 STATUS current 997 DESCRIPTION 998 "Arbitrary integer index that uniquely identifies 999 an instance of the class." 1000 ::= { frwkFeedbackTrafficThresEntry 1 } 1002 frwkFeedbackTrafficThresPackets OBJECT-TYPE 1003 SYNTAX Unsigned64 1004 STATUS current 1005 DESCRIPTION 1006 "The threshold, in terms of packets, that must be 1007 matched or exceeded to trigger a report in the 1008 next reporting interval. 1009 A value of 0 or a missing value (" 1010 ::= { frwkFeedbackTrafficThresEntry 2 } 1012 frwkFeedbackTrafficThresBytes OBJECT-TYPE 1013 SYNTAX Unsigned64 1014 STATUS current 1015 DESCRIPTION 1016 "The threshold, in terms of bytes, that must be 1017 exceeded to trigger a report in the next reporting 1018 interval." 1019 ::= { frwkFeedbackTrafficThresEntry 3 } 1021 -- 1022 -- All actual usage classes are in the separate 1023 -- frwkFeedbackUsageClasses group 1024 -- 1026 frwkFeedbackUsageClasses 1027 OBJECT IDENTIFIER ::= { frwkFeedbackPib 2 } 1029 -- 1030 -- The generic traffic (byte & packet count) usage class 1031 -- 1033 frwkFeedbackTrafficTable OBJECT-TYPE 1034 SYNTAX SEQUENCE OF FrwkFeedbackTrafficEntry 1035 PIB-ACCESS report-only 1036 STATUS current 1037 DESCRIPTION 1038 "This class defines the usage attributes that the PEP 1039 is to monitor for plain traffic handling elements 1040 like filters. All packets and the bytes contained in 1041 these packets are counted. It also contains the PRID 1042 of the linkage instance associating the selection 1043 criteria instance with the usage instance." 1045 ::= { frwkFeedbackUsageClasses 1} 1047 frwkFeedbackTrafficEntry OBJECT-TYPE 1048 SYNTAX FrwkFeedbackTrafficEntry 1049 STATUS current 1050 DESCRIPTION 1051 "Defines the attributes the PEP is to monitor, 1052 record and report." 1053 PIB-INDEX {frwkFeedbackTrafficId} 1054 UNIQUENESS { frwkFeedbackTrafficLinkRefID } 1056 ::= {frwkFeedbackTrafficTable 1} 1058 FrwkFeedbackTrafficEntry ::= SEQUENCE { 1059 frwkFeedbackTrafficId InstanceId, 1060 frwkFeedbackTrafficLinkRefID ReferenceId, 1061 frwkFeedbackTrafficPacketCount Usage64, 1062 frwkFeedbackTrafficByteCount Usage64 1064 } 1065 frwkFeedbackTrafficId OBJECT-TYPE 1066 SYNTAX InstanceId 1067 STATUS current 1068 DESCRIPTION 1069 "Arbitrary integer index that uniquely identifies 1070 an instance of the class." 1071 ::= { frwkFeedbackTrafficEntry 1 } 1073 frwkFeedbackTrafficLinkRefID OBJECT-TYPE 1074 SYNTAX ReferenceId 1075 PIB-REFERENCES { frwkFeedbackLinkEntry } 1076 STATUS current 1077 DESCRIPTION 1078 "The ReferenceId of the Linkage policy instance used 1079 to base this usage policy instance upon." 1081 ::= { frwkFeedbackTrafficEntry 2 } 1083 frwkFeedbackTrafficPacketCount OBJECT-TYPE 1084 SYNTAX Usage64 1085 STATUS current 1086 DESCRIPTION 1087 "The count of packets handled by the associated 1088 element." 1090 ::= {frwkFeedbackTrafficEntry 3} 1092 frwkFeedbackTrafficByteCount OBJECT-TYPE 1093 SYNTAX Usage64 1094 STATUS current 1095 DESCRIPTION 1096 "The byte count of packets handled by the associated 1097 element." 1098 ::= { frwkFeedbackTrafficEntry 4} 1100 -- 1101 -- The traffic usage class, qualified for an interface 1102 -- 1104 frwkFeedbackIfTrafficTable OBJECT-TYPE 1105 SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficEntry 1106 PIB-ACCESS report-only 1107 STATUS current 1108 DESCRIPTION 1109 "A usage class similar to the basic Traffic class that 1110 also contains a reference to an interface index. This 1111 class should be used with a underspecified selection 1112 criteria entry from the frwkRoleComboTable that matches 1113 an element that can be assigned to multiple interface 1114 indices. The interface field can be used to associate 1115 the instances of this class with the specific element's 1116 assignment." 1117 ::= { frwkFeedbackUsageClasses 2 } 1119 frwkFeedbackIfTrafficEntry OBJECT-TYPE 1120 SYNTAX FrwkFeedbackIfTrafficEntry 1121 STATUS current 1122 DESCRIPTION 1123 "Defines the attributes the PEP is to monitor, 1124 record and report." 1125 PIB-INDEX {frwkFeedbackIfTrafficId} 1126 UNIQUENESS { frwkFeedbackIfTrafficLinkRefID, 1127 frwkFeedbackIfTrafficIfIndex } 1129 ::= {frwkFeedbackIfTrafficTable 1} 1131 FrwkFeedbackIfTrafficEntry ::= SEQUENCE { 1132 frwkFeedbackIfTrafficId InstanceId, 1133 frwkFeedbackIfTrafficLinkRefID ReferenceId, 1134 frwkFeedbackIfTrafficIfIndex InterfaceIndex, 1135 frwkFeedbackIfTrafficPacketCount Usage64, 1136 frwkFeedbackIfTrafficByteCount Usage64 1138 } 1140 frwkFeedbackIfTrafficId OBJECT-TYPE 1141 SYNTAX InstanceId 1142 STATUS current 1143 DESCRIPTION 1144 "Arbitrary integer index that uniquely identifies 1145 an instance of the class." 1146 ::= { frwkFeedbackIfTrafficEntry 1 } 1148 frwkFeedbackIfTrafficLinkRefID OBJECT-TYPE 1149 SYNTAX ReferenceId 1150 PIB-REFERENCES { frwkFeedbackLinkEntry } 1151 STATUS current 1152 DESCRIPTION 1153 "The ReferenceId of the Linkage policy instance used 1154 to base this usage policy instance upon." 1155 ::= { frwkFeedbackIfTrafficEntry 2 } 1157 frwkFeedbackIfTrafficIfIndex OBJECT-TYPE 1158 SYNTAX InterfaceIndex 1159 STATUS current 1160 DESCRIPTION 1161 "The value of this attribute is the ifIndex which is 1162 associated with the specified RoleCombination and 1163 interface capability set name." 1165 ::= { frwkFeedbackIfTrafficEntry 3 } 1166 frwkFeedbackIfTrafficPacketCount OBJECT-TYPE 1167 SYNTAX Usage64 1168 STATUS current 1169 DESCRIPTION 1170 "The count of packets handled by the associated 1171 element." 1172 ::= { frwkFeedbackIfTrafficEntry 4 } 1174 frwkFeedbackIfTrafficByteCount OBJECT-TYPE 1175 SYNTAX Usage64 1176 STATUS current 1177 DESCRIPTION 1178 "The byte count of packets 1179 handled by the associated element." 1180 ::= { frwkFeedbackIfTrafficEntry 5 } 1182 -- 1183 -- All Selection classes are in the separate 1184 -- FrwkFeedbackSelectionClasses group 1185 -- 1187 frwkFeedbackSelectionClasses 1188 OBJECT IDENTIFIER ::= { frwkFeedbackPib 3 } 1190 -- 1191 -- The Role Combination Filter Selection Table 1192 -- 1194 frwkFeedbackRoleFilterSelTable OBJECT-TYPE 1195 SYNTAX SEQUENCE OF FrwkFeedbackRoleFilterSelEntry 1196 PIB-ACCESS install 1197 STATUS current 1198 DESCRIPTION 1199 "A selection class that defines selection of objects 1200 for monitoring based on the role combination, 1201 capability set and a filter." 1202 ::= { frwkFeedbackSelectionClasses 1 } 1204 frwkFeedbackRoleFilterSelEntry OBJECT-TYPE 1205 SYNTAX FrwkFeedbackRoleFilterSelEntry 1206 STATUS current 1207 DESCRIPTION 1208 "Each instance selects a filter on multiple interfaces 1209 that share the same frwkRoleCombo instance." 1210 PIB-INDEX { frwkFeedbackRoleFilterSelId} 1211 UNIQUENESS { frwkFeedbackRoleFilterSelRCombo, 1212 frwkFeedbackRoleFilterSelFilter 1213 } 1215 ::= {frwkFeedbackRoleFilterSelTable 1} 1217 FrwkFeedbackRoleFilterSelEntry ::= SEQUENCE { 1218 frwkFeedbackRoleFilterSelId InstanceId, 1219 frwkFeedbackRoleFilterSelRCombo ReferenceId, 1220 frwkFeedbackRoleFilterSelFilter Prid 1221 } 1223 frwkFeedbackRoleFilterSelId OBJECT-TYPE 1224 SYNTAX InstanceId 1225 STATUS current 1226 DESCRIPTION 1227 "Arbitrary integer index that uniquely identifies 1228 an instance of the class." 1229 ::= { frwkFeedbackRoleFilterSelEntry 1 } 1231 frwkFeedbackRoleFilterSelRCombo OBJECT-TYPE 1232 SYNTAX ReferenceId 1233 PIB-REFERENCES { frwkRoleComboEntry } 1234 STATUS current 1235 DESCRIPTION 1236 "The ReferenceId of the frwkRoleComboTable policy 1237 instance used for selection." 1238 ::= { frwkFeedbackRoleFilterSelEntry 2 } 1240 frwkFeedbackRoleFilterSelFilter OBJECT-TYPE 1241 SYNTAX Prid 1242 STATUS current 1243 DESCRIPTION 1244 "The identifier of a filter instance. Valid classes 1245 are the subclasses of frwkBaseFilter: 1246 - frwkIpFilter 1247 - frwk802Filter 1248 - frwkILabelFilter" 1249 ::= { frwkFeedbackRoleFilterSelEntry 3 } 1251 -- 1252 -- Compliance Section 1253 -- 1255 frwkFeedbackPibConformance 1256 OBJECT IDENTIFIER ::= { frwkFeedbackPib 4 } 1258 frwkFeedbackPibCompliances 1259 OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 1 } 1261 frwkFeedbackPibGroups 1262 OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 2 } 1264 frwkFeedbackPibCompliance MODULE-COMPLIANCE 1265 STATUS current 1266 DESCRIPTION 1267 "Describes the requirements for conformance to the feedback 1268 framework PIB" 1269 MODULE -- this module 1270 MANDATORY-GROUPS { frwkFeedbackLinkCapsGroup, 1271 frwkFeedbackLinkGroup, 1272 frwkFeedbackActionGroup } 1274 GROUP frwkFeedbackActionListGroup 1275 DESCRIPTION 1276 "The frwkFeedbackActionListGroup is mandatory if 1277 actions on subsets linkEntries are to be 1278 supported." 1280 GROUP frwkFeedbackTrafficGroup 1281 DESCRIPTION 1282 "The frwkFeedbackTrafficGroup is mandatory if 1283 monitoring of traffic data is to be supported." 1285 GROUP frwkFeedbackTrafficThresGroup 1286 DESCRIPTION 1287 "The frwkFeedbackTrafficThresGroup is mandatory 1288 if conditional reporting of traffic usage 1289 thresholds is to be supported." 1291 GROUP frwkFeedbackIfTrafficGroup 1292 DESCRIPTION 1293 "The frwkFeedbackIfTrafficGroup is mandatory if 1294 per-interface usage collection of traffic data is 1295 to be supported." 1297 GROUP frwkFeedbackRoleFilterSelGroup 1298 DESCRIPTION 1299 "The frwkFeedbackRoleFilterSelGroup is mandatory 1300 if monitoring of filters referenced through the 1301 frwkRoleCombo class is to be supported." 1303 ::= { frwkFeedbackPibCompliances 1 } 1305 frwkFeedbackLinkCapsGroup OBJECT-GROUP 1306 OBJECTS { 1307 frwkFeedbackLinkCapsId, 1308 frwkFeedbackLinkCapsSelection, 1309 frwkFeedbackLinkCapsUsage, 1310 frwkFeedbackLinkCapsThreshold } 1311 STATUS current 1312 DESCRIPTION 1313 "Objects from the frwkFeedbackLinkCapsTable." 1315 ::= { frwkFeedbackPibGroups 1 } 1317 frwkFeedbackLinkGroup OBJECT-GROUP 1318 OBJECTS { 1319 frwkFeedbackLinkId, 1320 frwkFeedbackLinkSel, 1321 frwkFeedbackLinkUsage, 1322 frwkFeedbackLinkInterval, 1323 frwkFeedbackLinkThreshold, 1324 frwkFeedbackLinkFlags } 1325 STATUS current 1326 DESCRIPTION 1327 "Objects from the frwkFeedbackLinkTable." 1329 ::= { frwkFeedbackPibGroups 2 } 1331 frwkFeedbackActionGroup OBJECT-GROUP 1332 OBJECTS { 1333 frwkFeedbackActionId, 1334 frwkFeedbackActionIndicator, 1335 frwkFeedbackActionSpecificPri, 1336 frwkFeedbackActionList } 1337 STATUS current 1338 DESCRIPTION 1339 "Objects from the frwkFeedbackActionTable." 1341 ::= { frwkFeedbackPibGroups 3 } 1343 frwkFeedbackActionListGroup OBJECT-GROUP 1344 OBJECTS { 1345 frwkFeedbackActionListId, 1346 frwkFeedbackActionListTag, 1347 frwkFeedbackActionListRefID } 1348 STATUS current 1349 DESCRIPTION 1350 "Objects from the frwkFeedbackActionListTable." 1352 ::= { frwkFeedbackPibGroups 4 } 1354 frwkFeedbackTrafficGroup OBJECT-GROUP 1355 OBJECTS { 1356 frwkFeedbackTrafficId, 1357 frwkFeedbackTrafficLinkRefID, 1358 frwkFeedbackTrafficPacketCount, 1359 frwkFeedbackTrafficByteCount } 1360 STATUS current 1361 DESCRIPTION 1362 "Objects from the frwkFeedbackTrafficTable." 1364 ::= { frwkFeedbackPibGroups 5 } 1366 frwkFeedbackTrafficThresGroup OBJECT-GROUP 1367 OBJECTS { 1368 frwkFeedbackTrafficThresId, 1369 frwkFeedbackTrafficThresPackets, 1370 frwkFeedbackTrafficThresBytes } 1371 STATUS current 1372 DESCRIPTION 1373 "Objects from the frwkFeedbackTrafficThresTable." 1374 ::= { frwkFeedbackPibGroups 6 } 1376 frwkFeedbackIfTrafficGroup OBJECT-GROUP 1377 OBJECTS { 1378 frwkFeedbackIfTrafficId, 1379 frwkFeedbackIfTrafficLinkRefID, 1380 frwkFeedbackIfTrafficIfIndex, 1381 frwkFeedbackIfTrafficPacketCount, 1382 frwkFeedbackIfTrafficByteCount } 1383 STATUS current 1384 DESCRIPTION 1385 "Objects from the frwkFeedbackIfTrafficTable." 1387 ::= { frwkFeedbackPibGroups 7 } 1389 frwkFeedbackRoleFilterSelGroup OBJECT-GROUP 1390 OBJECTS { 1391 frwkFeedbackRoleFilterSelId, 1392 frwkFeedbackRoleFilterSelRCombo, 1393 frwkFeedbackRoleFilterSelFilter } 1394 STATUS current 1395 DESCRIPTION 1396 "Objects from the frwkFeedbackRoleFilterSelTable." 1398 ::= { frwkFeedbackPibGroups 8 } 1400 END 1402 5 Security Considerations 1404 This PIB defines structured information that may be sensitive when 1405 transported by the COPS protocol [COPS-PR]. 1407 This PIB does not contain classes that directly contain security 1408 relevant information like passwords or monetary amounts, however 1409 unauthorized access or changes to information defined in this PIB 1410 could compromise network operations or reveal sensitive business or 1411 personal information. 1412 Specifically for the classes: 1413 frwkFeedbackLinkCaps 1414 This class has the ACCESS clause 'notify'. Access to this 1415 information reveals feedback collection capabilities of the COPS 1416 client and malicious changes could affect feedback operation by 1417 misleading the server to generate corrupt feedback configuration. 1418 frwkFeedbackLinkTable, frwkFeedbackAction, frwkFeedbackActionList, 1419 frwkFeedbackTrafficThres, frwkFeedbackRoleFilterSel 1420 These classes have the ACCESS clause 'install' and allow the COPS 1421 server to control feedback collection and reporting on the 1422 client. Access to this information exposes the client's 1423 configuration, malicious changes could disrupt network or 1424 business operations and raise privacy issues. 1425 frwkFeedbackTraffic, frwkFeedbackIfTraffic 1426 These classed have the ACCESS clause 'report-only' and contain 1427 the usage information delivered from the COPS client to the 1428 server. Unauthorized access to this information may reveal 1429 detailed information on the network and its users. Malicious 1430 changes may affect network and business operations. 1432 [COPS] and [COPS-PR] define mechanisms to secure the COPS protocol 1433 communication and implementations of COPS servers or clients 1434 supporting this PIB MUST follow the security guidelines specified 1435 there. 1437 6 IANA Considerations 1439 This document describes the frwkFeedbackPib Policy Information Base 1440 (PIB) module for standardization under the "pib" branch registered 1441 with IANA. An IANA assigned PIB number is requested for this PIB 1442 under the "pib" branch. 1444 This PIB uses "all" in the SUBJECT-CATEGORY clause, so it applies to 1445 all COPS client types. No new COPS client type is requested for this 1446 PIB. 1448 7 Acknowledgements 1450 The authors would like to thank Dave Durham and Russell Fenger of 1451 Intel and John K. Gallant of WorldCom for their contribution to this 1452 document. 1454 8 Authors' Addresses 1456 Diana Rawlins 1457 WorldCom 1458 901 International Parkway 1459 Richardson, Texas 75081 1460 Phone: 972-729-1044 1461 Email: Diana.Rawlins@wcom.com 1463 Amol Kulkarni 1464 JF3-206 1465 2111 NE 25th Ave 1466 Hillsboro, Oregon 97124 1467 Phone: 503-712-1168 1468 Email: amol.kulkarni@intel.com 1470 Kwok Ho Chan 1471 Nortel Networks 1472 600 Technology Park Drive 1473 Billerica, MA 01821 USA 1474 Phone: 978-288-8175 1475 Email: khchan@nortelnetworks.com 1476 Martin Bokaemper 1477 Juniper Networks 1478 700 Silver Seven Road 1479 Kanata, ON, K2V 1C3, Canada 1480 Phone: 613-591-2735 1481 Email: mbokaemper@juniper.net 1483 Dinesh G Dutt 1484 Cisco Systems, Inc. 1485 170 Tasman Dr. 1486 San Jose, CA 95134-1706 1487 Phone: 408-527-0955 1488 Email: ddutt@cisco.com 1490 9 References 1492 9.1 Normative References 1494 [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., 1495 and A. Sastry, "The COPS (Common Open Policy Service) Protocol" 1496 RFC 2748, January 2000. 1498 [COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. 1499 Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for 1500 Policy Provisioning," RFC 3084, May 2001. 1502 [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning 1503 Information," RFC 3159, August 2001. 1505 [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A. 1506 Smith, F. Reichmeyer "Framework Policy Information Base", RFC 1507 xxxx, xxxx 2002 1509 [FEEDBACKfWK] D. Rawlins, A. Kulkarni, K. Chan, M. Bokaemper, D. 1510 Dutt, "Framework of COPS-PR Policy Usage Feedback", RFC yyyy, yyyy 1511 2002. 1513 9.2 Informational References 1515 [COPS-TLS], Walker, J., Kulkarni, A.,"COPS Over TLS", draft-ietf- 1516 rap-cops-tls-04.txt, June 2002. 1518 [DIFFSERV-PIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K., 1519 Hahn, S., Bell, C., Smith, A. and Reichmeyer, A. "Differentiated 1520 Services Quality of Service Policy Information Base", draft-ietf- 1521 diffserv-pib-09.txt, June 2002 1523 10 Copyright 1525 Copyright (C) The Internet Society (2002). All Rights Reserved. 1527 This document and translations of it may be copied and furnished to 1528 others, and derivative works that comment on or otherwise explain it 1529 or assist in its implmentation may be prepared, copied, published 1530 and distributed, in whole or in part, without restriction of any 1531 kind, provided that the above copyright notice and this paragraph 1532 are included on all such copies and derivative works. However, this 1533 document itself may not be modified in any way, such as by removing 1534 the copyright notice or references to the Internet Society or other 1535 Internet organizations, except as needed for the purpose of 1536 developing Internet standards in which case the procedures for 1537 copyrights defined in the Internet Standards process must be 1538 followed, or as required to translate it into languages other than 1539 English. 1541 The limited permissions granted above are perpetual and will not be 1542 revoked by the Internet Society or its successors or assigns. 1544 This document and the information contained herein is provided on an 1545 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1546 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1547 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1548 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1549 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.