Skip to main content

Policy-Based Accounting

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3334.
Author Sebastian Zander
Last updated 2015-10-14 (Latest revision 2002-08-15)
RFC stream Legacy stream
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3334 (Experimental)
Telechat date (None)
Responsible AD Bert Wijnen
IESG note
Send notices to <>, <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3334

        Title:      Policy-Based Accounting
        Author(s):  T. Zseby, S. Zander, C. Carle
        Status:     Experimental
        Date:       October 2002
        Pages:      44
        Characters: 103014
        Updates/Obsoletes/SeeAlso:  None
        I-D Tag:    draft-irtf-aaaarch-pol-acct-05.txt


This document describes policy-based accounting which is an approach
to provide flexibility to accounting architectures.  Accounting
policies describe the configuration of an accounting architecture in
a standardized way.  They are used to instrument the accounting
architecture and can be exchanged between Authentication,
Authorization and Accounting (AAA) entities in order to
share configuration information.

This document describes building blocks and message sequences for
policy-based accounting in the generic AAA architecture
(RFC 2903).  Examples are given for the usage of accounting policies
in different scenarios.  It is also shown how accounting components
can be integrated into the AAA authorization framework (RFC 2904).
This document does not propose a language for the description of
accounting policies.  Rather, it is assumed that a suitable policy
language can be chosen from existing or upcoming standards. 

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  Distribution of this memo
is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.