RFC - 3579
RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)
| Original: | ftp://ftp.isi.edu/in-notes/rfc3579.txt |
|---|---|
| Authors: | B. Aboba [Microsoft], P. Calhoun [Airespace] |
| Date: | September 2003 |
| Category: | Informational |
| Updates: | |
|---|---|
| RFC-2869 | RADIUS Extensions (Updated by RFC-3579) |
| Referred by: | 17 RFC |
| Refers to: | 26 RFC |
Status
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
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 document updates RFC 2869.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry
