draft-ietf-rap-feedback-fr-pib-03.txt   draft-ietf-rap-feedback-fr-pib-04.txt 
Internet Draft Diana Rawlins Internet Draft Diana Rawlins
Expiration: February 2003 WorldCom Expiration: May 2003 WorldCom
File: draft-ietf-rap-feedback-fr-pib-03.txt Amol Kulkarni File: draft-ietf-rap-feedback-fr-pib-04.txt Amol Kulkarni
Intel Intel
Kwok Ho Chan Kwok Ho Chan
Nortel Networks Nortel Networks
Martin Bokaemper Martin Bokaemper
Unisphere Networks Juniper Networks
Dinesh Dutt Dinesh Dutt
Cisco Cisco
Framework of COPS-PR Policy Information Base for Policy Usage Framework Policy Information Base for Usage Feedback
Feedback
Last Updated June 30, 2002 Last Updated November 2, 2002
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 40 skipping to change at line 38
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. 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 Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in [RFC-2119]. 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 Table of Contents
1 Introduction.....................................................4 1 Introduction.....................................................3
2 General Concepts.................................................4 2 General Concepts.................................................3
2.1 Selection, Usage and Linkage Policies..........................4 2.1 Selection, Usage and Linkage Policies..........................3
2.2 Normal Operations..............................................5 2.2 Normal Operations..............................................4
2.2.1 Connection Establishment and Initial Configuration Request...5 2.2.1 Connection Establishment and Initial Configuration Request...4
2.2.2 Unsolicited Reports - Periodic Reporting.....................6 2.2.2 Unsolicited Reports - Periodic Reporting.....................5
2.2.3 Unsolicited Reports - Reporting Conditions...................6 2.2.3 Unsolicited Reports - Reporting Conditions...................5
2.2.4 Solicited Reports............................................6 2.2.4 Solicited Reports............................................5
2.2.5 Resuming and Suspending Periodic Feedback Reporting..........7 2.2.5 Resuming and Suspending Periodic Feedback Reporting..........6
2.2.6 Failover.....................................................7 2.2.6 Failover.....................................................6
2.3 Usage Policy and Under-specified Selection Criteria............7 2.3 Usage Policy and Under-specified Selection Criteria............6
3 Summary of the Feedback Framework Policy Information Base........9 3 Summary of the Feedback Framework Policy Information Base........7
3.1 SPPI ACCESS clause report-only.................................9 3.1 SPPI ACCESS clause report-only.................................7
3.2 Feedback Groups and PRCs.......................................9 3.2 Usage32 and Usage64 textual conventions........................7
3.2.1 Feedback Action Table.......................................10 3.3 Feedback Groups and PRCs.......................................8
3.2.2 Feedback List Table.........................................10 3.3.1 Feedback Action..............................................8
3.2.3 The Feedback Selection Usage Combination Capability Table...10 3.3.2 Feedback Action List.........................................9
3.2.4 The Feedback Report Linkage Table...........................11 3.3.3 Feedback Linkage Capability..................................9
3.2.5 The Feedback Traffic Statistics Threshold Table.............11 3.3.4 Feedback Linkage.............................................9
4 The Feedback Framework PIB Module...............................11 3.3.5 Feedback Traffic Statistics Threshold.......................10
5 Security Considerations.........................................25 4 The Feedback Framework PIB Module...............................10
6 Acknowledgements................................................25 6 IANA Considerations.............................................29
7 Authors' Addresses..............................................25 7 Acknowledgements................................................29
8 References......................................................26 8 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 1 Introduction
The Framework of COPS-PR Usage Feedback describes the overall The Framework of COPS-PR Usage Feedback describes the overall
approach to policy usage monitoring and reporting. This document approach to policy usage monitoring and reporting. This document
defines the specific Policy Information Base (PIB) framework for defines the specific Policy Information Base (PIB) framework for
policy usage feedback. The policy classes for monitoring and policy usage feedback. The policy classes for monitoring and
reporting policy usage feedback as well as policy classes for reporting policy usage feedback as well as policy classes for
controlling reporting intervals, suspension, resumption and controlling reporting intervals, suspension, resumption and
solicitation are also defined. solicitation are defined.
2 General Concepts 2 General Concepts
2.1 Selection, Usage and Linkage Policies 2.1 Selection, Usage and Linkage Policies
There are three basic types of policy used to define what the PEP is There are three basic types of policy used to define what the PEP is
to monitor, record and report. These are the selection criteria to monitor, record and report. These are the selection criteria
policy, the usage policy and the feedback report linkage policy. policy, the usage policy and the feedback report linkage policy.
The selection criteria policy is installed by the PDP. It defines the 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 conditions used by the PEP to monitor and record a usage policy. The
selection criteria policy may only be used for defining usage selection criteria policy may only be used for defining usage
feedback selection criteria. However, the more general case is that a feedback selection criteria. However, the more general case is that a
policy that already exists for policy enforcement may also be used policy that already exists for policy enforcement may also be used
for specifying feedback usage selection criteria. An example of this for specifying feedback usage selection criteria. An example of this
is the frwkRoleComboEntry may be used in defining QoS enforcement is the frwkRoleCombo instance, which may be used in defining QoS
policies but may also be used to specify conditions on which to base enforcement policies but may also be used to specify conditions on
usage - i.e. count the number of packets meeting the criterion of an which to base usage - i.e. count the number of packets meeting the
interface capability set name and role combination. criterion of an interface capability set name and role combination.
The usage policy defines what attributes are recorded by the PEP. The usage policy defines what attributes are recorded by the PEP.
These policies have an ACCESS clause of Report. Generally, the usage These policies have an ACCESS clause of 'report-only'. Generally, the
policies specify counts related to a specific action such as a packet usage policies specify counts related to a specific action such as a
being dropped. The feedback framework PIB defines two usage policy packet being dropped. The feedback framework PIB defines two usage
classes, frwkFeedbackTrafficUsage and frwkFeedbackIfTrafficUsage. policy classes, frwkFeedbackTraffic and frwkFeedbackIfTraffic. Usage
Usage PRCs may be generic, collecting basic statistics, or they may PRCs may be generic, collecting basic statistics, or they may be
be specific to a particular usage. The PDP decides which PRC(s) best specific to a particular usage. The PDP decides which PRC(s) best
suit(s) its requirements. The PEP may support only one usage feedback suit(s) its requirements. The PEP may support only one usage feedback
PRC, in which case all statistics are gathered using instances of PRC, in which case all statistics are gathered using instances of
that PRC. Alternatively, the PEP may support multiple usage feedback that PRC. Alternatively, the PEP may support multiple usage feedback
PRCs. The PDP then decides which PRC to associate with a particular PRCs. The PDP then decides which PRC to associate with a particular
selection criterion. selection criterion.
A usage feedback policy and selection policy are tightly associated A usage feedback policy and selection policy are tightly associated
with one another. A third policy, the frwkFeedbackLinkTable, is used with one another. A third policy, the frwkFeedbackLinkTable, is used
to associate, or provide a linkage for the selection and usage to associate, or provide a linkage for the selection and usage
policies. The frwkFeedbackLinkTable also specifies when to report the policies. The frwkFeedbackLinkTable also specifies when to report the
usage feedback. The frwkFeedbackLinkTable entry permits the same usage feedback. The frwkFeedbackLinkTable entry permits the same
selection criteria instance to be re-used for various usage feedback selection criteria instance to be re-used for various usage feedback
policies. The frwkFeedbackLinkTable contains the value of the policies. The frwkFeedbackLinkTable contains the value of the
selection criteria instance as well as the value of the usage selection criteria instance as well as the value of the usage
feedback PRC. feedback PRC.
Rawlins et al. Expires December 2002 [Page 3]
----------------- ------------------ ----------------- ----------------- ------------------ -----------------
| | | | | | | | | | | |
| Select Criteria | |Linkage Instance | |Usage Instance | | Select Criteria | |Linkage Instance | |Usage Instance |
| | |-instance ID | |- instance ID | | | |-instance ID | |- instance ID |
| -instance ID |<--|-PRID of selection|--->|- PRID of Linkage| | -instance ID |<--|-PRID of selection|--->|- PRID of Linkage|
| -conditions... | |-PRC of usage | |- counts... | | -conditions... | |-PRC of usage | |- counts... |
| | | | | | | | | | | |
----------------- ------------------ ----------------- ----------------- ------------------ -----------------
Figure 1 Figure 1
skipping to change at page 5, line 26 skipping to change at line 166
Figure 1 illustrates the relationship between the selection criteria, Figure 1 illustrates the relationship between the selection criteria,
linkage and usage policies. linkage and usage policies.
The PDP is not aware of the instance identifier of the usage feedback The PDP is not aware of the instance identifier of the usage feedback
policy when installing the selection criteria and feedback linkage policy when installing the selection criteria and feedback linkage
policies. The usage feedback policy is instantiated on the PEP by the policies. The usage feedback policy is instantiated on the PEP by the
installation of a feedback report linkage and the PEP designates the installation of a feedback report linkage and the PEP designates the
instance identifier. The usage feedback policy class always contains instance identifier. The usage feedback policy class always contains
an attribute of type ReferenceId that contains the instance value of an attribute of type ReferenceId that contains the instance value of
the associated frwkFeedbackLinkTable instance installed by the PDP. the associated frwkFeedbackLinkTable instance installed by the PDP.
An example of this is the attribute frwkFeedbackTrafficUsageLinkRef An example of this is the attribute frwkFeedbackTrafficLinkRef
2.2 Normal Operations 2.2 Normal Operations
2.2.1 Connection Establishment and Initial Configuration Request 2.2.1 Connection Establishment and Initial Configuration Request
The Accounting Timer object in the COPS Connection Accept message The Accounting Timer object in the COPS Connection Accept message
contains the minimum number of seconds between reporting intervals as contains the minimum number of seconds between reporting intervals as
described in [COPS] and [COPS-FEEDBACK-FRWK]. This is used as the described in [COPS] and [FEEDBACKfWK]. This is used as the basic unit
basic unit of measurement in defining intervals for specific usage of measurement in defining intervals for specific usage policies with
policies with the frwkFeedbackLinkInterval attribute. the frwkFeedbackLinkInterval attribute.
The PEP notifies the PDP of the selection criteria policy classes and The PEP notifies the PDP of the selection criteria policy classes and
usage policy classes it supports during the initial request for usage policy classes it supports during the initial request for
configuration data using the frwkPRCSupportTable entries [FR-PIB]. configuration data using frwkPRCSupport instances [FR-PIB]. The PEP
The PEP also indicates whether it supports the frwkFeedbackLinkTable also indicates whether it supports the frwkFeedbackLinkTable as well.
as well.
The PDP responds to the initial request for configuration with a The PDP responds to the initial request for configuration with a
DECISION that installs policies. The PDP may also specify maximum DECISION that installs policies. The PDP may also specify maximum
reporting intervals associated with each of the usage policies. This reporting intervals associated with each of the usage policies. This
is done with the frwkFeedbackLinkInterval attribute in the is done with the frwkFeedbackLinkInterval attribute in the
frwkFeedbackLinkTable instance. It may also specify reporting frwkFeedbackLink class. It may also specify reporting thresholds by
thresholds by including an instance of a threshold class (e.g. including an instance of a threshold class (e.g.
frwkFeedbackTrafficThresholdTable) in the decision. The PEP monitors frwkFeedbackTrafficThreshold) in the decision. The PEP monitors and
and records the usage per the conditions defined by its associated records the usage per the conditions defined by its associated
selection criteria policy. Periodically the PEP reports the usage selection criteria policy. Periodically the PEP reports the usage
with a REPORT message or provides a REPORT when solicited by the PDP. with a REPORT message or provides a REPORT when solicited by the PDP.
The PDP solicits usage feedback with the frwkFeedbackActionIndicator The PDP solicits usage feedback with the frwkFeedbackActionIndicator
attribute of the frwkFeedbackActionTable. attribute of the frwkFeedbackAction class.
Rawlins et al. Expires December 2002 [Page 4]
2.2.2 Unsolicited Reports - Periodic Reporting 2.2.2 Unsolicited Reports - Periodic Reporting
Reporting may be periodic in nature and unsolicited. The intervals Reporting may be periodic in nature and unsolicited. The intervals
at which the unsolicited reports are provided by the PEP are defined at which the unsolicited reports are provided by the PEP are defined
in the specific Linkage policies. The defined intervals are based on 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 number of seconds specified by the PDP in the ACCT Timer value.
The PDP may specify that the associated usage instance be included The PDP may specify that the associated usage instance be included
in a periodic unsolicited report only if the threshold is reached in a periodic unsolicited report only if the threshold is reached
and/or if the usage value has changed from the previous reporting and/or if the usage value has changed from the previous reporting
skipping to change at page 6, line 29 skipping to change at line 219
There are cases when the PEP must supply unsolicited feedback There are cases when the PEP must supply unsolicited feedback
reports that may not fall on an interval boundary. The PEP MUST reports that may not fall on an interval boundary. The PEP MUST
provide an unsolicited REPORT containing all defined usage instances provide an unsolicited REPORT containing all defined usage instances
just prior to the PEP issuing a Delete Request State and just prior just prior to the PEP issuing a Delete Request State and just prior
to the PEP de-activating a PIB instance context. to the PEP de-activating a PIB instance context.
2.2.3 Unsolicited Reports - Reporting Conditions 2.2.3 Unsolicited Reports - Reporting Conditions
Periodic unsolicited reports for individual usage feedback instances Periodic unsolicited reports for individual usage feedback instances
can be suppressed by specifying additional conditions in the can be suppressed by specifying additional conditions in the
frwkFeedbackLinkTable. Supported conditions are: frwkFeedbackLink instances. Supported conditions are:
ChangeOnly ChangeOnly
If this flag is set in the frwkFeedbackLinkFlags field, the If this flag is set in the frwkFeedbackLinkFlags attribute, the
associated usage instance is only included in a periodic associated usage instance is only included in a periodic
unsolicited report if its value changed since the last unsolicited report if its value changed since the last
unsolicited report. unsolicited report.
Threshold Threshold
If this flag is set in the frwkFeedbackLinkFlags field, the If this flag is set in the frwkFeedbackLinkFlags attribute, the
associated usage instance is only included in a periodic associated usage instance is only included in a periodic
unsolicited report, if the threshold condition referenced in unsolicited report, if the threshold condition referenced in
the frwkLinkThreshold field evaluates successfully for the the frwkLinkThreshold field evaluates successfully for the
associated usage instance. associated usage instance.
Both conditions can be combined in one frwkFeedbackLinkUsage object. Both conditions can be combined in one frwkFeedbackLinkUsage object.
In this case both conditions need to succeed for the usage instance In this case both conditions need to succeed for the usage instance
to be reported. to be reported.
Unsolicited reports triggered by a Delete Request State or the Unsolicited reports triggered by a Delete Request State or the
deactivation of a PIB instance are not subject to these conditions - deactivation of a PIB instance are not subject to these conditions -
all usage objects must be included in these cases. all usage objects must be included in these cases.
2.2.4 Solicited Reports 2.2.4 Solicited Reports
The PDP may solicit policy usage feedback by issuing an unsolicited The PDP may solicit policy usage feedback by issuing an unsolicited
Decision containing the frwkFeedbackActionIndicator set to SOLICIT Decision containing the frwkFeedbackActionIndicator set to
USAGE REPORT NOW. The PEP is to provide a solicited REPORT feedback 'solicitReport'. The PEP is to provide a solicited REPORT feedback
containing usage feedback. The PEP shall continue to provide containing usage feedback. The PEP shall continue to provide
periodic feedback as well at the specified intervals established at periodic feedback as well at the specified intervals established at
client connection acceptance. client connection acceptance.
Rawlins et al. Expires December 2002 [Page 5]
The reporting conditions (ChangeOnly and Threshold) do not affect The reporting conditions (ChangeOnly and Threshold) do not affect
solicited reports - all requested usage instances must be included. solicited reports - all requested usage instances must be included.
2.2.5 Resuming and Suspending Periodic Feedback Reporting 2.2.5 Resuming and Suspending Periodic Feedback Reporting
The PDP may suspend usage monitoring and tracking at the PEP with the The PDP may suspend usage monitoring and tracking at the PEP with the
frwkFeedbackActionIndicator set to SUSPEND USAGE MONITORING AND frwkFeedbackActionIndicator set to 'suspendMonitoringAndReports'. The
REPORTS. The PEP must stop tracking usage information and must not PEP must stop tracking usage information and must not issue any
issue any feedback reports. The PDP may only suspend feedback feedback reports. The PDP may only suspend feedback reporting by
reporting by setting the ActionIndicator to SUSPEND REPORTS ONLY. The setting the ActionIndicator to 'suspendReports'. The PEP must cease
PEP must cease sending unsolicited reports but is to continue sending unsolicited reports but is to continue monitoring and
monitoring and tracking usage. The PDP may resume the sending of tracking usage. The PDP may resume the sending of feedback reports
feedback reports and may resume usage monitoring by setting the and may resume usage monitoring by setting the ActionIndicator to
ActionIndicator to RESUME USAGE AND REPORTING. 'resume'.
The PDP may suspend or resume all usage instances or the PDP may 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. specify one or more instances that are to be suspended or resumed.
The frwkFeedbackActionList contains a tag identifier that references The frwkFeedbackActionList attribute contains a tag identifier that
a list of one or more frwkFeedbackActionListTable entries. references a list of one or more frwkFeedbackActionList instances.
The PDP may halt usage monitoring, tracking and reporting of usage The PDP may halt usage monitoring, tracking and reporting of usage
policies by removing the associated Linkage entry. policies by removing the associated Linkage entry.
2.2.6 Failover 2.2.6 Failover
In the event the connection is lost between the PEP and PDP, the PEP 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 continues to track usage information as long as it continues to
operate with the installed policy. When the locally installed policy operate with the installed policy. When the locally installed policy
at the PEP expires, the usage policy data also expires. at the PEP expires, the usage policy data also expires.
Upon successful reconnection where the PEP is still caching policy, Upon successful reconnection where the PEP is still caching policy,
the PDP indicates to the PEP that the PEP may resume sending of the the PDP indicates to the PEP that the PEP may resume sending of the
COPS accounting type report messages. The PDP does this COPS accounting type report messages. The PDP does this by issuing an
deterministically. It issues an unsolicited decision containing the unsolicited decision containing the frwkFeedbackResumeIndicator set
frwkFeedbackResumeIndicator set to resume reporting. The PEP should to 'resume'. The PEP should resume reporting at the next appropriate
resume reporting at the next appropriate feedback interval feedback interval established upon the acceptance of the re-
established upon the acceptance of the re-connection. The PDP is connection. The PDP is aware of the request state Handle(s) and the
aware of the request state Handle(s) and the supported PRCs either supported PRCs either through the state synchronization mechanism or
through the state synchronization mechanism or because the PDP because the PDP considers itself synchronized with the PEP upon
considers itself synchronized with the PEP upon reconnection. reconnection.
2.3 Usage Policy and Under-specified Selection Criteria 2.3 Usage Policy and Under-specified Selection Criteria
Some of the usage policy objects created in the PEP with COPS-PR can 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 be used by the PEP multiple times - they effectively act as
templates for the objects created by the PEP. COPS-PR only has the templates for the objects created by the PEP. COPS-PR only has the
identity (OID) of the object that is shared between all the identity (OID) of the object that is shared between all the
assignment the PEP created, however it is desirable to collect usage assignments the PEP created, however it is desirable to collect
information for each of the derived objects individually. usage information for each of the derived objects individually.
This capability is achieved in the feedback framework PIB by This capability is achieved in the feedback framework PIB by
distributing additional information to qualify a specific assignment 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 of an object between the selection criteria PRC and the feedback
usage PRC. usage PRC.
A selection criteria PRC that refers to a shared object but contains A selection criteria PRC that refers to a shared object but contains
no qualifying information selects all of the object's assignment. no qualifying information selects all of the object's assignments.
Such a selection criteria PRC SHOULD be combined with a feedback Such a selection criteria PRC SHOULD be combined with a feedback
usage PRC that includes all the necessary information to identify a usage PRC that includes all the necessary information to identify a
specific assignment - a single selection criteria policy can then specific assignment - a single selection criteria policy can then
result in the generation of many feedback usage objects, one for result in the generation of many feedback usage objects, one for
each derived object. each derived object.
If the selection criteria PRC contains all the required qualifying If the selection criteria PRC contains all the required qualifying
attributes for a specific assignment, it is combined with a feedback attributes for a specific assignment, it is combined with a feedback
usage PRC that only contains the desired metrics but no additional usage PRC that only contains the desired metrics but no additional
attributes. attributes.
Example: Example:
The frwkRoleComboEntry may be used as a selection criteria A frwkRoleCombo instance may be used as a selection criteria,
identifying the role combination and capability set. However, identifying a set of interfaces through their the role
there is a more granular piece of information associated with combination and capability set. If it is desired to get per-
capability set and role combination which is the interface index. interface traffic statistics, the usage PRC has to include an
The interface index is associated with a specific capability set additional attribute to qualify the specific interface.
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 the PEP.
The frwkFeedbackIfTrafficUsageIfIndex identifies 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 the qualifying attributes:
frwkRoleComboPrid InstanceId,
frwkRoleComboRoles RoleCombination,
frwkRoleComboCapSetName SnmpAdminString
To monitor traffic counts of a role combination and capability
set the policy would be combined in a frwkLinkageEntry with the
FrwkFeedbackTrafficUsage PRC. This combination will result in
only one FrwkFeedbackTrafficUsageEntry to be created which only
contains the traffic counters. The traffic counts would reflect
the aggregated counts of all interface indices associated with
a given capability set and role combination.
Traffic count details for each interface index can be obtained
by linking the frwkRoleComboEntry and the
frwkFeedbackIfTrafficUsage PRC.
By combining a frwkRoleComboEntry as selection criteria with This could be achieved by linking the frwkFeedbackIfTraffic class
the FrwkFeedbackIfTrafficUsage PRC, all the assignments are with a frwkRoleCombo instance in a frwkFeedbackLink instance.
selected and multiple FrwkFeedbackIfTrafficUsageEntries get Multiple frwkFeedbackIfTraffic instances will be created by the
created. Each entry not only carries the desired traffic PEP, one for each interface selected by the frwkRoleCombo
counters but also the IfIndex qualifying attributes to instance. The frwkFeedbackIfTraffic class contains the
associate it with the assignment: frwkFeedbackIfTrafficIfIndex attribute that allows the PDP to
identify each interface's individual counters when the PEP
reports the frwkFeedbackIfTraffic instances.
frwkFeedbackIfTrafficUsageId InstanceId, If traffic usage collection is only desired for an individual
frwkFeedbackIfTrafficUsageLinkRefID ReferenceId, interface, a selection criteria should be used that qualifies the
frwkFeedbackIfTrafficUsageIfIndex InterfaceIndex, interface completely, for example a frwkIfRoleCombo instance.
frwkFeedbackIfTrafficUsagePacketCount Counter64, In this case it can be linked to the usage class that has no
frwkFeedbackIfTrafficUsageByteCount Counter64 additional qualifying attributes, frwkFeedbackTraffic.
3 Summary of the Feedback Framework Policy Information Base 3 Summary of the Feedback Framework Policy Information Base
3.1 SPPI ACCESS clause report-only 3.1 SPPI ACCESS clause report-only
The selection criteria and linkage policy classes follow the The selection criteria and linkage policy classes follow the
definitions specified by [SPPI]. This structure specifies well- definitions specified by [SPPI]. This structure specifies well-
defined policy classes and their instances residing in a common, defined policy classes and their instances residing in a common,
virtual repository [FR-PIB]. The additional PIB-ACCESS clause virtual repository [FR-PIB]. The additional PIB-ACCESS clause
attribute of "report-only" denotes the usage policy class reported by attribute of "report-only" denotes the usage policy class reported by
the PEP. the PEP.
3.2 Feedback Groups and PRCs 3.2 Usage32 and Usage64 textual conventions
It is useful to define reporting intervals, and suspend, resume, and Rawlins et al. Expires December 2002 [Page 7]
solicit characteristics as well as the common usage and selection The SPPI does not support the Counter32/64 textual conventions (TC)
criteria polices. These policy classes are common to account type of SNMP - for feedback collection two similar textual conventions
have been defined in this PIB: Usage32 and Usage64.
In addition to 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- reporting for various technologies and apply to ALL SUBJECT-
CATEGORIES. The policy classes are divided into three new groups, CATEGORIES. The policy classes are divided into three new groups,
namely, The Feedback Report Group, The Feedback Usage Group and The namely, The Feedback Report Group, The Feedback Usage Group and The
Feedback Selection Group. Feedback Selection Group.
The policy classes in the Feedback Report Group are: The policy classes in the Feedback Report Group are:
- Feedback Action
1) Feedback Action Table - Feedback Action List
2) Feedback Action List Table - Feedback Selection Usage Combination Capability
3) Feedback Selection Usage Combination Capability Table - Feedback Linkage
4) Feedback Linkage Table - Feedback Traffic Statistics Threshold
5) Feedback Traffic Statistics Threshold Table
The policy classes in the Feedback Usage Group are: The policy classes in the Feedback Usage Group are:
1) Feedback Traffic Statistics Usage Table - Feedback Traffic
2) Feedback Interface Traffic Statistics Usage Table - Feedback Interface Traffic
The policy classes in the Feedback Selection Group are:
1) Feedback RoleCombo Filter Selection Table
Feedback PRI Selection Table
3.2.1 Feedback Action Table The policy class in the Feedback Selection Group is:
- Feedback RoleCombo Filter Selection
The Feedback Action Table contains the attributes that specify 3.3.1 Feedback Action
The Feedback Action class contains the attributes that specify
action that the PEP is to take regarding policy usage, monitoring action that the PEP is to take regarding policy usage, monitoring
and tracking. The PDP may suspend usage monitoring and periodic and tracking. The PDP may suspend usage monitoring and periodic
reporting, suspend periodic reporting only, resume usage and 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 periodic reporting or solicit immediate reporting. The action may
affect all feedback policies or be associated with one or more affect all feedback policies or be associated with one or more
policy instances. frwkFeedbackLink instances.
The Feedback Action Indicator defines the action. The Feedback The frwkFeedbackActionIndicator attribute defines the action. The
Specific PRI indicates whether the action applies to all of the frwkFeedbackActionPri attribute indicates whether the action applies
usage policies or to a list. The Feedback List ID is the identifier to all of the usage policies or to a list. The
of the list of Linkage policy instances to which the action is to be frwkFeedbackActionList attribute is the identifier of the list of
applied. Linkage policy instances to which the action is to be applied.
The PDP can solicit the PEP for immediate usage feedback. The PEP The PDP can solicit the PEP for immediate usage feedback. The PEP
shall respond with a solicited report containing the usage feedback. shall respond with a solicited report containing the usage feedback.
The PDP can direct the resumption of usage monitoring and reporting The PDP can direct the resumption of usage monitoring and reporting
per the defined intervals. For example, the PEP may have re- per the defined intervals. For example, the PEP may have re-
connected to a PDP and has cached usage policies. The PDP indicates 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 to the PEP to resume usage tracking and monitoring and to send all
the cached usage policy. The PEP shall respond at the next the cached usage policy. The PEP shall respond at the next
appropriate interval with an unsolicited report containing the usage appropriate interval with an unsolicited report containing the usage
skipping to change at page 10, line 46 skipping to change at line 444
maintains the current usage that has been monitored but discontinues maintains the current usage that has been monitored but discontinues
any further monitoring until the PDP directs the PEP to resume any further monitoring until the PDP directs the PEP to resume
monitoring in a subsequent Decision. monitoring in a subsequent Decision.
The PDP can also suspend just the reporting of usage, but not The PDP can also suspend just the reporting of usage, but not
interrupt the monitoring and tracking of usage. The PEP shall interrupt the monitoring and tracking of usage. The PEP shall
discontinue sending Report messages with usage feedback until the discontinue sending Report messages with usage feedback until the
PDP directs the PEP to resume. The PEP then begins reporting the PDP directs the PEP to resume. The PEP then begins reporting the
usage feedback at the next interval. usage feedback at the next interval.
3.2.2 Feedback List Table 3.3.2 Feedback Action List
This table contains a list of PRIDs of the linkage table for which This class defines sets of linkage instances that can be referred to
the PDP wants feedback reports. The value is referenced by an from the frwkFeedbackActionList attribute.
attribute in the Feedback Resume Table. There may be one or more
instances associated with a specific list identifier defined by the
Feedback Action List ID.
3.2.3 The Feedback Selection Usage Combination Capability Table 3.3.3 Feedback Linkage Capability
This table defines the valid selection criteria PRC, and usage PRC
and threshold PRC combinations supported.
3.2.4 The Feedback Report Linkage Table This class defines the valid selection criteria PRC, usage PRC and
threshold PRC combinations supported by the PEP.
This table links the selection criteria instance with the usage 3.3.4 Feedback Linkage
instance. It specifies the PRID of the selection criteria and the PRC
of the usage instance. This table permits the reuse of a selection This class links the selection criteria instance with the usage
criteria instance for multiple usage policies. 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 The linkage table also permits the definition of a maximum reporting
interval to use when issuing the COPS accounting type reports for the interval to use when issuing the COPS accounting type reports for the
usage instance. This interval is defined in units of the Accounting
Timer Interval specified in the client accept message. A value of 0
in this attribute indicates that the usage policy must be solicited.
3.2.5 The Feedback Traffic Statistics Threshold Table Rawlins et al. Expires December 2002 [Page 9]
usage instance. A value of 0 in this attribute indicates that the
usage policy must be solicited.
This table is used to provide threshold values for the attributes 3.3.5 Feedback Traffic Statistics Threshold
described in the above usage tables.
3.2.6 The Feedback Traffic Statistics Usage Table This class is used to provide threshold values for the attributes
described in the traffic usage classes below.
This table describes the packet counts, byte counts, last timestamp 3.3.6 Feedback Traffic
when a packet was received and the PRID of the associated Feedback
Report Linkage instance. The count and timestamp information is
monitored and recorded by the PEP and supplied to the PDP with the
COPS accounting type report message within the maximum interval
specified.
3.2.7 The Feedback Interface Traffic Statistics Usage Table This class includes the packet counts, byte counts and a reference to
the associated Linkage instance.
This table is similar to the table described above, except that it 3.3.7 Feedback Interface Traffic
includes an additional reference to an interface index. This table
should be used with a selection criteria that matches an element
that is assigned to multiple interfaces. The interface field can be
used to associate the instances of this table with the specific
elementĂs assignment.
3.2.8 The Feedback RoleCombo Filter Selection Table This class is similar to the previous Feedback Traffic class, except
that it includes an additional reference to an interface index. This
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 assignment.
This table is used to identify a selection criteria of Role 3.3.8 Feedback RoleCombo Filter Selection
Combination and either IP or 802 Filter. This Role Combination and
Filter is the basis upon which the usage performs monitoring and This class is used as selection criteria based on role combination,
collection. capability set and a filter instance.
4 The Feedback Framework PIB Module 4 The Feedback Framework PIB Module
FEEDBACK-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN FEEDBACK-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
ExtUTCTime, Unsigned32, Unsigned64, pib, Unsigned32, Unsigned64, Integer32,
Integer32, MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE, MODULE-COMPLIANCE, OBJECT-GROUP
FROM COPS-PR-SPPI FROM COPS-PR-SPPI
TruthValue, TEXTUAL-CONVENTION TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
InstanceId, ReferenceId InstanceId, ReferenceId, Prid,
TagId, TagReferenceId
FROM COPS-PR-SPPI-TC FROM COPS-PR-SPPI-TC
Counter64 PrcIdentifierOid, PrcIdentifierOidOrZero
FROM SNMPv2-SMI FROM FRAMEWORK-TC-PIB
frwkRoleComboEntry
FROM FRAMEWORK-PIB
InterfaceIndex InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
feedbackPolFrameworkPib MODULE-IDENTITY Rawlins et al. Expires December 2002 [Page 10]
frwkFeedbackPib MODULE-IDENTITY
SUBJECT-CATEGORIES { all } SUBJECT-CATEGORIES { all }
LAST-UPDATED "200011171000Z" LAST-UPDATED "200210281000Z"
ORGANIZATION "IETF RAP WG" ORGANIZATION "IETF RAP WG"
CONTACT-INFO " CONTACT-INFO "IETF RAP WG
Email: rap@ops.ietf.org
Diana Rawlins Diana Rawlins
WorldCom WorldCom
901 International Parkway 901 International Parkway
Richardson, TX 75081 Richardson, TX 75081
Phone: 972 729 1044 Phone: 972 729 1044
Email: diana.rawlins@wcom.com Email: diana.rawlins@wcom.com
Amol Kulkarni Amol Kulkarni
JF3-206 JF3-206
2111 NE 25th Ave 2111 NE 25th Ave
Hillsboro, Oregon 97124 Hillsboro, Oregon 97124
Phone: 503-712-1168 Phone: 503-712-1168
Email: amol.kulkarni@intel.com Email: amol.kulkarni@intel.com
Kwok Ho Chan Kwok Ho Chan
Nortel Networks, Inc. Nortel Networks.
600 Technology Park Drive 600 Technology Park Drive
Billerica, MA 01821 USA Billerica, MA 01821 USA
Phone: 978-288-8175 Phone: 978-288-8175
Email: khchan@nortelnetworks.com Email: khchan@nortelnetworks.com
Martin Bokaemper Martin Bokaemper
Unisphere Networks Juniper Networks
700 Silver Seven Road 700 Silver Seven Road
Kanata, ON, K2V 1C3, Canada Kanata, ON, K2V 1C3, Canada
Phone: 613-591-2735 Phone: 613-591-2735
Email: mbokaemper@unispherenetworks.com" Email: 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 DESCRIPTION
"The PIB module containing the base set of policy rule "The PIB module containing the base set of policy rule
classes that are required for support of all policy classes that are required for support of all policy
usage monitoring, tracking and reporting policies" usage monitoring, tracking and reporting policies"
::= { pib xx } -- xx will be assigned by IANA REVISION "200210280000Z"
DESCRIPTION
"Initial version, published in RFC xxxx."
-- xxxx to be assigned by RFC editor
::= { pib xx } -- xx will be assigned by IANA, according
-- to RFC 3159 (IANA considerations)
Rawlins et al. Expires December 2002 [Page 11]
--
-- Textual Conventions
--
Usage32 ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The Usage32 type represents a non-negative integer
which monotonically increases.
Usage32 initial value is 0 and the object-type using
Usage32 needs to specify when it is initialized.
The Usage32 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.
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 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 -- The feedback report group
-- --
frwkFeedbackGroupClasses frwkFeedbackGroupClasses
OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 1 } OBJECT IDENTIFIER ::= { frwkFeedbackPib 1 }
-- --
-- Feedback Action Table -- Feedback Action Table
-- --
frwkFeedbackActionTable OBJECT-TYPE frwkFeedbackActionTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackActionEntry SYNTAX SEQUENCE OF FrwkFeedbackActionEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class contains a single PRI that indicates "This class represents commands that the PDP sends to
that the PEP is to resume the sending of suspend, resume or solicit collection or reporting of
COPS accounting type reports." usage data."
::= { frwkFeedbackGroupClasses 1} ::= { frwkFeedbackGroupClasses 1}
frwkFeedbackActionEntry OBJECT-TYPE frwkFeedbackActionEntry OBJECT-TYPE
SYNTAX FrwkFeedbackActionEntry SYNTAX FrwkFeedbackActionEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this class can indicates a action "Each frwkFeedbackActionEntry represents a command from
the PEP is to take regarding the usage policies." 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 set that is
referenced by frwkFeedbackActionList."
PIB-INDEX { frwkFeedbackActionId} PIB-INDEX { frwkFeedbackActionId}
::= { frwkFeedbackActionTable 1} ::= { frwkFeedbackActionTable 1}
Rawlins et al. Expires December 2002 [Page 13]
FrwkFeedbackActionEntry ::= SEQUENCE { FrwkFeedbackActionEntry ::= SEQUENCE {
frwkFeedbackActionId InstanceId, frwkFeedbackActionId InstanceId,
frwkFeedbackActionIndicator INTEGER, frwkFeedbackActionIndicator INTEGER,
frwkFeedbackActionSpecificPri TruthValue, frwkFeedbackActionSpecificPri TruthValue,
frwkFeedbackActionList TagReferenceId frwkFeedbackActionList TagReferenceId
} }
frwkFeedbackActionId OBJECT-TYPE frwkFeedbackActionId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" An arbitrary integer index that uniquely identifies an " An arbitrary integer index that uniquely identifies an
instance of the frwkFeedbackActionTable class." instance of the frwkFeedbackAction class."
::= { frwkFeedbackActionEntry 1} ::= { frwkFeedbackActionEntry 1}
frwkFeedbackActionIndicator OBJECT-TYPE frwkFeedbackActionIndicator OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
SUSPEND_USAGE_MONITORING_AND_REPORTS(0), suspendMonitoringAndReports(0),
SUSPEND_REPORTS_ONLY(1), suspendReports(1),
RESUME_USAGE_AND_REPORTING(2), resume(2),
SOLICIT_USAGE_REPORT_NOW(3) solicitReport(3)
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value indicates if the PEP is to send cached "The value indicates if the PEP is to send cached
usage policies via COPS accounting type report usage policies via COPS accounting type report
messages. messages.
The enumeration values are: The enumeration values are:
(0) SUSPEND USAGE MONITORING_AND_REPORTS (0) suspendMonitoringAndReports
(1) SUSPEND_REPORTS_ONLY (1) suspendReports
(2) RESUME_USAGE AND REPORTING (2) resume
(3) SOLICIT USAGE REPORT NOW " (3) solicitReport "
::= { frwkFeedbackActionEntry 2 } ::= { frwkFeedbackActionEntry 2 }
frwkFeedbackActionSpecificPri OBJECT-TYPE frwkFeedbackActionSpecificPri OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value of 0 indicates that the "A value of 0 indicates that the
frwkFeedbackActionList attribute should be frwkFeedbackActionList attribute should be ignored,
ignored, and the action applied to all policies. A and the action applied to all policies. A value of
value of 1 indicates that the action entry has a 1 indicates that the action entry has a specific
specific list of policies to which it is to be list of policies to which it is to be applied."
applied."
::= { frwkFeedbackActionEntry 3} ::= { frwkFeedbackActionEntry 3}
frwkFeedbackActionList OBJECT-TYPE frwkFeedbackActionList OBJECT-TYPE
SYNTAX TagReferenceId SYNTAX TagReferenceId
PIB-TAG { frwkFeedbackActionListGroup } PIB-TAG { frwkFeedbackActionListTag }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a list of
frwkFeedbackActionListTable instances Rawlins et al. Expires December 2002 [Page 14]
associated with the action described by "Identifies a set of frwkFeedbackActionList
this instance" instances that this action should affect."
::= { frwkFeedbackActionEntry 4} ::= { frwkFeedbackActionEntry 4}
-- --
-- Feedback Action List Table -- Feedback Action List Table
-- --
frwkFeedbackActionListTable OBJECT-TYPE frwkFeedbackActionListTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackActionListEntry SYNTAX SEQUENCE OF FrwkFeedbackActionListEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class contains the ReferenceIDs of the "This class defines groups of linkage instances.
linkage instance which are to be impacted by Groups can be referenced by commands sent by the
the frwkFeedbackActionIndicator for this PDP in a frwkFeedbackActionEntry -in this case the
list." command affects all linkage instances that are part
of the group."
::= { frwkFeedbackGroupClasses 2} ::= { frwkFeedbackGroupClasses 2}
frwkFeedbackActionListEntry OBJECT-TYPE frwkFeedbackActionListEntry OBJECT-TYPE
SYNTAX FrwkFeedbackActionListEntry SYNTAX FrwkFeedbackActionListEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class identifies a set of linkage instances "Each instance associates a linkage instance with a
for which the PDP is suspending, resuming or specific ActionListGroup."
soliciting usage feedback."
PIB-INDEX {frwkFeedbackActionListId } PIB-INDEX {frwkFeedbackActionListId }
UNIQUENESS { frwkFeedbackActionListGroup, UNIQUENESS { frwkFeedbackActionListTag,
frwkFeedbackActionListRefID frwkFeedbackActionListRefID
} }
::= { frwkFeedbackActionListTable 1} ::= { frwkFeedbackActionListTable 1}
FrwkFeedbackActionListEntry::= SEQUENCE { FrwkFeedbackActionListEntry::= SEQUENCE {
frwkFeedbackActionListId InstanceId, frwkFeedbackActionListId InstanceId,
frwkFeedbackActionListGroup TagId, frwkFeedbackActionListTag TagId,
frwkFeedbackActionListRefID ReferenceId frwkFeedbackActionListRefID ReferenceId
} }
frwkFeedbackActionListId OBJECT-TYPE frwkFeedbackActionListId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Arbitrary integer index that uniquely "Arbitrary integer index that uniquely
identifies an instance of the class." identifies an instance of the class."
::= { frwkFeedbackActionListEntry 1 } ::= { frwkFeedbackActionListEntry 1 }
frwkFeedbackActionListGroup OBJECT-TYPE frwkFeedbackActionListTag OBJECT-TYPE
SYNTAX TagId SYNTAX TagId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the binding between the Action "Represents the binding between the Action
Rawlins et al. Expires December 2002 [Page 15]
table entry and the Action List table entries" table entry and the Action List table entries"
::= { frwkFeedbackActionListEntry 2 } ::= { frwkFeedbackActionListEntry 2 }
frwkFeedbackActionListRefID OBJECT-TYPE frwkFeedbackActionListRefID OBJECT-TYPE
SYNTAX ReferenceId SYNTAX ReferenceId
PIB-REFERENCES { frwkFeedbackLinkEntry } PIB-REFERENCES { frwkFeedbackLinkEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ReferenceID of the linkage instance(s) "The ReferenceID of the linkage instance(s)
belonging to the list of instances identified belonging to the list of instances identified
by the list id upon which the suspend, resume by the list id upon which the suspend, resume
or solicit action is directed." or solicit action is directed."
::= { frwkFeedbackActionListEntry 3 } ::= { frwkFeedbackActionListEntry 3 }
-- --
-- The Feedback Selection Usage Combination Capability Table -- The Feedback Link Capability Table
-- --
frwkFeedbackSelUsageComboCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackSelUsageComboCapsEntry frwkFeedbackLinkCapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackLinkCapsEntry
PIB-ACCESS notify PIB-ACCESS notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines the valid combinations of the "Instances of the frwkFeedbackLink class reference
selection criteria PRCs, the usage PRCs and the instances of selection and threshold classes and a
threshold PRCs that the PEP supports." usage class.
This class allows the PEP to communicate valid
combinations of these three classes to the PDP."
::= { frwkFeedbackGroupClasses 3} ::= { frwkFeedbackGroupClasses 3}
frwkFeedbackSelUsageComboCapsEntry OBJECT-TYPE frwkFeedbackLinkCapsEntry OBJECT-TYPE
SYNTAX FrwkFeedbackSelUsageComboCapsEntry SYNTAX FrwkFeedbackLinkCapsEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The attributes of this class identify valid "The attributes of this class identify valid
combinations of selection criteria, usage and combinations of selection criteria, usage and
threshold PRCs for feedback supported by the PEP threshold classes for feedback."
device." PIB-INDEX { frwkFeedbackLinkCapsId }
PIB-INDEX { frwkFeedbackSelUsageComboCapsId }
UNIQUENESS { UNIQUENESS {
frwkFeedbackSelUsageComboCapsSelection, frwkFeedbackLinkCapsSelection,
frwkFeedbackSelUsageComboCapsUsage, frwkFeedbackLinkCapsUsage,
frwkFeedbackSelUsageComboCapsThreshold frwkFeedbackLinkCapsThreshold
} }
::= {frwkFeedbackSelUsageComboCapsTable 1} ::= {frwkFeedbackLinkCapsTable 1}
FrwkFeedbackSelUsageComboCapsEntry ::= SEQUENCE { FrwkFeedbackLinkCapsEntry ::= SEQUENCE {
frwkFeedbackSelUsageComboCapsId InstanceId, frwkFeedbackLinkCapsId InstanceId,
frwkFeedbackSelUsageComboCapsSelection OBJECT IDENTIFIER, frwkFeedbackLinkCapsSelection PrcIdentifierOid,
frwkFeedbackSelUsageComboCapsUsage OBJECT IDENTIFIER, frwkFeedbackLinkCapsUsage PrcIdentifierOid,
frwkFeedbackSelUsageComboCapsThreshold OBJECT IDENTIFIER frwkFeedbackLinkCapsThreshold PrcIdentifierOidOrZero
} }
frwkFeedbackSelUsageComboCapsId OBJECT-TYPE Rawlins et al. Expires December 2002 [Page 16]
frwkFeedbackLinkCapsId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" An arbitrary integer index that uniquely identifies an " An arbitrary integer index that uniquely identifies an
instance of the frwkFeedbackSelUsageComboCapsEntry instance of the frwkFeedbackLinkCaps class."
class." ::= { frwkFeedbackLinkCapsEntry 1}
::= { frwkFeedbackSelUsageComboCapsEntry 1}
frwkFeedbackSelUsageComboCapsSelection OBJECT-TYPE frwkFeedbackLinkCapsSelection OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX PrcIdentifierOid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRC of the selection class that is supported by "The identifier of a class that is supported by the
the device in the combination defined by this instance." device for feedback selection in combination with the
::= { frwkFeedbackSelUsageComboCapsEntry 2} usage and threshold classes referenced in this
instance."
::= { frwkFeedbackLinkCapsEntry 2}
frwkFeedbackSelUsageComboCapsUsage OBJECT-TYPE frwkFeedbackLinkCapsUsage OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX PrcIdentifierOid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRC of the usage policy class that is supported by "The identifier of the usage class that is supported by
the device in combination with the selection PRC and the the PEP in combination with the selection and threshold
threshold PRC defined in this instance." classes referenced in this instance."
::= { frwkFeedbackSelUsageComboCapsEntry 3} ::= { frwkFeedbackLinkCapsEntry 3}
frwkFeedbackSelUsageComboCapsThreshold OBJECT-TYPE frwkFeedbackLinkCapsThreshold OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX PrcIdentifierOidOrZero
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRC of the threshold class that is supported by "The identifier of the threshold class that is
the device in the combination defined by this instance." supported by the PEP in combination with the selection
::= { frwkFeedbackSelUsageComboCapsEntry 4} and usage classes referenced in this instance.
0.0 is used if this combination does not allow a
threshold."
::= { frwkFeedbackLinkCapsEntry 4}
-- --
-- The Feedback Report Linkage Table -- The Feedback Report Linkage Table
-- --
frwkFeedbackLinkTable OBJECT-TYPE frwkFeedbackLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackLinkEntry SYNTAX SEQUENCE OF FrwkFeedbackLinkEntry
PIB-ACCESS Install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class associates the selection criteria with the "This class associates the selection criteria with the
usage policy. It also permits the defining of the max usage policy. It also permits the defining of the max
interval used for reporting the usage instance." interval used for reporting the usage instance."
Rawlins et al. Expires December 2002 [Page 17]
::= { frwkFeedbackGroupClasses 4} ::= { frwkFeedbackGroupClasses 4}
frwkFeedbackLinkEntry OBJECT-TYPE frwkFeedbackLinkEntry OBJECT-TYPE
SYNTAX FrwkFeedbackLinkEntry SYNTAX FrwkFeedbackLinkEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class associates the selection criteria with the "This class associates the selection criteria with the
usage policy. It also permits the defining of the max usage policy. It also permits the defining of the max
interval used for reporting the usage instance." interval used for reporting the usage instance."
PIB-INDEX { frwkFeedbackLinkId } PIB-INDEX { frwkFeedbackLinkId }
UNIQUENESS {frwkFeedbackLinkSel, UNIQUENESS {frwkFeedbackLinkSel,
frwkFeedbackLinkUsage } frwkFeedbackLinkUsage }
::= {frwkFeedbackLinkTable 1} ::= {frwkFeedbackLinkTable 1}
FrwkFeedbackLinkEntry ::= SEQUENCE { FrwkFeedbackLinkEntry ::= SEQUENCE {
frwkFeedbackLinkId InstanceId, frwkFeedbackLinkId InstanceId,
frwkFeedbackLinkSel Prid, frwkFeedbackLinkSel Prid,
frwkFeedbackLinkUsage OBJECT IDENTIFIER, frwkFeedbackLinkUsage PrcIdentifierOid,
frwkFeedbackLinkInterval Integer32, frwkFeedbackLinkInterval Integer32,
frwkFeedbackLinkThreshold Prid, frwkFeedbackLinkThreshold Prid,
frwkFeedbackLinkFlags BITS frwkFeedbackLinkFlags BITS
} }
frwkFeedbackLinkId OBJECT-TYPE frwkFeedbackLinkId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" An arbitrary integer index that uniquely identifies an " An arbitrary integer index that uniquely identifies an
instance of the frwkFeedbackLinkTable class." instance of the frwkFeedbackLinkTable class."
::= { frwkFeedbackLinkEntry 1} ::= { frwkFeedbackLinkEntry 1}
frwkFeedbackLinkSel OBJECT-TYPE frwkFeedbackLinkSel OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
skipping to change at page 18, line 24 skipping to change at line 932
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRID of the Policy Class instance as the monitoring "The PRID of the Policy Class instance as the monitoring
point, or the PRID of the selection criteria instance that point, or the PRID of the selection criteria instance that
defines the conditions for monitoring, to be use by the defines the conditions for monitoring, to be use by the
PEP for usage reporting." PEP for usage reporting."
::= { frwkFeedbackLinkEntry 2} ::= { frwkFeedbackLinkEntry 2}
frwkFeedbackLinkUsage OBJECT-TYPE frwkFeedbackLinkUsage OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX PrcIdentifierOid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRC of the usage policy class that the PEP uses to "The identifier of the usage class that the PEP uses to
monitor, record and report." monitor, record and report."
::= { frwkFeedbackLinkEntry 3} ::= { frwkFeedbackLinkEntry 3}
frwkFeedbackLinkInterval OBJECT-TYPE frwkFeedbackLinkInterval OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
Rawlins et al. Expires December 2002 [Page 18]
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum interval in units of the value of the "Maximum interval in units of the value of the
Accounting Timer specified by the PDP in the client Accounting Timer specified by the PDP in the client
accept message. A frwkFeedbackLinkInterval of 1 is accept message. A frwkFeedbackLinkInterval of 1 is
equal to the value of the Accounting Timer. This value equal to the value of the Accounting Timer. This value
must be 1 or greater. " must be 1 or greater. "
::= { frwkFeedbackLinkEntry 4} ::= { frwkFeedbackLinkEntry 4}
frwkFeedbackLinkThreshold OBJECT-TYPE frwkFeedbackLinkThreshold OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRID of the threshold class instance. This "The PRID of a threshold class instance. This instance
instance specifies the threshold values for the usage specifies the threshold values for the usage policy."
policy."
::= { frwkFeedbackLinkEntry 5} ::= { frwkFeedbackLinkEntry 5}
frwkFeedbackLinkFlags OBJECT-TYPE frwkFeedbackLinkFlags OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
periodic(0), periodic(0),
threshold(1), threshold(1),
changeOnly(2) changeOnly(2)
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates the reporting basis of the usage "This value indicates the reporting basis of the usage
policy. The feed back may be generated on demand, on a policy. The feed back may be generated on demand, on a
periodic basis regardless of a change in value from the periodic basis regardless of a change in value from the
previous report, on a periodic basis if a change in previous report, on a periodic basis if a change in
value has occurred, or the usage is reported when an value has occurred, or the usage is reported when an
identified threshold value in the usage instance has identified threshold value in the usage instance has
been reached. been reached.
If the ŠperiodicĂ flag is set, the PEP will provide If the 'periodic' flag is set, the PEP will provide
unsolicited reports at the rate specified in unsolicited reports at the rate specified in
frwkFeedbackLinkInterval. frwkFeedbackLinkInterval.
If the ŠperiodicĂ flag is not set, reports will only be If the 'periodic' flag is not set, reports will only be
generated when solicited by the PDP. generated when solicited by the PDP.
The ŠthresholdĂ and ŠchangeOnlyĂ flags make the The 'threshold' and 'changeOnly' flags make the
periodic reports conditional - these flags only make periodic reports conditional - these flags only make
sense in combination with the ŠperiodicĂ flag." sense in combination with the 'periodic' flag."
::= { frwkFeedbackLinkEntry 6} ::= { frwkFeedbackLinkEntry 6}
-- --
-- The Threshold class that accompanies the above Usage PRCs -- The Threshold class that accompanies the above Usage PRCs
-- --
frwkFeedbackTrafficThresholdTable OBJECT-TYPE frwkFeedbackTrafficThresTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresholdEntry SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresEntry
PIB-ACCESS Install PIB-ACCESS install
STATUS current STATUS current
Rawlins et al. Expires December 2002 [Page 19]
DESCRIPTION DESCRIPTION
"This class defines the threshold attributes "This class defines the threshold attributes
corresponding to usage attributes specified in corresponding to usage attributes specified in
frwkFeedbackTrafficUsageTable, frwkFeedbackTrafficTable, frwkFeedbackIfTrafficTable
frwkFeedbackIfTrafficUsageTable and other similar and other similar usage classes.
usage classes.
The usage object is considered to match the threshold The usage object is considered to match the threshold
condition if the following expression evaluates to condition if at least one of the packet or byte
ŠTRUEĂ: threshold conditions match.
{
byteCond = (ByteThreshold != NULL) ? The byte and packet thresholds are considered to
(ByteThreshold > ByteCounter) : FALSE; match, if the threshold is present (not ASN1 NULL)
packetCond (PacketThreshold != NULL) ? and the corresponding usage value exceeds the
(PacketThreshold > PacketCounter) : FALSE; threshold."
return ( byteCond || packetCond );
}"
::= { frwkFeedbackGroupClasses 5} ::= { frwkFeedbackGroupClasses 5}
frwkFeedbackTrafficThresholdEntry OBJECT-TYPE frwkFeedbackTrafficThresEntry OBJECT-TYPE
SYNTAX FrwkFeedbackTrafficThresholdEntry SYNTAX FrwkFeedbackTrafficThresEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the attributes to hold threshold values." "Defines the attributes to hold threshold values."
PIB-INDEX {frwkFeedbackTrafficThresholdId} PIB-INDEX {frwkFeedbackTrafficThresId}
::= {frwkFeedbackTrafficThresholdTable 1} ::= {frwkFeedbackTrafficThresTable 1}
FrwkFeedbackTrafficThresholdEntry ::= SEQUENCE { FrwkFeedbackTrafficThresEntry ::= SEQUENCE {
frwkFeedbackTrafficThresholdId InstanceId, frwkFeedbackTrafficThresId InstanceId,
frwkFeedbackTrafficThresholdPacketThreshold Integer64, frwkFeedbackTrafficThresPackets Unsigned64,
frwkFeedbackTrafficThresholdByteThreshold Integer64 frwkFeedbackTrafficThresBytes Unsigned64
} }
frwkFeedbackTrafficThresholdId OBJECT-TYPE frwkFeedbackTrafficThresId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Arbitrary integer index that uniquely identifies "Arbitrary integer index that uniquely identifies
an instance of the class." an instance of the class."
::= { frwkFeedbackTrafficThresholdEntry 1 } ::= { frwkFeedbackTrafficThresEntry 1 }
frwkFeedbackTrafficThresholdPacketThreshold OBJECT-TYPE frwkFeedbackTrafficThresPackets OBJECT-TYPE
SYNTAX Integer64 SYNTAX Unsigned64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The threshold, in terms of packets, that must be "The threshold, in terms of packets, that must be
exceeded to trigger a report in the next matched or exceeded to trigger a report in the
reporting interval." next reporting interval.
::= { frwkFeedbackTrafficThresholdEntry 2 } A value of 0 or a missing value ("
::= { frwkFeedbackTrafficThresEntry 2 }
frwkFeedbackTrafficThresholdByteThreshold OBJECT-TYPE frwkFeedbackTrafficThresBytes OBJECT-TYPE
SYNTAX Integer64 SYNTAX Unsigned64
STATUS current STATUS current
Rawlins et al. Expires December 2002 [Page 20]
DESCRIPTION DESCRIPTION
"The threshold, in terms of bytes, that must be "The threshold, in terms of bytes, that must be
exceeded to trigger a report in the next exceeded to trigger a report in the next reporting
reporting interval." interval."
::= { frwkFeedbackTrafficThresholdEntry 3 } ::= { frwkFeedbackTrafficThresEntry 3 }
-- --
-- All actual usage classes are in the separate -- All actual usage classes are in the separate
-- FrwkFeedbackUsageClasses group -- frwkFeedbackUsageClasses group
-- --
frwkFeedbackUsageClasses frwkFeedbackUsageClasses
OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 2 } OBJECT IDENTIFIER ::= { frwkFeedbackPib 2 }
-- --
-- The generic traffic (byte & packet count) usage class -- The generic traffic (byte & packet count) usage class
-- --
frwkFeedbackTrafficUsageTable OBJECT-TYPE frwkFeedbackTrafficTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackTrafficUsageEntry SYNTAX SEQUENCE OF FrwkFeedbackTrafficEntry
PIB-ACCESS report-only PIB-ACCESS report-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class defines the usage attributes that the PEP "This class defines the usage attributes that the PEP
is to monitor for plain traffic handling elements is to monitor for plain traffic handling elements
like filters. All packets and the bytes contained in like filters. All packets and the bytes contained in
these packets are counted. It also contains the PRID these packets are counted. It also contains the PRID
of the linkage instance associating the selection of the linkage instance associating the selection
criteria instance with the usage instance." criteria instance with the usage instance."
::= { frwkFeedbackUsageClasses 1} ::= { frwkFeedbackUsageClasses 1}
frwkFeedbackTrafficUsageEntry OBJECT-TYPE frwkFeedbackTrafficEntry OBJECT-TYPE
SYNTAX FrwkFeedbackTrafficUsageEntry SYNTAX FrwkFeedbackTrafficEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the attributes the PEP is to monitor, "Defines the attributes the PEP is to monitor,
record and report." record and report."
PIB-INDEX {frwkFeedbackTrafficUsageId} PIB-INDEX {frwkFeedbackTrafficId}
UNIQUENESS { frwkFeedbackTrafficUsageLinkRefID } UNIQUENESS { frwkFeedbackTrafficLinkRefID }
::= {frwkFeedbackTrafficUsageTable 1} ::= {frwkFeedbackTrafficTable 1}
FrwkFeedbackTrafficUsageEntry ::= SEQUENCE { FrwkFeedbackTrafficEntry ::= SEQUENCE {
frwkFeedbackTrafficUsageId InstanceId, frwkFeedbackTrafficId InstanceId,
frwkFeedbackTrafficUsageLinkRefID ReferenceId, frwkFeedbackTrafficLinkRefID ReferenceId,
frwkFeedbackTrafficUsagePacketCount Counter64, frwkFeedbackTrafficPacketCount Usage64,
frwkFeedbackTrafficUsageByteCount Counter64 frwkFeedbackTrafficByteCount Usage64
} }
frwkFeedbackTrafficUsageId OBJECT-TYPE Rawlins et al. Expires December 2002 [Page 21]
frwkFeedbackTrafficId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Arbitrary integer index that uniquely identifies "Arbitrary integer index that uniquely identifies
an instance of the class." an instance of the class."
::= { frwkFeedbackTrafficUsageEntry 1 } ::= { frwkFeedbackTrafficEntry 1 }
frwkFeedbackTrafficUsageLinkRefID OBJECT-TYPE frwkFeedbackTrafficLinkRefID OBJECT-TYPE
SYNTAX ReferenceId SYNTAX ReferenceId
PIB-REFERENCES { frwkFeedbackLinkEntry } PIB-REFERENCES { frwkFeedbackLinkEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ReferenceId of the Linkage policy instance used "The ReferenceId of the Linkage policy instance used
to base this usage policy instance upon." to base this usage policy instance upon."
::= { frwkFeedbackTrafficUsageEntry 2 } ::= { frwkFeedbackTrafficEntry 2 }
frwkFeedbackTrafficUsagePacketCount OBJECT-TYPE frwkFeedbackTrafficPacketCount OBJECT-TYPE
SYNTAX Counter64 SYNTAX Usage64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of packets handled by the associated "The count of packets handled by the associated
element during the reporting interval." element."
::= {frwkFeedbackTrafficUsageEntry 3} ::= {frwkFeedbackTrafficEntry 3}
frwkFeedbackTrafficUsageByteCount OBJECT-TYPE frwkFeedbackTrafficByteCount OBJECT-TYPE
SYNTAX Counter64 SYNTAX Usage64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The byte count of packets handled by the associated "The byte count of packets handled by the associated
element." element."
::= { frwkFeedbackTrafficUsageEntry 4} ::= { frwkFeedbackTrafficEntry 4}
-- --
-- The traffic usage class, qualified for an interface -- The traffic usage class, qualified for an interface
-- --
frwkFeedbackIfTrafficUsageTable OBJECT-TYPE frwkFeedbackIfTrafficTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficUsageEntry SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficEntry
PIB-ACCESS report-only PIB-ACCESS report-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A usage PRC similar to the basic TrafficUsage class "A usage class similar to the basic Traffic class that
that also contains a reference to an interface index. also contains a reference to an interface index. This
This class should be used with a underspecified class should be used with a underspecified selection
selection criteria entry from the frwkRoleComboTable criteria entry from the frwkRoleComboTable that matches
that matches an element that can be assigned to an element that can be assigned to multiple interface
multiple interface indices. The interface field can be indices. The interface field can be used to associate
used to associate the instances of this class with the
specific elementĂs assignment." Rawlins et al. Expires December 2002 [Page 22]
the instances of this class with the specific element's
assignment."
::= { frwkFeedbackUsageClasses 2 } ::= { frwkFeedbackUsageClasses 2 }
frwkFeedbackIfTrafficUsageEntry OBJECT-TYPE frwkFeedbackIfTrafficEntry OBJECT-TYPE
SYNTAX FrwkFeedbackIfTrafficUsageEntry SYNTAX FrwkFeedbackIfTrafficEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the attributes the PEP is to monitor, "Defines the attributes the PEP is to monitor,
record and report." record and report."
PIB-INDEX {frwkFeedbackIfTrafficUsageId} PIB-INDEX {frwkFeedbackIfTrafficId}
UNIQUENESS { frwkFeedbackIfTrafficUsageLinkRefID, UNIQUENESS { frwkFeedbackIfTrafficLinkRefID,
frwkFeedbackIfTrafficUsageIfIndex } frwkFeedbackIfTrafficIfIndex }
::= {frwkFeedbackIfTrafficUsageTable 1} ::= {frwkFeedbackIfTrafficTable 1}
FrwkFeedbackIfTrafficEntry ::= SEQUENCE {
frwkFeedbackIfTrafficId InstanceId,
frwkFeedbackIfTrafficLinkRefID ReferenceId,
frwkFeedbackIfTrafficIfIndex InterfaceIndex,
frwkFeedbackIfTrafficPacketCount Usage64,
frwkFeedbackIfTrafficByteCount Usage64
FrwkFeedbackIfTrafficUsageEntry ::= SEQUENCE {
frwkFeedbackIfTrafficUsageId InstanceId,
frwkFeedbackIfTrafficUsageLinkRefID ReferenceId,
frwkFeedbackIfTrafficUsageIfIndex InterfaceIndex,
frwkFeedbackIfTrafficUsagePacketCount Counter64,
frwkFeedbackIfTrafficUsageByteCount Counter64
} }
frwkFeedbackIfTrafficUsageId OBJECT-TYPE frwkFeedbackIfTrafficId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Arbitrary integer index that uniquely identifies "Arbitrary integer index that uniquely identifies
an instance of the class." an instance of the class."
::= { frwkFeedbackIfTrafficUsageEntry 1 } ::= { frwkFeedbackIfTrafficEntry 1 }
frwkFeedbackIfTrafficUsageLinkRefID OBJECT-TYPE frwkFeedbackIfTrafficLinkRefID OBJECT-TYPE
SYNTAX ReferenceId SYNTAX ReferenceId
PIB-REFERENCES { frwkFeedbackLinkEntry } PIB-REFERENCES { frwkFeedbackLinkEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ReferenceId of the Linkage policy instance used "The ReferenceId of the Linkage policy instance used
to base this usage policy instance upon." to base this usage policy instance upon."
::= { frwkFeedbackIfTrafficUsageEntry 2 } ::= { frwkFeedbackIfTrafficEntry 2 }
frwkFeedbackIfTrafficUsageIfIndex OBJECT-TYPE frwkFeedbackIfTrafficIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this attribute is the ifIndex which is "The value of this attribute is the ifIndex which is
associated with the specified RoleCombination and associated with the specified RoleCombination and
interface capability set name." interface capability set name."
::= { frwkFeedbackIfTrafficUsageEntry 3 } ::= { frwkFeedbackIfTrafficEntry 3 }
frwkFeedbackIfTrafficUsagePacketCount OBJECT-TYPE Rawlins et al. Expires December 2002 [Page 23]
SYNTAX Counter64 frwkFeedbackIfTrafficPacketCount OBJECT-TYPE
SYNTAX Usage64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of packets handled by the associated element "The count of packets handled by the associated
during the reporting interval." element."
::= { frwkFeedbackIfTrafficUsageEntry 4 } ::= { frwkFeedbackIfTrafficEntry 4 }
frwkFeedbackIfTrafficUsageByteCount OBJECT-TYPE frwkFeedbackIfTrafficByteCount OBJECT-TYPE
SYNTAX Counter64 SYNTAX Usage64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The byte count of packets "The byte count of packets
handled by the associated element." handled by the associated element."
::= { frwkFeedbackIfTrafficUsageEntry 5 } ::= { frwkFeedbackIfTrafficEntry 5 }
-- --
-- All Selection classes are in the separate -- All Selection classes are in the separate
-- FrwkFeedbackSelectionClasses group -- FrwkFeedbackSelectionClasses group
-- --
frwkFeedbackSelectionClasses frwkFeedbackSelectionClasses
OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 3 } OBJECT IDENTIFIER ::= { frwkFeedbackPib 3 }
-- --
-- The Role Combination Filter Selection Table -- The Role Combination Filter Selection Table
-- --
frwkFeedbackRoleComboFilterSelTable OBJECT-TYPE frwkFeedbackRoleFilterSelTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackRoleComboFilterSelEntry SYNTAX SEQUENCE OF FrwkFeedbackRoleFilterSelEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A selection PRC that defines selection for monitoring "A selection class that defines selection of objects
based on the role combination, capability set and for monitoring based on the role combination,
either IP or 802.1 filter." capability set and a filter."
::= { frwkFeedbackSelectionClasses 1 } ::= { frwkFeedbackSelectionClasses 1 }
frwkFeedbackRoleComboFilterSelEntry OBJECT-TYPE frwkFeedbackRoleFilterSelEntry OBJECT-TYPE
SYNTAX FrwkFeedbackRoleComboFilterSelEntry SYNTAX FrwkFeedbackRoleFilterSelEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the attributes on which the PEP is to "Each instance selects a filter on multiple interfaces
base selection." that share the same frwkRoleCombo instance."
PIB-INDEX { frwkFeedbackRoleFilterSelId}
PIB-INDEX { frwkFeedbackRoleComboFilterSelId} UNIQUENESS { frwkFeedbackRoleFilterSelRCombo,
UNIQUENESS { frwkFeedbackRoleComboFilterSelRoleComboRefID, frwkFeedbackRoleFilterSelFilter
frwkFeedbackRoleComboFilterSelBaseFilterRefID,
frwkFeedbackRoleComboFilterSelIP-802FilterRefID
} }
::= {frwkFeedbackRoleComboFilterSelTable 1} ::= {frwkFeedbackRoleFilterSelTable 1}
FrwkFeedbackRoleComboFilterSelEntry ::= SEQUENCE { FrwkFeedbackRoleFilterSelEntry ::= SEQUENCE {
frwkFeedbackRoleComboFilterSelId InstanceId,
frwkFeedbackRoleComboFilterSelRoleComboRefID ReferenceId,
frwkFeedbackRoleComboFilterSelBaseFilterRefID ReferenceId,
frwkFeedbackRoleComboFilterSelIP-802FilterRefID ReferenceId
Rawlins et al. Expires December 2002 [Page 24]
frwkFeedbackRoleFilterSelId InstanceId,
frwkFeedbackRoleFilterSelRCombo ReferenceId,
frwkFeedbackRoleFilterSelFilter Prid
} }
frwkFeedbackRoleComboFilterSelId OBJECT-TYPE frwkFeedbackRoleFilterSelId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Arbitrary integer index that uniquely identifies "Arbitrary integer index that uniquely identifies
an instance of the class." an instance of the class."
::= { frwkFeedbackRoleComboFilterSelEntry 1 } ::= { frwkFeedbackRoleFilterSelEntry 1 }
frwkFeedbackRoleComboFilterSelRoleComboRefID OBJECT-TYPE frwkFeedbackRoleFilterSelRCombo OBJECT-TYPE
SYNTAX ReferenceId SYNTAX ReferenceId
PIB-REFERENCES { frwkRoleComboEntry } PIB-REFERENCES { frwkRoleComboEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ReferenceId of the frwkRoleComboTable policy "The ReferenceId of the frwkRoleComboTable policy
instance used for selection." instance used for selection."
::= { frwkFeedbackRoleComboFilterSelEntry 2 } ::= { frwkFeedbackRoleFilterSelEntry 2 }
frwkFeedbackRoleComboFilterSelBaseFilterRefID OBJECT-TYPE frwkFeedbackRoleFilterSelFilter OBJECT-TYPE
SYNTAX ReferenceId SYNTAX Prid
PIB-REFERENCES { frwkBaseFilterEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ReferenceId of the frwkBaseFilterTable policy "The identifier of a filter instance. Valid classes
used for selection." are the subclasses of frwkBaseFilter:
::= { frwkFeedbackRoleComboFilterSelEntry 3 } - frwkIpFilter
- frwk802Filter
- frwkILabelFilter"
::= { frwkFeedbackRoleFilterSelEntry 3 }
frwkFeedbackRoleComboFilterSelIP-802FilterRefID OBJECT-TYPE --
SYNTAX ReferenceId -- Compliance Section
PIB-REFERENCES { frwkIpFilterEntry } --
frwkFeedbackPibConformance
OBJECT IDENTIFIER ::= { frwkFeedbackPib 4 }
frwkFeedbackPibCompliances
OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 1 }
frwkFeedbackPibGroups
OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 2 }
frwkFeedbackPibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ReferenceId of the frwkIPFilterTable policy used "Describes the requirements for conformance to the feedback
for selection." framework PIB"
::= { frwkFeedbackRoleComboFilterSelEntry 4 }
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."
::= { frwkFeedbackPibGroups 2 }
frwkFeedbackActionGroup OBJECT-GROUP
OBJECTS {
frwkFeedbackActionId,
frwkFeedbackActionIndicator,
frwkFeedbackActionSpecificPri,
frwkFeedbackActionList }
STATUS current
DESCRIPTION
"Objects from the frwkFeedbackActionTable."
::= { frwkFeedbackPibGroups 3 }
frwkFeedbackActionListGroup OBJECT-GROUP
OBJECTS {
frwkFeedbackActionListId,
frwkFeedbackActionListTag,
frwkFeedbackActionListRefID }
STATUS current
DESCRIPTION
"Objects from the frwkFeedbackActionListTable."
::= { frwkFeedbackPibGroups 4 }
frwkFeedbackTrafficGroup OBJECT-GROUP
OBJECTS {
frwkFeedbackTrafficId,
frwkFeedbackTrafficLinkRefID,
frwkFeedbackTrafficPacketCount,
frwkFeedbackTrafficByteCount }
STATUS current
DESCRIPTION
"Objects from the frwkFeedbackTrafficTable."
::= { frwkFeedbackPibGroups 5 }
frwkFeedbackTrafficThresGroup OBJECT-GROUP
OBJECTS {
frwkFeedbackTrafficThresId,
frwkFeedbackTrafficThresPackets,
frwkFeedbackTrafficThresBytes }
STATUS current
DESCRIPTION
"Objects from the frwkFeedbackTrafficThresTable."
Rawlins et al. Expires December 2002 [Page 27]
::= { frwkFeedbackPibGroups 6 }
frwkFeedbackIfTrafficGroup OBJECT-GROUP
OBJECTS {
frwkFeedbackIfTrafficId,
frwkFeedbackIfTrafficLinkRefID,
frwkFeedbackIfTrafficIfIndex,
frwkFeedbackIfTrafficPacketCount,
frwkFeedbackIfTrafficByteCount }
STATUS current
DESCRIPTION
"Objects from the frwkFeedbackIfTrafficTable."
::= { frwkFeedbackPibGroups 7 }
frwkFeedbackRoleFilterSelGroup OBJECT-GROUP
OBJECTS {
frwkFeedbackRoleFilterSelId,
frwkFeedbackRoleFilterSelRCombo,
frwkFeedbackRoleFilterSelFilter }
STATUS current
DESCRIPTION
"Objects from the frwkFeedbackRoleFilterSelTable."
::= { frwkFeedbackPibGroups 8 }
END END
5 Security Considerations 5 Security Considerations
The feedback information is sensitive and requires that authorized This PIB defines structured information that may be sensitive when
messaging occur between the PEP and the PDP. This protection can transported by the COPS protocol [COPS-PR].
be accomplished with IPSEC or TLS [COPS-TLS] between the PEP and
the PDP or using the security mechanisms described in the base This PIB does not contain classes that directly contain security
COPS protocol. 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 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 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
business operations and raise privacy issues.
frwkFeedbackTraffic, frwkFeedbackIfTraffic
These classed have the 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 "pib" branch registered
with IANA. An IANA assigned PIB number is requested for this PIB
under the "pib" branch.
This PIB uses "all" in the SUBJECT-CATEGORY clause, so it applies to
all COPS client types. No new COPS client type is requested for this
PIB.
7 Acknowledgements
6 Acknowledgements
The authors would like to thank Dave Durham and Russell Fenger of The authors would like to thank Dave Durham and Russell Fenger of
Intel and John K. Gallant of WorldCom for their contribution to Intel and John K. Gallant of WorldCom for their contribution to this
this document. document.
7 Authors' Addresses 8 Authors' Addresses
Diana Rawlins Diana Rawlins
WorldCom WorldCom
901 International Parkway 901 International Parkway
Richardson, Texas 75081 Richardson, Texas 75081
Phone: 972-729-1044 Phone: 972-729-1044
Email: Diana.Rawlins@wcom.com Email: Diana.Rawlins@wcom.com
Amol Kulkarni Amol Kulkarni
JF3-206 JF3-206
skipping to change at page 26, line 4 skipping to change at line 1523
Richardson, Texas 75081 Richardson, Texas 75081
Phone: 972-729-1044 Phone: 972-729-1044
Email: Diana.Rawlins@wcom.com Email: Diana.Rawlins@wcom.com
Amol Kulkarni Amol Kulkarni
JF3-206 JF3-206
2111 NE 25th Ave 2111 NE 25th Ave
Hillsboro, Oregon 97124 Hillsboro, Oregon 97124
Phone: 503-712-1168 Phone: 503-712-1168
Email: amol.kulkarni@intel.com Email: amol.kulkarni@intel.com
Kwok Ho Chan Kwok Ho Chan
Nortel Networks, Inc. Nortel Networks
600 Technology Park Drive 600 Technology Park Drive
Billerica, MA 01821 USA Billerica, MA 01821 USA
Phone: 978-288-8175 Phone: 978-288-8175
Email: khchan@nortelnetworks.com Email: khchan@nortelnetworks.com
Rawlins et al. Expires December 2002 [Page 29]
Martin Bokaemper Martin Bokaemper
Unisphere Networks Juniper Networks
700 Silver Seven Road 700 Silver Seven Road
Kanata, ON, K2V 1C3, Canada Kanata, ON, K2V 1C3, Canada
Phone: 613-591-2735 Phone: 613-591-2735
Email: mbokaemper@unispherenetworks.com Email: mbokaemper@juniper.net
Dinesh G Dutt Dinesh G Dutt
Cisco Systems, Inc. Cisco Systems, Inc.
170 Tasman Dr. 170 Tasman Dr.
San Jose, CA 95134-1706 San Jose, CA 95134-1706
Phone: 408-527-0955 Phone: 408-527-0955
Email: ddutt@cisco.com Email: ddutt@cisco.com
8 References 9 References
[FEEDBACKfWK] Rawlins, D., Kulkarni, A., "Framework of COPS-PR 9.1 Normative References
Policy Usage Feedback", draft-ietf-rap-feedback-frwk-02.txt,
February 2002.
[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R.,
and A. Sastry, "The COPS (Common Open Policy Service) Protocol" and A. Sastry, "The COPS (Common Open Policy Service) Protocol"
RFC 2748, January 2000. RFC 2748, January 2000.
[3084] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. [COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F.
Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for
Policy Provisioning," RFC 3084, May 2001. Policy Provisioning," RFC 3084, May 2001.
[SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning
Information," RFC 3159, August 2001. 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., [DIFFSERV-PIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K.,
Hahn, S., Bell, C., Smith, A. and Reichmeyer, A. "Differentiated Hahn, S., Bell, C., Smith, A. and Reichmeyer, A. "Differentiated
Services Quality of Service Policy Information Base", draft-ietf- Services Quality of Service Policy Information Base", draft-ietf-
diffserv-pib-09.txt, June 2002 diffserv-pib-09.txt, June 2002
[FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A. 10 Copyright
Smith, F. Reichmeyer "Framework Policy Information Base", draft-
ietf-rap-frameworkpib-09.txt, June 2002
[COPS-TLS], Walker, J., Kulkarni, A.,÷COPS Over TLS÷, draft-ietf- Copyright (C) The Internet Society (2002). All Rights Reserved.
rap-cops-tls-04.txt, June 2002.
Rawlins et al. Expires December 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]
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/