%% You should probably cite rfc5749 instead of this I-D.
@techreport{ietf-hokey-key-mgm-13,
    number =    {draft-ietf-hokey-key-mgm-13},
    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-key-mgm/13/},
    author =    {Madjid Nakhjiri and Katrin Hoeper and Yoshihiro Ohba},
    title =     {{Distribution of EAP-Based Keys for Handover and Re-Authentication}},
    pagetotal = 12,
    year =      2009,
    month =     dec,
    day =       3,
    abstract =  {This document describes an abstract mechanism for delivering root keys from an Extensible Authentication Protocol (EAP) server to another network server that requires the keys for offering security protected services, such as re-authentication, to an EAP peer. The distributed root key can be either a usage-specific root key (USRK), a domain-specific root key (DSRK), or a domain-specific usage- specific root key (DSUSRK) that has been derived from an Extended Master Session Key (EMSK) hierarchy previously established between the EAP server and an EAP peer. This document defines a template for a key distribution exchange (KDE) protocol that can distribute these different types of root keys using a AAA (Authentication, Authorization, and Accounting) protocol and discusses its security requirements. The described protocol template does not specify message formats, data encoding, or other implementation details. It thus needs to be instantiated with a specific protocol (e.g., RADIUS or Diameter) before it can be used. {[}STANDARDS-TRACK{]}},
}