State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 51
- Abstract
- This document describes a set of state machines for Extensible Authentication Protocol (EAP) peer, EAP stand-alone authenticator (non-pass-through), EAP backend authenticator (for use on Authentication, Authorization, and Accounting (AAA) servers), and EAP full authenticator (for both local and pass-through). This set of state machines shows how EAP can be implemented to support deployment in either a peer/authenticator or peer/authenticator/AAA Server environment. The peer and stand-alone authenticator machines are illustrative of how the EAP protocol defined in RFC 3748 may be implemented. The backend and full/pass-through authenticators illustrate how EAP/AAA protocol support defined in RFC 3579 may be implemented. Where there are differences, RFC 3748 and RFC 3579 are authoritative. The state machines are based on the EAP "Switch" model. This model includes events and actions for the interaction between the EAP Switch and EAP methods. A brief description of the EAP "Switch" model is given in the Introduction section. The state machine and associated model are informative only. Implementations may achieve the same results using different methods. This memo provides information for the Internet community.
- Publication Date
- 2005-08-01
- Status Note
- Informational
- DOI
10.17487/RFC4137- Link
- https://doi.org/10.17487/RFC4137
- Author(s)
- John VollbrechtPasi EronenNick L. PetroniYoshihiro Ohba
- Keyword(s)
- EAP Authenticator
Latest version of IETF RFC 4137
Document Versions — IETF RFC 4137
-
▶ IETF RFC 4137 (2005-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3579 [Active*]
- IETF RFC 3748 [Active*]
Bibliographic Reference(s)
- IEEE.STD802.1X.2004 — IEEE802.1X EXTERNAL
- Aboba, B., Simon, D., Arkko, J., Eronen, P., Levkowetz, H., "Extensible Authentication Protocol (EAP) Key Management Framework", Work in Progress, July 2005. EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4137.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4137, State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator. Available at https://doi.org/10.17487/RFC4137
Snippet:
IETF RFC 4137, State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator. Available at https://doi.org/10.17487/RFC4137
HTML (ISO 690 compliant)
Preview:
IETF RFC 4137, State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator. Available at https://doi.org/10.17487/RFC4137
Snippet:
<span class="citation"><cite>IETF RFC 4137</cite>, State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator. Available at <a href="https://doi.org/10.17487/RFC4137" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4137</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4137, State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator
doi: 10.17487/RFC4137
url: https://doi.org/10.17487/RFC4137
doi: 10.17487/RFC4137
url: https://doi.org/10.17487/RFC4137
Snippet:
<li> <cite id="bib-rfc4137">IETF RFC 4137</cite>, State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator <span class="doi">10.17487/RFC4137</span> </li>
Referenced By
- IETF draft-ietf-emu-tls-eap-types-04 [Active*]
- IETF RFC 4441 [Superseded*]
- IETF RFC 5191 [Active*]
- IETF RFC 7241 [Active*]
- IETF RFC 9190 [Active*]
- IETF RFC 9427 [Active*]