Internet Draft                                        Diana Rawlins
    Expiration:  February  May 2003                                      WorldCom
    File: draft-ietf-rap-feedback-fr-pib-03.txt draft-ietf-rap-feedback-fr-pib-04.txt           Amol Kulkarni
                                                                  Intel
                                                           Kwok Ho Chan
                                                        Nortel Networks
                                                       Martin Bokaemper
                                                     Unisphere
                                                       Juniper Networks
                                                            Dinesh Dutt
                                                                  Cisco

           Framework of COPS-PR Policy Information Base for Policy Usage Feedback

                     Last Updated June 30, November 2, 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.

Abstract

     This document describes a Policy Information Base (PIB) to control
     policy usage collection and reporting in a device.

     The provisioning classes specified here allow a Policy Decision
     Point (PDP) to select which policy objects should collect usage
     information, what information should be collected and when it
     should be reported.

     This PIB requires the presence of other PIBs (defined elsewhere)
     that provide the policy objects that usage information is collected
     from.

Rawlins et al.          Expires December 2002                [Page 1] 

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
     the policy classes for a feedback framework Policy information base
     (PIB).

Table of Contents

   1 Introduction.....................................................4 Introduction.....................................................3
   2 General Concepts.................................................4 Concepts.................................................3
   2.1 Selection, Usage and Linkage Policies..........................4 Policies..........................3
   2.2 Normal Operations..............................................5 Operations..............................................4
   2.2.1 Connection Establishment and Initial Configuration Request...5 Request...4
   2.2.2 Unsolicited Reports - Periodic Reporting.....................6 Reporting.....................5
   2.2.3 Unsolicited Reports - Reporting Conditions...................6 Conditions...................5
   2.2.4 Solicited Reports............................................6 Reports............................................5
   2.2.5 Resuming and Suspending Periodic Feedback Reporting..........7 Reporting..........6
   2.2.6 Failover.....................................................7 Failover.....................................................6
   2.3 Usage Policy and Under-specified Selection Criteria............7 Criteria............6
   3 Summary of the Feedback Framework Policy Information Base........9 Base........7
   3.1 SPPI ACCESS clause report-only.................................9 report-only.................................7
   3.2 Usage32 and Usage64 textual conventions........................7
   3.3 Feedback Groups and PRCs.......................................9
   3.2.1 Feedback Action Table.......................................10
   3.2.2 PRCs.......................................8
   3.3.1 Feedback List Table.........................................10
   3.2.3 The Action..............................................8
   3.3.2 Feedback Selection Usage Combination Capability Table...10
   3.2.4 The Action List.........................................9
   3.3.3 Feedback Report Linkage Table...........................11
   3.2.5 The Capability..................................9
   3.3.4 Feedback Linkage.............................................9
   3.3.5 Feedback Traffic Statistics Threshold Table.............11 Threshold.......................10
   4 The Feedback Framework PIB Module...............................11
   5 Security Considerations.........................................25 Module...............................10
   6 Acknowledgements................................................25 IANA Considerations.............................................29
   7 Authors' Addresses..............................................25 Acknowledgements................................................29
   8 References......................................................26 Authors' Addresses..............................................29
   9 References......................................................30
   9.1 Normative References..........................................30
   9.2 Informational References......................................30
   10 Copyright......................................................30

Rawlins et al.          Expires December 2002                [Page 2] 

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 frwkRoleComboEntry frwkRoleCombo instance, which may be used 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 of an interface capability set name and role combination.

   The usage policy defines what attributes are recorded by the PEP.
   These policies have an ACCESS clause of Report. 'report-only'. 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 frwkFeedbackTraffic and frwkFeedbackIfTrafficUsage. frwkFeedbackIfTraffic. 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 the value of the usage
   feedback PRC.

Rawlins et al.          Expires December 2002                [Page 3] 
       -----------------     ------------------      -----------------
      |                 |   |                  |    |                 |
      | 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 the 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 frwkFeedbackTrafficUsageLinkRef frwkFeedbackTrafficLinkRef

2.2 Normal Operations

2.2.1 Connection Establishment and Initial Configuration Request

   The Accounting Timer object in the COPS Connection Accept message
   contains the minimum number of seconds between reporting intervals as
   described in [COPS] and [COPS-FEEDBACK-FRWK]. [FEEDBACKfWK]. 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 frwkPRCSupport instances [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.
   frwkFeedbackLink class. It may also specify reporting thresholds by
   including an instance of a threshold class (e.g.
   frwkFeedbackTrafficThresholdTable)
   frwkFeedbackTrafficThreshold) in the decision. The PEP monitors and
   records the usage per the conditions defined by its associated
   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. frwkFeedbackAction class.

Rawlins et al.          Expires December 2002                [Page 4] 

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 usage 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.
   frwkFeedbackLink instances. Supported conditions are:
   ChangeOnly
        If this flag is set in the frwkFeedbackLinkFlags field, attribute, 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, attribute, 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

   The PDP may solicit policy usage feedback by issuing an unsolicited
   Decision containing the frwkFeedbackActionIndicator set to SOLICIT
   USAGE REPORT NOW.
   'solicitReport'. 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.

Rawlins et al.          Expires December 2002                [Page 5] 
   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. 'suspendMonitoringAndReports'. 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. 'suspendReports'. 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.
   'resume'.

   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 attribute contains a tag identifier that
   references a list of one or more frwkFeedbackActionListTable entries. frwkFeedbackActionList instances.

   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 by issuing an
   unsolicited decision containing the frwkFeedbackResumeIndicator set
   to resume reporting. 'resume'. The PEP should resume reporting at the next appropriate
   feedback interval established upon the acceptance of the re-connection. 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 Usage Policy and Under-specified Selection Criteria

   Some of the usage 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 (OID) of the object that is shared between all the
   assignment
   assignments 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

Rawlins et al.          Expires December 2002                [Page 6] 
   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. assignments.
   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:

      The frwkRoleComboEntry

      A frwkRoleCombo instance may be used as a selection criteria criteria,
      identifying a set of interfaces through their the role
      combination and capability set. However,
      there is a more granular piece of information associated with
      capability set and role combination which If it is the interface index.
      The desired to get per-
      interface index is associated with a specific capability set
      and role combination.

      The frwkIfFeedbackTrafficUsageEntry may be linked for feedback
      purposes with a frwkRoleComboEnry instance. The usage policy
      frwkFeedbackIfTrafficUsageEntry contains the item
      frwkFeedbackIfTrafficUsageIfIndex that is populated by traffic statistics, the PEP.
      The frwkFeedbackIfTrafficUsageIfIndex identifies usage PRC has to include an
      additional attribute to qualify the specific
      IfIndex for a given capability set and role combination selection
      pair that is being monitored.

        As the selection criteria policy a frwkRoleComboEntry is used
        which contains interface.

      This could be achieved by linking the qualifying attributes:

                   frwkRoleComboPrid         InstanceId,
                   frwkRoleComboRoles        RoleCombination,
                   frwkRoleComboCapSetName   SnmpAdminString

        To monitor traffic counts of frwkFeedbackIfTraffic class
      with a role combination and capability
        set the policy would be combined frwkRoleCombo instance in a frwkLinkageEntry with the
        FrwkFeedbackTrafficUsage PRC. This combination frwkFeedbackLink instance.
      Multiple frwkFeedbackIfTraffic instances will result in
        only one FrwkFeedbackTrafficUsageEntry to be created which only
        contains the traffic counters. The traffic counts would reflect by the aggregated counts of all interface indices associated with
        a given capability set and role combination.

        Traffic count details
      PEP, one for each interface index can be obtained selected by linking the frwkRoleComboEntry and frwkRoleCombo
      instance. The frwkFeedbackIfTraffic class contains the
        frwkFeedbackIfTrafficUsage PRC.

        By combining a  frwkRoleComboEntry as selection criteria with
      frwkFeedbackIfTrafficIfIndex attribute that allows the FrwkFeedbackIfTrafficUsage PRC, all PDP to
      identify each interface's individual counters when the assignments are
        selected and multiple FrwkFeedbackIfTrafficUsageEntries get
        created. Each entry not only carries PEP
      reports the desired frwkFeedbackIfTraffic instances.

      If traffic
        counters but also usage collection is only desired for an individual
      interface, a selection criteria should be used that qualifies the IfIndex qualifying attributes to
        associate
      interface completely, for example a frwkIfRoleCombo instance.
      In this case it with can be linked to the assignment:

         frwkFeedbackIfTrafficUsageId              InstanceId,
         frwkFeedbackIfTrafficUsageLinkRefID       ReferenceId,
         frwkFeedbackIfTrafficUsageIfIndex         InterfaceIndex,
         frwkFeedbackIfTrafficUsagePacketCount     Counter64,
         frwkFeedbackIfTrafficUsageByteCount       Counter64 usage class that has no
      additional qualifying attributes, frwkFeedbackTraffic.

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, Usage32 and
   solicit characteristics as well as Usage64 textual conventions

Rawlins et al.          Expires December 2002                [Page 7] 
   The SPPI does not support the common usage and selection
   criteria polices. These policy classes are common to account type
   reporting Counter32/64 textual conventions (TC)
   of SNMP - for various technologies feedback collection two similar textual conventions
   have been defined in this PIB: Usage32 and apply Usage64.

   In addition to ALL SUBJECT-
   CATEGORIES. The the differential functionality of 'Counter', where
   only the difference between two samples generally carries
   information, a single value of a 'Usage' attribute usually provides
   absolute information, since
   - its initial value is known (0)
   - no wrap-around events should occur
   - the time or event when the initial value was set should be
     available directly or indirectly from other objects.

   When 'Usage' attributes are defined in a PRC, events that could
   cause a reset of the attribute to it's initial value should be
   defined in the description as well as the mechanism that allows the
   PDP to detect the time of the last reset.

   No usual COPS activity however should cause the reset of a Usage
   attribute. In the case of a suspension of monitoring activity
   (frwkFeedbackActionIndicator set to 'suspendMonitoringAndReports'),
   'Usage' attributes should keep their values and continue counting
   after monitoring is resumed.

3.3 Feedback Groups and PRCs

   These policy classes defined in this PIB 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
      5)
      - Feedback Traffic Statistics Threshold Table

   The policy classes in the Feedback Usage Group are:
      1)
      - Feedback Traffic Statistics Usage Table
      2)
      - Feedback Interface Traffic Statistics Usage Table

   The policy classes class in the Feedback Selection Group are:
      1) is:
      - Feedback RoleCombo Filter Selection Table
   Feedback PRI Selection Table

3.2.1

3.3.1 Feedback Action Table

   The Feedback Action Table class 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

Rawlins et al.          Expires December 2002                [Page 8] 
   periodic reporting or solicit immediate reporting. The action may
   affect all feedback policies or be associated with one or more
   policy
   frwkFeedbackLink instances.

   The Feedback Action Indicator frwkFeedbackActionIndicator attribute defines the action. The Feedback
   Specific PRI
   frwkFeedbackActionPri attribute indicates whether the action applies
   to all of the usage policies or to a list. The Feedback List ID
   frwkFeedbackActionList attribute 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

3.3.2 Feedback Action List Table

   This table contains a list of PRIDs class defines sets 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 that can be referred to
   from the frwkFeedbackActionList attribute.

3.3.3 Feedback Action List ID.

3.2.3 The Feedback Selection Usage Combination Linkage Capability Table

   This table class defines the valid selection criteria PRC, and usage PRC and
   threshold PRC combinations supported.

3.2.4 The supported by the PEP.

3.3.4 Feedback Report Linkage Table

   This table class links the selection criteria instance with the usage
   instance. It specifies the PRID of the selection criteria and the PRC
   of the usage instance.
   class. 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

Rawlins et al.          Expires December 2002                [Page 9] 
   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.

3.2.5 The

3.3.5 Feedback Traffic Statistics Threshold Table

   This table class is used to provide threshold values for the attributes
   described in the above traffic usage tables.

3.2.6 The classes below.

3.3.6 Feedback Traffic Statistics Usage Table

   This table describes class includes the packet counts, byte counts, last timestamp
   when a packet was received counts and the PRID of a reference to
   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.7 The

3.3.7 Feedback Interface Traffic Statistics Usage Table

   This table class is similar to the table described above, previous Feedback Traffic class, except
   that it includes an additional reference to an interface index. This table
   class should be used with a selection criteria instance 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 element's assignment.

3.2.8 The

3.3.8 Feedback RoleCombo Filter Selection Table

   This table class is used to identify a as selection criteria of Role
   Combination and either IP or 802 Filter. This Role Combination and
   Filter is the basis upon which the usage performs monitoring based on role combination,
   capability set and
   collection. a filter instance.

4 The Feedback Framework PIB Module

   FEEDBACK-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN

      IMPORTS
          ExtUTCTime,
          pib, Unsigned32, Unsigned64, Integer32,
          MODULE-IDENTITY, OBJECT-TYPE OBJECT-TYPE, MODULE-COMPLIANCE, OBJECT-GROUP
                  FROM COPS-PR-SPPI
          TruthValue, TEXTUAL-CONVENTION
                  FROM SNMPv2-TC
          InstanceId, ReferenceId ReferenceId, Prid,
          TagId, TagReferenceId
                  FROM COPS-PR-SPPI-TC
          Counter64
          PrcIdentifierOid, PrcIdentifierOidOrZero
                  FROM FRAMEWORK-TC-PIB
          frwkRoleComboEntry
                  FROM SNMPv2-SMI FRAMEWORK-PIB
          InterfaceIndex
                  FROM IF-MIB;

      feedbackPolFrameworkPib

Rawlins et al.          Expires December 2002               [Page 10] 
        frwkFeedbackPib  MODULE-IDENTITY
          SUBJECT-CATEGORIES  { all }
          LAST-UPDATED "200011171000Z" "200210281000Z"
          ORGANIZATION "IETF RAP WG"
          CONTACT-INFO " "IETF RAP WG
                        Email: rap@ops.ietf.org

                        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. Networks.
                        600 Technology Park Drive
                        Billerica, MA 01821 USA
                        Phone: 978-288-8175
                        Email: khchan@nortelnetworks.com

                        Martin Bokaemper
                       Unisphere
                        Juniper Networks
                        700 Silver Seven Road
                        Kanata, ON, K2V 1C3, Canada
                        Phone: 613-591-2735
                        Email: mbokaemper@unispherenetworks.com" mbokaemper@juniper.net

                        Dinesh G Dutt
                        Cisco Systems, Inc.
                        170 Tasman Dr.
                        San Jose, CA 95134-1706
                        Phone: 408-527-0955
                        Email: ddutt@cisco.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"
      REVISION     "200210280000Z"
      DESCRIPTION
               "Initial version, published in RFC xxxx."
               -- xxxx to be assigned by RFC editor

            ::= { pib xx } -- xx will be assigned by IANA
   --
   -- The feedback report group IANA, according
                           --

   frwkFeedbackGroupClasses
                  OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib  1 } to RFC 3159 (IANA considerations)

Rawlins et al.          Expires December 2002               [Page 11] 
   --
   --  Feedback Action Table Textual Conventions
   --

   frwkFeedbackActionTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF FrwkFeedbackActionEntry
        PIB-ACCESS      install

   Usage32 ::= TEXTUAL-CONVENTION
        STATUS    current
        DESCRIPTION
                 "This class contains
                "The Usage32 type represents a single PRI that indicates
                 that non-negative integer
                which monotonically increases.
                Usage32 initial value is 0 and the PEP object-type using
                Usage32 needs to specify when it is initialized.

                The Usage32 type is intended to resume reflect the sending absolute
                number of counted events, so that even a new PDP
                after a COPS accounting type reports."

           ::= { frwkFeedbackGroupClasses  1}

   frwkFeedbackActionEntry OBJECT-TYPE
        SYNTAX  FrwkFeedbackActionEntry
        STATUS  current
        DESCRIPTION
                   "An instance of this class reconnect can indicates a action use the PEP value directly.

                If there is the possibility that the maximum Usage32
                value of 2^32-1 is exceeded during the lifetime
                of the Usage32 object, the larger Usage64 type
                should be used.

                If conditions other than the reset of the COPS
                subsystem exist that disrupt the monotonic
                characteristics of Usage32, these conditions and a
                method how to take regarding detect their presence should be
                specified in the description of the object-type using
                Usage32 or its enclosing object-types (e.g. the
                Entry or Table object-type of the Usage32
                object-type).

                Whenever the monotonic increase of Usage32 is violated,
                it should be reset to 0 and the fact that this occurred
                should be indicated through an appropriate mechanism,
                for example a corresponding object of type TimeStamp
                or TimeAndDate."
        SYNTAX Unsigned32

   Usage64 ::= TEXTUAL-CONVENTION
        STATUS    current
        DESCRIPTION
                "The Usage64 type represents a non-negative integer
                which monotonically increases.
                Usage64 initial value is 0 and the object-type using
                Usage64 needs to specify when it is initialized.

                The Usage64 type is intended to reflect the absolute
                number of counted events, so that even a new PDP
                after a COPS reconnect can use the value directly.

                The lifetime of the Usage64 object should be defined
                in a way that ensures the maximum Usage64 value of
                2^64-1 is never exceeded.

Rawlins et al.          Expires December 2002               [Page 12] 
                If conditions other than the reset of the COPS
                subsystem exist that disrupt the monotonic
                characteristics of Usage64, these conditions and a
                method how to detect their presence should be
                specified in the description of the object-type using
                Usage64 or its enclosing object-types (e.g. the
                Entry or Table object-type of the Usage64
                object-type).

                Whenever the monotonic increase of Usage64 is violated,
                it should be reset to 0 and the fact that this occurred
                should be indicated through an appropriate mechanism,
                for example a corresponding object of type TimeStamp
                or TimeAndDate."
        SYNTAX Unsigned64

   --
   -- The feedback report group
   --

   frwkFeedbackGroupClasses
                  OBJECT IDENTIFIER ::= { frwkFeedbackPib  1 }

   --
   --  Feedback Action Table
   --

   frwkFeedbackActionTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF FrwkFeedbackActionEntry
        PIB-ACCESS      install
        STATUS          current
        DESCRIPTION
                "This class represents commands that the PDP sends to
                suspend, resume or solicit collection or reporting of
                usage data."

           ::= { frwkFeedbackGroupClasses  1}

   frwkFeedbackActionEntry OBJECT-TYPE
        SYNTAX  FrwkFeedbackActionEntry
        STATUS  current
        DESCRIPTION
                "Each frwkFeedbackActionEntry represents a command from
                the PDP. FrwkFeedbackActionIndicator specifies the
                command itself while frwkFeedbackActionSpecificPri
                indicates if all frwkFeedbackLink objects in the system
                are affected by the command, or just the usage policies." set that is
                referenced by frwkFeedbackActionList."
        PIB-INDEX { frwkFeedbackActionId}

        ::= { frwkFeedbackActionTable 1}

Rawlins et al.          Expires December 2002               [Page 13] 
   FrwkFeedbackActionEntry ::= SEQUENCE {
           frwkFeedbackActionId                 InstanceId,
           frwkFeedbackActionIndicator          INTEGER,
           frwkFeedbackActionSpecificPri        TruthValue,
           frwkFeedbackActionList               TagReferenceId
        }

   frwkFeedbackActionId  OBJECT-TYPE
        SYNTAX        InstanceId
        STATUS        current
        DESCRIPTION
           " An
           "An arbitrary integer index that uniquely identifies an
            instance of the frwkFeedbackActionTable frwkFeedbackAction 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)
                   suspendMonitoringAndReports(0),
                   suspendReports(1),
                   resume(2),
                   solicitReport(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  suspendMonitoringAndReports
                   (1)  SUSPEND_REPORTS_ONLY  suspendReports
                   (2)  RESUME_USAGE AND REPORTING  resume
                   (3)  SOLICIT USAGE REPORT NOW  solicitReport "

          ::= { 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 frwkFeedbackActionListTag }
           STATUS        current
           DESCRIPTION

Rawlins et al.          Expires December 2002               [Page 14] 
                    "Identifies a list set of
                      frwkFeedbackActionListTable frwkFeedbackActionList
                    instances
                      associated with the action described by that this instance" action should affect."
           ::= { frwkFeedbackActionEntry 4}

   --
   --  Feedback Action List Table
   --

   frwkFeedbackActionListTable OBJECT-TYPE
           SYNTAX          SEQUENCE OF FrwkFeedbackActionListEntry
           PIB-ACCESS      install
           STATUS          current
           DESCRIPTION
                    "This class contains the ReferenceIDs defines groups of the linkage instance which are to instances.
                    Groups can be impacted referenced by commands sent by the frwkFeedbackActionIndicator for
                    PDP in a frwkFeedbackActionEntry -in this
                         list." case the
                    command affects all linkage instances that are part
                    of the group."
           ::= { frwkFeedbackGroupClasses  2}

   frwkFeedbackActionListEntry OBJECT-TYPE
           SYNTAX          FrwkFeedbackActionListEntry
           STATUS          current
           DESCRIPTION
                    "This class identifies
                    "Each instance associates a set of linkage instances
                     for which the  PDP is suspending, resuming or
                     soliciting usage feedback." instance with a
                     specific ActionListGroup."

           PIB-INDEX {frwkFeedbackActionListId }
           UNIQUENESS { frwkFeedbackActionListGroup, frwkFeedbackActionListTag,
                        frwkFeedbackActionListRefID
                      }
           ::= { frwkFeedbackActionListTable 1}

   FrwkFeedbackActionListEntry::= SEQUENCE {
              frwkFeedbackActionListId          InstanceId,
              frwkFeedbackActionListGroup
              frwkFeedbackActionListTag         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

   frwkFeedbackActionListTag OBJECT-TYPE
           SYNTAX       TagId
           STATUS       current
           DESCRIPTION
                     "Represents the binding between the Action

Rawlins et al.          Expires December 2002               [Page 15] 
                      table entry and the Action List table entries"
           ::= { frwkFeedbackActionListEntry 2 }

   frwkFeedbackActionListRefID   OBJECT-TYPE
           SYNTAX       ReferenceId
           PIB-REFERENCES { frwkFeedbackLinkEntry }
           STATUS       current
           DESCRIPTION
                         "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 Link Capability Table
   --
   frwkFeedbackSelUsageComboCapsTable

   frwkFeedbackLinkCapsTable OBJECT-TYPE
        SYNTAX           SEQUENCE OF FrwkFeedbackSelUsageComboCapsEntry FrwkFeedbackLinkCapsEntry
        PIB-ACCESS       notify
        STATUS           current
        DESCRIPTION
                "This table defines the valid combinations
                "Instances of the frwkFeedbackLink class reference
                instances of selection criteria PRCs, the usage PRCs and the threshold PRCs that classes and a
                usage class.
                This class allows the PEP supports." to communicate valid
                combinations of these three classes to the PDP."
         ::= { frwkFeedbackGroupClasses 3}

   frwkFeedbackSelUsageComboCapsEntry

   frwkFeedbackLinkCapsEntry OBJECT-TYPE
        SYNTAX          FrwkFeedbackSelUsageComboCapsEntry          FrwkFeedbackLinkCapsEntry
        STATUS          current
        DESCRIPTION
                 "The attributes of this class identify valid
                  combinations of selection criteria, usage and
                  threshold PRCs classes for feedback supported by the PEP
                  device." feedback."
        PIB-INDEX { frwkFeedbackSelUsageComboCapsId frwkFeedbackLinkCapsId }
        UNIQUENESS {
                    frwkFeedbackSelUsageComboCapsSelection,
                    frwkFeedbackSelUsageComboCapsUsage,
                    frwkFeedbackSelUsageComboCapsThreshold
                    frwkFeedbackLinkCapsSelection,
                    frwkFeedbackLinkCapsUsage,
                    frwkFeedbackLinkCapsThreshold
                 }
        ::= {frwkFeedbackSelUsageComboCapsTable {frwkFeedbackLinkCapsTable 1}

   FrwkFeedbackSelUsageComboCapsEntry

   FrwkFeedbackLinkCapsEntry ::= SEQUENCE {
          frwkFeedbackSelUsageComboCapsId
          frwkFeedbackLinkCapsId         InstanceId,
          frwkFeedbackSelUsageComboCapsSelection  OBJECT IDENTIFIER,
          frwkFeedbackSelUsageComboCapsUsage      OBJECT IDENTIFIER,
          frwkFeedbackSelUsageComboCapsThreshold  OBJECT IDENTIFIER
          frwkFeedbackLinkCapsSelection  PrcIdentifierOid,
          frwkFeedbackLinkCapsUsage      PrcIdentifierOid,
          frwkFeedbackLinkCapsThreshold  PrcIdentifierOidOrZero
   }

   frwkFeedbackSelUsageComboCapsId

Rawlins et al.          Expires December 2002               [Page 16] 
   frwkFeedbackLinkCapsId OBJECT-TYPE
        SYNTAX        InstanceId
        STATUS        current
        DESCRIPTION
           " An
           "An arbitrary integer index that uniquely identifies an
             instance of the frwkFeedbackSelUsageComboCapsEntry frwkFeedbackLinkCaps class."
        ::= { frwkFeedbackSelUsageComboCapsEntry frwkFeedbackLinkCapsEntry 1}

   frwkFeedbackSelUsageComboCapsSelection

   frwkFeedbackLinkCapsSelection OBJECT-TYPE
        SYNTAX        OBJECT IDENTIFIER        PrcIdentifierOid
        STATUS        current
        DESCRIPTION
                "The PRC identifier of the selection a class that is supported by the
                device for feedback selection in the combination defined by with the
                usage and threshold classes referenced in this
                instance."
        ::= { frwkFeedbackSelUsageComboCapsEntry frwkFeedbackLinkCapsEntry 2}

   frwkFeedbackSelUsageComboCapsUsage

   frwkFeedbackLinkCapsUsage OBJECT-TYPE
        SYNTAX        OBJECT IDENTIFIER        PrcIdentifierOid
        STATUS        current
        DESCRIPTION
                "The PRC identifier of the usage policy class that is supported by
                the device PEP in combination with the selection PRC and the threshold PRC defined
                classes referenced in this instance."
        ::= { frwkFeedbackSelUsageComboCapsEntry frwkFeedbackLinkCapsEntry 3}

   frwkFeedbackSelUsageComboCapsThreshold

   frwkFeedbackLinkCapsThreshold OBJECT-TYPE
           SYNTAX        OBJECT IDENTIFIER        PrcIdentifierOidOrZero
           STATUS        current
           DESCRIPTION
                "The PRC identifier of the threshold class that is
                supported by the device PEP in the combination defined by with the selection
                and usage classes referenced in this instance." instance.
                0.0 is used if this combination does not allow a
                threshold."
           ::= { frwkFeedbackSelUsageComboCapsEntry frwkFeedbackLinkCapsEntry 4}

   --
   -- The Feedback Report Linkage Table
   --

   frwkFeedbackLinkTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF FrwkFeedbackLinkEntry
        PIB-ACCESS      Install      install
        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."

Rawlins et al.          Expires December 2002               [Page 17] 
        ::= { 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 { frwkFeedbackLinkId }
        UNIQUENESS {frwkFeedbackLinkSel,
                    frwkFeedbackLinkUsage }
        ::= {frwkFeedbackLinkTable 1}

   FrwkFeedbackLinkEntry ::= SEQUENCE {
          frwkFeedbackLinkId         InstanceId,
          frwkFeedbackLinkSel        Prid,
          frwkFeedbackLinkUsage      OBJECT IDENTIFIER,      PrcIdentifierOid,
          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 Policy Class instance as the monitoring
             point, or the PRID of the selection criteria instance that
             defines the conditions for monitoring, to be use by the
             PEP for usage reporting."

        ::= { frwkFeedbackLinkEntry 2}

   frwkFeedbackLinkUsage OBJECT-TYPE
        SYNTAX      OBJECT IDENTIFIER      PrcIdentifierOid
        STATUS      current
        DESCRIPTION
             "The PRC identifier of the usage policy class that the PEP uses to
             monitor, record and report."

        ::= { frwkFeedbackLinkEntry 3}

   frwkFeedbackLinkInterval  OBJECT-TYPE
        SYNTAX   Integer32

Rawlins et al.          Expires December 2002               [Page 18] 
        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
        DESCRIPTION
                "The PRID of the a 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Ă 'periodic' flag is set, the PEP will provide
                unsolicited reports at the rate specified in
                frwkFeedbackLinkInterval.
                If the ŠperiodicĂ 'periodic' flag is not set, reports will only be
                generated when solicited by the PDP.
                The ŠthresholdĂ 'threshold' and ŠchangeOnlyĂ 'changeOnly' flags make the
                periodic reports conditional - these flags only make
                sense in combination with the ŠperiodicĂ 'periodic' flag."

           ::= { frwkFeedbackLinkEntry 6}

   --
   -- The Threshold class that accompanies the above Usage PRCs
   --

   frwkFeedbackTrafficThresholdTable

   frwkFeedbackTrafficThresTable OBJECT-TYPE
           SYNTAX         SEQUENCE OF FrwkFeedbackTrafficThresholdEntry FrwkFeedbackTrafficThresEntry
           PIB-ACCESS     Install     install
           STATUS         current

Rawlins et al.          Expires December 2002               [Page 19] 
           DESCRIPTION
                 "This class defines the threshold attributes
                  corresponding to usage attributes specified in
                  frwkFeedbackTrafficUsageTable,
                  frwkFeedbackIfTrafficUsageTable
                  frwkFeedbackTrafficTable, frwkFeedbackIfTrafficTable
                  and other similar usage classes.

                  The usage object is considered to match the threshold
                  condition if at least one of the following expression evaluates packet or byte
                  threshold conditions match.

                  The byte and packet thresholds are considered to
                  ŠTRUEĂ:
                  {
                    byteCond = (ByteThreshold != NULL) ?
                            (ByteThreshold > ByteCounter) : FALSE;
                    packetCond (PacketThreshold !=
                  match, if the threshold is present (not ASN1 NULL) ?
                            (PacketThreshold > PacketCounter) : FALSE;
                    return ( byteCond || packetCond );
                  }"
                  and the corresponding usage value exceeds the
                  threshold."

           ::= { frwkFeedbackGroupClasses  5}

      frwkFeedbackTrafficThresholdEntry

   frwkFeedbackTrafficThresEntry OBJECT-TYPE
           SYNTAX          FrwkFeedbackTrafficThresholdEntry          FrwkFeedbackTrafficThresEntry
           STATUS          current
           DESCRIPTION
                    "Defines the attributes to hold threshold values."
           PIB-INDEX {frwkFeedbackTrafficThresholdId} {frwkFeedbackTrafficThresId}

           ::= {frwkFeedbackTrafficThresholdTable {frwkFeedbackTrafficThresTable 1}

      FrwkFeedbackTrafficThresholdEntry

   FrwkFeedbackTrafficThresEntry ::= SEQUENCE {
            frwkFeedbackTrafficThresholdId
            frwkFeedbackTrafficThresId                  InstanceId,
            frwkFeedbackTrafficThresholdPacketThreshold     Integer64,
            frwkFeedbackTrafficThresholdByteThreshold       Integer64
            frwkFeedbackTrafficThresPackets            Unsigned64,
            frwkFeedbackTrafficThresBytes              Unsigned64
   }

   frwkFeedbackTrafficThresholdId

   frwkFeedbackTrafficThresId   OBJECT-TYPE
           SYNTAX       InstanceId
           STATUS       current
           DESCRIPTION
                     "Arbitrary integer index that uniquely identifies
                      an instance of the class."
           ::= { frwkFeedbackTrafficThresholdEntry frwkFeedbackTrafficThresEntry 1 }

   frwkFeedbackTrafficThresholdPacketThreshold

   frwkFeedbackTrafficThresPackets   OBJECT-TYPE
           SYNTAX       Integer64       Unsigned64
           STATUS       current
           DESCRIPTION
                     "The threshold, in terms of packets, that must be
                      matched or exceeded to trigger a report in the
                      next reporting interval." interval.
                     A value of 0 or a missing value ("
           ::= { frwkFeedbackTrafficThresholdEntry frwkFeedbackTrafficThresEntry 2 }

   frwkFeedbackTrafficThresholdByteThreshold

   frwkFeedbackTrafficThresBytes   OBJECT-TYPE
           SYNTAX       Integer64       Unsigned64
           STATUS       current

Rawlins et al.          Expires December 2002               [Page 20] 
           DESCRIPTION
                   "The threshold, in terms of bytes, that must be
                    exceeded to trigger a report in the next reporting
                    interval."
           ::= { frwkFeedbackTrafficThresholdEntry frwkFeedbackTrafficThresEntry 3 }

   --
   -- All actual usage classes are in the separate
   -- FrwkFeedbackUsageClasses frwkFeedbackUsageClasses group
   --

   frwkFeedbackUsageClasses
       OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib frwkFeedbackPib  2 }

   --
   -- The generic traffic (byte & packet count) usage class
   --

   frwkFeedbackTrafficUsageTable

   frwkFeedbackTrafficTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF FrwkFeedbackTrafficUsageEntry FrwkFeedbackTrafficEntry
        PIB-ACCESS      report-only
        STATUS          current
        DESCRIPTION
                 "This class defines the usage attributes that the PEP
                  is to monitor for plain traffic handling elements
                  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

   frwkFeedbackTrafficEntry OBJECT-TYPE
        SYNTAX          FrwkFeedbackTrafficUsageEntry          FrwkFeedbackTrafficEntry
        STATUS          current
        DESCRIPTION
                 "Defines the attributes the PEP is to monitor,
                  record and report."
        PIB-INDEX {frwkFeedbackTrafficUsageId} {frwkFeedbackTrafficId}
        UNIQUENESS { frwkFeedbackTrafficUsageLinkRefID frwkFeedbackTrafficLinkRefID }

        ::= {frwkFeedbackTrafficUsageTable {frwkFeedbackTrafficTable 1}

   FrwkFeedbackTrafficUsageEntry

   FrwkFeedbackTrafficEntry ::= SEQUENCE {
         frwkFeedbackTrafficUsageId
         frwkFeedbackTrafficId              InstanceId,
         frwkFeedbackTrafficUsageLinkRefID
         frwkFeedbackTrafficLinkRefID       ReferenceId,
         frwkFeedbackTrafficUsagePacketCount     Counter64,
         frwkFeedbackTrafficUsageByteCount       Counter64
         frwkFeedbackTrafficPacketCount     Usage64,
         frwkFeedbackTrafficByteCount       Usage64

   }

   frwkFeedbackTrafficUsageId

Rawlins et al.          Expires December 2002               [Page 21] 
   frwkFeedbackTrafficId   OBJECT-TYPE
        SYNTAX       InstanceId
        STATUS       current
        DESCRIPTION
                  "Arbitrary integer index that uniquely identifies
                   an instance of the class."
        ::= { frwkFeedbackTrafficUsageEntry frwkFeedbackTrafficEntry 1 }

   frwkFeedbackTrafficUsageLinkRefID

   frwkFeedbackTrafficLinkRefID  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 frwkFeedbackTrafficEntry 2 }

   frwkFeedbackTrafficUsagePacketCount

   frwkFeedbackTrafficPacketCount OBJECT-TYPE
        SYNTAX       Counter64       Usage64
        STATUS       current
        DESCRIPTION
                  "The count of packets handled by the associated
                   element during the reporting interval."
                   element."

        ::= {frwkFeedbackTrafficUsageEntry {frwkFeedbackTrafficEntry 3}

   frwkFeedbackTrafficUsageByteCount

   frwkFeedbackTrafficByteCount OBJECT-TYPE
        SYNTAX       Counter64       Usage64
        STATUS       current
        DESCRIPTION
                   "The byte count of packets handled by the associated
                    element."
        ::= { frwkFeedbackTrafficUsageEntry frwkFeedbackTrafficEntry 4}

   --
   -- The traffic usage class, qualified for an interface
   --

   frwkFeedbackIfTrafficUsageTable

   frwkFeedbackIfTrafficTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF FrwkFeedbackIfTrafficUsageEntry FrwkFeedbackIfTrafficEntry
        PIB-ACCESS      report-only
        STATUS          current
        DESCRIPTION
                "A usage PRC class similar to the basic TrafficUsage Traffic class that
                also contains a reference to an interface index. This
                class should be used with a underspecified selection
                criteria entry from the frwkRoleComboTable that matches
                an element that can be assigned to multiple interface
                indices. The interface field can be used to associate

Rawlins et al.          Expires December 2002               [Page 22] 
                the instances of this class with the specific elementĂs element's
                assignment."
        ::= { frwkFeedbackUsageClasses  2 }

   frwkFeedbackIfTrafficUsageEntry

   frwkFeedbackIfTrafficEntry OBJECT-TYPE
        SYNTAX          FrwkFeedbackIfTrafficUsageEntry          FrwkFeedbackIfTrafficEntry
        STATUS          current
        DESCRIPTION
                 "Defines the attributes the PEP is to monitor,
                  record and report."
        PIB-INDEX {frwkFeedbackIfTrafficUsageId} {frwkFeedbackIfTrafficId}
        UNIQUENESS { frwkFeedbackIfTrafficUsageLinkRefID,
                     frwkFeedbackIfTrafficUsageIfIndex frwkFeedbackIfTrafficLinkRefID,
                     frwkFeedbackIfTrafficIfIndex }

        ::= {frwkFeedbackIfTrafficUsageTable {frwkFeedbackIfTrafficTable 1}

   FrwkFeedbackIfTrafficUsageEntry

   FrwkFeedbackIfTrafficEntry ::= SEQUENCE {
         frwkFeedbackIfTrafficUsageId
         frwkFeedbackIfTrafficId              InstanceId,
         frwkFeedbackIfTrafficUsageLinkRefID
         frwkFeedbackIfTrafficLinkRefID       ReferenceId,
         frwkFeedbackIfTrafficUsageIfIndex
         frwkFeedbackIfTrafficIfIndex         InterfaceIndex,
         frwkFeedbackIfTrafficUsagePacketCount     Counter64,
         frwkFeedbackIfTrafficUsageByteCount       Counter64
         frwkFeedbackIfTrafficPacketCount     Usage64,
         frwkFeedbackIfTrafficByteCount       Usage64

   }

   frwkFeedbackIfTrafficUsageId

   frwkFeedbackIfTrafficId   OBJECT-TYPE
        SYNTAX       InstanceId
        STATUS       current
        DESCRIPTION
                  "Arbitrary integer index that uniquely identifies
                   an instance of the class."
        ::= { frwkFeedbackIfTrafficUsageEntry frwkFeedbackIfTrafficEntry 1 }

   frwkFeedbackIfTrafficUsageLinkRefID

   frwkFeedbackIfTrafficLinkRefID  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 frwkFeedbackIfTrafficEntry 2 }

   frwkFeedbackIfTrafficUsageIfIndex

   frwkFeedbackIfTrafficIfIndex  OBJECT-TYPE
          SYNTAX         InterfaceIndex
          STATUS         current
          DESCRIPTION
              "The value of this attribute is the ifIndex which is
              associated with the specified RoleCombination and
              interface capability set name."

          ::= { frwkFeedbackIfTrafficUsageEntry frwkFeedbackIfTrafficEntry 3 }

   frwkFeedbackIfTrafficUsagePacketCount

Rawlins et al.          Expires December 2002               [Page 23] 
   frwkFeedbackIfTrafficPacketCount OBJECT-TYPE
        SYNTAX       Counter64       Usage64
        STATUS       current
        DESCRIPTION
                "The count of packets handled by the associated element
                during the reporting interval."
                element."
        ::= { frwkFeedbackIfTrafficUsageEntry frwkFeedbackIfTrafficEntry 4 }

   frwkFeedbackIfTrafficUsageByteCount

   frwkFeedbackIfTrafficByteCount OBJECT-TYPE
        SYNTAX       Counter64       Usage64
        STATUS       current
        DESCRIPTION
                   "The byte count of packets
                    handled by the associated element."
        ::= { frwkFeedbackIfTrafficUsageEntry frwkFeedbackIfTrafficEntry 5 }

   --
   -- All Selection classes are in the separate
   -- FrwkFeedbackSelectionClasses group
   --

   frwkFeedbackSelectionClasses
       OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib frwkFeedbackPib  3 }

   --
   -- The Role Combination Filter Selection Table
   --

   frwkFeedbackRoleComboFilterSelTable

   frwkFeedbackRoleFilterSelTable OBJECT-TYPE
        SYNTAX          SEQUENCE OF FrwkFeedbackRoleComboFilterSelEntry FrwkFeedbackRoleFilterSelEntry
        PIB-ACCESS      install
        STATUS          current
        DESCRIPTION
                "A selection PRC class that defines selection of objects
                for monitoring based on the role combination, capability set and
                either IP or 802.1 filter." role combination,
                capability set and a filter."
        ::= { frwkFeedbackSelectionClasses  1 }

   frwkFeedbackRoleFilterSelEntry OBJECT-TYPE
        SYNTAX          FrwkFeedbackRoleFilterSelEntry
        STATUS          current
        DESCRIPTION
                "Each instance selects a filter on multiple interfaces
                that share the same frwkRoleCombo instance."
        PIB-INDEX { frwkFeedbackRoleFilterSelId}
        UNIQUENESS { frwkFeedbackRoleFilterSelRCombo,
                     frwkFeedbackRoleFilterSelFilter
                    }

        ::= {frwkFeedbackRoleFilterSelTable 1}

   FrwkFeedbackRoleFilterSelEntry ::= SEQUENCE {

Rawlins et al.          Expires December 2002               [Page 24] 
         frwkFeedbackRoleFilterSelId          InstanceId,
         frwkFeedbackRoleFilterSelRCombo      ReferenceId,
         frwkFeedbackRoleFilterSelFilter      Prid
   }

   frwkFeedbackRoleFilterSelId   OBJECT-TYPE
        SYNTAX       InstanceId
        STATUS       current
        DESCRIPTION
                  "Arbitrary integer index that uniquely identifies
                   an instance of the class."
        ::= { frwkFeedbackRoleFilterSelEntry 1 }

   frwkFeedbackRoleFilterSelRCombo  OBJECT-TYPE
        SYNTAX      ReferenceId
        PIB-REFERENCES { frwkRoleComboEntry }
        STATUS      current
        DESCRIPTION
                  "The ReferenceId of the frwkRoleComboTable policy
                   instance used for selection."
        ::= { frwkFeedbackRoleFilterSelEntry 2 }

   frwkFeedbackRoleFilterSelFilter     OBJECT-TYPE
        SYNTAX      Prid
        STATUS      current
        DESCRIPTION
                  "The identifier of a filter instance. Valid classes
                   are the subclasses of frwkBaseFilter:
                   - frwkIpFilter
                   - frwk802Filter
                   - frwkILabelFilter"
        ::= { frwkFeedbackRoleFilterSelEntry 3 }

   --
   -- Compliance Section
   --

   frwkFeedbackPibConformance
                OBJECT IDENTIFIER ::= { frwkFeedbackPib 4 }

   frwkFeedbackPibCompliances
                OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 1 }

   frwkFeedbackPibGroups
                OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 2 }

   frwkFeedbackPibCompliance MODULE-COMPLIANCE
        STATUS  current
        DESCRIPTION
        "Describes the requirements for conformance to the feedback
        framework PIB"

Rawlins et al.          Expires December 2002               [Page 25] 
      MODULE   -- this module
         MANDATORY-GROUPS { frwkFeedbackLinkCapsGroup,
                                 frwkFeedbackLinkGroup,
                                 frwkFeedbackActionGroup }

      GROUP frwkFeedbackActionListGroup
         DESCRIPTION
                      "The frwkFeedbackActionListGroup is mandatory if
                      actions on subsets linkEntries are to be
                      supported."

      GROUP frwkFeedbackTrafficGroup
         DESCRIPTION
                      "The frwkFeedbackTrafficGroup is mandatory if
                      monitoring of traffic data is to be supported."

      GROUP frwkFeedbackTrafficThresGroup
         DESCRIPTION
                      "The frwkFeedbackTrafficThresGroup is mandatory
                      if conditional reporting of traffic usage
                      thresholds is to be supported."

      GROUP frwkFeedbackIfTrafficGroup
         DESCRIPTION
                      "The frwkFeedbackIfTrafficGroup is mandatory if
                      per-interface usage collection of traffic data is
                      to be supported."

      GROUP frwkFeedbackRoleFilterSelGroup
         DESCRIPTION
                      "The frwkFeedbackRoleFilterSelGroup is mandatory
                      if monitoring of filters referenced through the
                      frwkRoleCombo class is to be supported."

      ::= { frwkFeedbackPibCompliances 1 }

    frwkFeedbackLinkCapsGroup OBJECT-GROUP
        OBJECTS {
                frwkFeedbackLinkCapsId,
                frwkFeedbackLinkCapsSelection,
                frwkFeedbackLinkCapsUsage,
                frwkFeedbackLinkCapsThreshold }
        STATUS  current
        DESCRIPTION
             "Objects from the frwkFeedbackLinkCapsTable."

        ::= { frwkFeedbackPibGroups 1 }

    frwkFeedbackLinkGroup OBJECT-GROUP
        OBJECTS {
                frwkFeedbackLinkId,
                frwkFeedbackLinkSel,

Rawlins et al.          Expires December 2002               [Page 26] 
                frwkFeedbackLinkUsage,
                frwkFeedbackLinkInterval,
                frwkFeedbackLinkThreshold,
                frwkFeedbackLinkFlags }
        STATUS  current
        DESCRIPTION
             "Objects from the frwkFeedbackLinkTable."

        ::= { frwkFeedbackSelectionClasses  1 frwkFeedbackPibGroups 2 }

    frwkFeedbackActionGroup OBJECT-GROUP
        OBJECTS {
                frwkFeedbackActionId,
                frwkFeedbackActionIndicator,
                frwkFeedbackActionSpecificPri,
                frwkFeedbackActionList }

   frwkFeedbackRoleComboFilterSelEntry OBJECT-TYPE
        SYNTAX          FrwkFeedbackRoleComboFilterSelEntry
        STATUS  current
        DESCRIPTION
                 "Defines the attributes on which
             "Objects from the PEP is to
                  base selection."

        PIB-INDEX frwkFeedbackActionTable."

        ::= { frwkFeedbackRoleComboFilterSelId}
        UNIQUENESS frwkFeedbackPibGroups 3 }

    frwkFeedbackActionListGroup OBJECT-GROUP
        OBJECTS { frwkFeedbackRoleComboFilterSelRoleComboRefID,
                     frwkFeedbackRoleComboFilterSelBaseFilterRefID,
                     frwkFeedbackRoleComboFilterSelIP-802FilterRefID
                frwkFeedbackActionListId,
                frwkFeedbackActionListTag,
                frwkFeedbackActionListRefID }
        STATUS  current
        DESCRIPTION
             "Objects from the frwkFeedbackActionListTable."

        ::= {frwkFeedbackRoleComboFilterSelTable 1}

   FrwkFeedbackRoleComboFilterSelEntry ::= SEQUENCE {
         frwkFeedbackRoleComboFilterSelId InstanceId,
         frwkFeedbackRoleComboFilterSelRoleComboRefID      ReferenceId,
         frwkFeedbackRoleComboFilterSelBaseFilterRefID     ReferenceId,
         frwkFeedbackRoleComboFilterSelIP-802FilterRefID   ReferenceId frwkFeedbackPibGroups 4 }

    frwkFeedbackTrafficGroup OBJECT-GROUP
        OBJECTS {
                frwkFeedbackTrafficId,
                frwkFeedbackTrafficLinkRefID,
                frwkFeedbackTrafficPacketCount,
                frwkFeedbackTrafficByteCount }

   frwkFeedbackRoleComboFilterSelId   OBJECT-TYPE
        SYNTAX       InstanceId
        STATUS  current
        DESCRIPTION
                  "Arbitrary integer index that uniquely identifies
                   an instance of
             "Objects from the class." frwkFeedbackTrafficTable."

        ::= { frwkFeedbackRoleComboFilterSelEntry 1 frwkFeedbackPibGroups 5 }

   frwkFeedbackRoleComboFilterSelRoleComboRefID  OBJECT-TYPE
        SYNTAX      ReferenceId
        PIB-REFERENCES

    frwkFeedbackTrafficThresGroup OBJECT-GROUP
        OBJECTS { frwkRoleComboEntry
               frwkFeedbackTrafficThresId,
                frwkFeedbackTrafficThresPackets,
               frwkFeedbackTrafficThresBytes }
        STATUS  current
        DESCRIPTION
                  "The ReferenceId of
             "Objects from the frwkRoleComboTable policy
                   instance used for selection." frwkFeedbackTrafficThresTable."

Rawlins et al.          Expires December 2002               [Page 27] 
        ::= { frwkFeedbackRoleComboFilterSelEntry 2 frwkFeedbackPibGroups 6 }

   frwkFeedbackRoleComboFilterSelBaseFilterRefID     OBJECT-TYPE
        SYNTAX      ReferenceId
        PIB-REFERENCES

    frwkFeedbackIfTrafficGroup OBJECT-GROUP
        OBJECTS { frwkBaseFilterEntry
                frwkFeedbackIfTrafficId,
                frwkFeedbackIfTrafficLinkRefID,
                frwkFeedbackIfTrafficIfIndex,
                frwkFeedbackIfTrafficPacketCount,
                frwkFeedbackIfTrafficByteCount }
        STATUS  current
        DESCRIPTION
                  "The ReferenceId of
             "Objects from the frwkBaseFilterTable policy
                   used for selection." frwkFeedbackIfTrafficTable."

        ::= { frwkFeedbackRoleComboFilterSelEntry 3 frwkFeedbackPibGroups 7 }

   frwkFeedbackRoleComboFilterSelIP-802FilterRefID OBJECT-TYPE
        SYNTAX      ReferenceId
        PIB-REFERENCES

    frwkFeedbackRoleFilterSelGroup OBJECT-GROUP
        OBJECTS { frwkIpFilterEntry
                frwkFeedbackRoleFilterSelId,
                frwkFeedbackRoleFilterSelRCombo,
                frwkFeedbackRoleFilterSelFilter }
        STATUS  current
        DESCRIPTION
                  "The ReferenceId of
             "Objects from the frwkIPFilterTable policy used
                   for selection." frwkFeedbackRoleFilterSelTable."

        ::= { frwkFeedbackRoleComboFilterSelEntry 4 frwkFeedbackPibGroups 8 }

   END

5 Security Considerations

     The feedback

  This PIB defines structured information is that may be sensitive and requires when
  transported by the COPS protocol [COPS-PR].

  This PIB does not contain classes that authorized
     messaging occur between directly contain security
  relevant information like passwords or monetary amounts, however
  unauthorized access or changes to information defined in this PIB
  could compromise network operations or reveal sensitive business or
  personal information.
  Specifically for the PEP classes:
  frwkFeedbackLinkCaps
      This class has the ACCESS clause 'notify'. Access to this
      information reveals feedback collection capabilities of the COPS
      client and malicious changes could affect feedback operation by
      misleading the PDP. This protection can
     be accomplished with IPSEC server to generate corrupt feedback configuration.
  frwkFeedbackLinkTable, frwkFeedbackAction, frwkFeedbackActionList,
  frwkFeedbackTrafficThres, frwkFeedbackRoleFilterSel
      These classes have the ACCESS clause 'install' and allow the COPS
      server to control feedback collection and reporting on the
      client. Access to this information exposes the client's

Rawlins et al.          Expires December 2002               [Page 28] 
      configuration, malicious changes could disrupt network or TLS [COPS-TLS] between
      business operations and raise privacy issues.
  frwkFeedbackTraffic, frwkFeedbackIfTraffic
      These classed have the PEP ACCESS clause 'report-only' and contain
      the usage information delivered from the COPS client to the
      server. Unauthorized access to this information may reveal
      detailed information on the network and its users. Malicious
      changes may affect network and business operations.

  [COPS] and [COPS-PR] define mechanisms to secure the COPS protocol
  communication and implementations of COPS servers or clients
  supporting this PIB MUST follow the security guidelines specified
  there.

6 IANA Considerations

  This document describes the frwkFeedbackPib Policy Information Base
  (PIB) module for standardization under the PDP or using "pib" branch registered
  with IANA. An IANA assigned PIB number is requested for this PIB
  under the security mechanisms described "pib" branch.

  This PIB uses "all" in the base SUBJECT-CATEGORY clause, so it applies to
  all COPS protocol.

6 client types. No new COPS client type is requested for this
  PIB.

7 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

8 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. Networks
      600 Technology Park Drive
      Billerica, MA 01821 USA
      Phone: 978-288-8175
      Email: khchan@nortelnetworks.com

Rawlins et al.          Expires December 2002               [Page 29] 
      Martin Bokaemper
      Unisphere
      Juniper Networks
      700 Silver Seven Road
      Kanata, ON, K2V 1C3, Canada
      Phone: 613-591-2735
      Email: mbokaemper@unispherenetworks.com mbokaemper@juniper.net

      Dinesh G Dutt
      Cisco Systems, Inc.
      170 Tasman Dr.
      San Jose, CA 95134-1706
      Phone: 408-527-0955
      Email: ddutt@cisco.com

8

9 References

9.1 Normative References

     [FEEDBACKfWK] Rawlins, D., Kulkarni, A., "Framework of COPS-PR
     Policy Usage Feedback", draft-ietf-rap-feedback-frwk-02.txt,
     February 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]

     [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," RFC 3084, May 2001.

     [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning
     Information," RFC 3159, August 2001.

     [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A.
     Smith, F. Reichmeyer "Framework Policy Information Base", RFC
     xxxx, xxxx 2002

     [FEEDBACKfWK] D. Rawlins, A. Kulkarni, K. Chan, M. Bokaemper, D.
     Dutt, "Framework of COPS-PR Policy Usage Feedback", RFC yyyy, yyyy
     2002.

9.2 Informational References

     [COPS-TLS], Walker, J., Kulkarni, A.,"COPS Over TLS", draft-ietf-
     rap-cops-tls-04.txt, June 2002.

     [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-09.txt, June 2002

     [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A.
     Smith, F. Reichmeyer "Framework Policy Information Base", draft-
     ietf-rap-frameworkpib-09.txt, June

10 Copyright

   Copyright (C) The Internet Society (2002). All Rights Reserved.

Rawlins et al.          Expires December 2002

     [COPS-TLS], Walker, J., Kulkarni, A.,÷COPS Over TLS÷, draft-ietf-
     rap-cops-tls-04.txt, June 2002.               [Page 30] 
   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implmentation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph
   are included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the  purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Rawlins et al.          Expires December 2002               [Page 31]