Problem Statement on EAP Efficient Re-authentication and Key Management
draft-vidya-eap-reauth-ps-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vidya Narayanan , Lakshminath R. Dondeti | ||
| Last updated | 2006-10-17 | ||
| 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
The extensible authentication protocol (EAP), specified in RFC3748 [1] is a generic framework for network access authentication, in which a peer engages in a full EAP conversation each time. A full EAP conversation involves several roundtrips between the peer and the authentication server in the home domain, and that is not acceptable for fast roaming. In this document, we explain the requirements for low-latency EAP re-authentication and associated key management.
Authors
Vidya Narayanan
Lakshminath R. Dondeti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)