EAP keying and handover support
draft-nakhjiri-eap-ho-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Madjid Nakhjiri | ||
| Last updated | 2005-06-06 | ||
| 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 current EAP documentation set, such as [EAP3748], [EAPKEY6], and [RADEAP3579] provide a powerful framework for performing combined authentication and key management using an EAP server and an AAA infrastructure. The framework competently deals with many issues related to network-access control and link security setup. However, when it comes to deploying these specifications for mobile wireless environments, where a peer is required to perform fast and/or heterogeneous handovers, the current framework can be extended with more clear guidelines and possibly specifications in ways that prevent interoperability or security issues. This draft intends to explore some of the complications in deploying the EAP framework for handovers and analyze a few solution alternatives. Further threat analysis of each alternative or providing trade-off guidelines for support of handover may be part of the future revisions of this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)