Extensible Authentication Protocol Support in RADIUS
draft-ietf-radius-eap-05
| Document | Type |
Expired Internet-Draft
(radius WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Allan Rubens , Dr. Bernard D. Aboba , Pat R. Calhoun | ||
| Last updated | 1998-05-13 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Extensible Authentication Protocol (EAP), described in [1], pro- vides a standard mechanism for support of additional authentication methods within PPP. Through the use of EAP, support for a number of authentication schemes may be added, including smart cards, Kerberos, Public Key, One Time Passwords, and others. In order to provide for support of EAP within RADIUS, two new attributes, EAP-Message and Sig- nature, were introduced as RADIUS extensions in [4]. This document describes how these new attributes may be used for providing EAP sup- port within RADIUS.
Authors
Allan Rubens
Dr. Bernard D. Aboba
Pat R. Calhoun
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)