@techreport{yegin-eap-boot-rfc3118-03,
    number =    {draft-yegin-eap-boot-rfc3118-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-yegin-eap-boot-rfc3118/03/},
    author =    {Hannes Tschofenig and Alper E. Yegin and Dan Forsberg},
    title =     {{Bootstrapping RFC3118 Delayed DHCP Authentication Using EAP-based Network Access Authentication}},
    pagetotal = 28,
    year =      2008,
    month =     jul,
    day =       14,
    abstract =  {The DHCP authentication extension (RFC 3118) cannot be widely deployed due to lack of a key agreement protocol. This document outlines how EAP-based network access authentication mechanisms can be used to establish bootstrap keying material that can be used to subsequently use RFC 3118 security.},
}