RADIUS was originally specified in an RFI by Merit Network in 1991 to control dial-in access to NSFnet. Livingston Enterprises responded to the RFI with a description of a RADIUS server. Merit Network awarded the contract to Livingston Enterprises that delivered their PortMaster series of Network Access Servers and the initial RADIUS server to Merit. RADIUS was later (1997) published as RFC 2058 and RFC 2059 (current versions are RFC 2865 and RFC 2866).
Now, several commercial and open-source RADIUS servers exist. Features can vary, but most can look up the users in text files, LDAP servers, various databases, etc. Accounting records can be written to text files, various databases, forwarded to external servers, etc. SNMP is often used for remote monitoring and keep-alive checking of a RADIUS server. RADIUS proxy servers are used for centralized administration and can rewrite RADIUS packets on the fly (for security reasons, or to convert between vendor dialects).
The Diameter protocol is the planned replacement for RADIUS. Diameter uses SCTP or TCP while RADIUS uses UDP as the transport layer.
Read more about this topic: RADIUS
Other articles related to "radius history, radius":
... RADIUS was originally specified in an RFI by Merit Network in 1991 to control dial-in access to NSFnet ... Livingston Enterprises responded to the RFI with a description of a RADIUS server ... of Network Access Servers and the initial RADIUS server to Merit ...
Famous quotes containing the word history:
“And now this is the way in which the history of your former life has reached my ears! As he said this he held out in his hand the fatal letter.”
—Anthony Trollope (18151882)