EAP client-side transport
draft-boursetty-eap-cst-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Benoit de Boursetty , Florent Bersani | ||
| Last updated | 2003-04-03 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
This document defines a new architecture on the client-side for authentication by EAP. This architecture complements the usual setup considered in EAP by making it become symmetric: the client-side is divided in two parts, the Authentication Token and the client, which are analogous respectively to the Authentication Server and the Authenticator on the server-side. Moreover, this document describes a framework for the use of Authentication Tokens with the EAP protocol.
Authors
Benoit de Boursetty
Florent Bersani
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)