draft-ietf-rap-feedback-fr-pib-06.txt   rfc3571.txt 
Internet Draft Diana Rawlins Network Working Group D. Rawlins
Expiration: October 2003 WorldCom Request for Comments: 3571 MCI
File: draft-ietf-rap-feedback-fr-pib-06.txt Amol Kulkarni Category: Informational A. Kulkarni
Intel Intel
Kwok Ho Chan K. Chan
Nortel Networks Nortel Networks
Martin Bokaemper M. Bokaemper
Juniper Networks Juniper Networks
Dinesh Dutt D. Dutt
Cisco Cisco
August 2003
Framework Policy Information Base for Usage Feedback Framework Policy Information Base for Usage Feedback
Last Updated April 4, 2003
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six This memo provides information for the Internet community. It does
months and may be updated, replaced, or obsoleted by other not specify an Internet standard of any kind. Distribution of this
documents at any time. It is inappropriate to use Internet-Drafts memo is unlimited.
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2003). All Rights Reserved.
http://www.ietf.org/shadow.html.
Abstract Abstract
This document describes a portion of the Policy Information Base This document describes a portion of the Policy Information Base
(PIB) to control policy usage collection and reporting in a device. (PIB) to control policy usage collection and reporting in a device.
The provisioning classes specified here allow a Policy Decision The provisioning classes specified here allow a Policy Decision Point
Point (PDP) to select which policy objects should collect usage (PDP) to select which policy objects should collect usage
information, what information should be collected and when it information, what information should be collected and when it should
should be reported. 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 October 2003 [Page 1]
Conventions used in this document This PIB requires the presence of other PIBs (defined elsewhere) that
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL provide the policy objects from which usage information is collected.
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
in this document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1 Introduction.....................................................3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 General Concepts.................................................3 2. General Concepts . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 Selection, Usage and Linkage Policies..........................3 2.1. Selection, Usage and Linkage Policies. . . . . . . . . . 3
2.2 Normal Operations..............................................4 2.2. Normal Operations. . . . . . . . . . . . . . . . . . . . 4
2.2.1 Connection Establishment and Initial Configuration Request...4 2.2.1. Connection Establishment and Initial
2.2.2 Unsolicited Reports - Periodic Reporting.....................5 Configuration Request. . . . . . . . . . . . . . 4
2.2.3 Unsolicited Reports - Reporting Conditions...................5 2.2.2. Unsolicited Reports - Periodic Reporting . . . . 5
2.2.4 Solicited Reports............................................5 2.2.3. Unsolicited Reports - Reporting Conditions . . . 5
2.2.5 Resuming and Suspending Periodic Feedback Reporting..........6 2.2.4. Solicited Reports. . . . . . . . . . . . . . . . 6
2.2.6 Failover.....................................................6 2.2.5. Resuming and Suspending Periodic Feedback
2.3 Usage Policy and Under-specified Selection Criteria............6 Reporting. . . . . . . . . . . . . . . . . . . . 6
3 Summary of the Feedback Framework Policy Information Base........7 2.2.6. Failover . . . . . . . . . . . . . . . . . . . . 6
3.1 SPPI ACCESS clause report-only.................................7 2.3. Usage Policy and Under-specified Selection Criteria. . . 7
3.2 Usage32 and Usage64 textual conventions........................7 3. Summary of the Feedback Framework Policy Information Base. . . 8
3.3 Feedback Groups and PRCs.......................................8 3.1. SPPI ACCESS Clause Report-Only . . . . . . . . . . . . . 8
3.3.1 Feedback Action..............................................8 3.2. Usage32 and Usage64 Textual Conventions. . . . . . . . . 8
3.3.2 Feedback Action List.........................................9 3.3. Feedback Groups and PRCs . . . . . . . . . . . . . . . . 9
3.3.3 Feedback Linkage Capability..................................9 3.3.1. Feedback Action. . . . . . . . . . . . . . . . . 9
3.3.4 Feedback Linkage.............................................9 3.3.2. Feedback Action List . . . . . . . . . . . . . . 10
3.3.5 Feedback Traffic Statistics Threshold.......................10 3.3.3. Feedback Linkage Capability. . . . . . . . . . . 10
4 The Feedback Framework PIB Module...............................10 3.3.4. Feedback Linkage . . . . . . . . . . . . . . . . 10
6 IANA Considerations.............................................29 3.3.5. Feedback Traffic Statistics Threshold. . . . . . 10
7 Acknowledgements................................................29 3.3.6. Feedback Traffic . . . . . . . . . . . . . . . . 10
8 Authors' Addresses..............................................29 3.3.7. Feedback Interface Traffic . . . . . . . . . . . 11
9 References......................................................30 3.3.8. Feedback RoleCombo Filter Selection. . . . . . . 11
9.1 Normative References..........................................30 4. The Feedback Framework PIB Module. . . . . . . . . . . . . . . 11
9.2 Informational References......................................31 5. Security Considerations. . . . . . . . . . . . . . . . . . . . 31
10 Copyright......................................................31 6. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 32
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1. Normative References . . . . . . . . . . . . . . . . . . 32
8.2. Informational References . . . . . . . . . . . . . . . . 33
9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 34
10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 35
Rawlins et al. Expires October 2003 [Page 2] 1. Introduction
1 Introduction The Framework of Common Open Policy Service with Policy Provisioning
(COPS-PR) Usage Feedback describes the overall approach to policy
usage monitoring and reporting. This document defines the specific
Policy Information Base (PIB) framework for policy usage feedback.
The policy classes for monitoring and reporting policy usage
feedback, as well as policy classes for controlling reporting
intervals, suspension, resumption and solicitation are defined.
The Framework of COPS-PR Usage Feedback describes the overall Conventions Used in this Document
approach to policy usage monitoring and reporting. This document
defines the specific Policy Information Base (PIB) framework for
policy usage feedback. The policy classes for monitoring and
reporting policy usage feedback as well as policy classes for
controlling reporting intervals, suspension, resumption and
solicitation are defined.
2 General Concepts The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2.1 Selection, Usage and Linkage Policies 2. General Concepts
There are three basic types of policy used to define what the PEP is 2.1. Selection, Usage and Linkage Policies
to monitor, record and report. These are the selection criteria
There are three basic types of policies used to define what the PEP
is to monitor, record and report. These are the selection criteria
policy, the usage policy and the feedback report linkage policy. 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
conditions used by the PEP to monitor and record a usage policy. The the conditions used by the PEP to monitor and record a usage policy.
selection criteria policy may only be used for defining usage The 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, a more general case is a
policy that already exists for policy enforcement may also be used policy that already exists for policy enforcement that may also be
for specifying feedback usage selection criteria. An example of this used for specifying feedback usage selection criteria. An example of
is the frwkRoleCombo instance, which may be used in defining QoS this is the frwkRoleCombo instance, which may be used in defining QoS
enforcement policies but may also be used to specify conditions on enforcement policies, but may also be used to specify conditions on
which to base usage - i.e. count the number of packets meeting the which to base usage - i.e. count the number of packets meeting the
criterion of an 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-only'. Generally, the These policies have an ACCESS clause of 'report-only'. Generally,
usage policies specify counts related to a specific action such as a the usage policies specify counts related to a specific action such
packet being dropped. The feedback framework PIB defines two usage as a packet being dropped. The feedback framework PIB defines two
policy classes, frwkFeedbackTraffic and frwkFeedbackIfTraffic. Usage usage policy classes, frwkFeedbackTraffic and frwkFeedbackIfTraffic.
PRCs may be generic, collecting basic statistics, or they may be Usage PRCs may be generic, collecting basic statistics, or they may
specific to a particular usage. The PDP decides which PRC(s) best be specific to a particular usage. The PDP decides which PRC(s) best
suit(s) its requirements. The PEP may support only one usage feedback suit(s) its requirements. The PEP may support only one usage
PRC, in which case all statistics are gathered using instances of feedback PRC, in which case all statistics are gathered using
that PRC. Alternatively, the PEP may support multiple usage feedback instances of that PRC. Alternatively, the PEP may support multiple
PRCs. The PDP then decides which PRC to associate with a particular usage feedback PRCs. The PDP then decides which PRC to associate
selection criterion. with a particular 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
usage feedback. The frwkFeedbackLinkTable entry permits the same the 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 October 2003 [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
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
installation of a feedback report linkage and the PEP designates the the installation of a feedback report linkage and the PEP designates
instance identifier. The usage feedback policy class always contains the instance identifier. The usage feedback policy class always
an attribute of type ReferenceId that contains the instance value of contains an attribute of type ReferenceId that contains the instance
the associated frwkFeedbackLinkTable instance installed by the PDP. value of the associated frwkFeedbackLinkTable instance installed by
An example of this is the attribute frwkFeedbackTrafficLinkRef the PDP. 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 [FEEDBACKfWK]. This is used as the basic unit described in [COPS] and [FEEDBACKFWK]. This is used as the basic
of measurement in defining intervals for specific usage policies with unit of measurement in defining intervals for specific usage policies
the frwkFeedbackLinkInterval attribute. 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 frwkPRCSupport instances [FR-PIB]. The PEP configuration data using frwkPRCSupport instances [FR-PIB]. The PEP
also indicates whether it supports the frwkFeedbackLinkTable as well. also indicates whether it supports the frwkFeedbackLinkTable 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
frwkFeedbackLink class. It may also specify reporting thresholds by frwkFeedbackLink class. It may also specify reporting thresholds by
including an instance of a threshold class (e.g. including an instance of a threshold class (e.g.
frwkFeedbackTrafficThreshold) in the decision. The PEP monitors and frwkFeedbackTrafficThreshold) in the decision. The PEP monitors 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 frwkFeedbackAction class. attribute of the frwkFeedbackAction class.
Rawlins et al. Expires October 2003 [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
in a periodic unsolicited report only if the threshold is reached a periodic unsolicited report only if the threshold is reached and/or
and/or if the usage value has changed from the previous reporting 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
reports that may not fall on an interval boundary. The PEP MUST that may not fall on an interval boundary. The PEP MUST provide an
provide an unsolicited REPORT containing all defined usage instances unsolicited REPORT containing all defined usage instances just prior
just prior to the PEP issuing a Delete Request State and just prior to the PEP issuing a Delete Request State and just prior to the PEP
to the PEP de-activating a PIB instance context. 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
frwkFeedbackLink instances. Supported conditions are: frwkFeedbackLink instances. Supported conditions are:
ChangeOnly ChangeOnly
If this flag is set in the frwkFeedbackLinkFlags attribute, 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
unsolicited report. report.
Threshold Threshold
If this flag is set in the frwkFeedbackLinkFlags attribute, 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
the frwkLinkThreshold field evaluates successfully for the frwkLinkThreshold field evaluates successfully for the associated
associated usage instance. 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 Decision containing the frwkFeedbackActionIndicator set to
'solicitReport'. 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 at the specified intervals established at client
client connection acceptance. connection acceptance.
Rawlins et al. Expires October 2003 [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 'suspendMonitoringAndReports'. The frwkFeedbackActionIndicator set to 'suspendMonitoringAndReports'.
PEP must stop tracking usage information and must not issue any The PEP must stop tracking usage information and must not issue any
feedback reports. The PDP may only suspend feedback reporting by feedback reports. The PDP may only suspend feedback reporting by
setting the ActionIndicator to 'suspendReports'. The PEP must cease setting the ActionIndicator to 'suspendReports'. The PEP must cease
sending unsolicited reports but is to continue monitoring and sending unsolicited reports but is to continue monitoring and
tracking usage. The PDP may resume the sending of feedback reports tracking usage. The PDP may resume the sending of feedback reports
and may resume usage monitoring by setting the ActionIndicator to and may resume usage monitoring by setting the ActionIndicator to
'resume'. '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 attribute contains a tag identifier that The frwkFeedbackActionList attribute contains a tag identifier that
references a list of one or more frwkFeedbackActionList instances. 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 that the connection is lost between the PEP and PDP, the
continues to track usage information as long as it continues to PEP 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 by issuing an COPS accounting type report messages. The PDP does this by issuing
unsolicited decision containing the frwkFeedbackResumeIndicator set an unsolicited decision containing the frwkFeedbackResumeIndicator
to 'resume'. The PEP should resume reporting at the next appropriate set to 'resume'. The PEP should resume reporting at the next
feedback interval established upon the acceptance of the re- appropriate feedback interval established upon the acceptance of the
connection. The PDP is aware of the request state Handle(s) and the re-connection. The PDP is aware of the request state Handle(s) and
supported PRCs either through the state synchronization mechanism or the supported PRCs either through the state synchronization mechanism
because the PDP considers itself synchronized with the PEP upon or because the PDP 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
templates for the objects created by the PEP. COPS-PR only has the for the objects created by the PEP. COPS-PR only has the identity
identity (OID) of the object that is shared between all the (OID) of the object that is shared between all the assignments the
assignments the PEP created, however it is desirable to collect PEP created. However it is desirable to collect usage information
usage information for each of the derived objects individually. 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 October 2003 [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 assignments. 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
each derived object. 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:
A frwkRoleCombo instance may be used as a selection criteria, A frwkRoleCombo instance may be used as a selection criteria,
identifying a set of interfaces through their the role identifying a set of interfaces through their role combination and
combination and capability set. If it is desired to get per- capability set. If it is desired to get per-interface traffic
interface traffic statistics, the usage PRC has to include an statistics, the usage PRC has to include an additional attribute
additional attribute to qualify the specific interface. to qualify the specific interface.
This could be achieved by linking the frwkFeedbackIfTraffic class This could be achieved by linking the frwkFeedbackIfTraffic class
with a frwkRoleCombo instance in a frwkFeedbackLink instance. with a frwkRoleCombo instance in a frwkFeedbackLink instance.
Multiple frwkFeedbackIfTraffic instances will be created by the Multiple frwkFeedbackIfTraffic instances will be created by the
PEP, one for each interface selected by the frwkRoleCombo PEP, one for each interface selected by the frwkRoleCombo
instance. The frwkFeedbackIfTraffic class contains the instance. The frwkFeedbackIfTraffic class contains the
frwkFeedbackIfTrafficIfIndex attribute that allows the PDP to frwkFeedbackIfTrafficIfIndex attribute that allows the PDP to
identify each interface's individual counters when the PEP identify each interface's individual counters when the PEP reports
reports the frwkFeedbackIfTraffic instances. the frwkFeedbackIfTraffic instances.
If traffic usage collection is only desired for an individual If traffic usage collection is only desired for an individual
interface, a selection criteria should be used that qualifies the interface, a selection criteria should be used that qualifies the
interface completely, for example a frwkIfRoleCombo instance. interface completely, for example a frwkIfRoleCombo instance. In
In this case it can be linked to the usage class that has no this case, it can be linked to the usage class that has no
additional qualifying attributes, frwkFeedbackTraffic. 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 Usage32 and Usage64 textual conventions 3.2. Usage32 and Usage64 Textual Conventions
Rawlins et al. Expires October 2003 [Page 7]
The SPPI does not support the Counter32/64 textual conventions (TC) The SPPI does not support the Counter32/64 textual conventions (TC)
of SNMP - for feedback collection two similar textual conventions of SNMP - for feedback collection two similar textual conventions
have been defined in this PIB: Usage32 and Usage64. have been defined in this PIB: Usage32 and Usage64.
In addition to the differential functionality of 'Counter', where In addition to the differential functionality of 'Counter', where
only the difference between two samples generally carries only the difference between two samples generally carries
information, a single value of a 'Usage' attribute usually provides information, a single value of a 'Usage' attribute usually provides
absolute information, since absolute information, since
- its initial value is known (0) - its initial value is known (0)
- no wrap-around events should occur - no wrap-around events should occur
- the time or event when the initial value was set should be - the time or event when the initial value was set should be
available directly or indirectly from other objects. available directly or indirectly from other objects.
When 'Usage' attributes are defined in a PRC, events that could When 'Usage' attributes are defined in a PRC, events that could cause
cause a reset of the attribute to it's initial value should be a reset of the attribute to its initial value should be defined in
defined in the description as well as the mechanism that allows the the description as well as the mechanism that allows the PDP to
PDP to detect the time of the last reset. detect the time of the last reset.
No usual COPS activity however should cause the reset of a Usage No usual COPS activity however should cause the reset of a Usage
attribute. In the case of a suspension of monitoring activity attribute. In the case of a suspension of monitoring activity
(frwkFeedbackActionIndicator set to 'suspendMonitoringAndReports'), (frwkFeedbackActionIndicator set to 'suspendMonitoringAndReports'),
'Usage' attributes should keep their values and continue counting 'Usage' attributes should keep their values and continue counting
after monitoring is resumed. after monitoring is resumed.
3.3 Feedback Groups and PRCs 3.3. Feedback Groups and PRCs
These policy classes defined in this PIB are common to account type 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 - Feedback Action
- Feedback Action List - Feedback Action List
- Feedback Selection Usage Combination Capability - Feedback Selection Usage Combination Capability
- Feedback Linkage - Feedback Linkage
- Feedback Traffic Statistics Threshold - Feedback Traffic Statistics Threshold
The policy classes in the Feedback Usage Group are: The policy classes in the Feedback Usage Group are:
- Feedback Traffic - Feedback Traffic
- Feedback Interface Traffic - Feedback Interface Traffic
The policy class in the Feedback Selection Group is: The policy class in the Feedback Selection Group is:
- Feedback RoleCombo Filter Selection
3.3.1 Feedback Action - Feedback RoleCombo Filter Selection
The Feedback Action class contains the attributes that specify 3.3.1. Feedback Action
action that the PEP is to take regarding policy usage, monitoring
and tracking. The PDP may suspend usage monitoring and periodic
reporting, suspend periodic reporting only, resume usage and
Rawlins et al. Expires October 2003 [Page 8] The Feedback Action class contains the attributes that specify action
periodic reporting or solicit immediate reporting. The action may that the PEP is to take regarding policy usage, monitoring and
affect all feedback policies or be associated with one or more tracking. The PDP may suspend usage monitoring and periodic
frwkFeedbackLink instances. reporting, suspend periodic reporting only, resume usage and periodic
reporting or solicit immediate reporting. The action may affect all
feedback policies or be associated with one or more frwkFeedbackLink
instances.
The frwkFeedbackActionIndicator attribute defines the action. The The frwkFeedbackActionIndicator attribute defines the action. The
frwkFeedbackActionPri attribute indicates whether the action applies frwkFeedbackActionPri attribute indicates whether the action applies
to all of the usage policies or to a list. The to all of the usage policies or to a list. The
frwkFeedbackActionList attribute is the identifier of the list of frwkFeedbackActionList attribute is the identifier of the list of
Linkage policy instances to which the action is to be 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
feedback. feedback.
The PDP can suspend the monitoring of usage policy. The PEP The PDP can suspend the monitoring of usage policy. The PEP
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
PDP directs the PEP to resume. The PEP then begins reporting the directs the PEP to resume. The PEP then begins reporting the usage
usage feedback at the next interval. feedback at the next interval.
3.3.2 Feedback Action List 3.3.2. Feedback Action List
This class defines sets of linkage instances that can be referred to This class defines sets of linkage instances that can be referred to
from the frwkFeedbackActionList attribute. from the frwkFeedbackActionList attribute.
3.3.3 Feedback Linkage Capability 3.3.3. Feedback Linkage Capability
This class defines the valid selection criteria PRC, usage PRC and This class defines the valid selection criteria PRC, usage PRC and
threshold PRC combinations supported by the PEP. threshold PRC combinations supported by the PEP.
3.3.4 Feedback Linkage 3.3.4. Feedback Linkage
This class links the selection criteria instance with the usage This class links the selection criteria instance with the usage
class. This table permits the reuse of a selection criteria instance class. This table permits the reuse of a selection criteria instance
for multiple usage policies. 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
Rawlins et al. Expires October 2003 [Page 9]
usage instance. A value of 0 in this attribute indicates that the usage instance. A value of 0 in this attribute indicates that the
usage policy must be solicited. usage policy must be solicited.
3.3.5 Feedback Traffic Statistics Threshold 3.3.5. Feedback Traffic Statistics Threshold
This class is used to provide threshold values for the attributes This class is used to provide threshold values for the attributes
described in the traffic usage classes below. described in the traffic usage classes below.
3.3.6 Feedback Traffic 3.3.6. Feedback Traffic
This class includes the packet counts, byte counts and a reference to This class includes the packet counts, byte counts and a reference to
the associated Linkage instance. the associated Linkage instance.
3.3.7 Feedback Interface Traffic 3.3.7. Feedback Interface Traffic
This class is similar to the previous Feedback Traffic class, except This class is similar to the previous Feedback Traffic class, except
that it includes an additional reference to an interface index. This that it includes an additional reference to an interface index. This
class should be used with a selection criteria instance that matches class should be used with a selection criteria instance that matches
an element that is assigned to multiple interfaces. The interface an element that is assigned to multiple interfaces. The interface
field can be used to associate the instances of this table with the field can be used to associate the instances of this table with the
specific element's assignment. specific element's assignment.
3.3.8 Feedback RoleCombo Filter Selection 3.3.8. Feedback RoleCombo Filter Selection
This class is used as selection criteria based on role combination, This class is used as selection criteria based on role combination,
capability set and a filter instance. capability set and a filter instance.
4 The Feedback Framework PIB Module 4. The Feedback Framework PIB Module
FRAMEWORK-FEEDBACK-PIB PIB-DEFINITIONS ::= BEGIN FRAMEWORK-FEEDBACK-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
pib, Unsigned32, Unsigned64, Integer32, pib, Unsigned32, Unsigned64, Integer32,
MODULE-IDENTITY, OBJECT-TYPE, MODULE-COMPLIANCE, OBJECT-GROUP 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, Prid, InstanceId, ReferenceId, Prid,
TagId, TagReferenceId TagId, TagReferenceId
FROM COPS-PR-SPPI-TC FROM COPS-PR-SPPI-TC
PrcIdentifierOid, PrcIdentifierOidOrZero PrcIdentifierOid, PrcIdentifierOidOrZero
FROM FRAMEWORK-TC-PIB FROM FRAMEWORK-TC-PIB
frwkRoleComboEntry frwkRoleComboEntry
FROM FRAMEWORK-PIB FROM FRAMEWORK-PIB
InterfaceIndex InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
Rawlins et al. Expires October 2003 [Page 10]
frwkFeedbackPib MODULE-IDENTITY frwkFeedbackPib MODULE-IDENTITY
SUBJECT-CATEGORIES { all } SUBJECT-CATEGORIES { all }
LAST-UPDATED "200304041400Z" LAST-UPDATED "200307140000Z" -- 14 July 2003
ORGANIZATION "IETF RAP WG" ORGANIZATION "IETF RAP WG"
CONTACT-INFO "IETF RAP WG CONTACT-INFO "IETF RAP WG
Email: rap@ops.ietf.org Email: rap@ops.ietf.org
Diana Rawlins Diana Rawlins
WorldCom MCI
901 International Parkway 400 International Parkway
Richardson, TX 75081 Richardson, Texas 75081
Phone: 972 729 1044 Phone: 972-729-4071
Email: diana.rawlins@wcom.com Email: Diana.Rawlins@mci.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. 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
Juniper 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
skipping to change at line 560 skipping to change at page 12, line 38
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"
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.
Copyright (C) The Internet Society (2003). This version Copyright (C) The Internet Society (2003). This version
of this PIB module is part of RFC xxxx; see the RFC of this PIB module is part of RFC 3571; see the RFC
itself for full legal notices." itself for full legal notices."
REVISION "200304041400Z" REVISION "200307140000Z"
DESCRIPTION DESCRIPTION
"Initial version, published in RFC xxxx." "Initial version, published in RFC 3571."
Rawlins et al. Expires October 2003 [Page 11]
-- xxxx to be assigned by RFC editor
::= { pib xx } -- xx will be assigned by IANA, according ::= { pib 5 }
-- to RFC 3159 (IANA considerations)
-- --
-- Textual Conventions -- Textual Conventions
-- --
Usage32 ::= TEXTUAL-CONVENTION Usage32 ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Usage32 type represents a non-negative integer "The Usage32 type represents a non-negative integer
which monotonically increases. which monotonically increases.
skipping to change at line 621 skipping to change at page 13, line 47
DESCRIPTION DESCRIPTION
"The Usage64 type represents a non-negative integer "The Usage64 type represents a non-negative integer
which monotonically increases. which monotonically increases.
Usage64 initial value is 0 and the object-type using Usage64 initial value is 0 and the object-type using
Usage64 needs to specify when it is initialized. Usage64 needs to specify when it is initialized.
The Usage64 type is intended to reflect the absolute The Usage64 type is intended to reflect the absolute
number of counted events, so that even a new PDP number of counted events, so that even a new PDP
after a COPS reconnect can use the value directly. after a COPS reconnect can use the value directly.
Rawlins et al. Expires October 2003 [Page 12]
The lifetime of the Usage64 object should be defined The lifetime of the Usage64 object should be defined
in a way that ensures the maximum Usage64 value of in a way that ensures the maximum Usage64 value of
2^64-1 is never exceeded. 2^64-1 is never exceeded.
If conditions other than the reset of the COPS If conditions other than the reset of the COPS
subsystem exist that disrupt the monotonic subsystem exist that disrupt the monotonic
characteristics of Usage64, these conditions and a characteristics of Usage64, these conditions and a
method how to detect their presence should be method how to detect their presence should be
specified in the description of the object-type using specified in the description of the object-type using
Usage64 or its enclosing object-types (e.g. the Usage64 or its enclosing object-types (e.g. the
skipping to change at line 674 skipping to change at page 15, line 4
frwkFeedbackActionEntry OBJECT-TYPE frwkFeedbackActionEntry OBJECT-TYPE
SYNTAX FrwkFeedbackActionEntry SYNTAX FrwkFeedbackActionEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each frwkFeedbackActionEntry represents a command from "Each frwkFeedbackActionEntry represents a command from
the PDP. FrwkFeedbackActionIndicator specifies the the PDP. FrwkFeedbackActionIndicator specifies the
command itself while frwkFeedbackActionSpecificPri command itself while frwkFeedbackActionSpecificPri
indicates if all frwkFeedbackLink objects in the system indicates if all frwkFeedbackLink objects in the system
are affected by the command, or just the set that is are affected by the command, or just the set that is
referenced by frwkFeedbackActionList." referenced by frwkFeedbackActionList."
Rawlins et al. Expires October 2003 [Page 13]
PIB-INDEX { frwkFeedbackActionId} PIB-INDEX { frwkFeedbackActionId}
::= { frwkFeedbackActionTable 1} ::= { frwkFeedbackActionTable 1}
FrwkFeedbackActionEntry ::= SEQUENCE { FrwkFeedbackActionEntry ::= SEQUENCE {
frwkFeedbackActionId InstanceId, frwkFeedbackActionId InstanceId,
frwkFeedbackActionIndicator INTEGER, frwkFeedbackActionIndicator INTEGER,
frwkFeedbackActionSpecificPri TruthValue, frwkFeedbackActionSpecificPri TruthValue,
frwkFeedbackActionList TagReferenceId frwkFeedbackActionList TagReferenceId
} }
skipping to change at line 698 skipping to change at page 15, line 26
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 frwkFeedbackAction class." instance of the frwkFeedbackAction class."
::= { frwkFeedbackActionEntry 1} ::= { frwkFeedbackActionEntry 1}
frwkFeedbackActionIndicator OBJECT-TYPE frwkFeedbackActionIndicator OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
suspendMonitoringAndReports(0), suspendMonitoringAndReports(1),
suspendReports(1), suspendReports(2),
resume(2), resume(3),
solicitReport(3) solicitReport(4)
} }
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) suspendMonitoringAndReports (1) suspendMonitoringAndReports
(1) suspendReports (2) suspendReports
(2) resume (3) resume
(3) solicitReport " (4) 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 ignored, frwkFeedbackActionList attribute should be ignored,
and the action applied to all policies. A value of and the action applied to all policies. A value of
1 indicates that the action entry has a specific 1 indicates that the action entry has a specific
list of policies to which it is to be applied." list of policies to which it is to be applied."
::= { frwkFeedbackActionEntry 3} ::= { frwkFeedbackActionEntry 3}
frwkFeedbackActionList OBJECT-TYPE frwkFeedbackActionList OBJECT-TYPE
SYNTAX TagReferenceId SYNTAX TagReferenceId
Rawlins et al. Expires October 2003 [Page 14]
PIB-TAG { frwkFeedbackActionListTag } PIB-TAG { frwkFeedbackActionListTag }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a group of frwkFeedbackLink instances "Identifies a group of frwkFeedbackLink instances
that this action should affect. The group is that this action should affect. The group is
identified through a tag reference in the identified through a tag reference in the
frwkFeedbackList class." frwkFeedbackList class."
::= { frwkFeedbackActionEntry 4} ::= { frwkFeedbackActionEntry 4}
-- --
skipping to change at line 784 skipping to change at page 17, line 14
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."
Rawlins et al. Expires October 2003 [Page 15]
::= { frwkFeedbackActionListEntry 1 } ::= { frwkFeedbackActionListEntry 1 }
frwkFeedbackActionListTag OBJECT-TYPE frwkFeedbackActionListTag OBJECT-TYPE
SYNTAX TagId SYNTAX TagId
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies a group of linkage instances that can "Identifies a group of linkage instances that can
be referenced from the Action class." be referenced from the Action class."
::= { frwkFeedbackActionListEntry 2 } ::= { frwkFeedbackActionListEntry 2 }
skipping to change at line 838 skipping to change at page 18, line 18
"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 classes for feedback." threshold classes for feedback."
PIB-INDEX { frwkFeedbackLinkCapsId } PIB-INDEX { frwkFeedbackLinkCapsId }
UNIQUENESS { UNIQUENESS {
frwkFeedbackLinkCapsSelection, frwkFeedbackLinkCapsSelection,
frwkFeedbackLinkCapsUsage, frwkFeedbackLinkCapsUsage,
frwkFeedbackLinkCapsThreshold frwkFeedbackLinkCapsThreshold
} }
Rawlins et al. Expires October 2003 [Page 16]
::= {frwkFeedbackLinkCapsTable 1} ::= {frwkFeedbackLinkCapsTable 1}
FrwkFeedbackLinkCapsEntry ::= SEQUENCE { FrwkFeedbackLinkCapsEntry ::= SEQUENCE {
frwkFeedbackLinkCapsId InstanceId, frwkFeedbackLinkCapsId InstanceId,
frwkFeedbackLinkCapsSelection PrcIdentifierOid, frwkFeedbackLinkCapsSelection PrcIdentifierOid,
frwkFeedbackLinkCapsUsage PrcIdentifierOid, frwkFeedbackLinkCapsUsage PrcIdentifierOid,
frwkFeedbackLinkCapsThreshold PrcIdentifierOidOrZero frwkFeedbackLinkCapsThreshold PrcIdentifierOidOrZero
} }
frwkFeedbackLinkCapsId OBJECT-TYPE frwkFeedbackLinkCapsId OBJECT-TYPE
skipping to change at line 891 skipping to change at page 19, line 22
and usage classes referenced in this instance. and usage classes referenced in this instance.
0.0 is used if this combination does not allow a 0.0 is used if this combination does not allow a
threshold." threshold."
::= { frwkFeedbackLinkCapsEntry 4} ::= { frwkFeedbackLinkCapsEntry 4}
-- --
-- The Feedback Report Linkage Table -- The Feedback Report Linkage Table
-- --
frwkFeedbackLinkTable OBJECT-TYPE frwkFeedbackLinkTable OBJECT-TYPE
Rawlins et al. Expires October 2003 [Page 17]
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."
::= { frwkFeedbackGroupClasses 4} ::= { frwkFeedbackGroupClasses 4}
skipping to change at line 946 skipping to change at page 20, line 28
"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 PrcIdentifierOid SYNTAX PrcIdentifierOid
STATUS current STATUS current
Rawlins et al. Expires October 2003 [Page 18]
DESCRIPTION DESCRIPTION
"The identifier of the usage 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at line 1000 skipping to change at page 21, line 32
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}
Rawlins et al. Expires October 2003 [Page 19]
-- --
-- The Threshold class that accompanies the above Usage PRCs -- The Threshold class that accompanies the above Usage PRCs
-- --
frwkFeedbackTrafficThresTable OBJECT-TYPE frwkFeedbackTrafficThresTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresEntry SYNTAX SEQUENCE OF FrwkFeedbackTrafficThresEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class defines the threshold attributes "This class defines the threshold attributes
skipping to change at line 1053 skipping to change at page 22, line 36
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."
::= { frwkFeedbackTrafficThresEntry 1 } ::= { frwkFeedbackTrafficThresEntry 1 }
frwkFeedbackTrafficThresPackets OBJECT-TYPE frwkFeedbackTrafficThresPackets OBJECT-TYPE
SYNTAX Unsigned64 SYNTAX Unsigned64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Rawlins et al. Expires October 2003 [Page 20]
"The threshold, in terms of packets, that must be "The threshold, in terms of packets, that must be
matched or exceeded to trigger a report in the matched or exceeded to trigger a report in the
next reporting interval. next reporting interval."
A value of 0 or a missing value ("
::= { frwkFeedbackTrafficThresEntry 2 } ::= { frwkFeedbackTrafficThresEntry 2 }
frwkFeedbackTrafficThresBytes OBJECT-TYPE frwkFeedbackTrafficThresBytes OBJECT-TYPE
SYNTAX Unsigned64 SYNTAX Unsigned64
STATUS current STATUS current
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 reporting exceeded to trigger a report in the next reporting
interval." interval."
::= { frwkFeedbackTrafficThresEntry 3 } ::= { frwkFeedbackTrafficThresEntry 3 }
skipping to change at line 1107 skipping to change at page 23, line 40
SYNTAX FrwkFeedbackTrafficEntry 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 {frwkFeedbackTrafficId} PIB-INDEX {frwkFeedbackTrafficId}
UNIQUENESS { frwkFeedbackTrafficLinkRefID } UNIQUENESS { frwkFeedbackTrafficLinkRefID }
::= {frwkFeedbackTrafficTable 1} ::= {frwkFeedbackTrafficTable 1}
Rawlins et al. Expires October 2003 [Page 21]
FrwkFeedbackTrafficEntry ::= SEQUENCE { FrwkFeedbackTrafficEntry ::= SEQUENCE {
frwkFeedbackTrafficId InstanceId, frwkFeedbackTrafficId InstanceId,
frwkFeedbackTrafficLinkRefID ReferenceId, frwkFeedbackTrafficLinkRefID ReferenceId,
frwkFeedbackTrafficPacketCount Usage64, frwkFeedbackTrafficPacketCount Usage64,
frwkFeedbackTrafficByteCount Usage64 frwkFeedbackTrafficByteCount Usage64
} }
frwkFeedbackTrafficId OBJECT-TYPE frwkFeedbackTrafficId OBJECT-TYPE
SYNTAX InstanceId SYNTAX InstanceId
skipping to change at line 1158 skipping to change at page 24, line 43
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. The initial value of 0 is set when the element. The initial value of 0 is set when the
frwkFeedbackTraffic instance is created." frwkFeedbackTraffic instance is created."
::= { frwkFeedbackTrafficEntry 4} ::= { frwkFeedbackTrafficEntry 4}
-- --
-- The traffic usage class, qualified for an interface -- The traffic usage class, qualified for an interface
-- --
Rawlins et al. Expires October 2003 [Page 22]
frwkFeedbackIfTrafficTable OBJECT-TYPE frwkFeedbackIfTrafficTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficEntry SYNTAX SEQUENCE OF FrwkFeedbackIfTrafficEntry
PIB-ACCESS report-only PIB-ACCESS report-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A usage class similar to the basic Traffic class that "A usage class similar to the basic Traffic class that
also contains a reference to an interface index. This also contains a reference to an interface index. This
class should be used with a underspecified selection class should be used with an underspecified selection
criteria entry from the frwkRoleComboTable that matches criteria entry from the frwkRoleComboTable that matches
an element that can be assigned to multiple interface an element that can be assigned to multiple interface
indices. The interface field can be used to associate indices. The interface field can be used to associate
the instances of this class with the specific element's the instances of this class with the specific element's
assignment." assignment."
::= { frwkFeedbackUsageClasses 2 } ::= { frwkFeedbackUsageClasses 2 }
frwkFeedbackIfTrafficEntry OBJECT-TYPE frwkFeedbackIfTrafficEntry OBJECT-TYPE
SYNTAX FrwkFeedbackIfTrafficEntry SYNTAX FrwkFeedbackIfTrafficEntry
STATUS current STATUS current
skipping to change at line 1213 skipping to change at page 25, line 50
frwkFeedbackIfTrafficLinkRefID 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."
::= { frwkFeedbackIfTrafficEntry 2 } ::= { frwkFeedbackIfTrafficEntry 2 }
Rawlins et al. Expires October 2003 [Page 23]
frwkFeedbackIfTrafficIfIndex 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."
::= { frwkFeedbackIfTrafficEntry 3 } ::= { frwkFeedbackIfTrafficEntry 3 }
skipping to change at line 1263 skipping to change at page 27, line 4
frwkFeedbackRoleFilterSelTable OBJECT-TYPE frwkFeedbackRoleFilterSelTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkFeedbackRoleFilterSelEntry SYNTAX SEQUENCE OF FrwkFeedbackRoleFilterSelEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A selection class that defines selection of objects "A selection class that defines selection of objects
for monitoring based on the role combination, for monitoring based on the role combination,
capability set and a filter." capability set and a filter."
::= { frwkFeedbackSelectionClasses 1 } ::= { frwkFeedbackSelectionClasses 1 }
Rawlins et al. Expires October 2003 [Page 24]
frwkFeedbackRoleFilterSelEntry OBJECT-TYPE frwkFeedbackRoleFilterSelEntry OBJECT-TYPE
SYNTAX FrwkFeedbackRoleFilterSelEntry SYNTAX FrwkFeedbackRoleFilterSelEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each instance selects a filter on multiple interfaces "Each instance selects a filter on multiple interfaces
that share the same frwkRoleCombo instance." that share the same frwkRoleCombo instance."
PIB-INDEX { frwkFeedbackRoleFilterSelId} PIB-INDEX { frwkFeedbackRoleFilterSelId}
UNIQUENESS { frwkFeedbackRoleFilterSelRCombo, UNIQUENESS { frwkFeedbackRoleFilterSelRCombo,
frwkFeedbackRoleFilterSelFilter frwkFeedbackRoleFilterSelFilter
} }
skipping to change at line 1311 skipping to change at page 28, line 4
frwkFeedbackRoleFilterSelFilter OBJECT-TYPE frwkFeedbackRoleFilterSelFilter OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The identifier of a filter instance. Valid classes "The identifier of a filter instance. Valid classes
are the subclasses of frwkBaseFilter: are the subclasses of frwkBaseFilter:
- frwkIpFilter - frwkIpFilter
- frwk802Filter - frwk802Filter
- frwkILabelFilter" - frwkILabelFilter"
::= { frwkFeedbackRoleFilterSelEntry 3 } ::= { frwkFeedbackRoleFilterSelEntry 3 }
-- --
-- Compliance Section -- Compliance Section
-- --
frwkFeedbackPibConformance frwkFeedbackPibConformance
Rawlins et al. Expires October 2003 [Page 25]
OBJECT IDENTIFIER ::= { frwkFeedbackPib 4 } OBJECT IDENTIFIER ::= { frwkFeedbackPib 4 }
frwkFeedbackPibCompliances frwkFeedbackPibCompliances
OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 1 } OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 1 }
frwkFeedbackPibGroups frwkFeedbackPibGroups
OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 2 } OBJECT IDENTIFIER ::= { frwkFeedbackPibConformance 2 }
frwkFeedbackPibCompliance MODULE-COMPLIANCE frwkFeedbackPibCompliance MODULE-COMPLIANCE
STATUS current STATUS current
skipping to change at line 1371 skipping to change at page 29, line 14
GROUP frwkFeedbackRoleFilterSelGroup GROUP frwkFeedbackRoleFilterSelGroup
DESCRIPTION DESCRIPTION
"The frwkFeedbackRoleFilterSelGroup is mandatory "The frwkFeedbackRoleFilterSelGroup is mandatory
if monitoring of filters referenced through the if monitoring of filters referenced through the
frwkRoleCombo class is to be supported." frwkRoleCombo class is to be supported."
::= { frwkFeedbackPibCompliances 1 } ::= { frwkFeedbackPibCompliances 1 }
frwkFeedbackLinkCapsGroup OBJECT-GROUP frwkFeedbackLinkCapsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
Rawlins et al. Expires October 2003 [Page 26]
frwkFeedbackLinkCapsId, frwkFeedbackLinkCapsId,
frwkFeedbackLinkCapsSelection, frwkFeedbackLinkCapsSelection,
frwkFeedbackLinkCapsUsage, frwkFeedbackLinkCapsUsage,
frwkFeedbackLinkCapsThreshold } frwkFeedbackLinkCapsThreshold }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkFeedbackLinkCapsTable." "Objects from the frwkFeedbackLinkCapsTable."
::= { frwkFeedbackPibGroups 1 } ::= { frwkFeedbackPibGroups 1 }
skipping to change at line 1426 skipping to change at page 30, line 19
"Objects from the frwkFeedbackActionListTable." "Objects from the frwkFeedbackActionListTable."
::= { frwkFeedbackPibGroups 4 } ::= { frwkFeedbackPibGroups 4 }
frwkFeedbackTrafficGroup OBJECT-GROUP frwkFeedbackTrafficGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkFeedbackTrafficId, frwkFeedbackTrafficId,
frwkFeedbackTrafficLinkRefID, frwkFeedbackTrafficLinkRefID,
frwkFeedbackTrafficPacketCount, frwkFeedbackTrafficPacketCount,
frwkFeedbackTrafficByteCount } frwkFeedbackTrafficByteCount }
Rawlins et al. Expires October 2003 [Page 27]
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkFeedbackTrafficTable." "Objects from the frwkFeedbackTrafficTable."
::= { frwkFeedbackPibGroups 5 } ::= { frwkFeedbackPibGroups 5 }
frwkFeedbackTrafficThresGroup OBJECT-GROUP frwkFeedbackTrafficThresGroup OBJECT-GROUP
OBJECTS { OBJECTS {
frwkFeedbackTrafficThresId, frwkFeedbackTrafficThresId,
frwkFeedbackTrafficThresPackets, frwkFeedbackTrafficThresPackets,
skipping to change at line 1471 skipping to change at page 31, line 14
frwkFeedbackRoleFilterSelRCombo, frwkFeedbackRoleFilterSelRCombo,
frwkFeedbackRoleFilterSelFilter } frwkFeedbackRoleFilterSelFilter }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects from the frwkFeedbackRoleFilterSelTable." "Objects from the frwkFeedbackRoleFilterSelTable."
::= { frwkFeedbackPibGroups 8 } ::= { frwkFeedbackPibGroups 8 }
END END
5 Security Considerations 5. Security Considerations
This PIB defines structured information that may be sensitive when This PIB defines structured information that may be sensitive when
transported by the COPS protocol [COPS-PR]. transported by the COPS protocol [COPS-PR].
This PIB does not contain classes that directly contain security This PIB does not contain classes that directly contain security
relevant information like passwords or monetary amounts, however relevant information like passwords or monetary amounts. However,
unauthorized access or changes to information defined in this PIB unauthorized access or changes to information defined in this PIB
Rawlins et al. Expires October 2003 [Page 28]
could compromise network operations or reveal sensitive business or could compromise network operations or reveal sensitive business or
personal information. personal information.
Specifically for the classes: Specifically for the classes:
frwkFeedbackLinkCaps frwkFeedbackLinkCaps
This class has the ACCESS clause 'notify'. Access to this This class has the ACCESS clause 'notify'. Access to this
information reveals feedback collection capabilities of the COPS information reveals feedback collection capabilities of the COPS
client and malicious changes could affect feedback operation by client and malicious changes could affect feedback operation by
misleading the server to generate corrupt feedback configuration. misleading the server to generate corrupt feedback configuration.
frwkFeedbackLinkTable, frwkFeedbackAction, frwkFeedbackActionList, frwkFeedbackLinkTable, frwkFeedbackAction, frwkFeedbackActionList,
frwkFeedbackTrafficThres, frwkFeedbackRoleFilterSel frwkFeedbackTrafficThres, frwkFeedbackRoleFilterSel
These classes have the ACCESS clause 'install' and allow the COPS These classes have the ACCESS clause 'install' and allow the COPS
server to control feedback collection and reporting on the server to control feedback collection and reporting on the client.
client. Access to this information exposes the client's Access to this information exposes the client's configuration;
configuration, malicious changes could disrupt network or malicious changes could disrupt network or business operations and
business operations and raise privacy issues. raise privacy issues.
frwkFeedbackTraffic, frwkFeedbackIfTraffic frwkFeedbackTraffic, frwkFeedbackIfTraffic
These classed have the ACCESS clause 'report-only' and contain
the usage information delivered from the COPS client to the These classes have the ACCESS clause 'report-only' and contain the
server. Unauthorized access to this information may reveal usage information delivered from the COPS client to the server.
detailed information on the network and its users. Malicious Unauthorized access to this information may reveal detailed
changes may affect network and business operations. 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 [COPS] and [COPS-PR] define mechanisms to secure the COPS protocol
communication and implementations of COPS servers or clients communication and implementations of COPS servers or clients
supporting this PIB MUST follow the security guidelines specified supporting this PIB MUST follow the security guidelines specified
there. there.
6 IANA Considerations 6. IANA Considerations
This document describes the frwkFeedbackPib Policy Information Base This document describes the frwkFeedbackPib Policy Information Base
(PIB) module for registration under the "pib" branch registered with (PIB) module for registration under the "pib" branch registered with
IANA. The IANA has assigned PIB number TBD. IANA. The IANA has assigned PIB number 5.
This PIB uses "all" in the SUBJECT-CATEGORY clause, so it applies to 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 all COPS client types. No new COPS client type is requested for this
PIB. PIB.
7 Acknowledgements 7. Acknowledgements
The authors would like to thank Dave Durham and Russell Fenger of The authors would like to thank Dave Durham, Ravi Sahita, and Russell
Intel and John K. Gallant of WorldCom for their contribution to this Fenger of Intel and John K. Gallant of WorldCom for their
document. contribution to this document.
8 Authors' Addresses 8. References
8.1. Normative References
[COPS] Durham, D., Boyle, J., Cohen, R., Herzog, S., Rajan,
R. and A. Sastry, "The COPS (Common Open Policy
Service) Protocol", RFC 2748, January 2000.
[COPS-PR] Chan, K., Seligson, J., Durham, D., Gai, S.,
McCloghrie, K., Herzog, S., Reichmeyer, F., Yavatkar,
R. and A. Smith, "COPS Usage for Policy
Provisioning", RFC 3084, May 2001.
[IFMIB] McCloghrie, K. and F. Kastenholz, "The Interfaces
Group MIB", RFC 2863, June 2000.
[FR-PIB] Sahita, R., Hahn, S., Chan, K. and K. McCloghrie,
"Framework Policy Information Base", RFC 3318, March
2003.
[FEEDBACKFWK] Rawlins, D., Kulkarni, A., Bokaemper, M. and K. Chan,
"Framework for Policy Usage Feedback for Common Open
Policy Service with Policy Provisioning (COPS-PR)",
RFC 3483, March 2003.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
8.2. Informational References
[COPS-TLS], Walker, J., Kulkarni, A.,"COPS Over TLS", Work in
Progress.
[DIFFSERV-PIB] Chan, K., Sahita, R., Hahn, S. and K. McCloghrie,
"Differentiated Services Quality of Service Policy
Information Base", RFC 3317, March 2003.
9. Authors' Addresses
Diana Rawlins Diana Rawlins
WorldCom MCI
901 International Parkway 400 International Parkway
Richardson, Texas 75081 Richardson, Texas 75081
Phone: 972-729-1044
Rawlins et al. Expires October 2003 [Page 29] Phone: 972-729-4071
Email: Diana.Rawlins@wcom.com EMail: Diana.Rawlins@mci.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 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
Juniper 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@juniper.net 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
Email: ddutt@cisco.com
9 References
9.1 Normative References
[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R.,
and A. Sastry, "The COPS (Common Open Policy Service) Protocol",
RFC 2748, January 2000.
[COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F.
Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for
Policy Provisioning", RFC 3084, May 2001.
[SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning
Information", RFC 3159, August 2001.
[SMI2] K. McCloghrie, et.al., "Structure of Management Information
Version 2 (SMIv2)", RFC 2587, April 1999
[IFMIB] K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB", Phone: 408-527-0955
RFC 2863, June 2000 EMail: ddutt@cisco.com
Rawlins et al. Expires October 2003 [Page 30]
[FR-PIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Hahn, A.
Smith, F. Reichmeyer "Framework Policy Information Base", RFC
3318, March 2003
[FEEDBACKfWK] D. Rawlins, A. Kulkarni, K. Chan, M. Bokaemper, D.
Dutt, "Framework for Policy Usage Feedback for Common Open Policy
Service with Policy Provisioning (COPS-PR)", RFC 3483, March 2003.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
9.2 Informational References
[COPS-TLS], Walker, J., Kulkarni, A.,"COPS Over TLS", draft-ietf-
rap-cops-tls-05.txt, February 2003.
[DIFFSERV-PIB] Fine, M., McCloghrie, K., Seligson, J., Chan, K.,
Hahn, S., Bell, C., Smith, A. and Reichmeyer, A. "Differentiated
Services Quality of Service Policy Information Base", RFC 3317,
March 2003
10 Copyright 10. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph are
are included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Rawlins et al. Expires October 2003 [Page 31] Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

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