UpdatedINFORMATIONALIETF stream

RFC 3579: RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)

Still current, but amended. Parts of this document are changed or extended by RFC 5080. Read both.

In plain English — editorial summary, not part of the RFC

This document defines Remote Authentication Dial In User Service (RADIUS) support for the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication mechanisms. In the proposed scheme, the Network Access Server (NAS) forwards EAP packets to and from the RADIUS server, encapsulated within EAP-Message attributes. This has the advantage of allowing the NAS to support any EAP authentication method, without the need for method- specific code, which resides on the RADIUS server. While EAP was originally developed for use with PPP, it is now also in use with IEEE 802. This memo provides information for the Internet community.

Document record

Document ID: RFC3579
Published: September 2003
Authors: B. Aboba; P. Calhoun
Status: INFORMATIONAL
Stream: IETF
Area: —
Pages: 46
Also known as: —

Updates:: RFC 2869
Updated by:: RFC 5080

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

RFC 5080Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested FixesCurrent
December 2007

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 23 August 2026. RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?