RFC 1672: Accounting Requirements for IPng
In plain English — editorial summary, not part of the RFC
This white paper discusses accounting requirements for IPng. It recommends that all IPng packets carry accounting tags, which would vary in size. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1672
- Published
- August 1994
- Authors
- N. Brownlee
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 3
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1673Electric Power Research Institute Comments on IPngCurrent
August 1994
- RFC 1670Input to IPng Engineering ConsiderationsCurrent
August 1994
- RFC 1674A Cellular Industry View of IPngCurrent
August 1994
- RFC 1669Market Viability as a IPng CriteriaCurrent
August 1994
- RFC 1675Security Concerns for IPngCurrent
August 1994
- RFC 1676INFN Requirements for an IPngCurrent
August 1994
- RFC 1668Unified Routing Requirements for IPngCurrent
August 1994
- RFC 1667Modeling and Simulation Requirements for IPngCurrent
August 1994
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?