RFC 2139 on RADIUS Accounting

RFC Editor <rfc-ed@isi.edu> Fri, 18 April 1997 20:13 UTC

Received: from ietf.org by ietf.org id aa09949; 18 Apr 97 16:13 EDT
Received: from zephyr.isi.edu by ietf.org id aa09768; 18 Apr 97 16:07 EDT
Received: from zephyr.isi.edu by zephyr.isi.edu (5.65c/5.61+local-23) id <AA01276>; Fri, 18 Apr 1997 13:04:04 -0700
Message-Id: <199704182004.AA01276@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC 2139 on RADIUS Accounting
Cc: rfc-ed@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 18 Apr 1997 13:04:04 -0700
Sender: ietf-announce-request@ietf.org
From: RFC Editor <rfc-ed@isi.edu>

A new Request for Comments is now available in online RFC libraries.


        RFC 2139:

        Title:      RADIUS Accounting
        Author:     C. Rigney
        Date:       April 1997
        Mailbox:    cdr@livingston.com
        Pages:      25
        Characters: 44919
        Updates/Obsoletes: 2059

        URL:        ftp://ds.internic.net/rfc/rfc2139.txt


This document describes a protocol for carrying accounting
information between a Network Access Server and a shared Accounting
Server. This document is the product of the Remote Authentication
Dial-In User Service Working Group of the IETF.

Implementation Note: This memo documents the RADIUS Accounting
protocol.  There has been some confusion in the assignment of port
numbers for this protocol.  The early deployment of RADIUS Accounting
was done using the erroneously chosen port number 1646, which
conflicts with the "sa-msg-port" service.  The officially assigned
port number for RADIUS Accounting is 1813.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  Distribution of
this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ds.internic.net/rfc/rfc2139.txt"><ftp://ds.internic.net/rfc/rfc2139.txt>