@techreport{ietf-pppext-rfc2284bis-10,
    number =    {draft-ietf-pppext-rfc2284bis-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-pppext-rfc2284bis/10/},
    author =    {Larry Blunk and John Vollbrecht and Dr. Bernard D. Aboba and James D. Carlson},
    title =     {{Extensible Authentication Protocol (EAP)}},
    pagetotal = 40,
    year =      2003,
    month =     jan,
    day =       23,
    abstract =  {This document defines the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication mechanisms. EAP typically runs directly over the link layer without requiring IP, but is reliant on lower layer ordering guarantees as in PPP and IEEE 802. EAP does provide its own support for duplicate elimination and retransmission. Fragmentation is not supported within EAP itself; however, individual EAP methods may support this. While EAP was originally developed for use with PPP, it is also now in use with IEEE 802. This document obsoletes RFC 2284.},
}