Handover Key Management and Re-authentication Problem Statement
draft-clancy-hokey-reauth-ps-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Charles Clancy | ||
| Last updated | 2008-04-02 (Latest revision 2007-01-03) | ||
| Replaced by | draft-ietf-hokey-reauth-ps | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-hokey-reauth-ps | |
| 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 describes the Handover Keying (HOKEY) problem statement. The current EAP keying framework is not designed to support re-authentication and handovers. This often cause unacceptable latency in various mobile wireless environments. HOKEY plans to address these HOKEY plans to address these problems by implementing a generic mechanism to reuse derived EAP keying material for hand-off.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)