draft-ietf-rap-acct-fr-pib-00.txt   draft-ietf-rap-acct-fr-pib-01.txt 
Internet Draft Diana Rawlins Internet Draft Diana Rawlins
Expiration: May 2001 WorldCom Expiration: March 2001 WorldCom
File: draft-ietf-rap-acct-fr-pib-00.txt Amol Kulkarni File: draft-ietf-rap-acct-fr-pib-01.txt Amol Kulkarni
Intel Intel
Kwok Ho Chan Kwok Ho Chan
Nortel Networks Nortel Networks
Dinesh Dutt Dinesh Dutt
Cisco Cisco
Framework of COPS-PR Policy Information Base for Accounting Usage Framework of COPS-PR Policy Information Base for Accounting Usage
Status of this Memo Last Updated March 2 2001
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.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
skipping to change at page 1, line 37 skipping to change at page 1, line 38
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC-2119]. [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 accounting framework PIB that specifies document is to define the accounting framework PIB that specifies the
the policy classes common for COPS accounting type reports. The policy classes common for COPS accounting type reports. The basic
basic operation and objects for reporting usage information are operation and objects for reporting usage information are defined in
defined in [COPS]. A specific clientSI accounting type object named [COPS]. A specific clientSI accounting type object named REPORT is
REPORT is defined in [COPS-PR]. This document further describes defined in [COPS-PR]. This document further describes operational
operational behavior that is implied in [COPS] and [COPS-PR.] behavior that is implied in [COPS] and [COPS-PR.]
Table Of Contents Table Of Contents
1 Introduction.....................................................3 1 Introduction.....................................................3
2 General Concepts.................................................3 2 General Concepts.................................................3
2.1 Overview.......................................................3 2.1 Overview.......................................................3
2.2 Normal Operation...............................................3 2.2 Normal Operation...............................................3
2.3 Failover.......................................................4 2.3 Failover.......................................................4
2.4 Context........................................................4 2.4 Context........................................................4
2.5 Delete Request States..........................................4 2.5 Delete Request States..........................................4
2.6 Periodic nature of report accounting...........................5 2.6 Periodic nature of report accounting...........................4
3 Definition of Accounting Type Report Policy......................5 3 Definition of Accounting Type Report Policy......................5
4 Summary of the Accounting Framework Policy Information Base......6 4 Summary of the Accounting Framework Policy Information Base......6
4.1 SPPI ACCESS clause Report......................................6 4.1 SPPI ACCESS clause report-only.................................6
4.2 Textual Conventions Counts.....................................7 4.2 Textual Conventions Counts.....................................6
4.3 Accounting Type Report Group and PRCs..........................7 4.3 Accounting Type Report Group and PRCs..........................6
4.3.1 The Accounting Type Report Device Table......................7 4.3.1 The Accounting Type Report Resume Table......................7
4.3.2 The Accounting Type Report Resume Table......................7 4.3.2 The Accounting Type Report Linkage Table.....................7
4.3.3 The Accounting Type Report Linkage Table.....................7 4.3.3 The Filter Usage Table.......................................7
4.3.4 The Filter Usage Table.......................................7 5 The Accounting Framework PIB Module..............................7
5 The Accounting Framework PIB Module..............................8 6 Security Considerations.........................................13
6 Security Considerations.........................................14 7 Acknowledgements................................................13
7 Acknowledgements................................................14 8 Authors' Addresses..............................................13
8 Authors' Addresses..............................................14 9 References......................................................13
9 References......................................................15
1 Introduction 1 Introduction
Policy usage reported by the PEP makes a richer set of information Policy usage reported by the PEP makes a richer set of information
available to the PDP for decision-making. This report accounting available to the PDP for decision-making. This report accounting
information can influence future decisions made by the PDP and the information can influence future decisions made by the PDP and the
resulting policy installed by the PDP at the PEP. For example, A PDP resulting policy installed by the PDP at the PEP. For example, A PDP
determining policy for a SIP signaled multimedia session may need to determining policy for a SIP signaled multimedia session may need to
base the decision in part on usage information related to previously base the decision in part on usage information related to previously
installed QoS policy decisions. Further, the PDP may coordinate this installed QoS policy decisions. Further, the PDP may coordinate this
usage information with other external systems to determine the usage information with other external systems to determine the future
future policy such as the case with the PDP coordinating multimedia policy such as the case with the PDP coordinating multimedia session
session QoS and clearinghouse authorizations [SIP-AAA-QOS] QoS and clearinghouse authorizations [SIP-AAA-QOS]
The scope of this document is to describe the policy class framework The scope of this document is to describe the policy class framework
for policy usage monitored and reported by the PEP and collected at for policy usage monitored and reported by the PEP and collected at
the PDP. The charging and billing models as well as other accounting the PDP. The charging and billing models as well as other accounting
events detectable by the PDP are beyond the scope of this framework. events detectable by the PDP are beyond the scope of this framework.
2 General Concepts 2 General Concepts
2.1 Overview 2.1 Overview
There are two aspects to defining policies for an accounting type There are two aspects to defining policies for an accounting type
report ū the "who" aspect and the "what" aspect. The "who" is report “ the selection aspect and the policy usage aspect. The
referred to generically as the selection criteria policy class. The
"what" is referred to generically as the usage policy class. The
usage policy and selection policy are associated with one another. usage policy and selection policy are associated with one another.
The usage criteria policy class defines what is monitored, recorded The usage criteria policy class defines what metrics are monitored,
and reported by the PEP. The selection criteria policy class recorded and reported by the PEP. The selection criteria policy class
specifies the conditions for the monitoring and recording of the specifies the conditions for the monitoring and recording of the
associated usage policy. For example, a usage policy may be defined associated usage policy. For example, a usage policy may be defined
to provide counts of packets received. The selection criteria policy to provide counts of packets received. The selection criteria policy
may identify the filter on which to base the packet counts. A third may identify the filter on which to base the packet counts. A third
policy associates, or links, the selection and usage policies. This policy may be used to associate, or link, the selection and usage
is the accounting type report linkage policy. policies. The linking is performed by the accounting type report
linkage policy.
2.2 Normal Operation 2.2 Normal Operation
The PDP specifies the minimum accounting interval in the Accounting The PDP specifies the minimum accounting interval in the Accounting
Timer object that is included in the Client Accept message during Timer object that is included in the Client Accept message during
connection establishment. This specifies the frequency with which connection establishment. This specifies the maximum frequency with
the PEP issues unsolicited accounting type reports. The PEP notifies which the PEP issues unsolicited accounting type reports. The PEP
the PDP of the maximum reporting interval as well as the selection notifies the PDP of the selection criteria policy classes and usage
criteria policy classes and usage policy classes it supports during policy classes it supports during the initial request for
the initial request for configuration data. configuration data using the frwkPRCSupportTable entries[FR-PIB].
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. The PEP monitors and records the usage per the reporting intervals associated with each of the policies. The PEP
selection criteria defined by the PDP. Periodically the PEP reports monitors and records the usage per the selection criteria defined by
the usage with an accounting type REPORT. The interval of the the PDP. Periodically the PEP reports the usage with an accounting
reporting may be defined for the policy instance as long as the type REPORT.
interval does not conflict with the intervals specified in the
Client Accept or device reporting limitations.
While it is not anticipated, if the volume of the usage policy
instances for an accounting type report exceeds the maximum message
size, multiple report messages containing the usage policy instances
are constructed and issued to the PDP for that accounting interval.
The Report-Type Object has a new parameter, Continuation Flag. This
4-bit element is set to 0x1 to indicate additional report messages
are immediately following and contain information related to the
current report. The last accounting type report message in the
series for this particular accounting interval clears the
Continuation Flag.
The PDP is the collection point for the usage information monitored The PDP is the collection point for the usage information monitored
and reported by the PEP clients within the administrative domain. and reported by the PEP clients within the administrative domain. The
The PDP may also collect other accounting event information that is PDP may also collect other accounting event information that is
outside the scope of this document. outside the scope of this document.
2.3 Failover 2.3 Failover
In the event the connection is lost between the PEP and PDP, the PEP In the event the connection is lost between the PEP and PDP, the PEP
continues to track usage information as long as it continues to continues to track usage information as long as it continues to
operate with the installed policy. When the locally installed policy operate with the installed policy. When the locally installed policy
at the PEP expires, the usage policy data also expires. at the PEP expires, the usage policy data also expires.
Upon successful reconnection where the PEP is still caching policy, Upon successful reconnection where the PEP is still caching policy,
the PDP indicates to the PEP that the PEP may resume sending of the the PDP indicates to the PEP that the PEP may resume sending of the
accounting type report messages. The PDP does this accounting type report messages. The PDP does this deterministically.
deterministically. It issues an unsolicited decision containing the It issues an unsolicited decision containing the
frwkAtRptResumeIndicator set to resume reporting. The PDP is aware frwkAtRptResumeIndicator set to resume reporting. The PDP is aware of
of the request state Handle(s) and the supported PRCs either through the request state Handle(s) and the supported PRCs either through the
the state synchronization mechanism or because the PDP considers state synchronization mechanism or because the PDP considers itself
itself synchronized with the PEP upon reconnection. synchronized with the PEP upon reconnection.
2.4 Context 2.4 Context
The monitoring and recording of usage policies is subject to context The monitoring and recording of usage policies is subject to context
switches in a manner similar to enforcement policy. The usage policy switches in a manner similar to enforcement policy. The usage policy
is monitored, recorded and reported while the associated PIB is monitored, recorded and reported while the associated PIB instance
instance is active. The PEP should retain existing accounting data is active. The PEP should retain existing accounting data during
during inactive contexts and resume it's monitoring and reporting inactive contexts and resume it's monitoring and reporting when the
when the PIB instance becomes active again. PIB instance becomes active again.
2.5 Delete Request States 2.5 Delete Request States
The PEP may send any outstanding accounting data monitored during The PEP may send any outstanding accounting data monitored during the
the interval to the PDP via an unsolicited report immediately prior interval to the PDP via an unsolicited report immediately prior to
to issuing a Delete Request State if the time interval since the issuing a Delete Request State if the time interval since the last
last report is not less than the interval defined by the Accounting report is not less than the interval defined by the Accounting Timer.
Timer. This is also the case when the PDP initiates the Delete This is also the case when the PDP initiates the Delete Request State
Request State with a decision request delete state. with a decision request delete state. In this case where a PDP
initiates a Decision Request State Remove, the PEP acknowledges with
the Report, but the actual Delete Request State may be delayed until
the next reporting interval has completed.
2.6 Periodic nature of report accounting 2.6 Periodic nature of report accounting
The PDP informs the PEP of the minimal accounting interval it The PDP informs the PEP of the minimal accounting interval it
supports in the Accounting Timer object during client connection supports in the Accounting Timer object during client connection
establishment. The PEP notifies the PDP of its maximum accounting establishment. The PDP may specify accounting intervals in the
interval capability during the initial configuration request. The specific accounting policies per the PEP's indicated capabilities.
PDP may specify accounting intervals in the specific accounting The PDP may also halt reporting for a request state by issuing an
policies per the PEP's indicated capabilities. unsolicited decision with the frwkAtRptResumeIndicator set to halt
reporting. Any usage information associated with that request state
at the PEP since the last accounting interval is discarded by the
PEP.
Generally the accounting policy is periodic in nature and the Generally the accounting policy is periodic in nature and the
reporting is unsolicited. The unsolicited reports are supplied reporting is unsolicited. The unsolicited reports are supplied within
within the interval decided by the PDP. Note that periodic the interval decided by the PDP. Note that periodic unsolicited
unsolicited reports (as dictated by timer intervals) use a reports (as dictated by timer intervals) use a deterministic amount
deterministic amount of network resources. of network resources.
There may be instances where the nature of the accounting policy for There may be instances where the nature of the accounting policy for
a given client type or accounting PIB module is such that it is a given client type or accounting PIB module is such that it is
useful for the PDP to control when it receives the feedback. The PDP useful for the PDP to control when it receives the feedback. The PDP
may therefore have the capability to solicit the accounting report. may therefore have the capability to solicit the accounting report
for a request state.
3 Definition of Accounting Type Report Policy 3 Definition of Accounting Type Report Policy
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 accounting type report linkage policy, the usage policy and the accounting type report linkage
policy. policy.
The selection criteria policy is installed by the PDP. It defines The selection criteria policy is installed by the PDP. It defines the
the conditions used by the PEP to monitor and record a usage policy. conditions used by the PEP to monitor and record a usage policy.
Generally, the selection criterion is an existing PRC such as the Generally, the selection criterion is an existing PRC such as the
frwkIPFilterTable. This PRC is useful for specifying conditions on frwkIPFilterTable. This PRC is useful for specifying conditions on
which to base usage ū i.e. count the number of packets received for which to base usage - i.e. count the number of packets received for
this filter. The filter (source address, destination address, etc.) this filter. The filter (source address, destination address, etc.)
in this case defines the conditions. In the case of the accounting in this case defines the conditions. In the case of the accounting
framework PIB, the frwkIPFilterTable is the only PRC used to base framework PIB, the frwkIPFilterTable is the only PRC used to base
selection on. selection on.
The usage policy defines what attributes are monitored and recorded The usage policy defines what attributes are monitored and recorded
by the PEP. These policies have an ACCESS clause of Report. by the PEP. These policies have an ACCESS clause of Report.
Generally, the usage policies specify counts related to a specific Generally, the usage policies specify counts related to a specific
action such as a packet being dropped. The accounting framework PIB action such as a packet being dropped. The accounting framework PIB
defines one usage policy class, frwkAtRptFilterStats. It counts defines one usage policy class, frwkAtRptFilterStats. It counts
packets and bytes as well as records the timestamp when the last packets and bytes as well as records the timestamp when the last
packet was received. Usage PRCs may be generic, collecting basic packet was received. Usage PRCs may be generic, collecting basic
statistics, or specific to a particular usage. The PDP decides which statistics, or they may be specific to a particular usage. The PDP
PRC(s) best suit(s) its requirements. The PEP may support only one decides which PRC(s) best suit(s) its requirements. The PEP may
usage PRC, in which case all statistics are gathered using instances support only one usage PRC, in which case all statistics are gathered
of that PRC. Alternatively, the PEP may support multiple usage PRCs. using instances of that PRC. Alternatively, the PEP may support
The PDP then decides which PRC to associate with a particular multiple usage PRCs. The PDP then decides which PRC to associate with
selection criterion. Multiple selection criteria may be associated a particular selection criterion.
with multiple instances of a single PRC.
The accounting type report linkage permits the same selection The accounting type report linkage permits the same selection
criteria instance to be re-used for various usage policies. For criteria instance to be re-used for various usage policies. For
example, the same IP Filter selection criteria could be the basis of example, the same IP Filter selection criteria could be the basis of
different usage policies such as packet count, drop count, and different usage policies such as packet count, drop count, and remark
remark count. The accounting type report linkage references the count. The accounting type report linkage references the selection
selection criteria instance as well as defines the policy class of criteria instance as well as defines the policy class of the usage
the usage PRC. As noted above, the selection criteria policy may be PRC. As noted above, the selection criteria policy may be used for
used for enforcement policies as well as usage policies. This is the enforcement policies as well as usage policies. This is the case with
case with the frwkIPFilterTable. the frwkIPFilterTable.
------------------- ----------------- ----------------- ----------------- ------------------ -----------------
| | | | | | | | | | | |
| Select Criteria | |Linkage Instance| |Usage Instance | | Select Criteria | |Linkage Instance| |Usage Instance |
| | |-instance ID | |- instance ID | | | |-instance ID | |- instance ID |
| -instance ID |<--|-PRID of select |-->|- 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 a selection criteria,
linkage and usage policies. linkage and usage policies.
The PDP is not aware of the instance identifier of the usage policy The PDP is not aware of the instance identifier of the usage policy
when installing the selection criteria and accounting type report when installing the selection criteria and accounting type report
linkage policies. The usage policy is enabled on the PEP by the linkage policies. The usage policy is enabled on the PEP by the
accounting type report linkage and the PEP designates the instance installation of an accounting type report linkage and the PEP
identifier. The usage policy class always contains an attribute of designates the instance identifier. The usage policy class always
type Prid. This attribute contains the value of the accounting type contains an attribute of type Prid. This attribute contains the value
report linkage PRID [COPS-PR] installed by the PDP. The Prid type is of the accounting type report linkage PRID [COPS-PR] installed by the
a textual convention for an object identifier that is the PRC of the PDP that is associated with the usage policy. Note that the Prid type
table used for the selection criteria and where the last sub- is a textual convention for an object identifier that is the PRC of
the table used for the selection criteria and where the last sub-
identifier is an instance ID of the accounting type report linkage. identifier is an instance ID of the accounting type report linkage.
4 Summary of the Accounting Framework Policy Information Base 4 Summary of the Accounting Framework Policy Information Base
4.1 SPPI ACCESS clause Report 4.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" denotes the usage policy class reported by the attribute of "report-only" denotes the usage policy class reported by
PEP. the PEP.
4.2 Textual Conventions Counts 4.2 Textual Conventions Counts
The usage policy attributes are often defined in the terms of The usage policy attributes are often defined in the terms of counts.
counts. This type is a non-negative value that is incremented. This This type is a non-negative value that is incremented. This value is
value is to "stick" at the maximum value if the maximum value is to "stick" at the maximum value if the maximum value is reached
reached before the reporting interval. It is reset to the value zero before the reporting interval. It is reset to the value zero after
after the usage is reported to the PDP and continues the incremental the usage is reported to the PDP and continues the incremental
operation. A textual convention defining the counts is defined in operation. A textual convention defining the counts is defined in the
the Accounting Framework PIB. Accounting Framework PIB.
4.3 Accounting Type Report Group and PRCs 4.3 Accounting Type Report Group and PRCs
It is useful to define reporting intervals and restart It is useful to define reporting intervals and restart
characteristics as well as the common usage and selection criteria characteristics as well as the common usage and selection criteria
polices. These policy classes are common to account type reporting polices. These policy classes are common to account type reporting
for various technologies and apply to ALL SUBJECT-CATEGORIES. The for various technologies and apply to ALL SUBJECT-CATEGORIES. The
policy classes belong to a new group, Accounting Type Report Group. policy classes belong to a new group, Accounting Type Report Group.
The policy classes in the Accounting Type Report Group are: The policy classes in the Accounting Type Report Group are:
1) Accounting Type Report Device Intervals Table 1) Accounting Type Report Device Intervals Table
2) Accounting Type Report Linkage Table 2) Accounting Type Report Linkage Table
3) Accounting Type Filter Statistics Usage Table 3) Accounting Type Filter Statistics Usage Table
skipping to change at page 7, line 28 skipping to change at page 7, line 15
characteristics as well as the common usage and selection criteria characteristics as well as the common usage and selection criteria
polices. These policy classes are common to account type reporting polices. These policy classes are common to account type reporting
for various technologies and apply to ALL SUBJECT-CATEGORIES. The for various technologies and apply to ALL SUBJECT-CATEGORIES. The
policy classes belong to a new group, Accounting Type Report Group. policy classes belong to a new group, Accounting Type Report Group.
The policy classes in the Accounting Type Report Group are: The policy classes in the Accounting Type Report Group are:
1) Accounting Type Report Device Intervals Table 1) Accounting Type Report Device Intervals Table
2) Accounting Type Report Linkage Table 2) Accounting Type Report Linkage Table
3) Accounting Type Filter Statistics Usage Table 3) Accounting Type Filter Statistics Usage Table
4.3.1 The Accounting Type Report Device Table 4.3.1 The Accounting Type Report Resume Table
This table contains exactly one row. It defines the maximum
reporting interval in seconds that the PEP can support.
4.3.2 The Accounting Type Report Resume Table
This table contains one row. It indicates that the PDP, to which a This table contains one row. It indicates that the PDP, to which a
PEP having cached usage policy has reconnected, is ready to receive PEP having cached usage policy has reconnected, is ready to receive
the accounting type report messages from the PEP. the accounting type report messages from the PEP.
4.3.3 The Accounting Type Report Linkage Table 4.3.2 The Accounting Type Report Linkage Table
This table links the selection criteria instance with the usage This table links the selection criteria instance with the usage
instance. It specifies the PRID of the selection criteria and the instance. It specifies the PRID of the selection criteria and the PRC
PRC of the usage instance. This table permits the reuse of a of the usage instance. This table permits the reuse of a selection
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 accounting type reports for the interval to use when issuing the accounting type reports for the
usage instance. The interval is not to conflict with the maximum usage instance. This interval is defined in units of the Accounting
interval for the device defined in the Accounting Type Report Device Timer Interval specified in the client accept message.
Table.
4.3.4 The Filter Usage Table 4.3.3 The Filter 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 Accounting when a packet was received and the PRID of the associated Accounting
Type Report Linkage instance. The count and timestamp information is Type 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
accounting type report message within the maximum interval accounting type report message within the maximum interval specified.
specified.
5 The Accounting Framework PIB Module 5 The Accounting Framework PIB Module
ACCOUNTING-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN ACCOUNTING-FRAMEWORK-PIB PIB-DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
ExtUTCTime, Unsigned32, Unsigned64, IpAddress, 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 PolicyInstanceId, PolicyReferenceId
FROM COPS-PR-SPPI-TC; FROM COPS-PR-SPPI-TC;
RoleCombination RoleCombination
FROM POLICY-DEVICE-AUX-MIB; FROM POLICY-DEVICE-AUX-MIB;
acctPolFrameworkPib MODULE-IDENTITY acctPolFrameworkPib MODULE-IDENTITY
skipping to change at page 9, line 28 skipping to change at page 9, line 11
"A count represents a value used by attributes that "A count represents a value used by attributes that
record policy usage. A count is of value zero or record policy usage. A count is of value zero or
greater and is incremented according to defined greater and is incremented according to defined
policy usage. When the maximum value is reached, the policy usage. When the maximum value is reached, the
value sticks. The value is reset to zero upon value sticks. The value is reset to zero upon
reporting the value to the PDP." reporting the value to the PDP."
SYNTAX Unsigned64 ( 0..18446744073709551615) SYNTAX Unsigned64 ( 0..18446744073709551615)
-- --
-- The accounting type report device characteristics
--
frwkAtRptDevTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkAtRptDevEntry
PIB-ACCESS notify
STATUS current
DESCRIPTION
"This class contains a single PRI that specifies the
common reporting characteristics for the device."
::= { frwkAtRptGroupClasses 1}
frwkAtRptDevEntry OBJECT-TYPE
SYNTAX FrwkAtRptDevEntry
STATUS current
DESCRIPTION
"An instance of this class specifies the max
interval supported by the PEP."
::= { frwkAtRptDevTable 1}
FrwkAtRptDevEntry ::= SEQUENCE {
frwkAtRptDevPrid InstanceId,
frwkAtRptDevMax Unsigned32
}
frwkAtRptDevPrid OBJECT-TYPE
SYNTAX InstanceID
STATUS current
DESCRIPTION
" An arbitrary integer index that uniquely identifies an
instance of the frwkAtRptDevTable class."
::= { frwkAtRptDevEntry 1}
frwkAtRptDevMax OBJECT-TYPE
SYNTAX Unsigned32
STATUS current
DESCRIPTION
"The maximum reporting interval in seconds between
accounting type reporting messages issued by the
PEP. "
::= { frwkAtRptDevEntry 2 }
--
-- resume reporting indicator -- resume reporting indicator
-- --
frwkAtRptResumeTable OBJECT-TYPE frwkAtRptResumeTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkAtRptResumeEntry SYNTAX SEQUENCE OF FrwkAtRptResumeEntry
PIB-ACCESS install PIB-ACCESS install
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class contains a single PRI that indicates "This class contains a single PRI that indicates
that the PEP is to resume the sending of that the PEP is to resume the sending of
accounting type reports." accounting type reports."
::= { frwkAtRptGroupClasses 2} ::= { frwkAtRptGroupClasses 1}
frwkAtRptResumeEntry OBJECT-TYPE frwkAtRptResumeEntry OBJECT-TYPE
SYNTAX FrwkAtRptResumeEntry SYNTAX FrwkAtRptResumeEntry
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An instance of this class can indicate when to "An instance of this class can indicate when to
resume sending accounting type reports resume sending accounting type reports
by the PEP." by the PEP."
PIB-INDEX { frwkAtRptResumeId}
::= { frwkAtRptResumeTable 1} ::= { frwkAtRptResumeTable 1}
FrwkAtRptResumeEntry ::= SEQUENCE { FrwkAtRptResumeEntry ::= SEQUENCE {
frwkAtRptResumePrid InstanceId, frwkAtRptResumeId InstanceId,
frwkAtRptResumeIndicator INTEGER frwkAtRptResumeIndicator INTEGER
} }
frwkAtRptDevPrid OBJECT-TYPE frwkAtRptResumeId OBJECT-TYPE
SYNTAX InstanceID SYNTAX InstanceID
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" An arbitrary integer index that uniquely identifies an " An arbitrary integer index that uniquely identifies an
instance of the frwkAtRptResumeTable class." instance of the frwkAtRptResumeTable class."
::= { frwkAtRptResumeEntry 1} ::= { frwkAtRptResumeEntry 1}
frwkAtRptResumeIndicator OBJECT-TYPE frwkAtRptResumeIndicator OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
NO_REPORTS(0), NO_REPORTS(0),
SEND_REPORTS(1) SEND_REPORTS(1)
} }
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 accounting type report messages. usage policies via accounting type report messages.
The enumeration values are: The enumeration values are:
(0) DonĘt send accounting type report messages (0) DonĖt send accounting type report messages
(1) Resume accounting type report messages. Send (1) Resume accounting type report messages. Send
cached usage policies now " cached usage policies now "
::= { frwkAtRptResumeEntry 2 } ::= { frwkAtRptResumeEntry 2 }
-- --
-- The Accounting Type Report Linkage Table -- The Accounting Type Report Linkage Table
-- --
frwkAtRptLinkTable OBJECT-TYPE frwkAtRptLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkAtRptLinkEntry SYNTAX SEQUENCE OF FrwkAtRptLinkEntry
PIB-ACCESS notify PIB-ACCESS notify
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 permit the defining of the max
interval used for reporting the usage instance." interval used for reporting the usage instance."
::= { frwkAtRptGroupClasses 3} ::= { frwkAtRptGroupClasses 2}
frwkAtRptLinkEntry OBJECT-TYPE frwkAtRptLinkEntry OBJECT-TYPE
SYNTAX FrwkAtRptLinkEntry SYNTAX FrwkAtRptLinkEntry
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 permit the defining of the max
interval used for reporting the usage instance." interval used for reporting the usage instance."
PIB-INDEX {frwkAtRptLinkId} PIB-INDEX {frwkAtRptLinkId}
UNIQUENESS { frwkAtRptLinkId, UNIQUENESS { frwkAtRptLinkId,
skipping to change at page 12, line 41 skipping to change at page 11, line 26
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."
::= { frwkAtRptLinkEntry 3} ::= { frwkAtRptLinkEntry 3}
frwkAtRptInterval OBJECT-TYPE frwkAtRptInterval OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum interval in seconds between issuing accounting "Maximum interval in units of the value of the
type reports of this policy instance." Accounting Timer specificed by the PDP in the client
accept message. A frwkAtRptInterval of 1 is equal to
the value of the Accounting Timer. This value must be 1
or greater. "
::= { frwkAtRptLinkEntry 4} ::= { frwkAtRptLinkEntry 4}
-- --
-- The filter statistics usage -- The filter statistics usage
-- --
frwkAtRptFilterStatsUsageTable OBJECT-TYPE frwkAtRptFilterStatsUsageTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrwkAtRptFilterStatsUsageEntry SYNTAX SEQUENCE OF FrwkAtRptFilterStatsUsageEntry
PIB-ACCESS report PIB-ACCESS report-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This class defines the usage attributes that the PEP "This class defines the usage attributes that the PEP
is to monitor, record and report. It contains the is to monitor, record and report. It contains the
of the PRID of the linkage instance associating of the PRID of the linkage instance associating
the selection criteria instance with the usage the selection criteria instance with the usage
instance." instance."
::= { frwkAtRptGroupClasses 4} ::= { frwkAtRptGroupClasses 3}
frwkAtRptFilterStatsUsageEntry OBJECT-TYPE frwkAtRptFilterStatsUsageEntry OBJECT-TYPE
SYNTAX FrwkAtRptFilterStatsUsageEntry SYNTAX FrwkAtRptFilterStatsUsageEntry
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 {frwkAtRptFilterStatsUsageId} PIB-INDEX {frwkAtRptFilterStatsUsageId}
UNIQUENESS { frwkAtRptFilterStatsUsagePRID } UNIQUENESS { frwkAtRptFilterStatsUsageLinkPRID }
::= {frwkAtRptFilterStatsUsageTable 1} ::= {frwkAtRptFilterStatsUsageTable 1}
FrwkAtRptFilterStatsUsageEntry ::= SEQUENCE { FrwkAtRptFilterStatsUsageEntry ::= SEQUENCE {
frwkAtRptFilterStatsUsageId InstanceID, frwkAtRptFilterStatsUsageId InstanceID,
frwkAtRptFilterStatsUsagePRID Prid, frwkAtRptFilterStatsUsageLinkPRID Prid,
frwkAtRptFilterStatsUsagePacketCount Counts, frwkAtRptFilterStatsUsagePacketCount Counts,
frwkAtRptFilterStatsUsageByteCount Counts, frwkAtRptFilterStatsUsageByteCount Counts,
fwkAtRptFilterStatsUsageTimeStamp ExtUTCTime fwkAtRptFilterStatsUsageTimeStamp ExtUTCTime
} }
frwkAtRptFilterStatsUsageId OBJECT-TYPE frwkAtRptFilterStatsUsageId 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."
::= { frwkAtRptFilterStatsUsageEntry 1 } ::= { frwkAtRptFilterStatsUsageEntry 1 }
frwkAtRptFilterStatsUsagePRID OBJECT-TYPE frwkAtRptFilterStatsUsageLinkPRID OBJECT-TYPE
SYNTAX Prid SYNTAX Prid
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PRID of the selection criteria policy instance "The PRID of the Linkage policy instance used to base
used to base this usage policy instance upon. The this usage policy instance upon."
PRID is composed of the PRC of the selection
criteria
Instance and the last sub-identifier is that value
Of the selection criteria policy instance."
::= { frwkAtRptFilterStatsUsageEntry 2 } ::= { frwkAtRptFilterStatsUsageEntry 2 }
frwkAtRptFilterStatsUsagePacketCount OBJECT-TYPE frwkAtRptFilterStatsUsagePacketCount OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of packets matching the specified filter "The count of packets matching the specified filter
during the reporting interval." during the reporting interval."
::= {frwkAtRptFilterStatsUsageEntry 3} ::= {frwkAtRptFilterStatsUsageEntry 3}
frwkAtRptFilterStatsUsageByteCount OBJECT-TYPE frwkAtRptFilterStatsUsageByteCount OBJECT-TYPE
SYNTAX Unsigned64 SYNTAX Unsigned64
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The byte count of packets matching the "The byte count of packets matching the
specified filter during the reporting interval." specified filter during the reporting interval."
::= { frwkAtRptFilterStatsUsageEntry 4} ::= { frwkAtRptFilterStatsUsageEntry 4}
skipping to change at page 15, line 18 skipping to change at page 14, line 4
Email: khchan@nortelnetworks.com Email: khchan@nortelnetworks.com
Dinesh G Dutt Dinesh G Dutt
Cisco Systems, Inc. Cisco Systems, Inc.
170 Tasman Dr. 170 Tasman Dr.
San Jose, CA 95134-1706 San Jose, CA 95134-1706
Phone: 408-527-0955 Phone: 408-527-0955
Email: ddutt@cisco.com Email: ddutt@cisco.com
9 References 9 References
[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R., [COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Rajan, R.,
and A. Sastry, "The COPS (Common Open Policy Service) Protocol" and A. Sastry, "The COPS (Common Open Policy Service) Protocol"
RFC 2748, January 2000. RFC 2748, January 2000.
[COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F. [COPS-PR] K. Chan, D. Durham, S. Gai, S. Herzog, K. McCloghrie, F.
Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for Reichmeyer, J. Seligson, A. Smith, R. Yavatkar, "COPS Usage for
Policy Provisioning," draft-ietf-rap-cops-pr-02.txt, March 2000. Policy Provisioning," draft-ietf-rap-cops-pr-05.txt, March 2000.
[SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning [SPPI] K. McCloghrie, et.al., "Structure of Policy Provisioning
Information," draft-ietf-rap-sppi-00.txt, march 2000. Information," draft-ietf-rap-sppi-05.txt, February 2001.
[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", Internet Smith, F. Reichmeyer "Framework Policy Information Base", draft-
Draft , March 2000 ietf-rap-frameworkpib-03.txt, November 2000
[DSPIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Han, A. [DSPIB] M. Fine, K. McCloghrie, J. Seligson, K. Chan, S. Han, A.
Smith, F. Reichmeyer, "Differentiated Services Quality of Service Smith, F. Reichmeyer, "Differentiated Services Quality of Service
Policy Information Base", Internet Draft, March 2000 Policy Information Base", draft-ietf-diffserv-pib-02.txt, November
2000
[SIP-AAA-QOS] Gross, G.,Sinnreich, H. Rawlins D., Havinis, T. " QoS [SIP-AAA-QOS] Gross, G.,Sinnreich, H. Rawlins D., Havinis, T. " QoS
and AAA Usage with SIP Based IP Communications" draft-gross-sipaq- and AAA Usage with SIP Based IP Communications" draft-gross-sipaq-
00.txt, November 2000. 00.txt, November 2000.
 End of changes. 

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