Internet Draft Diana Rawlins Expiration: September 2002 WorldCom File: draft-ietf-rap-feedback-fr-pib-02.txt Amol Kulkarni Intel Kwok Ho Chan Nortel Networks Martin Bokaemper Unisphere Networks Dinesh Dutt Cisco Framework of COPS-PR Policy Information Base for Policy Usage Feedback Last Updated March 1, 2002 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC-2119]. Abstract Currently there are no policy classes defined for the PEP to convey provisioned policy usage feedback to the PDP. The purpose of this document is to define the policy usage feedback framework PIB that specifies the policy classes common for COPS feedback reports. The basic operation and objects for reporting usage information are defined in [COPS]. A specific clientSI feedback object named REPORT is defined in [COPS-PR]. A framework for approaching solicited and periodic usage feedback is described in [COPS-FEED-FRWK.]The COPS- PR Policy Usage Feedback Policy Information Base document defines Rawlins et al. Expires September 2002 [Page 1] Internet Draft Feedback-FR-PIB March 2002 the policy classes for a feedback framework Policy information base (PIB). Rawlins et al. Expires September 2002 [Page 2] Internet Draft Feedback-FR-PIB March 2002 Table of Contents 1 Introduction.....................................................4 2 General Concepts.................................................4 2.1 Selection, Usage and Linkage Policies..........................4 2.2 Normal Operations..............................................5 2.2.1 Connection Establishment and Initial Configuration Request...5 2.2.2 Unsolicited Reports - Periodic Reporting.....................6 2.2.3 Unsolicited Reports - Reporting Conditions...................6 2.2.4 Solicited Reports............................................6 2.2.5 Resuming and Suspending Periodic Feedback Reporting..........7 2.2.6 Failover.....................................................7 2.3 Detail Policy Usage Feedback Reporting.........................7 3 Summary of the Feedback Framework Policy Information Base........9 3.1 SPPI ACCESS clause report-only.................................9 3.2 Feedback Groups and PRCs.......................................9 3.2.1 Feedback Action Table........................................9 3.2.2 Feedback List Table.........................................10 3.2.3 The Feedback Selection Usage Combination Capability Table...10 3.2.4 The Feedback Report Linkage Table...........................10 3.2.7 The Feedback Traffic Statistics Threshold Table.............11 3.2.8 Feedback DPE Selection Criteria Table.......................11 3.2.9 Feedback DPE Selection Query Table..........................11 4 The Feedback Framework PIB Module...............................12 5 Security Considerations.........................................26 6 Acknowledgements................................................27 7 Authors' Addresses..............................................27 8 References......................................................27 Rawlins et al. Expires September 2002 [Page 3] Internet Draft Feedback-FR-PIB March 2002 1 Introduction The Framework of COPS-PR Usage Feedback describes the overall approach to policy usage monitoring and reporting. This document defines the specific Policy Information Base (PIB) framework for policy usage feedback. The policy classes for monitoring and reporting policy usage feedback as well as policy classes for controlling reporting intervals, suspension, resumption and solicitation are also defined. 2 General Concepts 2.1 Selection, Usage and Linkage Policies There are three basic types of policy used to define what the PEP is to monitor, record and report. These are the selection criteria policy, the usage policy and the feedback report linkage policy. The selection criteria policy is installed by the PDP. It defines the conditions used by the PEP to monitor and record a usage policy. The selection criteria policy may only be used for defining usage feedback selection criteria. However, the more general case is that a policy that already exists for policy enforcement may also be used for specifying feedback usage selection criteria. An example of this is the qosClfrElementEntry which is useful in defining QoS enforcement policies but may also be used to specify conditions on which to base usage - i.e. count the number of packets meeting the criterion. The usage policy defines what attributes are monitored and recorded by the PEP. These policies have an ACCESS clause of Report. Generally, the usage policies specify counts related to a specific action such as a packet being dropped. The feedback framework PIB defines two usage policy classes, frwkFeedbackTrafficUsage and frwkFeedbackIfTrafficUsage. Usage PRCs may be generic, collecting basic statistics, or they may be specific to a particular usage. The PDP decides which PRC(s) best suit(s) its requirements. The PEP may support only one usage feedback PRC, in which case all statistics are gathered using instances of that PRC. Alternatively, the PEP may support multiple usage feedback PRCs. The PDP then decides which PRC to associate with a particular selection criterion. A usage feedback policy and selection policy are tightly associated with one another. A third policy, the frwkFeedbackLinkTable, is used to associate, or provide a linkage for the selection and usage policies. The frwkFeedbackLinkTable also specifies when to report the usage feedback. The frwkFeedbackLinkTable entry permits the same selection criteria instance to be re-used for various usage feedback policies. The frwkFeedbackLinkTable contains the value of the selection criteria instance as well as contains the value of the usage feedback PRC. Rawlins et al. Expires September 2002 [Page 4] Internet Draft Feedback-FR-PIB March 2002 ----------------- ------------------ ----------------- | | | | | | | Select Criteria | |Linkage Instance | |Usage Instance | | | |-instance ID | |- instance ID | | -instance ID |<--|-PRID of selection|--->|- PRID of Linkage| | -conditions... | |-PRC of usage | |- counts... | | | | | | | ----------------- ------------------ ----------------- Figure 1 Figure 1 illustrates the relationship between a selection criteria, linkage and usage policies. The PDP is not aware of the instance identifier of the usage feedback policy when installing the selection criteria and feedback linkage policies. The usage feedback policy is instantiated on the PEP by the installation of a feedback report linkage and the PEP designates the instance identifier. The usage feedback policy class always contains an attribute of type ReferenceId that contains the instance value of the associated frwkFeedbackLinkTable instance installed by the PDP. An example of this is the attribute frwkFeddbackTrafficUsageLinkRef 2.2 Normal Operations 2.2.1 Connection Establishment and Initial Configuration Request The Accounting Timer object in the Connection Accept message contains the minimum number of seconds between reporting intervals as described in [COPS] and [COPS-FEEDBACK-FRWK.] This is used as the basic unit of measurement in defining intervals for specific usage policies with the frwkFeedbackLinkInterval attribute. The PEP notifies the PDP of the selection criteria policy classes and usage policy classes it supports during the initial request for configuration data using the frwkPRCSupportTable entries [FR-PIB]. The PEP also indicates whether it supports the frwkFeedbackLinkTable as well. The PDP responds to the initial request for configuration with a DECISION that installs policies. The PDP may also specify maximum reporting intervals associated with each of the usage policies. This is done with the frwkFeedbackLinkInterval attribute in the frwkFeedbackLinkTable instance. It may also specify reporting thresholds by including an instance of a threshold class (e.g. frwkFeedbackTrafficThresholdTable) in the decision. The PEP monitors and records the usage per the conditions defined by its associated Rawlins et al. Expires September 2002 [Page 5] Internet Draft Feedback-FR-PIB March 2002 selection criteria policy. Periodically the PEP reports the usage with a REPORT message or provides a REPORT when solicited by the PDP. The PDP solicits usage feedback with the frwkFeedbackActionIndicator attribute of the frwkFeedbackActionTable. 2.2.2 Unsolicited Reports - Periodic Reporting Reporting may be periodic in nature and unsolicited. The intervals at which the unsolicited reports are provided by the PEP are defined in the specific Linkage policies. The defined intervals are based on the number of seconds specified by the PDP in the ACCT Timer value. The PDP may specify that the associated usage instance be included in a periodic unsolicited report only if the threshold is reached and/or if the usage value has changed from the previous reporting interval. There are cases when the PEP must supply unsolicited feedback reports that may not fall on an interval boundary. The PEP MUST provide an unsolicited REPORT containing all defined usages instances just prior to the PEP issuing a Delete Request State and just prior to the PEP de-activating a PIB instance context. 2.2.3 Unsolicited Reports - Reporting Conditions Periodic unsolicited reports for individual usage feedback instances can be suppressed by specifying additional conditions in the frwkFeedbackLinkTable. Supported conditions are: ChangeOnly If this flag is set in the frwkFeedbackLinkFlags field, the associated usage instance is only included in a periodic unsolicited report if its value changed since the last unsolicited report. Threshold If this flag is set in the frwkFeedbackLinkFlags field, the associated usage instance is only included in a periodic unsolicited report, if the threshold condition referenced in the frwkLinkThreshold field evaluates successfully for the associated usage instance. Both conditions can be combined in one frwkFeedbackLinkUsage object. In this case both conditions need to succeed for the usage instance to be reported. Unsolicited reports triggered by a Delete Request State or the deactivation of a PIB instance are not subject to these conditions - all usage objects must be included in these cases. 2.2.4 Solicited Reports Rawlins et al. Expires September 2002 [Page 6] Internet Draft Feedback-FR-PIB March 2002 The PDP may solicit policy usage feedback by issuing an unsolicited Decision containing the frwkFeedbackActionIndicator set to SOLICIT USAGE REPORT NOW. The PEP is to provide a solicited REPORT feedback containing usage feedback. The PEP shall continue to provide periodic feedback as well at the specified intervals established at client connection acceptance. The reporting conditions (ChangeOnly and Threshold) do not affect solicited reports - all requested usage instances must be included. 2.2.5 Resuming and Suspending Periodic Feedback Reporting The PDP may suspend usage monitoring and tracking at the PEP with the frwkFeedbackActionIndicator set to SUSPEND USAGE MONITORING AND REPORTS. The PEP must stop tracking usage information and must not issue any feedback reports. The PDP may only suspend feedback reporting by setting the ActionIndicator to SUSPEND REPORTS ONLY. The PEP must cease sending unsolicited reports but is to continue monitoring and tracking usage. The PDP may resume the sending of feedback reports and may resume usage monitoring by setting the ActionIndicator to RESUME USAGE AND REPORTING. The PDP may suspend or resume all usage instances or the PDP may specify one or more instances that are to be suspended or resumed. The frwkFeedbackActionList contains a tag identifier that references a list of one or more frwkFeedbackActionListTable entries. The PDP may halt usage monitoring, tracking and reporting of usage policies by removing the associated Linkage entry. 2.2.6 Failover In the event the connection is lost between the PEP and PDP, the PEP continues to track usage information as long as it continues to operate with the installed policy. When the locally installed policy at the PEP expires, the usage policy data also expires. Upon successful reconnection where the PEP is still caching policy, the PDP indicates to the PEP that the PEP may resume sending of the COPS accounting type report messages. The PDP does this deterministically. It issues an unsolicited decision containing the frwkFeedbackResumeIndicator set to resume reporting. The PEP should resume reporting at the next appropriate feedback interval established upon the acceptance of the re-connection. The PDP is aware of the request state Handle(s) and the supported PRCs either through the state synchronization mechanism or because the PDP considers itself synchronized with the PEP upon reconnection. 2.3 Detail Policy Usage Feedback Reporting Some of the policy objects created in the PEP with COPS-PR can be used by the PEP multiple times - they effectively act as templates for the objects created by the PEP. COPS-PR only has the identity Rawlins et al. Expires September 2002 [Page 7] Internet Draft Feedback-FR-PIB March 2002 (OID) of the object that is shared between all the assignment the PEP created, however it is desirable to collect usage information for each of the derived objects individually. This capability is achieved in the feedback framework PIB by distributing additional information to qualify a specific assignment of an object between the selection criteria PRC and the feedback usage PRC. A selection criteria PRC that refers to a shared object but contains no qualifying information selects all of the object's assignment. Such a selection criteria PRC should be combined with a feedback usage PRC that includes all the necessary information to identify a specific assignment - a single selection criteria policy can then result in the generation of many feedback usage objects, one for each derived object. If the selection criteria PRC contains all the required qualifying attributes for a specific assignment, it is combined with a feedback usage PRC that only contains the desired metrics but no additional attributes. Example: As part of a data path, an IPFilter object can be assigned to many combinations of interface and direction. To refer to a specific assignment of an IPFilter for feedback purposes, the reference to the IPFilter instance has to be qualified with the interface and direction attributes. Feedback from the filter on a specific interface: As the selection criteria policy a frwkFeedbackDPESelectionEntry is used which contains the qualifying attributes: frwkFeedbackDPESelectionDataPathElement Prid frwkFeedbackDPESelectionInterface Prid frwkFeedbackDPESelectionIfDirection IfDirection In this case this policy would be combined in a frwkLinkageEntry with the FrwkFeedbackTrafficUsage PRC. This combination will result in only one FrwkFeedbackTrafficUsageEntry to be created which only contains the traffic counters. Feedback from all interfaces a filter is assigned to: By combining a frwkFeedbackDPESelectionQueryEntry as selection criteria with the FrwkFeedbackIfTrafficUsage PRC, all the assignments are selected and multiple FrwkFeedbackIfTrafficUsageEntries get created. Each entry not only carries the desired traffic counters but also the qualifying attributes to associate it with the assignment: frwkFeedbackIfTrafficUsageInterface Prid, frwkFeedbackIfTrafficUsageIfDirection IfDirection Rawlins et al. Expires September 2002 [Page 8] Internet Draft Feedback-FR-PIB March 2002 3 Summary of the Feedback Framework Policy Information Base 3.1 SPPI ACCESS clause report-only The selection criteria and linkage policy classes follow the definitions specified by [SPPI]. This structure specifies well- defined policy classes and their instances residing in a common, virtual repository [FR-PIB]. The additional PIB-ACCESS clause attribute of "report-only" denotes the usage policy class reported by the PEP. 3.2 Feedback Groups and PRCs It is useful to define reporting intervals, and suspend, resume, and solicit characteristics as well as the common usage and selection criteria polices. These policy classes are common to account type reporting for various technologies and apply to ALL SUBJECT- CATEGORIES. The policy classes are divided into three new groups, namely, The Feedback Report Group, The Feedback Usage Group and The Feedback Selection Group. The policy classes in the Feedback Report Group are: 1) Feedback Action Table 2) Feedback Action List Table 3) Feedback Selection Usage Combination Capability Table 4) Feedback Linkage Table The policy classes in the Feedback Usage Group are: 1) Feedback Traffic Statistics Usage Table 2) Feedback Interface Traffic Statistics Usage Table 3) Feedback Traffic Statistics Threshold Table The policy classes in the Feedback Selection Group are: 1) Feedback DPE Selection Criteria Table 2) Feedback DPE Selection Query Table 3) Feedback DPE Interface Usage Table 3.2.1 Feedback Action Table The Feedback Action Table contains the attributes that specify action that the PEP is to take regarding policy usage, monitoring and tracking. The PDP may suspend usage monitoring and periodic reporting, suspend periodic reporting only, resume usage and periodic reporting or solicit immediate reporting. The action may affect all feedback policies or be associated with one or more policy instances. The Feedback Action Indicator defines the action. The Feedback Specific PRI indicates whether the action applies to all of the Rawlins et al. Expires September 2002 [Page 9] Internet Draft Feedback-FR-PIB March 2002 usage policies or to a list. The Feedback List ID is the identifier of the list of Linkage policy instances to which the action is to be applied. The PDP can solicit the PEP for immediate usage feedback. The PEP shall respond with a solicited report containing the usage feedback. The PDP can direct the resumption of usage monitoring and reporting per the defined intervals. For example, the PEP may have re- connected to a PDP and has cached usage policies. The PDP indicates to the PEP to resume usage tracking and monitoring and to send all the cached usage policy. The PEP shall respond at the next appropriate interval with an unsolicited report containing the usage feedback. The PDP can suspend the monitoring of usage policy. The PEP maintains the current usage that has been monitored but discontinues any further monitoring until the PDP directs the PEP to resume monitoring in a subsequent Decision. The PDP can also suspend just the reporting of usage, but not interrupt the monitoring and tracking of usage. The PEP shall discontinue sending Report messages with usage feedback until the PDP directs the PEP to resume. The PEP then begins reporting the usage feedback at the next interval. 3.2.2 Feedback List Table This table contains a list of PRIDs of the linkage table for which the PDP wants feedback reports. The value is referenced by an attribute in the Feedback Resume Table. There may be one or more instances associated with a specific list identifier defined by the Feedback Action List ID. 3.2.3 The Feedback Selection Usage Combination Capability Table This table defines the valid selection criteria PRC, and usage PRC and threshold PRC combinations supported. 3.2.4 The Feedback Report Linkage Table This table links the selection criteria instance with the usage instance. It specifies the PRID of the selection criteria and the PRC of the usage instance. This table permits the reuse of a selection criteria instance for multiple usage policies. The linkage table also permits the definition of a maximum reporting interval to use when issuing the COPS accounting type reports for the usage instance. This interval is defined in units of the Accounting Timer Interval specified in the client accept message. A value of 0 in this attribute indicates that the usage policy must be solicited. Rawlins et al. Expires September 2002 [Page 10] Internet Draft Feedback-FR-PIB March 2002 3.2.5 The Feedback Traffic Statistics Usage Table This table describes the packet counts, byte counts, last timestamp when a packet was received and the PRID of the associated Feedback Report Linkage instance. The count and timestamp information is monitored and recorded by the PEP and supplied to the PDP with the COPS accounting type report message within the maximum interval specified. 3.2.6 The Feedback Interface Traffic Statistics Usage Table This table is similar to the table described above, except that it includes an additional reference to an interface. This table should be used with a selection criteria that matches an element that is assigned to multiple interfaces. The interface field can be used to associate the instances of this table with the specific elementÆs assignment. 3.2.7 The Feedback Traffic Statistics Threshold Table This table is used to provide threshold values for the attributes described in the above usage tables. 3.2.8 Feedback DPE Selection Criteria Table This table is an example of a Selection Criteria PRC that references a specific instance of a shared object. It is based on the popular model of a data path consisting of multiple linked data path elements (DPEs). A single data path can be assigned to multiple interfaces by a single entry in the Data Path Table [DIFFSERV-PIB], elements within this data path however can collect usage information for each assignment individually. Instances of this class allow the PDP to select a specific assignment of a data path element to be selected for usage reporting. This is achieved by the combination of references to a Data Path Entry, a Data Path Element and the Interface. It is expected to be used in combination with the FrwkFeedbackTrafficUsage PRC. 3.2.9 Feedback DPE Selection Query Table This Selection Criteria PRC is similar to the DPE Selection Criteria Table, however it is missing the reference to a specific interface. This means an instance of this class can select multiple assignments of a data path element for usage collection. Each selected assignment of the DPE creates its own usage instance. This selection criteria PRC is expected to be used together with a usage PRC that includes the a reference to an interface, so the results can be assigned uniquely. Rawlins et al. Expires September 2002 [Page 11] Internet Draft Feedback-FR-PIB March 2002 3.2.11 Feedback DPE Interface Usage Table The DPE Interface Usage class is an extension of the generic Traffic Usage class that also includes a reference to a frwkIfRoleComboEntry that represents the interface, this instance is associated with. 4 The Feedback Framework PIB Module FEEDBACK-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN IMPORTS ExtUTCTime, Unsigned32, Unsigned64, Integer32, MODULE-IDENTITY, OBJECT-TYPE FROM COPS-PR-SPPI TruthValue, TEXTUAL-CONVENTION FROM SNMPv2-TC PolicyInstanceId, PolicyReferenceId FROM COPS-PR-SPPI-TC Counter64 FROM SNMPv2-SMI; feedbackPolFrameworkPib MODULE-IDENTITY SUBJECT-CATEGORIES { all } LAST-UPDATED "200011171000Z" ORGANIZATION "IETF RAP WG" CONTACT-INFO " Diana Rawlins WorldCom 901 International Parkway Richardson, TX 75081 Phone: 972 729 1044 Email: diana.rawlins@wcom.com Amol Kulkarni JF3-206 2111 NE 25th Ave Hillsboro, Oregon 97124 Phone: 503-712-1168 Email: amol.kulkarni@intel.com Kwok Ho Chan Nortel Networks, Inc. 600 Technology Park Drive Billerica, MA 01821 USA Phone: 978-288-8175 Email: khchan@nortelnetworks.com Martin Bokaemper Unisphere Networks 700 Silver Seven Road Rawlins et al. Expires September 2002 [Page 12] Internet Draft Feedback-FR-PIB March 2002 Kanata, ON, K2V 1C3, Canada Phone: 613-591-2735 Email: mbokaemper@unispherenetworks.com" DESCRIPTION "The PIB module containing the base set of policy rule classes that are required for support of all policy usage monitoring, tracking and reporting policies" ::= { pib xx } -- xx will be assigned by IANA -- -- The feedback report group -- frwkFeedbackGroupClasses OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 1 } -- -- Feedback Action Table -- frwkFeedbackActionTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackActionEntry PIB-ACCESS install STATUS current DESCRIPTION "This class contains a single PRI that indicates that the PEP is to resume the sending of COPS accounting type reports." ::= { frwkFeedbackGroupClasses 1} frwkFeedbackActionEntry OBJECT-TYPE SYNTAX FrwkFeedbackActionEntry STATUS current DESCRIPTION "An instance of this class can indicates a action the PEP is to take regarding the usage policies." PIB-INDEX { frwkFeedbackActionId} ::= { frwkFeedbackActionTable 1} FrwkFeedbackActionEntry ::= SEQUENCE { frwkFeedbackActionId InstanceId, frwkFeedbackActionIndicator INTEGER, frwkFeedbackActionSpecificPri TruthValue, frwkFeedbackActionList TagReferenceId } frwkFeedbackActionId OBJECT-TYPE SYNTAX InstanceId STATUS current Rawlins et al. Expires September 2002 [Page 13] Internet Draft Feedback-FR-PIB March 2002 DESCRIPTION " An arbitrary integer index that uniquely identifies an instance of the frwkFeedbackActionTable class." ::= { frwkFeedbackActionEntry 1} frwkFeedbackActionIndicator OBJECT-TYPE SYNTAX INTEGER { SUSPEND_USAGE_MONITORING_AND_REPORTS(0), SUSPEND_REPORTS_ONLY(1), RESUME_USAGE_AND_REPORTING(2), SOLICIT_USAGE_REPORT_NOW(3) } STATUS current DESCRIPTION "The value indicates if the PEP is to send cached usage policies via COPS accounting type report messages. The enumeration values are: (0) SUSPEND USAGE MONITORING_AND_REPORTS (1) SUSPEND_REPORTS_ONLY (2) RESUME_USAGE AND REPORTING (3) SOLICIT USAGE REPORT NOW " ::= { frwkFeedbackActionEntry 2 } frwkFeedbackActionSpecificPri OBJECT-TYPE SYNTAX TruthValue STATUS current DESCRIPTION "A value of 0 indicates that the frwkFeedbackActionList attribute should be ignored, and the action applied to all policies. A value of 1 indicates that the action entry has a specific list of policies to which it is to be applied." ::= { frwkFeedbackActionEntry 3} frwkFeedbackActionList OBJECT-TYPE SYNTAX TagReferenceId PIB-TAG { frwkFeedbackActionListGroup } STATUS current DESCRIPTION "Identifies a list of frwkFeedbackActionListTable instances associated with the action described by this instance" ::= { frwkFeedbackActionEntry 4} -- -- Feedback Action List Table -- Rawlins et al. Expires September 2002 [Page 14] Internet Draft Feedback-FR-PIB March 2002 frwkFeedbackActionListTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackActionListEntry PIB-ACCESS install STATUS current DESCRIPTION "This class contains the ReferenceIDs of the linkage instance which are to be impacted by the frwkFeedbackActionIndicator for this list." ::= { frwkFeedbackGroupClasses 2} frwkFeedbackActionListEntry OBJECT-TYPE SYNTAX FrwkFeedbackActionListEntry STATUS current DESCRIPTION "This class identifies a set of linkage instances for which the PDP is suspending, resuming or soliciting usage feedback." PIB-INDEX {frwkFeedbackActionListId } UNIQUENESS { frwkFeedbackActionListGroup, frwkFeedbackActionListRefID } ::= { frwkFeedbackActionListTable 1} FrwkFeedbackActionListEntry::= SEQUENCE { frwkFeedbackActionListId InstanceId, frwkFeedbackActionListGroup TagId, frwkFeedbackActionListRefID ReferenceId } frwkFeedbackActionListId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackActionListEntry 1 } frwkFeedbackActionListGroup OBJECT-TYPE SYNTAX TagId STATUS current DESCRIPTION "Represents the binding between the Action table entry and the Action List table entries" ::= { frwkFeedbackActionListEntry 2 } frwkFeedbackActionListRefID OBJECT-TYPE SYNTAX ReferenceId PIB-REFERENCES { frwkFeedbackLinkEntry } STATUS current DESCRIPTION Rawlins et al. Expires September 2002 [Page 15] Internet Draft Feedback-FR-PIB March 2002 "The ReferenceID of the linkage instance(s) belonging to the list of instances identified by the list id upon which the suspend, resume or solicit action is directed." ::= { frwkFeedbackActionListEntry 3 } -- -- The Feedback Selection Usage Combination Capability Table -- frwkFeedbackSelUsageComboCapsTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackSelUsageComboCapsEntry PIB-ACCESS notify STATUS current DESCRIPTION "This table defines the valid combinations of the selection criteria PRCs, the usage PRCs and the threshold PRCs that the PEP supports." ::= { frwkFeedbackGroupClasses 3} frwkFeedbackSelUsageComboCapsEntry OBJECT-TYPE SYNTAX FrwkFeedbackSelUsageComboCapsEntry STATUS current DESCRIPTION "The attributes of this class identify valid combinations of selection criteria, usage and threshold PRCs for feedback supported by the PEP device." PIB-INDEX { frwkFeedbacSelUsageComboCapsId } UNIQUENESS { frwkFeedbackSelUsageComboCapsSelection, frwkFeedbackSelUsageComboCapsUsage, frwkFeedbackSelUsageComboCapsThreshold } ::= {frwkFeedbackSelUsageComboCapsTable 1} FrwkFeedbackSelUsageComboCapsEntry ::= SEQUENCE { frwkFeedbackSelUsageComboCapsId InstanceId, frwkFeedbackSelUsageComboCapsSelection OBJECT IDENTIFIER, frwkFeedbackSelUsageComboCapsUsage OBJECT IDENTIFIER, frwkFeedbackSelUsageComboCapsThreshold OBJECT IDENTIFIER } frwkFeedbackSelUsageComboCapsId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION " An arbitrary integer index that uniquely identifies an instance of the frwkFeedbackSelUsageComboCapsEntry class." ::= { frwkFeedbackSelUsageComboCapsEntry 1} Rawlins et al. Expires September 2002 [Page 16] Internet Draft Feedback-FR-PIB March 2002 frwkFeedbackSelUsageComboCapsSelection OBJECT-TYPE SYNTAX OBJECT IDENTIFIER STATUS current DESCRIPTION "The PRC of the selection class that is supported by the device in the combination defined by this instance." ::= { frwkFeedbackSelUsageComboCapsEntry 2} frwkFeedbackSelUsageComboCapsUsage OBJECT-TYPE SYNTAX OBJECT IDENTIFIER STATUS current DESCRIPTION "The PRC of the usage policy class that is supported by the device in combination with the selection PRC and the threshold PRC defined in this instance." ::= { frwkFeedbackSelUsageComboCapsEntry 3} frwkFeedbackSelUsageComboCapsThreshold OBJECT-TYPE SYNTAX OBJECT IDENTIFIER STATUS current DESCRIPTION "The PRC of the threshold class that is supported by the device in the combination defined by this instance." ::= { frwkFeedbackSelUsageComboCapsEntry 4} -- -- The Feedback Report Linkage Table -- frwkFeedbackLinkTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackLinkEntry PIB-ACCESS Install STATUS current DESCRIPTION "This class associates the selection criteria with the usage policy. It also permit the defining of the max interval used for reporting the usage instance." ::= { frwkFeedbackGroupClasses 4} frwkFeedbackLinkEntry OBJECT-TYPE SYNTAX FrwkFeedbackLinkEntry STATUS current DESCRIPTION "This class associates the selection criteria with the usage policy. It also permits the defining of the max interval used for reporting the usage instance." PIB-INDEX {frwkFeedbackActionLinkId} UNIQUENESS { frwkFeedbackLinkId, frwkFeedbackLinkSel, frwkFeedbackLinkUsage } Rawlins et al. Expires September 2002 [Page 17] Internet Draft Feedback-FR-PIB March 2002 ::= {frwkFeedbackLinkTable 1} FrwkFeedbackLinkEntry ::= SEQUENCE { frwkFeedbackLinkId InstanceId, frwkFeedbackLinkSel Prid, frwkFeedbackLinkUsage OBJECT IDENTIFIER, frwkFeedbackLinkInterval Integer32, frwkFeedbackLinkThreshold Prid, frwkFeedbackLinkFlags BITS } frwkFeedbackLinkId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION " An arbitrary integer index that uniquely identifies an instance of the frwkFeedbackLinkTable class." ::= { frwkFeedbackLinkEntry 1} frwkFeedbackLinkSel OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "The PRID of the selection criteria instance that defines the conditions to use by the PEP for monitoring the usage." ::= { frwkFeedbackLinkEntry 2} frwkFeedbackLinkUsage OBJECT-TYPE SYNTAX OBJECT IDENTIFIER STATUS current DESCRIPTION "The PRC of the usage policy class that the PEP uses to monitor, record and report." ::= { frwkFeedbackLinkEntry 3} frwkFeedbackLinkInterval OBJECT-TYPE SYNTAX Integer32 STATUS current DESCRIPTION "Maximum interval in units of the value of the Accounting Timer specified by the PDP in the client accept message. A frwkFeedbackLinkInterval of 1 is equal to the value of the Accounting Timer. This value must be 1 or greater. " ::= { frwkFeedbackLinkEntry 4} frwkFeedbackLinkThreshold OBJECT-TYPE SYNTAX Prid STATUS current Rawlins et al. Expires September 2002 [Page 18] Internet Draft Feedback-FR-PIB March 2002 DESCRIPTION "The PRID of the threshold class instance. This instance specifies the threshold values for the usage policy." ::= { frwkFeedbackLinkEntry 5} frwkFeedbackLinkFlags OBJECT-TYPE SYNTAX BITS { periodic(0), threshold(1), changeOnly(2) } STATUS current DESCRIPTION "This value indicates the reporting basis of the usage policy. The feed back may be generated on demand, on a periodic basis regardless of a change in value from the previous report, on a periodic basis if a change in value has occurred, or the usage is reported when an identified threshold value in the usage instance has been reached. If the æperiodicÆ flag is set, the PEP will provide unsolicited reports at the rate specified in frwkFeedbackLinkInterval. If the æperiodicÆ flag is not set, reports will only be generated when solicited by the PDP. The æthresholdÆ and æchangeOnlyÆ flags make the periodic reports conditional - these flags only make sense in combination with the æperiodicÆ flag." ::= { frwkFeedbackLinkEntry 6} -- -- All actual usage classes are in the separate -- FrwkFeedbackUsageClasses group -- frwkFeedbackUsageClasses OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 2 } -- -- The generic traffic (byte & packet count) usage class -- frwkFeedbackTrafficUsageTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackTrafficUsageEntry PIB-ACCESS report-only STATUS current DESCRIPTION "This class defines the usage attributes that the PEP is to monitor for plain traffic handling elements Rawlins et al. Expires September 2002 [Page 19] Internet Draft Feedback-FR-PIB March 2002 like filters. All packets and the bytes contained in these packets are counted. It also contains the PRID of the linkage instance associating the selection criteria instance with the usage instance." ::= { frwkFeedbackUsageClasses 1} frwkFeedbackTrafficUsageEntry OBJECT-TYPE SYNTAX FrwkFeedbackTrafficUsageEntry STATUS current DESCRIPTION "Defines the attributes the PEP is to monitor, record and report." PIB-INDEX {frwkFeedbackTrafficUsageId} UNIQUENESS { frwkFeedbackTrafficUsageLinkRefID } ::= {frwkFeedbackTrafficUsageTable 1} FrwkFeedbackTrafficUsageEntry ::= SEQUENCE { frwkFeedbackTrafficUsageId InstanceId, frwkFeedbackTrafficUsageLinkRefID ReferenceId, frwkFeedbackTrafficUsagePacketCount Counter64, frwkFeedbackTrafficUsageByteCount Counter64 } frwkFeedbackTrafficUsageId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackTrafficUsageEntry 1 } frwkFeedbackTrafficUsageLinkRefID OBJECT-TYPE SYNTAX ReferenceId PIB-REFERENCES { frwkFeedbackLinkEntry } STATUS current DESCRIPTION "The ReferenceId of the Linkage policy instance used to base this usage policy instance upon." ::= { frwkFeedbackTrafficUsageEntry 2 } frwkFeedbackTrafficUsagePacketCount OBJECT-TYPE SYNTAX Counter64 STATUS current DESCRIPTION "The count of packets handled by the associated element during the reporting interval." ::= {frwkFeedbackTrafficUsageEntry 3} Rawlins et al. Expires September 2002 [Page 20] Internet Draft Feedback-FR-PIB March 2002 frwkFeedbackTrafficUsageByteCount OBJECT-TYPE SYNTAX Counter64 STATUS current DESCRIPTION "The byte count of packets handled by the associated element." ::= { frwkFeedbackTrafficUsageEntry 4} -- -- The traffic usage class, qualified for an interface -- frwkFeedbackIfTrafficUsageTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficUsageEntry PIB-ACCESS report-only STATUS current DESCRIPTION "A usage PRC similar to the basic TrafficUsage class that also contains a reference to an interface. This class should be used with a selection criteria that matches an element that is assigned to multiple interfaces. The interface field can be used to associate the instances of this class with the specific elementÆs assignment." ::= { frwkFeedbackUsageClasses 2 } frwkFeedbackIfTrafficUsageEntry OBJECT-TYPE SYNTAX FrwkFeedbackIfTrafficUsageEntry STATUS current DESCRIPTION "Defines the attributes the PEP is to monitor, record and report." PIB-INDEX {frwkFeedbackIfTrafficUsageId} UNIQUENESS { frwkFeedbackIfTrafficUsageLinkRefID, frwkFeedbackIfTrafficUsageInterface } ::= {frwkFeedbackIfTrafficUsageTable 1} FrwkFeedbackIfTrafficUsageEntry ::= SEQUENCE { frwkFeedbackIfTrafficUsageId InstanceId, frwkFeedbackIfTrafficUsageLinkRefID ReferenceId, frwkFeedbackIfTrafficUsageInterface ReferenceId, frwkFeedbackIfTrafficUsageIfDirection IfDirection, frwkFeedbackIfTrafficUsagePacketCount Counter64, frwkFeedbackIfTrafficUsageByteCount Counter64 } frwkFeedbackIfTrafficUsageId OBJECT-TYPE SYNTAX InstanceId STATUS current Rawlins et al. Expires September 2002 [Page 21] Internet Draft Feedback-FR-PIB March 2002 DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackIfTrafficUsageEntry 1 } frwkFeedbackIfTrafficUsageLinkRefID OBJECT-TYPE SYNTAX ReferenceId PIB-REFERENCES { frwkFeedbackLinkEntry } STATUS current DESCRIPTION "The ReferenceId of the Linkage policy instance used to base this usage policy instance upon." ::= { frwkFeedbackIfTrafficUsageEntry 2 } frwkFeedbackIfTrafficUsageInterface OBJECT-TYPE SYNTAX ReferenceId PIB-REFERENCES { frwkIfRoleComboEntry } STATUS current DESCRIPTION "The ReferenceID of a frwkIfRoleCombo instance, uniquely identifying a specific interface." ::= { frwkFeedbackIfTrafficUsageEntry 3 } frwkFeedbackIfTrafficUsageIfDirection OBJECT-TYPE SYNTAX IfDirection STATUS current DESCRIPTION " The direction of the selected interface.ö ::= { frwkFeedbackIfTrafficUsageEntry 4 } frwkFeedbackIfTrafficUsagePacketCount OBJECT-TYPE SYNTAX Counter64 STATUS current DESCRIPTION "The count of packets handled by the associated element during the reporting interval." ::= { frwkFeedbackIfTrafficUsageEntry 5 } frwkFeedbackIfTrafficUsageByteCount OBJECT-TYPE SYNTAX Counter64 STATUS current DESCRIPTION "The byte count of packets handled by the associated element." ::= { frwkFeedbackIfTrafficUsageEntry 6 } -- -- The Threshold class that accompanies the above Usage PRCs -- frwkFeedbackTrafficThresholdTable OBJECT-TYPE Rawlins et al. Expires September 2002 [Page 22] Internet Draft Feedback-FR-PIB March 2002 SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresholdEntry PIB-ACCESS Install STATUS current DESCRIPTION "This class defines the threshold attributes corresponding to usage attributes specified in frwkFeedbackTrafficUsageTable, frwkFeedbackIfTrafficUsageTable and other similar usage classes. The usage object is considered to match the threshold condition if the following expression evaluates to æTRUEÆ: { byteCond = (ByteThreshold != NULL) ? (ByteThreshold > ByteCounter) : FALSE; packetCond (PacketThreshold != NULL) ? (PacketThreshold > PacketCounter) : FALSE; return ( byteCond || packetCond ); }" ::= { frwkFeedbackUsageClasses 3} frwkFeedbackTrafficThresholdEntry OBJECT-TYPE SYNTAX FrwkFeedbackTrafficThresholdEntry STATUS current DESCRIPTION "Defines the attributes to hold threshold values." PIB-INDEX {frwkFeedbackTrafficThresholdId} ::= {frwkFeedbackTrafficThresholdTable 1} FrwkFeedbackTrafficThresholdEntry ::= SEQUENCE { frwkFeedbackTrafficThresholdId InstanceId, frwkFeedbackTrafficThresholdPacketThreshold Integer64, frwkFeedbackTrafficThresholdByteThreshold Integer64 } frwkFeedbackTrafficThresholdId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackTrafficThresholdEntry 1 } frwkFeedbackTrafficThresholdPacketThreshold OBJECT-TYPE SYNTAX Integer64 STATUS current DESCRIPTION "The threshold, in terms of packets, that must be exceeded to trigger a report in the next reporting interval." ::= { frwkFeedbackTrafficThresholdEntry 2 } Rawlins et al. Expires September 2002 [Page 23] Internet Draft Feedback-FR-PIB March 2002 frwkFeedbackTrafficThresholdByteThreshold OBJECT-TYPE SYNTAX Integer64 STATUS current DESCRIPTION "The threshold, in terms of bytes, that must be exceeded to trigger a report in the next reporting interval." ::= { frwkFeedbackTrafficThresholdEntry 3 } -- -- All Selection classes are in the separate -- FrwkFeedbackSelectionClasses group -- frwkFeedbackSelectionClasses OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 3 } -- -- DPE Selection Class -- frwkFeedbackDPESelectionTable OBJECT-TYPE SYNTAX SEQUENCE OF frwkFeedbackDPESelectionEntry PIB-ACCESS Install STATUS current DESCRIPTION "This class defines a selection criteria that identifies a specific data path element to collect usage information" ::= { frwkFeedbackSelectionClasses 2} frwkFeedbackDPESelectionEntry OBJECT-TYPE SYNTAX frwkFeedbackDPESelectionEntry STATUS current DESCRIPTION "Defines the attributes the of the selection criteria identifying a specific policy where to monitor the associated usage." PIB-INDEX { frwkFeedbackDPESelectionId } UNIQUENESS { frwkFeedbackDPESelectionDataPathElement, frwkFeedbackDPESelectionInterface, frwkFeedbackDPESelectionIfDirection } ::= {frwkFeedbackDPESelectionTable 1} frwkFeedbackDPESelectionEntry ::= SEQUENCE { frwkFeedbackDPESelectionId InstanceId, frwkFeedbackDPESelectionDataPathElement Prid, Rawlins et al. Expires September 2002 [Page 24] Internet Draft Feedback-FR-PIB March 2002 frwkFeedbackDPESelectionInterface Prid, frwkFeedbackDPESelectionIfDirection IfDirection } frwkFeedbackDPESelectionId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackDPESelectionEntry 1 } frwkFeedbackDPESelectionDataPathElement OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "The PRID of the element in the data path that we want to collect usage information from. This element must be part of the data path assigned to the interface/direction combination referenced in this object." ::= { frwkFeedbackDPESelectionEntry 2 } frwkFeedbackDPESelectionInterface OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "The PRID of a frwkIfRoleCombo instance, uniquely identifying a specific interface" ::= { frwkFeedbackDPESelectionEntry 3 } frwkFeedbackDPESelectionIfDirection OBJECT-TYPE SYNTAX IfDirection STATUS current DESCRIPTION "The direction (ingress/egress) that to which the DPE is attached that we want to match." ::= { frwkFeedbackDPESelectionEntry 4 } -- -- DPE Selection Query Class -- frwkFeedbackDPESelectionQueryTable OBJECT-TYPE SYNTAX SEQUENCE OF frwkFeedbackDPESelectionQueryEntry PIB-ACCESS Install STATUS current DESCRIPTION "This class defines a selection criteria that identifies a set of assignments of a data path element Rawlins et al. Expires September 2002 [Page 25] Internet Draft Feedback-FR-PIB March 2002 based on an entry in the data path anchor table such as the Data Path Table. Each matched assignment will collect and report usage independently, so this selection criteria should be combined with a Usage PRC that includes an interface reference." ::= { frwkFeedbackSelectionClasses 3} frwkFeedbackDPESelectionQueryEntry OBJECT-TYPE SYNTAX frwkFeedbackDPESelectionQueryEntry STATUS current DESCRIPTION "Defines the attributes the of the selection criteria identifying a specific policy where to monitor the associated usage." PIB-INDEX { frwkFeedbackDPESelectionQueryId } UNIQUENESS { frwkFeedbackDPESelectionQueryDataPathElement } ::= {frwkFeedbackDPESelectionQueryTable 1} frwkFeedbackDPESelectionQueryEntry ::= SEQUENCE { frwkFeedbackDPESelectionQueryId InstanceId, frwkFeedbackDPESelectionQueryDataPathElement Prid } frwkFeedbackDPESelectionQueryId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackDPESelectionQueryEntry 1 } frwkFeedbackDPESelectionQueryDataPathElement OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "The PRID of the element in the data path that we want to collect usage information from. This element must be part of the data path referenced from the frwkFeedbackDPESelectionQueryDataPath field." ::= { frwkFeedbackDPESelectionQueryEntry 2 } END 5 Security Considerations The feedback information is sensitive and requires that authorized messaging occur between the PEP and the PDP. This protection can be accomplished with IPSEC or TLS [COPS-TLS] between the PEP and the PDP or using the security mechanisms described in the base COPS protocol. Rawlins et al. Expires September 2002 [Page 26] Internet Draft Feedback-FR-PIB March 2002 6 Acknowledgements The authors would like to thank Dave Durham and Russell Fenger of Intel and John K. Gallant of WorldCom for their contribution to this document. 7 Authors' Addresses Diana Rawlins WorldCom 901 International Parkway Richardson, Texas 75081 Phone: 972-729-1044 Email: Diana.Rawlins@wcom.com Amol Kulkarni JF3-206 2111 NE 25th Ave Hillsboro, Oregon 97124 Phone: 503-712-1168 Email: amol.kulkarni@intel.com Kwok Ho Chan Nortel Networks, Inc. 600 Technology Park Drive Billerica, MA 01821 USA Phone: 978-288-8175 Email: khchan@nortelnetworks.com Martin Bokaemper Unisphere Networks 700 Silver Seven Road Kanata, ON, K2V 1C3, Canada Phone: 613-591-2735 Email: mbokaemper@unispherenetworks.com Dinesh G Dutt Cisco Systems, Inc. 170 Tasman Dr. San Jose, CA 95134-1706 Phone: 408-527-0955 Email: ddutt@cisco.com 8 References [FEEDBACKfWK] Rawlins, D., Kulkarni, A., "Framework of COPS-PR Policy Usage Feedback", draft-ietf-rap-feedback-frwk-02.txt, February 2002. Rawlins et al. Expires September 2002 [Page 27] Internet Draft Feedback-FR-PIB March 2002 [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., and A. Sastry, "The COPS (Common Open Policy Service) Protocol" RFC 2748, January 2000. [3084] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for Policy Provisioning," RFC 3084, May 2001. [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning Information," RFC 3159, August 2001. [DIFFSERV-PIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K., Hahn, S., Bell, C., Smith, A. and Reichmeyer, A. "Differentiated Services Quality of Service Policy Information Base", draft-ietf- diffserv-pib-05.txt, November 2001 [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A. Smith, F. Reichmeyer "Framework Policy Information Base", draft- ietf-rap-frameworkpib-06.txt, November 2001 [COPS-TLS], Walker, J., Kulkarni, A.,öCOPS Over TLSö, draft-ietf- rap-cops-tls-02.txt, October 2001. Rawlins et al. Expires September 2002 [Page 28]