Extensible Authentication Protocol
RFC 3748, “Extensible Authentication Protocol”, is a Proposed Standard document published in June 2004 by B. Aboba, L. Blunk, J. Vollbrecht, J. Carlson, H. Levkowetz. It obsoletes RFC 2284. It has since been updated by RFC 5247, RFC 7057. The canonical text is published by the RFC Editor.
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) or IEEE 802, 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 2284. A summary of the changes between this document and RFC 2284 is available in Appendix A. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3748 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3747 The Differentiated Services Configuration MIB
- RFC 3749 Transport Layer Security Protocol Compression Methods
- RFC 3746 Forwarding and Control Element Separation Framework
- RFC 3750 Unmanaged Networks IPv6 Transition Scenarios
- RFC 3745 MIME Type Registrations for JPEG 2000
- RFC 3751 Omniscience Protocol Requirements
- RFC 3744 Web Distributed Authoring and Versioning Access Control Protocol
- RFC 3752 Open Pluggable Edge Services Use Cases and Deployment Scenarios