%% You should probably cite rfc6630 instead of this I-D. @techreport{ietf-hokey-erp-aak-10, number = {draft-ietf-hokey-erp-aak-10}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-hokey-erp-aak/10/}, author = {Zehn Cao and DENG Hui and Qin Wu and Glen Zorn}, title = {{EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK)}}, pagetotal = 20, year = 2012, month = feb, day = 17, abstract = {The Extensible Authentication Protocol (EAP) is a generic framework supporting multiple types of authentication methods. The EAP Re-authentication Protocol (ERP) specifies extensions to EAP and the EAP keying hierarchy to support an EAP method-independent protocol for efficient re-authentication between the peer and an EAP re-authentication server through any authenticator. Authenticated Anticipatory Keying (AAK) is a method by which cryptographic keying material may be established upon one or more candidate attachment points (CAPs) prior to handover. AAK uses the AAA infrastructure for key transport. This document specifies the extensions necessary to enable AAK support in ERP.}, }