RADIUS Support For Extensible Authentication Protocol
RFC 3579, “RADIUS Support For Extensible Authentication Protocol”, is an Informational document published in September 2003 by B. Aboba, P. Calhoun. It updates RFC 2869. It has since been updated by RFC 5080. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3579 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3578 Mapping of Integrated Services Digital Network User Part Overlap Signalling to the Session Initiation Protocol
- RFC 3580 IEEE 802.1X Remote Authentication Dial In User Service Usage Guidelines
- RFC 3577 Introduction to the Remote Monitoring Family of MIB Modules
- RFC 3581 An Extension to the Session Initiation Protocol for Symmetric Response Routing
- RFC 3576 Dynamic Authorization Extensions to Remote Authentication Dial In User Service
- RFC 3582 Goals for IPv6 Site-Multihoming Architectures
- RFC 3575 IANA Considerations for RADIUS
- RFC 3583 Requirements of a Quality of Service Solution for Mobile IP