draft-ietf-radius-accounting-01.txt   draft-ietf-radius-accounting-02.txt 
RADIUS Working Group C Rigney RADIUS Working Group C Rigney
INTERNET-DRAFT Livingston INTERNET-DRAFT Livingston
expires in six months November 1995
RADIUS Accounting RADIUS Accounting
draft-ietf-radius-accounting-01.txt draft-ietf-radius-accounting-02.txt
Status of this Memo Status of this Memo
This document is a submission to the RADIUS Working Group of the This document is a submission to the RADIUS Working Group of the
Internet Engineering Task Force (IETF). Comments should be submitted Internet Engineering Task Force (IETF). Comments should be submitted
to the ietf-radius@livingston.com mailing list. to the ietf-radius@livingston.com mailing list.
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
skipping to change at page 1, line 34 skipping to change at page 1, line 32
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
This document expires May 31st, 1996. This document expires November 24th, 1996.
Abstract Abstract
This document describes a protocol for carrying accounting This document describes a protocol for carrying accounting
information between a Network Access Server and a shared Accounting information between a Network Access Server and a shared Accounting
Server. Server.
Table of Contents Table of Contents
1. Introduction .......................................... 1 1. Introduction .......................................... 1
1.1 Specification of Requirements ................... 2 1.1 Specification of Requirements ................ 2
1.2 Terminology ..................................... 2 1.2 Terminology ..................................... 2
2. Operation ............................................. 4 2. Operation ............................................. 3
3. Packet Format ......................................... 5 3. Packet Format ......................................... 4
4. Packet Types .......................................... 8 4. Packet Types .......................................... 6
4.1 Accounting-Request .............................. 8 4.1 Accounting-Request .............................. 6
4.2 Accounting-Response ............................. 10 4.2 Accounting-Response ............................. 7
5. Attributes ............................................ 12 5. Attributes ............................................ 9
5.1 Acct-Status-Type ................................ 13 5.1 Acct-Status-Type ................................ 10
5.2 Acct-Delay-Time ................................. 14 5.2 Acct-Delay-Time ................................. 11
5.3 Acct-Input-Octets ............................... 15 5.3 Acct-Input-Octets ............................... 12
5.4 Acct-Output-Octets .............................. 15 5.4 Acct-Output-Octets .............................. 12
5.5 Acct-Session-Id ................................. 16 5.5 Acct-Session-Id ................................. 13
5.6 Acct-Authentic .................................. 17 5.6 Acct-Authentic .................................. 14
5.7 Acct-Session-Time ............................... 18 5.7 Acct-Session-Time ............................... 15
5.8 Acct-Input-Packets .............................. 19 5.8 Acct-Input-Packets .............................. 16
5.9 Acct-Output-Packets ............................. 19 5.9 Acct-Output-Packets ............................. 16
5.10 Acct-Terminate-Cause ............................ 20 5.10 Acct-Terminate-Cause ............................ 17
5.11 Table of Attributes ............................. 22 5.11 Acct-Multi-Session-Id ........................... 19
5.12 Table of Attributes ............................. 20
Security Considerations ...................................... 24 Security Considerations ...................................... 22
References ................................................... 24 References ................................................... 22
Acknowledgements ............................................. 24 Acknowledgements ............................................. 22
Chair's Address .............................................. 25 Chair's Address .............................................. 23
Author's Address ............................................. 25 Author's Address ............................................. 23
1. Introduction 1. Introduction
Managing dispersed serial line and modem pools for large numbers of Managing dispersed serial line and modem pools for large numbers of
users can create the need for significant administrative support. users can create the need for significant administrative support.
Since modem pools are by definition a link to the outside world, they Since modem pools are by definition a link to the outside world, they
require careful attention to security, authorization and accounting. require careful attention to security, authorization and accounting.
This can be best achieved by managing a single "database" of users, This can be best achieved by managing a single "database" of users,
which allows for authentication (verifying user name and password) as which allows for authentication (verifying user name and password) as
well as configuration information detailing the type of service to well as configuration information detailing the type of service to
skipping to change at page 1, line 124 skipping to change at page 2, line 5
Transactions between the client and RADIUS accounting server Transactions between the client and RADIUS accounting server
are authenticated through the use of a shared secret, which is are authenticated through the use of a shared secret, which is
never sent over the network. never sent over the network.
Extensible Protocol Extensible Protocol
All transactions are comprised of variable length Attribute- All transactions are comprised of variable length Attribute-
Length-Value 3-tuples. New attribute values can be added Length-Value 3-tuples. New attribute values can be added
without disturbing existing implementations of the protocol. without disturbing existing implementations of the protocol.
Source Code Availability
Livingston Enterprises is making the C source code for an example
RADIUS accounting server available without use restrictions.
Other companies have also implemented RADIUS Accounting.
1.1. Specification of Requirements 1.1. Specification of Requirements
In this document, several words are used to signify the requirements In this document, several words are used to signify the
of the specification. These words are often capitalized. requirements of the specification. These words are often
capitalized.
MUST This word, or the adjective "required", means that the MUST This word, or the adjective "required", means that the
definition is an absolute requirement of the specification. definition is an absolute requirement of the
specification.
MUST NOT This phrase means that the definition is an absolute MUST NOT This phrase means that the definition is an absolute
prohibition of the specification. prohibition of the specification.
SHOULD This word, or the adjective "recommended", means that there SHOULD This word, or the adjective "recommended", means that
may exist valid reasons in particular circumstances to there may exist valid reasons in particular
ignore this item, but the full implications must be circumstances to ignore this item, but the full
understood and carefully weighed before choosing a implications must be understood and carefully weighed
different course. before choosing a different course.
MAY This word, or the adjective "optional", means that this MAY This word, or the adjective "optional", means that this
item is one of an allowed set of alternatives. An item is one of an allowed set of alternatives. An
implementation which does not include this option MUST be implementation which does not include this option MUST
prepared to interoperate with another implementation which be prepared to interoperate with another implementation
does include the option. which does include the option.
1.2. Terminology 1.2. Terminology
This document uses the following terms: This document uses the following terms:
service The NAS provides a service to the dial-in user, such as PPP service The NAS provides a service to the dial-in user, such as PPP
or Telnet. or Telnet.
session Each service provided by the NAS to a dial-in user session Each service provided by the NAS to a dial-in user
constitutes a session, with the beginning of the session constitutes a session, with the beginning of the session
defined as the point where service is first provided and defined as the point where service is first provided and
the end of the session defined as the point where service the end of the session defined as the point where service
is ended. A user may have multiple sessions in parallel or is ended. A user may have multiple sessions in parallel or
series if the NAS supports that, with each session series if the NAS supports that, with each session
generating a separate start and stop accounting record. generating a separate start and stop accounting record with
its own Acct-Session-Id.
silently discard silently discard
This means the implementation discards the packet without This means the implementation discards the packet without
further processing. The implementation SHOULD provide the further processing. The implementation SHOULD provide the
capability of logging the error, including the contents of capability of logging the error, including the contents of
the silently discarded packet, and SHOULD record the event the silently discarded packet, and SHOULD record the event
in a statistics counter. in a statistics counter.
2. Operation 2. Operation
skipping to change at page 4, line 20 skipping to change at page 3, line 20
being delivered to, and will send that to the RADIUS Accounting being delivered to, and will send that to the RADIUS Accounting
server, which will send back an acknowledgement that the packet has server, which will send back an acknowledgement that the packet has
been received. At the end of service delivery the client will been received. At the end of service delivery the client will
generate an Accounting Stop packet describing the type of service generate an Accounting Stop packet describing the type of service
that was delivered and optionally statistics such as elapsed time, that was delivered and optionally statistics such as elapsed time,
input and output octets, or input and output packets. It will send input and output octets, or input and output packets. It will send
that to the RADIUS Accounting server, which will send back an that to the RADIUS Accounting server, which will send back an
acknowledgement that the packet has been received. acknowledgement that the packet has been received.
The Accounting-Request (whether for Start or Stop) is submitted to The Accounting-Request (whether for Start or Stop) is submitted to
the RADIUS accounting server via the network. If no response is the RADIUS accounting server via the network. It is recommended that
returned within a length of time, the request is re-sent a number of the client continue attempting to send the Accounting-Request packet
times. The client can also forward requests to an alternate server until it receives an acknowledgement, using some form of backoff. If
or servers in the event that the primary server is down or no response is returned within a length of time, the request is re-
unreachable. An alternate server can be used either after a number sent a number of times. The client can also forward requests to an
of tries to the primary server fail, or in a round-robin fashion. alternate server or servers in the event that the primary server is
Retry and fallback algorithms are the topic of current research and down or unreachable. An alternate server can be used either after a
are not specified in detail in this document. number of tries to the primary server fail, or in a round-robin
fashion. Retry and fallback algorithms are the topic of current
It is recommended that the client continue attempting to send the research and are not specified in detail in this document.
Accounting packet until it receives an acknowledgement, using some
form of backoff. It MAY elect to send the packet to an alternate
accounting server. The nature of the timeout algorithms to be used
are the topic of current research, and are not further specified
here.
The RADIUS accounting server MAY make requests of other servers in The RADIUS accounting server MAY make requests of other servers in
order to satisfy the request, in which case it acts as a client. order to satisfy the request, in which case it acts as a client.
If the RADIUS accounting server is unable to successfully record the If the RADIUS accounting server is unable to successfully record the
accounting packet it MUST NOT send an Accounting-Response accounting packet it MUST NOT send an Accounting-Response
acknowledgment to the client. acknowledgment to the client.
3. Packet Format 3. Packet Format
skipping to change at page 6, line 18 skipping to change at page 5, line 18
Authenticator Authenticator
The Authenticator field is sixteen (16) octets. The most significant The Authenticator field is sixteen (16) octets. The most significant
octet is transmitted first. This value is used to authenticate the octet is transmitted first. This value is used to authenticate the
messages between the client and RADIUS accounting server. messages between the client and RADIUS accounting server.
Request Authenticator Request Authenticator
In Accounting-Request Packets, the Authenticator value is a 16 In Accounting-Request Packets, the Authenticator value is a 16
octet MD5 [3] checksum. octet MD5 [3] checksum, called the Request Authenticator.
The NAS and RADIUS accounting server share a secret. The The NAS and RADIUS accounting server share a secret. The Request
Authenticator field in Accounting-Request packets contains a one- Authenticator field in Accounting-Request packets contains a one-
way MD5 hash calculated over a stream of octets consisting of the way MD5 hash calculated over a stream of octets consisting of the
Code + Identifier + Length + 16 zero octets + request attributes + Code + Identifier + Length + 16 zero octets + request attributes +
shared secret (where + indicates concatenation). The 16 octet MD5 shared secret (where + indicates concatenation). The 16 octet MD5
hash value is stored in the Authenticator field of the hash value is stored in the Authenticator field of the
Accounting-Request packet. Accounting-Request packet.
Note that the Request Authenticator of an Accounting-Request can Note that the Request Authenticator of an Accounting-Request can
not be done the same way as the Request Authenticator of a RADIUS not be done the same way as the Request Authenticator of a RADIUS
Access-Request, because there is no User-Password attribute in an Access-Request, because there is no User-Password attribute in an
Accounting-Request. Accounting-Request.
[Draft Note - the implementation of RADIUS Accounting in
Livingston's ComOS 3.1 through 3.1.4 sets the Request
Authenticator to all 0's. A future release will implement the
method described here, after which this Note will be removed
from the Draft.]
Response Authenticator Response Authenticator
The Authenticator field in an Accounting-Response packet contains The Authenticator field in an Accounting-Response packet is called
a one-way MD5 hash calculated over a stream of octets consisting the Response Authenticator, and contains a one-way MD5 hash
of the Accounting-Response Code, Identifier, Length, the calculated over a stream of octets consisting of the Accounting-
Authenticator field from the Accounting-Request packet being Response Code, Identifier, Length, the Request Authenticator field
replied to, and the response attributes if any, followed by the from the Accounting-Request packet being replied to, and the response
shared secret. The resulting 16 octet MD5 hash value is stored in attributes if any, followed by the shared secret. The resulting 16
the Authenticator field of the Accounting-Response packet. octet MD5 hash value is stored in the Authenticator field of the
Accounting-Response packet.
Attributes Attributes
Attributes may have multiple instances, in such a case the order of Attributes may have multiple instances, in such a case the order of
attributes of the same type SHOULD be preserved. The order of attributes of the same type SHOULD be preserved. The order of
attributes of different types is not required to be preserved. attributes of different types is not required to be preserved.
4. Packet Types 4. Packet Types
The RADIUS packet type is determined by the Code field in the first The RADIUS packet type is determined by the Code field in the first
skipping to change at page 8, line 29 skipping to change at page 6, line 29
Upon receipt of an Accounting-Request, the server MUST transmit an Upon receipt of an Accounting-Request, the server MUST transmit an
Accounting-Response reply if it successfully records the Accounting-Response reply if it successfully records the
accounting packet, and MUST NOT transmit any reply if it fails to accounting packet, and MUST NOT transmit any reply if it fails to
record the accounting packet. record the accounting packet.
Any attribute valid in a RADIUS Access-Request or Access-Accept Any attribute valid in a RADIUS Access-Request or Access-Accept
packet is valid in a RADIUS Accounting-Request packet, except that packet is valid in a RADIUS Accounting-Request packet, except that
the following attributes MUST NOT be present in an Accounting- the following attributes MUST NOT be present in an Accounting-
Request: User-Password, CHAP-Password, Reply-Message, State. Request: User-Password, CHAP-Password, Reply-Message, State.
Either NAS-IP-Address or NAS-Identifier MUST be present in a Either NAS-IP-Address or NAS-Identifier MUST be present in a
RADIUS Accounting-Request. RADIUS Accounting-Request. It SHOULD contain a NAS-Port or NAS-
Port-Type attribute or both unless the service does not involve a
It SHOULD contain a NAS-Port or NAS-Port-Id attribute unless the port or the NAS does not distinguish among its ports.
service does not involve a port or the NAS does not distinguish
among its ports.
A summary of the Accounting-Request packet format is shown below. A summary of the Accounting-Request packet format is shown below.
The fields are transmitted from left to right. The fields are transmitted from left to right.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Identifier | Length | | Code | Identifier | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Authenticator | | Request Authenticator |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attributes ... | Attributes ...
+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-
Code Code
4 for Accounting-Request. 4 for Accounting-Request.
Identifier Identifier
The Identifier field MUST be changed whenever the content of the The Identifier field MUST be changed whenever the content of the
Attributes field changes, and whenever a valid reply has been Attributes field changes, and whenever a valid reply has been
received for a previous request. For retransmissions where the received for a previous request. For retransmissions where the
contents are identical, the Identifier MUST remain unchanged. contents are identical, the Identifier MUST remain unchanged.
skipping to change at page 9, line 35 skipping to change at page 7, line 21
Attributes field changes, and whenever a valid reply has been Attributes field changes, and whenever a valid reply has been
received for a previous request. For retransmissions where the received for a previous request. For retransmissions where the
contents are identical, the Identifier MUST remain unchanged. contents are identical, the Identifier MUST remain unchanged.
Note that if Acct-Delay-Time is included in the attributes of an Note that if Acct-Delay-Time is included in the attributes of an
Accounting-Request then the Acct-Delay-Time value will be updated Accounting-Request then the Acct-Delay-Time value will be updated
when the packet is retransmitted, changing the content of the when the packet is retransmitted, changing the content of the
Attributes field and requiring a new Identifier and Request Attributes field and requiring a new Identifier and Request
Authenticator. Authenticator.
Authenticator Request Authenticator
The Authenticator of an Accounting-Request contains a 16-octet MD5
hash value calculated according to the method described in
"Request Authenticator", above.
[Draft Note - the implementation of RADIUS Accounting in The Request Authenticator of an Accounting-Request contains a 16-
Livingston's ComOS 3.1 through 3.1.4 sets the Request octet MD5 hash value calculated according to the method described
Authenticator to all 0's. A future release will implement the in "Request Authenticator" above.
method described here, after which this Note will be removed
from the Draft.]
Attributes Attributes
The Attributes field is variable in length, and contains a list of The Attributes field is variable in length, and contains a list of
Attributes. Attributes.
4.2. Accounting-Response 4.2. Accounting-Response
Description Description
Accounting-Response packets are sent by the RADIUS accounting Accounting-Response packets are sent by the RADIUS accounting
server to the client to acknowledge that the Accounting-Request server to the client to acknowledge that the Accounting-Request
has been received and recorded successfully. has been received and recorded successfully. If the Accounting-
Request was recorded successfully then the RADIUS accounting
If the Accounting-Request was recorded successfully then the server MUST transmit a packet with the Code field set to 5
RADIUS accounting server MUST transmit a packet with the Code (Accounting-Response). On reception of an Accounting-Response by
field set to 5 (Accounting-Response). the client, the Identifier field is matched with a pending
Accounting-Request. Invalid packets are silently discarded.
A RADIUS Accounting-Response is not required to have any A RADIUS Accounting-Response is not required to have any
attributes in it. attributes in it.
On reception of an Accounting-Response by the client, the
Identifier field is matched with a pending Accounting-Request.
Invalid packets are silently discarded.
A summary of the Accounting-Response packet format is shown below. A summary of the Accounting-Response packet format is shown below.
The fields are transmitted from left to right. The fields are transmitted from left to right.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Identifier | Length | | Code | Identifier | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Authenticator | | Response Authenticator |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Attributes ... | Attributes ...
+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-
Code Code
5 for Accounting-Response. 5 for Accounting-Response.
Identifier Identifier
The Identifier field is a copy of the Identifier field of the The Identifier field is a copy of the Identifier field of the
Accounting-Request which caused this Accounting-Response. Accounting-Request which caused this Accounting-Response.
Authenticator Response Authenticator
The Authenticator of an Accounting-Response contains a 16-octet The Response Authenticator of an Accounting-Response contains a
MD5 hash value calculated according to the method described in 16-octet MD5 hash value calculated according to the method
"Response Authenticator", above. described in "Response Authenticator" above.
Attributes Attributes
The Attributes field is variable in length, and contains a list of The Attributes field is variable in length, and contains a list of
zero or more Attributes. zero or more Attributes.
5. Attributes 5. Attributes
RADIUS Attributes carry the specific authentication, authorization RADIUS Attributes carry the specific authentication, authorization
and accounting details for the request and response. and accounting details for the request and response.
skipping to change at page 12, line 45 skipping to change at page 9, line 45
1-39 (refer to RADIUS Internet-Draft) 1-39 (refer to RADIUS Internet-Draft)
40 Acct-Status-Type 40 Acct-Status-Type
41 Acct-Delay-Time 41 Acct-Delay-Time
42 Acct-Input-Octets 42 Acct-Input-Octets
43 Acct-Output-Octets 43 Acct-Output-Octets
44 Acct-Session-Id 44 Acct-Session-Id
45 Acct-Authentic 45 Acct-Authentic
46 Acct-Session-Time 46 Acct-Session-Time
47 Acct-Input-Packets 47 Acct-Input-Packets
48 Acct-Output-Packets 48 Acct-Output-Packets
49 Acct-Termination-Cause 49 Acct-Terminate-Cause
50 Acct-Multi-Session-Id
60+ (refer to RADIUS Internet-Draft) 60+ (refer to RADIUS Internet-Draft)
Length Length
The Length field is one octet, and indicates the length of this The Length field is one octet, and indicates the length of this
attribute including the Type, Length and Value fields. If an attribute including the Type, Length and Value fields. If an
attribute is received in an Accounting-Request with an invalid attribute is received in an Accounting-Request with an invalid
Length, the entire request should be silently discarded. Length, the entire request should be silently discarded.
Value Value
skipping to change at page 13, line 33 skipping to change at page 10, line 34
Attributes do not use this data type but it is presented Attributes do not use this data type but it is presented
here for possible use within Vendor-Specific attributes. here for possible use within Vendor-Specific attributes.
5.1. Acct-Status-Type 5.1. Acct-Status-Type
Description Description
This attribute indicates whether this Accounting-Request marks the This attribute indicates whether this Accounting-Request marks the
beginning of the user service (Start) or the end (Stop). beginning of the user service (Start) or the end (Stop).
It MAY also be used by the client to mark the start of accounting It MAY be used by the client to mark the start of accounting (for
(for example, upon booting) by specifying Accounting-On and to example, upon booting) by specifying Accounting-On and to mark the
mark the end of accounting (for example, just before a scheduled end of accounting (for example, just before a scheduled reboot) by
reboot) by specifying Accounting-Off. specifying Accounting-Off.
A summary of the Acct-Status-Type attribute format is shown below. A summary of the Acct-Status-Type attribute format is shown below.
The fields are transmitted from left to right. The fields are transmitted from left to right.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value | Type | Length | Value
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Value (cont) | Value (cont) |
skipping to change at page 14, line 18 skipping to change at page 11, line 18
Length Length
6 6
Value Value
The Value field is four octets. The Value field is four octets.
1 Start 1 Start
2 Stop 2 Stop
3 Accounting-On 7 Accounting-On
4 Accounting-Off 8 Accounting-Off
5.2. Acct-Delay-Time 5.2. Acct-Delay-Time
Description Description
This attribute indicates how many seconds the client has been This attribute indicates how many seconds the client has been
trying to send this record for, and can be subtracted from the trying to send this record for, and can be subtracted from the
time of arrival on the server to find the approximate time of the time of arrival on the server to find the approximate time of the
event generating this Accounting-Request. (Network transit time event generating this Accounting-Request. (Network transit time
is ignored.) is ignored.)
skipping to change at page 21, line 23 skipping to change at page 18, line 23
1 User Request 1 User Request
2 Lost Carrier 2 Lost Carrier
3 Lost Service 3 Lost Service
4 Idle Timeout 4 Idle Timeout
5 Session Timeout 5 Session Timeout
6 Admin Reset 6 Admin Reset
7 Admin Reboot 7 Admin Reboot
8 Port Error 8 Port Error
9 NAS Error 9 NAS Error
10 NAS Request 10 NAS Request
11 NAS Reboot
[Draft Note - These values are the topic of current research 12 Port Unneeded
and discussion and may change by the next draft depending on 13 Port Preempted
implementation experience. Please contact the document editor 14 Port Suspended
for an updated list.] 15 Service Unavailable
16 Callback
17 User Error
18 Host Request
The termination causes are as follows: The termination causes are as follows:
User Request User requested termination of service, for User Request User requested termination of service, for
example with LCP Terminate or by logging out. example with LCP Terminate or by logging out.
Lost Carrier DCD was dropped on the port. Lost Carrier DCD was dropped on the port.
Lost Service Service can no longer be provided; for example, Lost Service Service can no longer be provided; for
user's connection to a host was interrupted. example, user's connection to a host was
interrupted.
Idle Timeout Idle timer expired. Idle Timeout Idle timer expired.
Session Timeout Maximum Session length timer expired. Session Timeout Maximum session length timer expired.
Admin Reset Administrator reset the port or session. Admin Reset Administrator reset the port or session.
Admin Reboot Administrator is ending service on the NAS, for Admin Reboot Administrator is ending service on the NAS,
example prior to bringing the NAS down. for example prior to rebooting the NAS.
Port Error NAS detected an error on the port which required Port Error NAS detected an error on the port which
ending the session. required ending the session.
NAS Error NAS detected some error (other than on the port) NAS Error NAS detected some error (other than on the
which required ending the session. port) which required ending the session.
NAS Request NAS ended session for a reason other than the NAS Request NAS ended session for a non-error reason not
above. For example, a low-water mark may have otherwise listed here.
been reached or a resource-limit exceeded.
5.11. Table of Attributes NAS Reboot The NAS ended the session in order to reboot
non-administratively ("crash").
Port Unneeded NAS ended session because resource usage fell
below low-water mark (for example, if a
bandwidth-on-demand algorithm decided that
the port was no longer needed).
Port Preempted NAS ended session in order to allocate the
port to a higher priority use.
Port Suspended NAS ended session to suspend a virtual
session.
Service Unavailable NAS was unable to provide requested service.
Callback NAS is terminating current session in order
to perform callback for a new session.
User Error Input from user is in error, causing
termination of session.
Host Request Login Host terminated session normally.
5.11. Acct-Multi-Session-Id
Description
This attribute is a unique Accounting ID to make it easy to link
together multiple related sessions in a log file. Each session
linked together would have a unique Acct-Session-Id but the same
Acct-Multi-Session-Id. It is strongly recommended that the Acct-
Multi-Session-Id be a printable ASCII string.
A summary of the Acct-Session-Id attribute format is shown below.
The fields are transmitted from left to right.
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | String ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
50 for Acct-Multi-Session-Id.
Length
>= 3
String
The String field SHOULD be a string of printable ASCII characters.
5.12. Table of Attributes
The following table provides a guide to which attributes may be found The following table provides a guide to which attributes may be found
in Accounting-Request packets. No attributes should be found in in Accounting-Request packets. No attributes should be found in
Accounting-Response packets (except possibly for Vendor-Specific). Accounting-Response packets (except possibly for Vendor-Specific).
# Attribute # Attribute
0-1 User-Name 0-1 User-Name
0 User-Password 0 User-Password
0 CHAP-Password 0 CHAP-Password
0-1 NAS-IP-Address [4] 0-1 NAS-IP-Address [4]
skipping to change at page 22, line 34 skipping to change at page 20, line 45
0-1 Service-Type 0-1 Service-Type
0-1 Framed-Protocol 0-1 Framed-Protocol
0-1 Framed-IP-Address 0-1 Framed-IP-Address
0-1 Framed-IP-Netmask 0-1 Framed-IP-Netmask
0-1 Framed-Routing 0-1 Framed-Routing
0+ Filter-Id 0+ Filter-Id
0-1 Framed-MTU 0-1 Framed-MTU
0+ Framed-Compression 0+ Framed-Compression
0+ Login-IP-Host 0+ Login-IP-Host
0-1 Login-Service 0-1 Login-Service
0-1 Login-Port 0-1 Login-TCP-Port
0 Reply-Message 0 Reply-Message
0-1 Callback-Number 0-1 Callback-Number
0-1 Callback-Id 0-1 Callback-Id
0+ Framed-Route 0+ Framed-Route
0-1 Framed-IPX-Network 0-1 Framed-IPX-Network
0 State 0 State
0+ Class 0+ Class
0+ Vendor-Specific 0+ Vendor-Specific
0-1 Session-Timeout 0-1 Session-Timeout
0-1 Idle-Timeout 0-1 Idle-Timeout
skipping to change at page 23, line 20 skipping to change at page 21, line 33
1 Acct-Status-Type 1 Acct-Status-Type
0-1 Acct-Delay-Time 0-1 Acct-Delay-Time
0-1 Acct-Input-Octets 0-1 Acct-Input-Octets
0-1 Acct-Output-Octets 0-1 Acct-Output-Octets
1 Acct-Session-Id 1 Acct-Session-Id
0-1 Acct-Authentic 0-1 Acct-Authentic
0-1 Acct-Session-Time 0-1 Acct-Session-Time
0-1 Acct-Input-Packets 0-1 Acct-Input-Packets
0-1 Acct-Output-Packets 0-1 Acct-Output-Packets
0-1 Acct-Terminate-Cause 0-1 Acct-Terminate-Cause
0+ Acct-Multi-Session-Id
0 CHAP-Challenge 0 CHAP-Challenge
0-1 NAS-Port-Id 0-1 NAS-Port-Type
0-1 Port-Limit 0-1 Port-Limit
0-1 Login-LAT-Port
[4] An Accounting-Request MUST contain either a NAS-IP-Address or a [4] An Accounting-Request MUST contain either a NAS-IP-Address or a
NAS-Identifier, and it is permitted (but not recommended) for it to NAS-Identifier, and it is permitted (but not recommended) for it to
contain both. contain both.
The following table defines the meaning of the above table entries. The following table defines the above table entries.
0 This attribute MUST NOT be present 0 This attribute MUST NOT be present
0+ Zero or more instances of this attribute MAY be present. 0+ Zero or more instances of this attribute MAY be present.
0-1 Zero or one instance of this attribute MAY be present. 0-1 Zero or one instance of this attribute MAY be present.
1 Exactly one instance of this attribute MUST be present. 1 Exactly one instance of this attribute MUST be present.
Security Considerations Security Considerations
Security issues are briefly discussed in sections concerning the Security issues are briefly discussed in sections concerning the
authenticator included in accounting requests and responses, using a authenticator included in accounting requests and responses, using a
shared secret which is never sent over the network. shared secret which is never sent over the network.
References References
[1] Postel, J., "User Datagram Protocol", RFC 768, USC/Information [1] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
Sciences Institute, August 1980. USC/Information Sciences Institute, August 1980.
[2] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1700, [2] Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC
USC/Information Sciences Institute, October 1994. 1700, USC/Information Sciences Institute, October 1994.
[3] Rivest, R., and S. Dusse, "The MD5 Message-Digest Algorithm", [3] Rivest, R., and S. Dusse, "The MD5 Message-Digest Algorithm",
MIT Laboratory for Computer Science and RSA Data Security, RFC 1321, MIT Laboratory for Computer Science, RSA Data
Inc., RFC 1321, April 1992. Security Inc., April 1992.
Acknowledgments Acknowledgments
RADIUS and RADIUS Accounting were originally developed by Livingston RADIUS and RADIUS Accounting were originally developed by Livingston
Enterprises for their PortMaster series of Network Access Servers. Enterprises for their PortMaster series of Network Access Servers.
Chair's Address Chair's Address
The RADIUS working group can be contacted via the current chair: The RADIUS working group can be contacted via the current chair:
Carl Rigney Carl Rigney
Livingston Enterprises Livingston Enterprises
6920 Koll Center Parkway, Suite 220 6920 Koll Center Parkway, Suite 220
Pleasanton, California 94566 Pleasanton, California 94566
Phone: +1 510 426 0770 Phone: +1 510 426 0770
EMail: cdr@livingston.com E-Mail: cdr@livingston.com
Author's Address Author's Address
Questions about this memo can also be directed to: Questions about this memo can also be directed to:
Carl Rigney Carl Rigney
Livingston Enterprises Livingston Enterprises
6920 Koll Center Parkway, Suite 220 6920 Koll Center Parkway, Suite 220
Pleasanton, California 94566 Pleasanton, California 94566
EMail: cdr@livingston.com E-Mail: cdr@livingston.com
This document expires May 31st, 1996. This document expires November 24th, 1996.
 End of changes. 57 change blocks. 
143 lines changed or deleted 177 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/