Mike, Saw this come across my mailbox. Is this supported by Radiator in the 2.13.1? -------------------------------------------------------------------- _/_/_/ Peter Chow Chief Technical Advisor _/_/_/ interQ Corporation - System Division _/_/_/ [EMAIL PROTECTED] Shibuya Infoss Tower 10F _/_/_/ (tel)+81-3-5456-2555 20-1 Sakuragaokacho, Shibuya-ku _/_/_/ (fax)+81-3-5456-2556 Tokyo, Japan _/_/_/ http://www.interq.ad.jp 150-0031 -------------------------------------------------------------------- ---------- Forwarded message ---------- Date: Mon, 21 Jun 1999 16:24:12 -0700 From: RFC Editor <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RFC 2621 on RADIUS Accounting Server MIB A new Request for Comments is now available in online RFC libraries. RFC 2621: Title: RADIUS Accounting Server MIB Author(s): G. Zorn, B. Aboba Status: Informational Date: June 1999 Mailbox: [EMAIL PROTECTED], [EMAIL PROTECTED] Pages: 15 Characters: 27768 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-radius-acc-servmib-05.txt URL: ftp://ftp.isi.edu/in-notes/rfc2621.txt This memo defines a set of extensions which instrument RADIUS accounting server functions. These extensions represent a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Using these extensions IP-based management stations can manage RADIUS accounting servers. This document is a product of the Remote Authentication Dial-In User Service Working Group of the IETF. 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 [EMAIL PROTECTED] Requests to be added to or deleted from the RFC-DIST distribution list should be sent to [EMAIL PROTECTED] Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to [EMAIL PROTECTED] with the message body help: ways_to_get_rfcs. For example: To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to [EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Alegre Ramos 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.
<<< multipart/alternative: No recognizable part >>>
