RADIUS - RFCs

RFCs

The RADIUS protocol is currently defined in the following IETF RFCs: Obsolete RFCs are indicated with strikethrough text.

# Title Date published Related article Obsoleted by Notes
RFC 2058 Remote Authentication Dial In User Service (RADIUS) January 1997 RADIUS RFC 2138
RFC 2059 RADIUS Accounting January 1997 RADIUS RFC 2139
RFC 2138 Remote Authentication Dial In User Service (RADIUS) April 1997 RADIUS RFC 2865
RFC 2139 RADIUS Accounting April 1997 RADIUS RFC 2866
RFC 2548 Microsoft Vendor-specific RADIUS Attributes March 1999 RADIUS
RFC 2607 Proxy Chaining and Policy Implementation in Roaming June 1999
RFC 2618 RADIUS Authentication Client MIB Management information base RFC 4668
RFC 2619 RADIUS Authentication Server MIB Management information base RFC 4669
RFC 2620 RADIUS Accounting Client MIB June 1999 Management information base RFC 4670
RFC 2621 RADIUS Accounting Server MIB June 1999 Management information base RFC 4671
RFC 2809 Implementation of L2TP Compulsory Tunneling via RADIUS April 2000
RFC 2865 Remote Authentication Dial In User Service (RADIUS) June 2000 RADIUS Updated by: RFC 2868, RFC 3575, RFC 5080
RFC 2866 RADIUS Accounting June 2000 RADIUS
RFC 2867 RADIUS Accounting Modifications for Tunnel Protocol Support June 2000 RADIUS Updates RFC 2866
RFC 2868 RADIUS Attributes for Tunnel Protocol Support June 2000 Updates RFC 2865
RFC 2869 RADIUS Extensions June 2000 updated by RFC 3579, RFC 5080
RFC 2882 Network Access Servers Requirements: Extended RADIUS Practices July 2000
RFC 3162 RADIUS and IPv6 August 2001
RFC 3575 IANA Considerations for RADIUS July 2003
RFC 3576 Dynamic Authorization Extensions to RADIUS July 2003 RFC 5176
RFC 3579 RADIUS Support for EAP September 2003 Extensible Authentication Protocol Updates: RFC 2869
RFC 3580 IEEE 802.1X RADIUS Usage Guidelines September 2003 802.1X
RFC 4014 RADIUS Attributes Suboption for the DHCP Relay Agent Information Option February 2005
RFC 4372 Chargeable User Identity January 2006
RFC 4590 RADIUS Extension for Digest Authentication July 2006 RFC 5090
RFC 4668 RADIUS Authentication Client MIB for IPv6 August 2006 Management information base
RFC 4669 RADIUS Authentication Server MIB for IPv6 August 2006 Management information base
RFC 4670 RADIUS Accounting Client MIB for IPv6 August 2006 Management information base
RFC 4671 RADIUS Accounting Server MIB for IPv6 August 2006 Management information base
RFC 4675 RADIUS Attributes for Virtual LAN and Priority Support September 2006
RFC 4679 DSL Forum Vendor-Specific RADIUS Attributes September 2006
RFC 4818 RADIUS Delegated-IPv6-Prefix Attribute April 2007
RFC 4849 RADIUS Filter Rule Attribute April 2007
RFC 5080 Common RADIUS Implementation Issues and Suggested Fixes December 2007 Updates RFC 3579
RFC 5090 RADIUS Extension for Digest Authentication February 2008
RFC 5176 Dynamic Authorization Extensions to RADIUS January 2008
RFC 5607 RADIUS Authorization for NAS Management July 2009
RFC 5997 Use of Status-Server Packets in the RADIUS Protocol August 2010 Updates RFC 2866
RFC 6158 RADIUS Design Guidelines March 2011

Read more about this topic:  RADIUS

Other articles related to "rfcs, rfc":

Media Gateway Control Protocol (MGCP) - RFCs
... RFC 3435 - Media Gateway Control Protocol (MGCP) Version 1.0 (this supersedes RFC 2705) RFC 3660 - Basic Media Gateway Control Protocol (MGCP) Packages (inf ...
Request For Comments - Production and Evolution - Streams
... There are four streams of RFCs (1) IETF, (2) IRTF, (3) IAB, and (4) independent submission ... Only the IETF creates BCPs and RFCs on standards track ... In other words, IRTF and independent RFCs are supposed to contain relevant info or experiments for the Internet at large not in conflict with IETF work, compare RFC 4846, RFC 5742, and RFC 5744 ...
List Of RFCs
... This is a partial list of RFCs (request for comments memoranda) ... While there are over 6000 RFCs, this list consists of RFCs that have related articles ...
Application Delivery Network - ADN Optimization Techniques - TCP Optimization
... There are a number of RFCs which describe mechanisms for improving the performance of TCP ... Many ADN implement these RFCs in order to provide enhanced delivery of applications through more efficient use of TCP ... The RFCs most commonly implemented are Delayed Acknowledgements Nagle Algorithm Selective Acknowledgements Explicit Congestion Notification ECN Limited and Fast ...
Request For Comments - Status - Status "historic"
... A historic RFC is one that has been made obsolete by a newer version, documents a protocol that is not considered interesting in the current Internet, or has been removed from the ... Some obsolete RFCs are not classified as historic, because the Internet standards process generally does not allow normative references from a standards track RFC to ... few are interested in working through the required procedural details to get RFCs classified as historic and update all RFCs normatively depending on it ...