Light-weight Flow Accounting Protocol Data Definition Specification Version 5.0
draft-riverstone-lfap-data-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul Amsden , Mike MacFaden | ||
| Last updated | 2002-07-25 | ||
| 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
The Light-weight Flow Accounting Protocol Data Definition Specification defines the data which may be sent via the Light- weight Flow Accounting Protocol transport. LFAP transport and LFAP Data Definition, allow an external Flow Accounting Service (FAS) to record flow accounting information from a Connection Control Entity (CCE), allowing flexible Flow Accounting Services to be deployed by a vendor or customer without changes to, or undue burden on, the CCE. Specifically, this document specifies the data that may be exchanged between the CCE and the external FAS. Using LFAP, a FAS can maintain details of current or historical flows for billing, capacity planning and other purposes
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)