Prepaid Extensions to Radius for Event-based Charging
draft-guenther-radext-ppebc-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Christian Guenther , Hannes Tschofenig | ||
Last updated | 2004-07-13 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In event-based charging procedures, customers get charged for service usage per se. This type of charging can be independent of data volume transferred, time period of service availment, or user subscription status. This memo introduces Radius attributes appropriate for event-based charging with debiting of prepaid user accounts.
Authors
Christian Guenther
Hannes Tschofenig
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)