RFC 6697

Handover Keying (HOKEY) Architecture Design, July 2012

File formats:
icon for text file icon for PDF icon for HTML
G. Zorn, Ed.
Q. Wu
T. Taylor
Y. Nir
K. Hoeper
S. Decugis
hokey (sec)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC6697

Discuss this RFC: Send questions or comments to hokey@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


The Handover Keying (HOKEY) Working Group seeks to minimize handover delay due to authentication when a peer moves from one point of attachment to another. Work has progressed on two different approaches to reduce handover delay: early authentication (so that authentication does not need to be performed during handover), and reuse of cryptographic material generated during an initial authentication to save time during re-authentication. A basic assumption is that the mobile host or "peer" is initially authenticated using the Extensible Authentication Protocol (EAP), executed between the peer and an EAP server as defined in RFC 3748.

This document defines the HOKEY architecture. Specifically, it describes design objectives, the functional environment within which handover keying operates, the functions to be performed by the HOKEY architecture itself, and the assignment of those functions to architectural components. It goes on to illustrate the operation of the architecture within various deployment scenarios that are described more fully in other documents produced by the HOKEY Working Group. This document is not an Internet Standards Track specification; it is published for informational purposes.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.