Goals of the Old Internet Accounting Working Group
- Provide an Internet accounting framework
(RFC 1272, Internet Accounting Background)
- Provide a near-term architecture for Internet accounting
(Internet-Draft, Internet Accounting Architecture)
- Provide a draft MIB for experimentation
(Internet-Draft, Internet Accounting: Meter Services
Usage reporting, billing, network management and policy research
are applications which operate on an accounting application data
- Accounting applications: manage the accounting database,
correlate information from separate metering systems, direct
monitoring and control of meters.
- Collection and network management protocols: provide transport
between applications and meters.
- Meters perform the aggregation and attribution of counts (packets,
View the Internet as a Loose Hierarchy for Internet Accounting
Approaches to Reducing Overhead
- Counting every packet for every user in every network at every
router is too fine a granularity---too much overhead. (This is the
same problem that routing protocols have!)
(GIF - 24306 bytes)
- Hold each network responsible/accountable for its own traffic.
- Perform accounting only at entry and/or exit gateways.
- Use coarser granularity for measuring transit traffic.
- Use multiple granularities to differentiate exception traffic.
- Use simple collection mechanisms real-time (if reliable enough)
and post-process into accounting records.
Selecting the "Right" Granularity
(GIF - 17287 bytes)
Internet Accounting Process
(GIF - 24352 bytes)
- Finer granularities
- Quality of Service
- Host participation in identifying end-users
- Upper-layer protocols (application-level accounting)
- Quota systems
- Limiting costs and resources
- Real-time interactions and access control
- Additional features
- Reserved bandwidth
- Inter-domain policy routing
- Standardized file formats
- Exchanging accumulated and/or reduced usage data between