Handover Key Management and Re-Authentication Problem Statement
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 15
- Abstract
- 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.
- Publication Date
- 2008-03-01
- Status Note
- Informational
- DOI
10.17487/RFC5169- Link
- https://doi.org/10.17487/RFC5169
- Author(s)
- Charles ClancyMadjid NakhjiriVidya NarayananLakshminath R. Dondeti
- Keyword(s)
- HOKEY, Handover Key Management, Fast Re-authentication, Mobility
Latest version of IETF RFC 5169
Document Versions — IETF RFC 5169
-
▶ IETF RFC 5169 (2008-03-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3748 [Active*]
- IETF RFC 4017 [Active*]
- IETF RFC 4962 [Active*]
Bibliographic Reference(s)
- IEEE.STD802.11R.2008 — IEEE.802-11R-D9.0 EXTERNAL
- Fajardo, V., Asveren, T., Tschofenig, H., McGregor, G., and J. Loughney, "Diameter Applications Design Guidelines", Work in Progress, January 2008. EXTERNAL
- Josefsson, S., Palekar, A., Simon, D., and G. Zorn, "Protected EAP Protocol (PEAP) Version 2", Work in Progress, October 2004. EXTERNAL
- Calhoun, P., Montemurro, M., and D. Stanely, "CAPWAP Protocol Specification", Work in Progress, March 2008. EXTERNAL
- Aboba, B., Simon, D., and P. Eronen, "Extensible Authentication Protocol (EAP) Key Management Framework", Work in Progress, November 2007. EXTERNAL
- Mishra, A., Shin, M., and W. Arbaugh, "An Empirical Analysis of the IEEE 802.11 MAC- Layer Handoff Process", ACM SIGCOMM Computer and Communications Review, April 2003. EXTERNAL
- Weber, G. and A. DeKok, "RADIUS Design Guidelines", Work in Progress, December 2007. EXTERNAL
- Mishra, A., Shin, M., Petroni, N., Clancy, T., and W. Arbaugh, "Proactive Key Distribution using Neighbor Graphs", IEEE Wireless Communications, February 2004. EXTERNAL
- Ledlie, J., Gardner, P., and M. Selter, "Network Coordinates in the Wild", USENIX Symposium on Networked System Design and Implementation, April 2007. EXTERNAL
- Funk, P. and S. Blake-Wilson, "EAP Tunneled TLS Authentication Protocol Version 0 (EAP- TTLSv0)", Work in Progress, March 2008. EXTERNAL
- IETF RFC 3990 [Active*]
- IETF RFC 4186 [Active*]
- IETF RFC 4187 [Active*]
- IETF RFC 4851 [Active*]
- IETF RFC 5077 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5169.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5169, Handover Key Management and Re-Authentication Problem Statement. Available at https://doi.org/10.17487/RFC5169
Snippet:
IETF RFC 5169, Handover Key Management and Re-Authentication Problem Statement. Available at https://doi.org/10.17487/RFC5169
HTML (ISO 690 compliant)
Preview:
IETF RFC 5169, Handover Key Management and Re-Authentication Problem Statement. Available at https://doi.org/10.17487/RFC5169
Snippet:
<span class="citation"><cite>IETF RFC 5169</cite>, Handover Key Management and Re-Authentication Problem Statement. Available at <a href="https://doi.org/10.17487/RFC5169" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5169</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5169, Handover Key Management and Re-Authentication Problem Statement
doi: 10.17487/RFC5169
url: https://doi.org/10.17487/RFC5169
doi: 10.17487/RFC5169
url: https://doi.org/10.17487/RFC5169
Snippet:
<li> <cite id="bib-rfc5169">IETF RFC 5169</cite>, Handover Key Management and Re-Authentication Problem Statement <span class="doi">10.17487/RFC5169</span> </li>
Referenced By
- IETF RFC 5296 [Superseded*]
- IETF RFC 5836 [Active*]
- IETF RFC 6696 [Active*]