draft-ietf-rap-feedback-fr-pib-02.txt   draft-ietf-rap-feedback-fr-pib-03.txt 
Internet Draft Diana Rawlins Internet Draft Diana Rawlins
Expiration: September 2002 WorldCom Expiration: February 2003 WorldCom
File: draft-ietf-rap-feedback-fr-pib-02.txt Amol Kulkarni File: draft-ietf-rap-feedback-fr-pib-03.txt Amol Kulkarni
Intel Intel
Kwok Ho Chan Kwok Ho Chan
Nortel Networks Nortel Networks
Martin Bokaemper Martin Bokaemper
Unisphere Networks Unisphere Networks
Dinesh Dutt Dinesh Dutt
Cisco Cisco
Framework of COPS-PR Policy Information Base for Policy Usage Framework of COPS-PR Policy Information Base for Policy Usage
Feedback Feedback
Last Updated March 1, 2002 Last Updated June 30, 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 53 skipping to change at page 1, line 53
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 Abstract
Currently there are no policy classes defined for the PEP to convey Currently there are no policy classes defined for the PEP to convey
provisioned policy usage feedback to the PDP. The purpose of this provisioned policy usage feedback to the PDP. The purpose of this
document is to define the policy usage feedback framework PIB that document is to define the policy usage feedback framework PIB that
specifies the policy classes common for COPS feedback reports. The specifies the policy classes common for COPS feedback reports. The
basic operation and objects for reporting usage information are basic operation and objects for reporting usage information are
defined in [COPS]. A specific clientSI feedback object named REPORT defined in [COPS]. A specific clientSI feedback object named REPORT
is defined in [COPS-PR]. A framework for approaching solicited and is defined in [COPS-PR]. A framework for approaching solicited and
periodic usage feedback is described in [COPS-FEED-FRWK.]The COPS- periodic usage feedback is described in [COPS-FEED-FRWK]. The COPS-
PR Policy Usage Feedback Policy Information Base document defines PR Policy Usage Feedback Policy Information Base document defines
the policy classes for a feedback framework Policy information base the policy classes for a feedback framework Policy information base
(PIB). (PIB).
Table of Contents Table of Contents
1 Introduction.....................................................4 1 Introduction.....................................................4
2 General Concepts.................................................4 2 General Concepts.................................................4
2.1 Selection, Usage and Linkage Policies..........................4 2.1 Selection, Usage and Linkage Policies..........................4
2.2 Normal Operations..............................................5 2.2 Normal Operations..............................................5
2.2.1 Connection Establishment and Initial Configuration Request...5 2.2.1 Connection Establishment and Initial Configuration Request...5
2.2.2 Unsolicited Reports - Periodic Reporting.....................6 2.2.2 Unsolicited Reports - Periodic Reporting.....................6
2.2.3 Unsolicited Reports - Reporting Conditions...................6 2.2.3 Unsolicited Reports - Reporting Conditions...................6
2.2.4 Solicited Reports............................................6 2.2.4 Solicited Reports............................................6
2.2.5 Resuming and Suspending Periodic Feedback Reporting..........7 2.2.5 Resuming and Suspending Periodic Feedback Reporting..........7
2.2.6 Failover.....................................................7 2.2.6 Failover.....................................................7
2.3 Detail Policy Usage Feedback Reporting.........................7 2.3 Usage Policy and Under-specified Selection Criteria............7
3 Summary of the Feedback Framework Policy Information Base........9 3 Summary of the Feedback Framework Policy Information Base........9
3.1 SPPI ACCESS clause report-only.................................9 3.1 SPPI ACCESS clause report-only.................................9
3.2 Feedback Groups and PRCs.......................................9 3.2 Feedback Groups and PRCs.......................................9
3.2.1 Feedback Action Table........................................9 3.2.1 Feedback Action Table.......................................10
3.2.2 Feedback List Table.........................................10 3.2.2 Feedback List Table.........................................10
3.2.3 The Feedback Selection Usage Combination Capability Table...10 3.2.3 The Feedback Selection Usage Combination Capability Table...10
3.2.4 The Feedback Report Linkage Table...........................10 3.2.4 The Feedback Report Linkage Table...........................11
3.2.7 The Feedback Traffic Statistics Threshold Table.............11 3.2.5 The Feedback Traffic Statistics Threshold Table.............11
3.2.8 Feedback DPE Selection Criteria Table.......................11 4 The Feedback Framework PIB Module...............................11
3.2.9 Feedback DPE Selection Query Table..........................11 5 Security Considerations.........................................25
4 The Feedback Framework PIB Module...............................12 6 Acknowledgements................................................25
5 Security Considerations.........................................26 7 Authors' Addresses..............................................25
6 Acknowledgements................................................27 8 References......................................................26
7 Authors' Addresses..............................................27
8 References......................................................27
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 also defined.
skipping to change at page 4, line 29 skipping to change at page 4, line 29
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 qosClfrElementEntry which is useful in defining QoS is the frwkRoleComboEntry may be used in defining QoS enforcement
enforcement policies but may also be used to specify conditions on policies but may also be used to specify conditions on which to base
which to base usage - i.e. count the number of packets meeting the usage - i.e. count the number of packets meeting the criterion of an
criterion. interface capability set name and role combination.
The usage policy defines what attributes are monitored and recorded The usage policy defines what attributes are recorded by the PEP.
by the PEP. These policies have an ACCESS clause of Report. These policies have an ACCESS clause of Report. Generally, the usage
Generally, the usage policies specify counts related to a specific policies specify counts related to a specific action such as a packet
action such as a packet being dropped. The feedback framework PIB being dropped. The feedback framework PIB defines two usage policy
defines two usage policy classes, frwkFeedbackTrafficUsage and classes, frwkFeedbackTrafficUsage and frwkFeedbackIfTrafficUsage.
frwkFeedbackIfTrafficUsage. Usage PRCs may be generic, collecting Usage PRCs may be generic, collecting basic statistics, or they may
basic statistics, or they may be specific to a particular usage. The be specific to a particular usage. The PDP decides which PRC(s) best
PDP decides which PRC(s) best suit(s) its requirements. The PEP may suit(s) its requirements. The PEP may support only one usage feedback
support only one usage feedback PRC, in which case all statistics are PRC, in which case all statistics are gathered using instances of
gathered using instances of that PRC. Alternatively, the PEP may that PRC. Alternatively, the PEP may support multiple usage feedback
support multiple usage feedback PRCs. The PDP then decides which PRC PRCs. The PDP then decides which PRC to associate with a particular
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 contains the value of the selection criteria instance as well as the value of the usage
usage feedback PRC. feedback PRC.
----------------- ------------------ ----------------- ----------------- ------------------ -----------------
| | | | | | | | | | | |
| 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
Figure 1 illustrates the relationship between a 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 frwkFeddbackTrafficUsageLinkRef An example of this is the attribute frwkFeedbackTrafficUsageLinkRef
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 Connection Accept message contains The Accounting Timer object in the COPS Connection Accept message
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 [COPS-FEEDBACK-FRWK]. This is used as the
basic unit of measurement in defining intervals for specific usage basic unit of measurement in defining intervals for specific usage
policies with the frwkFeedbackLinkInterval attribute. policies with 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 the frwkPRCSupportTable entries [FR-PIB].
The PEP also indicates whether it supports the frwkFeedbackLinkTable The PEP 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
skipping to change at page 6, line 22 skipping to change at page 6, line 21
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
interval. interval.
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 usages provide an unsolicited REPORT containing all defined usage instances
instances just prior to the PEP issuing a Delete Request State and just prior to the PEP issuing a Delete Request State and just prior
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: frwkFeedbackLinkTable. Supported conditions are:
ChangeOnly ChangeOnly
If this flag is set in the frwkFeedbackLinkFlags field, the If this flag is set in the frwkFeedbackLinkFlags field, 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
skipping to change at page 7, line 51 skipping to change at page 7, line 49
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
deterministically. It issues an unsolicited decision containing the deterministically. It issues an unsolicited decision containing the
frwkFeedbackResumeIndicator set to resume reporting. The PEP should frwkFeedbackResumeIndicator set to resume reporting. The PEP should
resume reporting at the next appropriate feedback interval resume reporting at the next appropriate feedback interval
established upon the acceptance of the re-connection. The PDP is established upon the acceptance of the re-connection. The PDP is
aware of the request state Handle(s) and the supported PRCs either aware of the request state Handle(s) and the supported PRCs either
through the state synchronization mechanism or because the PDP through the state synchronization mechanism or because the PDP
considers itself synchronized with the PEP upon reconnection. considers itself synchronized with the PEP upon reconnection.
2.3 Detail Policy Usage Feedback Reporting 2.3 Usage Policy and Under-specified Selection Criteria
Some of the policy objects created in the PEP with COPS-PR can be Some of the usage policy objects created in the PEP with COPS-PR can
used by the PEP multiple times - they effectively act as templates be used by the PEP multiple times - they effectively act as
for the objects created by the PEP. COPS-PR only has the identity templates for the objects created by the PEP. COPS-PR only has the
(OID) of the object that is shared between all the assignment the identity (OID) of the object that is shared between all the
PEP created, however it is desirable to collect usage information assignment the PEP created, however it is desirable to collect usage
for each of the derived objects individually. 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
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 assignment.
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:
As part of a data path, an IPFilter object can be assigned to
many combinations of interface and direction.
To refer to a specific assignment of an IPFilter for feedback
purposes, the reference to the IPFilter instance has to be
qualified with the interface and direction attributes.
Feedback from the filter on a specific interface: The frwkRoleComboEntry may be used as a selection criteria
As the selection criteria policy a identifying the role combination and capability set. However,
frwkFeedbackDPESelectionEntry is used which contains the there is a more granular piece of information associated with
qualifying attributes: capability set and role combination which is the interface index.
frwkFeedbackDPESelectionDataPathElement Prid The interface index is associated with a specific capability set
frwkFeedbackDPESelectionInterface Prid and role combination.
frwkFeedbackDPESelectionIfDirection IfDirection
In this case this policy would be combined in a
frwkLinkageEntry with the FrwkFeedbackTrafficUsage PRC. This
combination will result in only one
FrwkFeedbackTrafficUsageEntry to be created which only contains
the traffic counters.
Feedback from all interfaces a filter is assigned to: The frwkIfFeedbackTrafficUsageEntry may be linked for feedback
By combining a frwkFeedbackDPESelectionQueryEntry as selection purposes with a frwkRoleComboEnry instance. The usage policy
criteria with the FrwkFeedbackIfTrafficUsage PRC, all the frwkFeedbackIfTrafficUsageEntry contains the item
assignments are selected and multiple frwkFeedbackIfTrafficUsageIfIndex that is populated by the PEP.
FrwkFeedbackIfTrafficUsageEntries get created. Each entry not The frwkFeedbackIfTrafficUsageIfIndex identifies the specific
only carries the desired traffic counters but also the IfIndex for a given capability set and role combination selection
qualifying attributes to associate it with the assignment: pair that is being monitored.
frwkFeedbackIfTrafficUsageInterface Prid,
frwkFeedbackIfTrafficUsageIfDirection IfDirection 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
the FrwkFeedbackIfTrafficUsage PRC, all the assignments are
selected and multiple FrwkFeedbackIfTrafficUsageEntries get
created. Each entry not only carries the desired traffic
counters but also the IfIndex qualifying attributes to
associate it with the assignment:
frwkFeedbackIfTrafficUsageId InstanceId,
frwkFeedbackIfTrafficUsageLinkRefID ReferenceId,
frwkFeedbackIfTrafficUsageIfIndex InterfaceIndex,
frwkFeedbackIfTrafficUsagePacketCount Counter64,
frwkFeedbackIfTrafficUsageByteCount Counter64
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
skipping to change at page 9, line 32 skipping to change at page 9, line 49
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:
1) Feedback Action Table 1) Feedback Action Table
2) Feedback Action List Table 2) Feedback Action List Table
3) Feedback Selection Usage Combination Capability Table 3) Feedback Selection Usage Combination Capability Table
4) Feedback Linkage Table 4) Feedback Linkage Table
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 1) Feedback Traffic Statistics Usage Table
2) Feedback Interface Traffic Statistics Usage Table 2) Feedback Interface Traffic Statistics Usage Table
3) Feedback Traffic Statistics Threshold Table
The policy classes in the Feedback Selection Group are: The policy classes in the Feedback Selection Group are:
1) Feedback DPE Selection Criteria Table 1) Feedback RoleCombo Filter Selection Table
2) Feedback DPE Selection Query Table Feedback PRI Selection Table
3) Feedback DPE Interface Usage Table
3.2.1 Feedback Action Table 3.2.1 Feedback Action Table
The Feedback Action Table contains the attributes that specify The Feedback Action Table 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
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. policy instances.
skipping to change at page 11, line 5 skipping to change at page 11, line 20
instance. It specifies the PRID of the selection criteria and the PRC instance. It specifies the PRID of the selection criteria and the PRC
of the usage instance. This table permits the reuse of a selection of the usage instance. This table permits the reuse of a selection
criteria instance for multiple usage policies. 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 usage instance. This interval is defined in units of the Accounting
Timer Interval specified in the client accept message. A value of 0 Timer Interval specified in the client accept message. A value of 0
in this attribute indicates that the usage policy must be solicited. in this attribute indicates that the usage policy must be solicited.
3.2.5 The Feedback Traffic Statistics Usage Table 3.2.5 The Feedback Traffic Statistics Threshold Table
This table is used to provide threshold values for the attributes
described in the above usage tables.
3.2.6 The Feedback Traffic Statistics Usage Table
This table describes the packet counts, byte counts, last timestamp This table describes the packet counts, byte counts, last timestamp
when a packet was received and the PRID of the associated Feedback when a packet was received and the PRID of the associated Feedback
Report Linkage instance. The count and timestamp information is Report Linkage instance. The count and timestamp information is
monitored and recorded by the PEP and supplied to the PDP with the monitored and recorded by the PEP and supplied to the PDP with the
COPS accounting type report message within the maximum interval COPS accounting type report message within the maximum interval
specified. specified.
3.2.6 The Feedback Interface Traffic Statistics Usage Table 3.2.7 The Feedback Interface Traffic Statistics Usage Table
This table is similar to the table described above, except that it This table is similar to the table described above, except that it
includes an additional reference to an interface. This table should includes an additional reference to an interface index. This table
be used with a selection criteria that matches an element that is should be used with a selection criteria that matches an element
assigned to multiple interfaces. The interface field can be used to that is assigned to multiple interfaces. The interface field can be
associate the instances of this table with the specific elementĂs used to associate the instances of this table with the specific
assignment. elementĂs assignment.
3.2.7 The Feedback Traffic Statistics Threshold Table
This table is used to provide threshold values for the attributes
described in the above usage tables.
3.2.8 Feedback DPE Selection Criteria Table
This table is an example of a Selection Criteria PRC that references
a specific instance of a shared object.
It is based on the popular model of a data path consisting of
multiple linked data path elements (DPEs).
A single data path can be assigned to multiple interfaces by a
single entry in the Data Path Table [DIFFSERV-PIB], elements within
this data path however can collect usage information for each
assignment individually.
Instances of this class allow the PDP to select a specific
assignment of a data path element to be selected for usage
reporting. This is achieved by the combination of references to a
Data Path Entry, a Data Path Element and the Interface.
It is expected to be used in combination with the
FrwkFeedbackTrafficUsage PRC.
3.2.9 Feedback DPE Selection Query Table
This Selection Criteria PRC is similar to the DPE Selection Criteria
Table, however it is missing the reference to a specific interface.
This means an instance of this class can select multiple assignments
of a data path element for usage collection. Each selected
assignment of the DPE creates its own usage instance.
This selection criteria PRC is expected to be used together with a
usage PRC that includes the a reference to an interface, so the
results can be assigned uniquely.
3.2.11 Feedback DPE Interface Usage Table 3.2.8 The Feedback RoleCombo Filter Selection Table
The DPE Interface Usage class is an extension of the generic Traffic This table is used to identify a selection criteria of Role
Usage class that also includes a reference to a frwkIfRoleComboEntry Combination and either IP or 802 Filter. This Role Combination and
that represents the interface, this instance is associated with. Filter is the basis upon which the usage performs monitoring and
collection.
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, ExtUTCTime, Unsigned32, Unsigned64,
Integer32, MODULE-IDENTITY, OBJECT-TYPE Integer32, MODULE-IDENTITY, OBJECT-TYPE
FROM COPS-PR-SPPI FROM COPS-PR-SPPI
TruthValue, TEXTUAL-CONVENTION TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
PolicyInstanceId, PolicyReferenceId InstanceId, ReferenceId
FROM COPS-PR-SPPI-TC FROM COPS-PR-SPPI-TC
Counter64 Counter64
FROM SNMPv2-SMI; FROM SNMPv2-SMI
InterfaceIndex
FROM IF-MIB;
feedbackPolFrameworkPib MODULE-IDENTITY feedbackPolFrameworkPib MODULE-IDENTITY
SUBJECT-CATEGORIES { all } SUBJECT-CATEGORIES { all }
LAST-UPDATED "200011171000Z" LAST-UPDATED "200011171000Z"
ORGANIZATION "IETF RAP WG" ORGANIZATION "IETF RAP WG"
CONTACT-INFO " CONTACT-INFO "
Diana Rawlins Diana Rawlins
WorldCom WorldCom
901 International Parkway 901 International Parkway
Richardson, TX 75081 Richardson, TX 75081
skipping to change at page 16, line 33 skipping to change at page 16, line 22
::= { frwkFeedbackGroupClasses 3} ::= { frwkFeedbackGroupClasses 3}
frwkFeedbackSelUsageComboCapsEntry OBJECT-TYPE frwkFeedbackSelUsageComboCapsEntry OBJECT-TYPE
SYNTAX FrwkFeedbackSelUsageComboCapsEntry SYNTAX FrwkFeedbackSelUsageComboCapsEntry
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 PRCs for feedback supported by the PEP
device." device."
PIB-INDEX { frwkFeedbacSelUsageComboCapsId } PIB-INDEX { frwkFeedbackSelUsageComboCapsId }
UNIQUENESS { UNIQUENESS {
frwkFeedbackSelUsageComboCapsSelection, frwkFeedbackSelUsageComboCapsSelection,
frwkFeedbackSelUsageComboCapsUsage, frwkFeedbackSelUsageComboCapsUsage,
frwkFeedbackSelUsageComboCapsThreshold frwkFeedbackSelUsageComboCapsThreshold
} }
::= {frwkFeedbackSelUsageComboCapsTable 1} ::= {frwkFeedbackSelUsageComboCapsTable 1}
FrwkFeedbackSelUsageComboCapsEntry ::= SEQUENCE { FrwkFeedbackSelUsageComboCapsEntry ::= SEQUENCE {
frwkFeedbackSelUsageComboCapsId InstanceId, frwkFeedbackSelUsageComboCapsId InstanceId,
frwkFeedbackSelUsageComboCapsSelection OBJECT IDENTIFIER, frwkFeedbackSelUsageComboCapsSelection OBJECT IDENTIFIER,
skipping to change at page 17, line 39 skipping to change at page 17, line 30
-- --
-- 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 permit 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."
::= { 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 {frwkFeedbackActionLinkId} PIB-INDEX { frwkFeedbackLinkId }
UNIQUENESS { frwkFeedbackLinkId, UNIQUENESS {frwkFeedbackLinkSel,
frwkFeedbackLinkSel,
frwkFeedbackLinkUsage } frwkFeedbackLinkUsage }
::= {frwkFeedbackLinkTable 1} ::= {frwkFeedbackLinkTable 1}
FrwkFeedbackLinkEntry ::= SEQUENCE { FrwkFeedbackLinkEntry ::= SEQUENCE {
frwkFeedbackLinkId InstanceId, frwkFeedbackLinkId InstanceId,
frwkFeedbackLinkSel Prid, frwkFeedbackLinkSel Prid,
frwkFeedbackLinkUsage OBJECT IDENTIFIER, frwkFeedbackLinkUsage OBJECT IDENTIFIER,
frwkFeedbackLinkInterval Integer32, frwkFeedbackLinkInterval Integer32,
frwkFeedbackLinkThreshold Prid, frwkFeedbackLinkThreshold Prid,
frwkFeedbackLinkFlags BITS frwkFeedbackLinkFlags BITS
skipping to change at page 18, line 27 skipping to change at page 18, line 16
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRID of the selection criteria instance that "The PRID of the Policy Class instance as the monitoring
defines the conditions to use by the PEP for point, or the PRID of the selection criteria instance that
monitoring the usage." defines the conditions for monitoring, to be use by the
PEP for usage reporting."
::= { frwkFeedbackLinkEntry 2} ::= { frwkFeedbackLinkEntry 2}
frwkFeedbackLinkUsage OBJECT-TYPE frwkFeedbackLinkUsage OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRC of the usage policy class that the PEP uses to "The PRC of the usage policy class that the PEP uses to
monitor, record and report." monitor, record and report."
skipping to change at page 19, line 37 skipping to change at page 19, line 27
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
--
frwkFeedbackTrafficThresholdTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresholdEntry
PIB-ACCESS Install
STATUS current
DESCRIPTION
"This class defines the threshold attributes
corresponding to usage attributes specified in
frwkFeedbackTrafficUsageTable,
frwkFeedbackIfTrafficUsageTable and other similar
usage classes.
The usage object is considered to match the threshold
condition if the following expression evaluates to
ŠTRUEĂ:
{
byteCond = (ByteThreshold != NULL) ?
(ByteThreshold > ByteCounter) : FALSE;
packetCond (PacketThreshold != NULL) ?
(PacketThreshold > PacketCounter) : FALSE;
return ( byteCond || packetCond );
}"
::= { frwkFeedbackGroupClasses 5}
frwkFeedbackTrafficThresholdEntry OBJECT-TYPE
SYNTAX FrwkFeedbackTrafficThresholdEntry
STATUS current
DESCRIPTION
"Defines the attributes to hold threshold values."
PIB-INDEX {frwkFeedbackTrafficThresholdId}
::= {frwkFeedbackTrafficThresholdTable 1}
FrwkFeedbackTrafficThresholdEntry ::= SEQUENCE {
frwkFeedbackTrafficThresholdId InstanceId,
frwkFeedbackTrafficThresholdPacketThreshold Integer64,
frwkFeedbackTrafficThresholdByteThreshold Integer64
}
frwkFeedbackTrafficThresholdId OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"Arbitrary integer index that uniquely identifies
an instance of the class."
::= { frwkFeedbackTrafficThresholdEntry 1 }
frwkFeedbackTrafficThresholdPacketThreshold OBJECT-TYPE
SYNTAX Integer64
STATUS current
DESCRIPTION
"The threshold, in terms of packets, that must be
exceeded to trigger a report in the next
reporting interval."
::= { frwkFeedbackTrafficThresholdEntry 2 }
frwkFeedbackTrafficThresholdByteThreshold OBJECT-TYPE
SYNTAX Integer64
STATUS current
DESCRIPTION
"The threshold, in terms of bytes, that must be
exceeded to trigger a report in the next
reporting interval."
::= { frwkFeedbackTrafficThresholdEntry 3 }
--
-- All 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 ::= { feedbackPolFrameworkPib 2 }
-- --
-- The generic traffic (byte & packet count) usage class -- The generic traffic (byte & packet count) usage class
-- --
skipping to change at page 21, line 22 skipping to change at page 22, line 28
-- --
-- The traffic usage class, qualified for an interface -- The traffic usage class, qualified for an interface
-- --
frwkFeedbackIfTrafficUsageTable OBJECT-TYPE frwkFeedbackIfTrafficUsageTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficUsageEntry SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficUsageEntry
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 PRC similar to the basic TrafficUsage class
that also contains a reference to an interface. This that also contains a reference to an interface index.
class should be used with a selection criteria that This class should be used with a underspecified
matches an element that is assigned to multiple selection criteria entry from the frwkRoleComboTable
interfaces. The interface field can be used to that matches an element that can be assigned to
associate the instances of this class with the specific multiple interface indices. The interface field can be
elementĂs assignment." used to associate the instances of this class with the
specific elementĂs assignment."
::= { frwkFeedbackUsageClasses 2 } ::= { frwkFeedbackUsageClasses 2 }
frwkFeedbackIfTrafficUsageEntry OBJECT-TYPE frwkFeedbackIfTrafficUsageEntry OBJECT-TYPE
SYNTAX FrwkFeedbackIfTrafficUsageEntry SYNTAX FrwkFeedbackIfTrafficUsageEntry
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 {frwkFeedbackIfTrafficUsageId}
UNIQUENESS { frwkFeedbackIfTrafficUsageLinkRefID, UNIQUENESS { frwkFeedbackIfTrafficUsageLinkRefID,
frwkFeedbackIfTrafficUsageInterface } frwkFeedbackIfTrafficUsageIfIndex }
::= {frwkFeedbackIfTrafficUsageTable 1} ::= {frwkFeedbackIfTrafficUsageTable 1}
FrwkFeedbackIfTrafficUsageEntry ::= SEQUENCE { FrwkFeedbackIfTrafficUsageEntry ::= SEQUENCE {
frwkFeedbackIfTrafficUsageId InstanceId, frwkFeedbackIfTrafficUsageId InstanceId,
frwkFeedbackIfTrafficUsageLinkRefID ReferenceId, frwkFeedbackIfTrafficUsageLinkRefID ReferenceId,
frwkFeedbackIfTrafficUsageInterface ReferenceId, frwkFeedbackIfTrafficUsageIfIndex InterfaceIndex,
frwkFeedbackIfTrafficUsageIfDirection IfDirection,
frwkFeedbackIfTrafficUsagePacketCount Counter64, frwkFeedbackIfTrafficUsagePacketCount Counter64,
frwkFeedbackIfTrafficUsageByteCount Counter64 frwkFeedbackIfTrafficUsageByteCount Counter64
} }
frwkFeedbackIfTrafficUsageId OBJECT-TYPE frwkFeedbackIfTrafficUsageId 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 } ::= { frwkFeedbackIfTrafficUsageEntry 1 }
skipping to change at page 22, line 18 skipping to change at page 23, line 23
frwkFeedbackIfTrafficUsageLinkRefID OBJECT-TYPE frwkFeedbackIfTrafficUsageLinkRefID 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 } ::= { frwkFeedbackIfTrafficUsageEntry 2 }
frwkFeedbackIfTrafficUsageInterface OBJECT-TYPE frwkFeedbackIfTrafficUsageIfIndex OBJECT-TYPE
SYNTAX ReferenceId SYNTAX InterfaceIndex
PIB-REFERENCES { frwkIfRoleComboEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ReferenceID of a frwkIfRoleCombo instance, "The value of this attribute is the ifIndex which is
uniquely identifying a specific interface." associated with the specified RoleCombination and
::= { frwkFeedbackIfTrafficUsageEntry 3 } interface capability set name."
frwkFeedbackIfTrafficUsageIfDirection OBJECT-TYPE ::= { frwkFeedbackIfTrafficUsageEntry 3 }
SYNTAX IfDirection
STATUS current
DESCRIPTION
" The direction of the selected interface.÷
::= { frwkFeedbackIfTrafficUsageEntry 4 }
frwkFeedbackIfTrafficUsagePacketCount OBJECT-TYPE frwkFeedbackIfTrafficUsagePacketCount OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of packets handled by the associated element "The count of packets handled by the associated element
during the reporting interval." during the reporting interval."
::= { frwkFeedbackIfTrafficUsageEntry 5 } ::= { frwkFeedbackIfTrafficUsageEntry 4 }
frwkFeedbackIfTrafficUsageByteCount OBJECT-TYPE frwkFeedbackIfTrafficUsageByteCount OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
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 6 } ::= { frwkFeedbackIfTrafficUsageEntry 5 }
--
-- The Threshold class that accompanies the above Usage PRCs
--
frwkFeedbackTrafficThresholdTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresholdEntry
PIB-ACCESS Install
STATUS current
DESCRIPTION
"This class defines the threshold attributes
corresponding to usage attributes specified in
frwkFeedbackTrafficUsageTable,
frwkFeedbackIfTrafficUsageTable and other similar
usage classes.
The usage object is considered to match the threshold
condition if the following expression evaluates to
ŠTRUEĂ:
{
byteCond = (ByteThreshold != NULL) ?
(ByteThreshold > ByteCounter) : FALSE;
packetCond (PacketThreshold != NULL) ?
(PacketThreshold > PacketCounter) : FALSE;
return ( byteCond || packetCond );
}"
::= { frwkFeedbackUsageClasses 3}
frwkFeedbackTrafficThresholdEntry OBJECT-TYPE
SYNTAX FrwkFeedbackTrafficThresholdEntry
STATUS current
DESCRIPTION
"Defines the attributes to hold threshold values."
PIB-INDEX {frwkFeedbackTrafficThresholdId}
::= {frwkFeedbackTrafficThresholdTable 1}
FrwkFeedbackTrafficThresholdEntry ::= SEQUENCE {
frwkFeedbackTrafficThresholdId InstanceId,
frwkFeedbackTrafficThresholdPacketThreshold Integer64,
frwkFeedbackTrafficThresholdByteThreshold Integer64
}
frwkFeedbackTrafficThresholdId OBJECT-TYPE
SYNTAX InstanceId
STATUS current
DESCRIPTION
"Arbitrary integer index that uniquely identifies
an instance of the class."
::= { frwkFeedbackTrafficThresholdEntry 1 }
frwkFeedbackTrafficThresholdPacketThreshold OBJECT-TYPE
SYNTAX Integer64
STATUS current
DESCRIPTION
"The threshold, in terms of packets, that must be
exceeded to trigger a report in the next
reporting interval."
::= { frwkFeedbackTrafficThresholdEntry 2 }
frwkFeedbackTrafficThresholdByteThreshold OBJECT-TYPE
SYNTAX Integer64
STATUS current
DESCRIPTION
"The threshold, in terms of bytes, that must be
exceeded to trigger a report in the next
reporting interval."
::= { frwkFeedbackTrafficThresholdEntry 3 }
-- --
-- All Selection classes are in the separate -- All Selection classes are in the separate
-- FrwkFeedbackSelectionClasses group -- FrwkFeedbackSelectionClasses group
-- --
frwkFeedbackSelectionClasses frwkFeedbackSelectionClasses
OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 3 } OBJECT IDENTIFIER ::= { feedbackPolFrameworkPib 3 }
-- --
-- DPE Selection Class -- The Role Combination Filter Selection Table
-- --
frwkFeedbackDPESelectionTable OBJECT-TYPE frwkFeedbackRoleComboFilterSelTable OBJECT-TYPE
SYNTAX SEQUENCE OF frwkFeedbackDPESelectionEntry SYNTAX SEQUENCE OF FrwkFeedbackRoleComboFilterSelEntry
PIB-ACCESS Install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class defines a selection criteria that "A selection PRC that defines selection for monitoring
identifies a specific data path element to collect based on the role combination, capability set and
usage information" either IP or 802.1 filter."
::= { frwkFeedbackSelectionClasses 1 }
::= { frwkFeedbackSelectionClasses 2}
frwkFeedbackDPESelectionEntry OBJECT-TYPE frwkFeedbackRoleComboFilterSelEntry OBJECT-TYPE
SYNTAX frwkFeedbackDPESelectionEntry SYNTAX FrwkFeedbackRoleComboFilterSelEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the attributes the of the selection "Defines the attributes on which the PEP is to
criteria identifying a specific policy base selection."
where to monitor the associated usage."
PIB-INDEX { frwkFeedbackDPESelectionId }
UNIQUENESS { frwkFeedbackDPESelectionDataPathElement,
frwkFeedbackDPESelectionInterface,
frwkFeedbackDPESelectionIfDirection }
::= {frwkFeedbackDPESelectionTable 1} PIB-INDEX { frwkFeedbackRoleComboFilterSelId}
UNIQUENESS { frwkFeedbackRoleComboFilterSelRoleComboRefID,
frwkFeedbackRoleComboFilterSelBaseFilterRefID,
frwkFeedbackRoleComboFilterSelIP-802FilterRefID
}
::= {frwkFeedbackRoleComboFilterSelTable 1}
FrwkFeedbackRoleComboFilterSelEntry ::= SEQUENCE {
frwkFeedbackRoleComboFilterSelId InstanceId,
frwkFeedbackRoleComboFilterSelRoleComboRefID ReferenceId,
frwkFeedbackRoleComboFilterSelBaseFilterRefID ReferenceId,
frwkFeedbackRoleComboFilterSelIP-802FilterRefID ReferenceId
frwkFeedbackDPESelectionEntry ::= SEQUENCE {
frwkFeedbackDPESelectionId InstanceId,
frwkFeedbackDPESelectionDataPathElement Prid,
frwkFeedbackDPESelectionInterface Prid,
frwkFeedbackDPESelectionIfDirection IfDirection
} }
frwkFeedbackDPESelectionId OBJECT-TYPE frwkFeedbackRoleComboFilterSelId 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."
::= { frwkFeedbackDPESelectionEntry 1 } ::= { frwkFeedbackRoleComboFilterSelEntry 1 }
frwkFeedbackDPESelectionDataPathElement OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"The PRID of the element in the data path that we
want to collect usage information from. This element
must be part of the data path assigned to the
interface/direction combination referenced in this
object."
::= { frwkFeedbackDPESelectionEntry 2 }
frwkFeedbackDPESelectionInterface OBJECT-TYPE
SYNTAX Prid
STATUS current
DESCRIPTION
"The PRID of a frwkIfRoleCombo instance, uniquely
identifying a specific interface"
::= { frwkFeedbackDPESelectionEntry 3 }
frwkFeedbackDPESelectionIfDirection OBJECT-TYPE
SYNTAX IfDirection
STATUS current
DESCRIPTION
"The direction (ingress/egress) that to which the DPE
is attached that we want to match."
::= { frwkFeedbackDPESelectionEntry 4 }
--
-- DPE Selection Query Class
--
frwkFeedbackDPESelectionQueryTable OBJECT-TYPE
SYNTAX SEQUENCE OF frwkFeedbackDPESelectionQueryEntry
PIB-ACCESS Install
STATUS current
DESCRIPTION
"This class defines a selection criteria that
identifies a set of assignments of a data path element
based on an entry in the data path anchor table such as
the Data Path Table.
Each matched assignment will collect and report usage
independently, so this selection criteria should be
combined with a Usage PRC that includes an interface
reference."
::= { frwkFeedbackSelectionClasses 3}
frwkFeedbackDPESelectionQueryEntry OBJECT-TYPE frwkFeedbackRoleComboFilterSelRoleComboRefID OBJECT-TYPE
SYNTAX frwkFeedbackDPESelectionQueryEntry SYNTAX ReferenceId
PIB-REFERENCES { frwkRoleComboEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the attributes the of the selection "The ReferenceId of the frwkRoleComboTable policy
criteria identifying a specific policy instance used for selection."
where to monitor the associated usage." ::= { frwkFeedbackRoleComboFilterSelEntry 2 }
PIB-INDEX { frwkFeedbackDPESelectionQueryId }
UNIQUENESS { frwkFeedbackDPESelectionQueryDataPathElement }
::= {frwkFeedbackDPESelectionQueryTable 1}
frwkFeedbackDPESelectionQueryEntry ::= SEQUENCE {
frwkFeedbackDPESelectionQueryId InstanceId,
frwkFeedbackDPESelectionQueryDataPathElement Prid
}
frwkFeedbackDPESelectionQueryId OBJECT-TYPE frwkFeedbackRoleComboFilterSelBaseFilterRefID OBJECT-TYPE
SYNTAX InstanceId SYNTAX ReferenceId
PIB-REFERENCES { frwkBaseFilterEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Arbitrary integer index that uniquely identifies "The ReferenceId of the frwkBaseFilterTable policy
an instance of the class." used for selection."
::= { frwkFeedbackDPESelectionQueryEntry 1 } ::= { frwkFeedbackRoleComboFilterSelEntry 3 }
frwkFeedbackDPESelectionQueryDataPathElement OBJECT-TYPE frwkFeedbackRoleComboFilterSelIP-802FilterRefID OBJECT-TYPE
SYNTAX Prid SYNTAX ReferenceId
PIB-REFERENCES { frwkIpFilterEntry }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRID of the element in the data path that we "The ReferenceId of the frwkIPFilterTable policy used
want to collect usage information from. This element for selection."
must be part of the data path referenced from the ::= { frwkFeedbackRoleComboFilterSelEntry 4 }
frwkFeedbackDPESelectionQueryDataPath field."
::= { frwkFeedbackDPESelectionQueryEntry 2 }
END END
5 Security Considerations 5 Security Considerations
The feedback information is sensitive and requires that authorized The feedback information is sensitive and requires that authorized
messaging occur between the PEP and the PDP. This protection can messaging occur between the PEP and the PDP. This protection can
be accomplished with IPSEC or TLS [COPS-TLS] between the PEP and be accomplished with IPSEC or TLS [COPS-TLS] between the PEP and
the PDP or using the security mechanisms described in the base the PDP or using the security mechanisms described in the base
COPS protocol. COPS protocol.
skipping to change at page 28, line 19 skipping to change at page 26, line 45
[3084] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. [3084] 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.
[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-05.txt, November 2001 diffserv-pib-09.txt, June 2002
[FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A. [FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A.
Smith, F. Reichmeyer "Framework Policy Information Base", draft- Smith, F. Reichmeyer "Framework Policy Information Base", draft-
ietf-rap-frameworkpib-06.txt, November 2001 ietf-rap-frameworkpib-09.txt, June 2002
[COPS-TLS], Walker, J., Kulkarni, A.,÷COPS Over TLS÷, draft-ietf- [COPS-TLS], Walker, J., Kulkarni, A.,÷COPS Over TLS÷, draft-ietf-
rap-cops-tls-02.txt, October 2001. rap-cops-tls-04.txt, June 2002.
 End of changes. 

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