RFC 2138: Remote Authentication Dial In User Service (RADIUS)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2865.
Current document in this lineage: RFC 2865 — Remote Authentication Dial In User Service (RADIUS)
In plain English — editorial summary, not part of the RFC
This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2138
- Published
- April 1997
- Authors
- C. Rigney; A. Rubens; W. Simpson; S. Willens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 65
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2058 (1997)
- RFC 2138 (1997)
- RFC 2865 (2000) ✓
Read the full history of Remote Authentication Dial In User Service (RADIUS) →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 2000
- RFC 2869RADIUS ExtensionsUpdated
June 2000
- RFC 3579RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)Updated
September 2003
- RFC 2607Proxy Chaining and Policy Implementation in RoamingCurrent
June 1999
- RFC 3575IANA Considerations for RADIUS (Remote Authentication Dial In User Service)Updated
July 2003
- RFC 2867RADIUS Accounting Modifications for Tunnel Protocol SupportCurrent
June 2000
- RFC 2261An Architecture for Describing SNMP Management FrameworksObsoleted
January 1998
- RFC 2285Benchmarking Terminology for LAN Switching DevicesCurrent
February 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?