@techreport{arkko-emu-rfc3748bis-00,
    number =    {draft-arkko-emu-rfc3748bis-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-arkko-emu-rfc3748bis/00/},
    author =    {Dr. Bernard D. Aboba and Larry Blunk and John Vollbrecht and James D. Carlson and Henrik Levkowetz and Jari Arkko and John Preuß Mattsson},
    title =     {{Extensible Authentication Protocol (EAP)}},
    pagetotal = 72,
    year =      2021,
    month =     feb,
    day =       21,
    abstract =  {This document defines the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication methods. EAP typically runs directly over data link layers such as Point-to-Point Protocol (PPP), IEEE 802, or 3GPP 5G without requiring IP. EAP provides its own support for duplicate elimination and retransmission, but is reliant on lower layer ordering guarantees. Fragmentation is not supported within EAP itself; however, individual EAP methods may support this. This document obsoletes RFC 3748, which in turn obsoleted RFC 2284. This document updates some of the security considerations, terms, references, the IANA considerations, and few other minor updates. A summary of the changes between this document and RFC 3748 is in Appendix A, and the changes from RFC 2284 were listed in RFC 3748.},
}