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

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (ops)
Authors Pat Calhoun  , Bernard Aboba 
Last updated 2020-05-05 (latest revision 2003-05-16)
Stream Independent Submission
Formats plain text pdf htmlized bibtex
Stream ISE state (None)
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3579 (Informational)
Telechat date
Responsible AD Randy Bush
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3579

        Title:      RADIUS (Remote Authentication Dial In User
                    Service) Support For Extensible Authentication
                    Protocol (EAP)
        Author(s):  B. Aboba, P. Calhoun
        Status:     Informational
        Date:       September 2003
        Mailbox:    bernarda@microsoft.com, pcalhoun@airespace.com
        Pages:      46
        Characters: 104469
        Updates:    2869

        I-D Tag:    draft-aboba-radius-rfc2869bis-22.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3579.txt

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.  It 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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.