Internet Draft Diana Rawlins Expiration: January 2002 WorldCom File: draft-ietf-rap-feedback-fr-pib-00.txt Amol Kulkarni Intel Kwok Ho Chan Nortel Networks Dinesh Dutt Cisco Martin Bokaemper Unisphere Networks Framework of COPS-PR Policy Information Base for Policy Usage Feedback Last Updated July 12 2001 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]. This Rawlins et al. Expires January 2002 [Page 1] Internet Draft FEED-FRWK-PIB July 2001 document defines the policy classes for a feedback framework Policy information base (PIB). Table of Contents 1 Introduction.....................................................3 2 General Concepts.................................................3 2.1 Selection, Usage and Linkage Policies..........................3 2.2 Normal Operations..............................................4 2.2.1 Connection Establishment and Initial Configuration Request...4 2.2.2 Unsolicited Reports - Periodic Reporting.....................5 2.2.3 Solicited Reports............................................5 2.2.4 Resuming and Suspending Periodic Feedback Reporting..........5 2.2.5 Failover.....................................................6 3 Summary of the Feedback Framework Policy Information Base........6 3.1 SPPI ACCESS clause report-only.................................6 3.2 Feedback Type Report Group and PRCs............................6 3.2.1 Feedback Action Table........................................6 3.2.2 Feedback List Table..........................................7 3.2.3 The Feedback Report Linkage Table............................7 4 The Feedback Framework PIB Module................................8 5 Security Considerations.........................................15 6 Acknowledgements................................................15 7 Authors' Addresses..............................................15 8 References......................................................15 Rawlins et al. Expires January 2002 [Page 2] Internet Draft FEED-FRWK-PIB July 2001 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. Generally, the selection criterion is an existing PRI such as an instance of the frwkIPFilterTable. This PRC is useful for specifying conditions on which to base usage - i.e. count the number of packets received for this filter. The filter (source address, destination address, etc.) in this case defines the conditions. In the case of the feedback framework PIB, the frwkIPFilterTable is the only PRC used to base selection on. 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 one usage policy class, frwkFeedbackFilterStats. It counts packets and bytes as well as records the timestamp when the last packet was received. 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 PRC, in which case all statistics are gathered using instances of that PRC. Alternatively, the PEP may support multiple usage PRCs. The PDP then decides which PRC to associate with a particular selection criterion. A usage policy and selection policy are tightly associated with one another. A third policy is used to associate, or link, the selection and usage policies. The frwkFeedbackLinkTable performs this linking of the selection and usage policies. The feedback report linkage permits the same selection criteria instance to be re-used for Rawlins et al. Expires January 2002 [Page 3] Internet Draft FEED-FRWK-PIB July 2001 various usage policies. For example, the same IP Filter selection criteria could be the basis of different usage policies such as packet count, drop count, and remark count. The feedback type report linkage references the selection criteria instance as well as defines the policy class of the usage PRC. As noted above, the selection criteria policy may be used for enforcement policies as well as usage policies. This is the case with the frwkIPFilterTable. ----------------- ------------------ ----------------- | | | | | | | 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. There is a one to one relationship between the report linkage policy instance and the usage policy instance. The PDP is not aware of the instance identifier of the usage policy when installing the selection criteria and feedback report linkage policies. The usage policy is instantiated on the PEP by the installation of a feedback report linkage and the PEP designates the instance identifier. The usage policy class always contains an attribute of type Prid which contains the value of the associated feedback report linkage PRID [COPS-PR] installed by the PDP. Note that the Prid type is a textual convention for an object identifier that is the PRC of the table used for the feedback report linkage and where the last sub-identifier is an instance ID of the feedback report linkage. 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-FEED-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. Rawlins et al. Expires January 2002 [Page 4] Internet Draft FEED-FRWK-PIB July 2001 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 and does this with the frwkFeedbackLinkInterval attribute in the frwkFeedbackLinkTable instance. The PEP monitors and records the usage per the conditions defined by its associated selection criteria policy. Periodically the PEP reports the usage with an feedback type REPORT or provides a REPORT when solicited by the PDP. The PDP solicits usage feedback with the frwkFeedbackResumeIndicator attribute of the frwkFeedbackResumeTable. 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. 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 Solicited Reports The PDP may solicit policy usage feedback by issuing an unsolicited Decision containing the frwkFeedbackResumeIndicator set to SOLICIT USAGE 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. 2.2.4 Resuming and Suspending Periodic Feedback Reporting The PDP may suspend usage monitoring and tracking at the PEP with the frwkFeedbackResumeIndicator 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 ResumeIndicator 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 ResumeIndicator to RESUME USAGE AND REPORTING. The PDP may suspend or resume for all usage instances or the PDP may specify one or more instances that are to be suspended or resumed. The ResumeList contains a tag identifier that references a list of one or more frwkFeedbackSolList entries. The PDP may halt usage monitoring, tracking and reporting of usage policies by removing the associated Linkage entry. Rawlins et al. Expires January 2002 [Page 5] Internet Draft FEED-FRWK-PIB July 2001 2.2.5 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 feedback 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. 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 Type Report Group 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 belong to a new group, Feedback Type Report Group. The policy classes in the Feedback Type Report Group are: 1) Feedback Action Table 2) Feedback Action List Table 3) Feedback Linkage Table 4) Feedback Filter Statistics 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 Rawlins et al. Expires January 2002 [Page 6] Internet Draft FEED-FRWK-PIB July 2001 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 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 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 feedback type reports for the usage instance. This interval is defined in units of the Accounting Timer Rawlins et al. Expires January 2002 [Page 7] Internet Draft FEED-FRWK-PIB July 2001 Interval specified in the client accept message. A value of 0 in this attribute indicates that the usage policy must be solicited. 3.2.4 The Feedback Filter 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 feedback type report message within the maximum interval specified. 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; RoleCombination FROM POLICY-DEVICE-AUX-MIB; 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 Rawlins et al. Expires January 2002 [Page 8] Internet Draft FEED-FRWK-PIB July 2001 Phone: 978-288-8175 Email: khchan@nortelnetworks.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ö ::= { tbd } -- -- 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 feedback type reports." ::= { frwkFeedbackGroupClasses 1} frwkFeedbackActionEntry OBJECT-TYPE SYNTAX FrwkFeedbackActionEntry STATUS current DESCRIPTION "An instance of this class indicates an action the PEP is to take regarding the usage policies." PIB-INDEX { frwkFeedbackActionId} ::= { frwkFeedbackActionTable 1} FrwkFeedbackActionEntry ::= SEQUENCE { frwkFeedbackActionId InstanceId, frwkFeedbackActionIndicator INTEGER, frwkFeedbackActionSpecificPri INTEGER, frwkFeedbackActionListId TagReference } frwkFeedbackActionId OBJECT-TYPE SYNTAX InstanceID STATUS current Rawlins et al. Expires January 2002 [Page 9] Internet Draft FEED-FRWK-PIB July 2001 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 feedback 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 frwkFeedbackActionListId attribute should be ignored, and the action applied to all policies. A value of 1 that the action entry has a specific list of policies to which it is to be applied.ö ::= { frwkFeedbackActionEntry 3} frwkFeedbackActionListId OBJECT-TYPE SYNTAX TagReference STATUS current DESCRIPTION "Identifies a list of frwkFeedbackActionListTable instances associated with the action described by this instance" ::= { frwkFeedbackActionEntry 4} -- -- Feedback Action List Table -- --- frwkFeedbackActionListTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackActionListEntry Rawlins et al. Expires January 2002 [Page 10] Internet Draft FEED-FRWK-PIB July 2001 PIB-ACCESS install STATUS current DESCRIPTION "This class contains the PRIDs 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, frwkFeedbackActionListPRID } ::= { frwkFeedbackActionListTable 1} FrwkFeedbackActionListEntry::= SEQUENCE { frwkFeedbackActionListId InstanceID, frwkFeedbackActionListGroup TagId, frwkFeedbackActionListPRID Prid } frwkFeedbackActionListId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackActionListEntry 1 } frwkFeedbackActionListListGroup OBJECT-TYPE SYNTAX TagId STATUS current DESCRIPTION "Represents the binding between the Action table entry and the Action List table entries" ::= { frwkFeedbackActionListEntry 2 } frwkFeedbackActionListPRID OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "The PRID of the linkage instance(s) belonging to the list of instances identified by the list id upon which the suspend, resume or Rawlins et al. Expires January 2002 [Page 11] Internet Draft FEED-FRWK-PIB July 2001 solict action is directed." ::= { frwkFeedbackActionListEntry 3 } -- -- 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 3} frwkFeedbackLinkEntry OBJECT-TYPE SYNTAX FrwkFeedbackLinkEntry 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." PIB-INDEX {frwkFeedbackLinkId} UNIQUENESS {frwkFeedbackLinkSel, frwkFeedbackLinkUsage } ::= {frwkFeedbackLinkTable 1} FrwkFeedbackLinkEntry ::= SEQUENCE { frwkFeedbackLinkId InstanceID, frwkFeedbackLinkSel Prid, frwkFeedbackLinkUsage OBJECT IDENTIFIER, frwkFeedbackLinkInterval Integer32 } 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 Rawlins et al. Expires January 2002 [Page 12] Internet Draft FEED-FRWK-PIB July 2001 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} frwkFeedbackInterval OBJECT-TYPE SYNTAX Integer32 STATUS current DESCRIPTION "Maximum interval in units of the value of the Accounting Timer specificed by the PDP in the client accept message. A frwkFeedbackInterval of 1 is equal to the value of the Accounting Timer. This value must be 1 or greater. " ::= { frwkFeedbackLinkEntry 4} -- -- The filter statistics usage -- frwkFeedbackFilterStatsUsageTable OBJECT-TYPE SYNTAX SEQUENCE OF FrwkFeedbackFilterStatsUsageEntry PIB-ACCESS report-only STATUS current DESCRIPTION "This class defines the usage attributes that the PEP is to monitor, record and report. It contains the of the PRID of the linkage instance associating the selection criteria instance with the usage instance." ::= { frwkFeedbackGroupClasses 4} frwkFeedbackFilterStatsUsageEntry OBJECT-TYPE SYNTAX FrwkFeedbackFilterStatsUsageEntry STATUS current DESCRIPTION "Defines the attributes the PEP is to monitor, record and report." PIB-INDEX {frwkFeedbackFilterStatsUsageId} UNIQUENESS { frwkFeedbackFilterStatsUsageLinkPRID } ::= {frwkFeedbackFilterStatsUsageTable 1} Rawlins et al. Expires January 2002 [Page 13] Internet Draft FEED-FRWK-PIB July 2001 FrwkFeedbackFilterStatsUsageEntry ::= SEQUENCE { frwkFeedbackFilterStatsUsageId InstanceID, frwkFeedbackFilterStatsUsageLinkPRID Prid, frwkFeedbackFilterStatsUsagePacketCount Counter64, frwkFeedbackFilterStatsUsageByteCount Counter64, fwkFeedbackFilterStatsUsageTimeStamp ExtUTCTime } frwkFeedbackFilterStatsUsageId OBJECT-TYPE SYNTAX InstanceId STATUS current DESCRIPTION "Arbitrary integer index that uniquely identifies an instance of the class." ::= { frwkFeedbackFilterStatsUsageEntry 1 } frwkFeedbackFilterStatsUsageLinkPRID OBJECT-TYPE SYNTAX Prid STATUS current DESCRIPTION "The PRID of the Linkage policy instance used to base this usage policy instance upon." ::= { frwkFeedbackFilterStatsUsageEntry 2 } frwkFeedbackFilterStatsUsagePacketCount OBJECT-TYPE SYNTAX Counter64 STATUS current DESCRIPTION "The count of packets matching the specified filter during the reporting interval." ::= {frwkFeedbackFilterStatsUsageEntry 3} frwkFeedbackFilterStatsUsageByteCount OBJECT-TYPE SYNTAX Counter64 STATUS current DESCRIPTION "The byte count of packets matching the specified filter during the reporting interval." ::= { frwkFeedbackFilterStatsUsageEntry 4} frwkFeedbackFilterStatsSelectTimeStamp OBJECT-TYPE SYNTAX ExtUTCTime STATUS current DESCRIPTION "The last timestamp when a packet was received." ::= { frwkFeedbackFilterStatsSelectEntry 5} END Rawlins et al. Expires January 2002 [Page 14] Internet Draft FEED-FRWK-PIB July 2001 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 between the PEP and the PDP or using the security mechanisms described in the base COPS protocol. 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 Dinesh G Dutt Cisco Systems, Inc. 170 Tasman Dr. San Jose, CA 95134-1706 Phone: 408-527-0955 Email: ddutt@cisco.com Martin Bokaemper Unisphere Networks 700 Silver Seven Road Kanata, On, K2V 1C3 Canada Phone: +1 (613) 591 2735 EMail: mbokaemper@unispherenetworks.com 8 References Rawlins et al. Expires January 2002 [Page 15] Internet Draft FEED-FRWK-PIB July 2001 [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. [COPS-FEED-FRWK] D. Rawlins, A. Kulkarni, "Framework of COPS-PR Policy Usage Feedback", draft-ietf-rap-feedback-frwk-00.txt, July 2001 [COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for Policy Provisioning," draft-ietf-rap-cops-pr-05.txt, March 2000. [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A. Smith, F. Reichmeyer "Framework Policy Information Base", draft- ietf-rap-frameworkpib-03.txt, November 2000 [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning Information," draft-ietf-rap-sppi-05.txt, February 2001. Rawlins et al. Expires January 2002 [Page 16]