| 1 |
<pre>Network Working Group N. Brownlee |
| 2 |
Request for Comments: 1672 The University of Auckland |
| 3 |
Category: Informational August 1994 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">Accounting Requirements for IPng</span> |
| 7 |
|
| 8 |
Status of this Memo |
| 9 |
|
| 10 |
This memo provides information for the Internet community. This memo |
| 11 |
does not specify an Internet standard of any kind. Distribution of |
| 12 |
this memo is unlimited. |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
This document was submitted to the IETF IPng area in response to <a href="./rfc1550">RFC</a> |
| 17 |
<a href="./rfc1550">1550</a>. Publication of this document does not imply acceptance by the |
| 18 |
IPng area of any ideas expressed within. Comments should be |
| 19 |
submitted to the [email protected] mailing list. |
| 20 |
|
| 21 |
Summary |
| 22 |
|
| 23 |
This white paper discusses accounting requirements for IPng. It |
| 24 |
recommends that all IPng packets carry accounting tags, which would |
| 25 |
vary in size. In the simplest case a tag would simply be a voucher |
| 26 |
identifying the party responsible for the packet. At other times tags |
| 27 |
should also carry other higher-level accounting information. |
| 28 |
|
| 29 |
Background |
| 30 |
|
| 31 |
The Internet Accounting Model - described in <a href="./rfc1272">RFC 1272</a> - specifies how |
| 32 |
accounting information is structured, and how it is collected for use |
| 33 |
by accounting aplications. The model is very general, with |
| 34 |
accounting variables being defined for various layers of a protocol |
| 35 |
stack. The group's work has so far concentrated on the lower layers, |
| 36 |
but the model can be extended simply by defining the variables |
| 37 |
required, e.g., for session and application layers. |
| 38 |
|
| 39 |
Brian Carpenter [<a href="#ref-1" title=""IPng White Paper on Transition and Other Considerations"">1</a>] suggests that IPng packets should carry |
| 40 |
authenticated (source, destination, transaction) triplets, which |
| 41 |
could be used for policy-based routing and accounting. The following |
| 42 |
sections explain how the transaction field - hereafter called an |
| 43 |
'accounting tag' - could be used. |
| 44 |
|
| 45 |
Lower-layer (Transport) Accounting |
| 46 |
|
| 47 |
At the lower (network) layers the tag would simply be a voucher. This |
| 48 |
means it is an arbitrary string which identifies the party |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Brownlee [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1672">RFC 1672</a> Accounting Requirements for IPng August 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
responsible, i.e., willing to pay for, a packet. It would initially |
| 58 |
be set by the host which originates the packet, hence at that stage |
| 59 |
the tag would identify the user who sent it. |
| 60 |
|
| 61 |
A tag could be changed at various points along a packet's path. This |
| 62 |
could be done as part of the routing policy processing so as to |
| 63 |
reflect changes of the party responsible over each section of the |
| 64 |
path. For example: |
| 65 |
|
| 66 |
user - provider tag identifies user |
| 67 |
provider A - provider B tag identifies provider A |
| 68 |
|
| 69 |
The tag could be used by accounting meters to identify the party |
| 70 |
responsible for a traffic flow, without having to deduce this using |
| 71 |
tables of rules. This should considerably simplify accounting for |
| 72 |
transit traffic across intermediate networks. |
| 73 |
|
| 74 |
Higher-layer (Session and Application) Accounting |
| 75 |
|
| 76 |
At higher layers there is a clear need to measure accounting |
| 77 |
variables and communicate them to various points along a packet's |
| 78 |
path, for example an application server may wish to inform a client |
| 79 |
about its usage of resources. A tag containing this information could |
| 80 |
be read by meters at any point along the packet's path for charging |
| 81 |
purposes, and could also be used by the client to inform the user of |
| 82 |
charges incurred. |
| 83 |
|
| 84 |
It would make the collection of accounting data much simpler if this |
| 85 |
information was carried in a standard tag within each packet, rather |
| 86 |
than having different protocols provide this service in differing |
| 87 |
ways. |
| 88 |
|
| 89 |
For 'old' applications which remain unaware of the tag field, a meter |
| 90 |
could be placed at a gateway for the application's host. This |
| 91 |
'gateway' meter could determine what the application is by watching |
| 92 |
its streams of packets, then set an appropriate value in thir tag |
| 93 |
fields. |
| 94 |
|
| 95 |
Structure of the accounting tag |
| 96 |
|
| 97 |
The two uses of tags outlined above must be able to coexist. Since |
| 98 |
many - indeed most - of the packets will only carry a voucher, it |
| 99 |
seems simplest to keep this as part of the routing tuple (see below). |
| 100 |
|
| 101 |
For the application variables, a separate tag seems sensible. This |
| 102 |
would simply contain a list of the variables. Having two tags in |
| 103 |
this way would keep separate the management of routers and meters. |
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Brownlee [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1672">RFC 1672</a> Accounting Requirements for IPng August 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
If the encryption/digital signature overhead of the second tag proves |
| 114 |
to be too high, it should be possible to combine this with the |
| 115 |
voucher. |
| 116 |
|
| 117 |
The fine detail of this, or at least the way variables are packed |
| 118 |
into the tags, could be standardised by the Accounting Working Group |
| 119 |
in due course. For the purpose of IPng all that is required is the |
| 120 |
ability to carry one or two variable-size objects in every packet. |
| 121 |
|
| 122 |
References |
| 123 |
|
| 124 |
[<a id="ref-1">1</a>] Carpenter, B., "IPng White Paper on Transition and Other |
| 125 |
Considerations", <a href="./rfc1671">RFC 1671</a>, CERN, August 1994. |
| 126 |
|
| 127 |
Security Considerations |
| 128 |
|
| 129 |
For IPng to provide reliable transport in a hostile environment, |
| 130 |
routing and accounting information, i.e., the (source, dest, |
| 131 |
network-tag) and (application-tag) tuples, must be tamper-proof. |
| 132 |
Routers and meters which need to use the tuples will need to hold |
| 133 |
appropriate keys for them. Network operators will have to plan |
| 134 |
for this, for example by determining which routers need which |
| 135 |
sets of keys. This will be neccessary in any case for reliable |
| 136 |
policy-based routing, so the extra work required to set up |
| 137 |
accounting meters should be acceptable. |
| 138 |
|
| 139 |
Author's Address |
| 140 |
|
| 141 |
Nevil Brownlee |
| 142 |
Deputy Director |
| 143 |
Computer Centre, The University of Auckland |
| 144 |
Private Bag 92019, Auckland, New Zealand |
| 145 |
|
| 146 |
Phone: +64 9 373 7599 |
| 147 |
Fax: +64 9 373 7425 |
| 148 |
EMail: [email protected] |
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
Brownlee [Page 3] |
| 165 |
</pre> |