RFC 5169: Handover Key Management and Re-Authentication Problem Statement
In plain English — editorial summary, not part of the RFC
This document describes the Handover Keying (HOKEY) re-authentication problem statement. The current Extensible Authentication Protocol (EAP) keying framework is not designed to support re-authentication and handovers without re-executing an EAP method. This often causes unacceptable latency in various mobile wireless environments. This document details the problem and defines design goals for a generic mechanism to reuse derived EAP keying material for handover. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5169
- Published
- March 2008
- Authors
- T. Clancy; M. Nakhjiri; V. Narayanan; L. Dondeti
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5749Distribution of EAP-Based Keys for Handover and Re-AuthenticationCurrent
March 2010
- RFC 4866Enhanced Route Optimization for Mobile IPv6Current
May 2007
- RFC 5522Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile NetworksCurrent
October 2009
- RFC 5844IPv4 Support for Proxy Mobile IPv6Current
May 2010
- RFC 6059Simple Procedures for Detecting Network Attachment in IPv6Current
November 2010
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 3775Mobility Support in IPv6Obsoleted
June 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?