RFC 3748: Extensible Authentication Protocol (EAP)

This document defines the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication methods. EAP typically…

Read RFC 3748 on the RFC Editor

Outgoing relationships (26 related RFCs)

Obsoletes, Informative reference — RFC 2284: PPP Extensible Authentication Protocol (EAP)
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 1661: The Point-to-Point Protocol (PPP)
Normative reference — RFC 2279: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 2988: Computing TCP's Retransmission Timer
Normative reference — RFC 1994: PPP Challenge Handshake Authentication Protocol (CHAP)
Normative reference — RFC 2289: A One-Time Password System
Informative reference — RFC 793: Transmission Control Protocol
Informative reference — RFC 2865: Remote Authentication Dial In User Service (RADIUS)
Informative reference — RFC 2246: The TLS Protocol Version 1.0
Informative reference — RFC 2409: The Internet Key Exchange (IKE)
Informative reference — RFC 3454: Preparation of Internationalized Strings ("stringprep")
Informative reference — RFC 3579: RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)
Informative reference — RFC 2960: Stream Control Transmission Protocol
Informative reference — RFC 1750: Randomness Recommendations for Security
Informative reference — RFC 3692: Assigning Experimental and Testing Numbers Considered Useful
Informative reference — RFC 2661: Layer Two Tunneling Protocol "L2TP"
Informative reference — RFC 2408: Internet Security Association and Key Management Protocol (ISAKMP)
Informative reference — RFC 1510: The Kerberos Network Authentication Service (V5)
Informative reference — RFC 3162: RADIUS and IPv6
Informative reference — RFC 3580: IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines
Informative reference — RFC 2607: Proxy Chaining and Policy Implementation in Roaming
Informative reference — RFC 2486: The Network Access Identifier
Informative reference — RFC 2716: PPP EAP TLS Authentication Protocol
Informative reference — RFC 2433: Microsoft PPP CHAP Extensions

Incoming relationships (75 related RFCs)

Showing 50 of 75 related RFCs.

Updated by — RFC 5247: Extensible Authentication Protocol (EAP) Key Management Framework
Updated by, Normatively referenced by — RFC 7057: Update to the Extensible Authentication Protocol (EAP) Applicability Statement for Application Bridging for Federated Access Beyond Web (ABFAB)
Normatively referenced by — RFC 5996: Internet Key Exchange Protocol Version 2 (IKEv2)
Normatively referenced by — RFC 4017: Extensible Authentication Protocol (EAP) Method Requirements for Wireless LANs
Normatively referenced by — RFC 4187: Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA)
Normatively referenced by — RFC 4186: Extensible Authentication Protocol Method for Global System for Mobile Communications (GSM) Subscriber Identity Modules (EAP-SIM)
Normatively referenced by — RFC 4137: State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator
Normatively referenced by — RFC 4284: Identity Selection Hints for the Extensible Authentication Protocol (EAP)
Normatively referenced by — RFC 5296: EAP Extensions for EAP Re-authentication Protocol (ERP)
Normatively referenced by — RFC 5448: Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA')
Normatively referenced by — RFC 6696: EAP Extensions for the EAP Re-authentication Protocol (ERP)
Normatively referenced by — RFC 4334: Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)
Normatively referenced by — RFC 6677: Channel-Binding Support for Extensible Authentication Protocol (EAP) Methods
Normatively referenced by — RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI)
Normatively referenced by — RFC 5836: Extensible Authentication Protocol (EAP) Early Authentication Problem Statement
Normatively referenced by — RFC 9190: EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3
Normatively referenced by — RFC 4764: The EAP-PSK Protocol: A Pre-Shared Key Extensible Authentication Protocol (EAP) Method
Normatively referenced by — RFC 5998: An Extension for EAP-Only Authentication in IKEv2
Normatively referenced by — RFC 7593: The eduroam Architecture for Network Roaming
Normatively referenced by — RFC 4763: Extensible Authentication Protocol Method for Shared-secret Authentication and Key Establishment (EAP-SAKE)
Normatively referenced by — RFC 5749: Distribution of EAP-Based Keys for Handover and Re-Authentication
Normatively referenced by — RFC 6734: Diameter Attribute-Value Pairs for Cryptographic Key Transport
Normatively referenced by — RFC 7831: Application Bridging for Federated Access Beyond Web (ABFAB) Architecture
Normatively referenced by — RFC 9140: Nimble Out-of-Band Authentication for EAP (EAP-NOOB)
Normatively referenced by — RFC 9191: Handling Large Certificates and Long Certificate Chains in TLS-Based EAP Methods
Normatively referenced by — RFC 4746: Extensible Authentication Protocol (EAP) Password Authenticated Exchange
Normatively referenced by — RFC 5193: Protocol for Carrying Authentication for Network Access (PANA) Framework
Normatively referenced by — RFC 5421: Basic Password Exchange within the Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST)
Normatively referenced by — RFC 6697: Handover Keying (HOKEY) Architecture Design
Normatively referenced by — RFC 7652: Port Control Protocol (PCP) Authentication Mechanism
Normatively referenced by — RFC 5807: Definition of Master Key between PANA Client and Enforcement Point
Normatively referenced by — RFC 6252: A Framework of Media-Independent Pre-Authentication (MPA) for Inter-Domain Handover Optimization
Normatively referenced by — RFC 6678: Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method
Normatively referenced by — RFC 6786: Encrypting the Protocol for Carrying Authentication for Network Access (PANA) Attribute-Value Pairs
Normatively referenced by — RFC 6942: Diameter Support for the EAP Re-authentication Protocol (ERP)
Normatively referenced by — RFC 8940: Extensible Authentication Protocol (EAP) Session-Id Derivation for EAP Subscriber Identity Module (EAP-SIM), EAP Authentication and Key Agreement (EAP-AKA), and Protected EAP (PEAP)
Normatively referenced by — RFC 9048: Improved Extensible Authentication Protocol Method for 3GPP Mobile Network Authentication and Key Agreement (EAP-AKA')
Normatively referenced by — RFC 9820: Authentication Service Based on the Extensible Authentication Protocol (EAP) for Use with the Constrained Application Protocol (CoAP)
Normatively referenced by — RFC 9965: The eap.arpa. Domain and Extensible Authentication Protocol (EAP) Provisioning
Informatively referenced by — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informatively referenced by — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Informatively referenced by — RFC 4949: Internet Security Glossary, Version 2
Informatively referenced by — RFC 6973: Privacy Considerations for Internet Protocols
Informatively referenced by — RFC 4282: The Network Access Identifier
Informatively referenced by — RFC 6733: Diameter Base Protocol
Informatively referenced by — RFC 5056: On the Use of Channel Bindings to Secure Channels
Informatively referenced by — RFC 6709: Design Considerations for Protocol Extensions
Informatively referenced by — RFC 5072: IP Version 6 over PPP
Informatively referenced by — RFC 7357: Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol
Informatively referenced by — RFC 7696: Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms