Diameter Extensible Authentication Protocol (EAP) Application
RFC 4072
Document | Type |
RFC - Proposed Standard
(August 2005; Errata)
Was draft-ietf-aaa-eap (aaa WG)
|
|
---|---|---|---|
Authors | Tom Hiller , Glen Zorn , Pasi Eronen | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4072 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Bert Wijnen | ||
Send notices to | (None) |
Network Working Group P. Eronen, Ed. Request for Comments: 4072 Nokia Category: Standards Track T. Hiller Lucent Technologies G. Zorn Cisco Systems August 2005 Diameter Extensible Authentication Protocol (EAP) Application Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). Abstract The Extensible Authentication Protocol (EAP) provides a standard mechanism for support of various authentication methods. This document defines the Command-Codes and AVPs necessary to carry EAP packets between a Network Access Server (NAS) and a back-end authentication server. Table of Contents 1. Introduction ...................................................2 1.1. Conventions Used in This Document ........................3 2. Extensible Authentication Protocol Support in Diameter .........3 2.1. Advertising Application Support ..........................3 2.2. Protocol Overview ........................................4 2.3. Sessions and NASREQ Interaction ..........................6 2.3.1. Scenario 1: Direct Connection .....................7 2.3.2. Scenario 2: Direct Connection with Redirects ......8 2.3.3. Scenario 3: Direct EAP, Authorization via Agents ..9 2.3.4. Scenario 4: Proxy Agents .........................10 2.4. Invalid Packets .........................................10 2.5. Retransmission ..........................................11 2.6. Fragmentation ...........................................12 2.7. Accounting ..............................................12 2.8. Usage Guidelines ........................................13 Eronen, et al. Standards Track [Page 1] RFC 4072 Diameter EAP Application August 2005 2.8.1. User-Name AVP ....................................13 2.8.2. Conflicting AVPs .................................13 2.8.3. Displayable Messages .............................14 2.8.4. Role Reversal ....................................14 2.8.5. Identifier Space .................................14 3. Command-Codes .................................................14 3.1. Diameter-EAP-Request (DER) Command ......................15 3.2. Diameter-EAP-Answer (DEA) Command .......................16 4. Attribute-Value Pairs .........................................18 4.1. New AVPs ................................................18 4.1.1. EAP-Payload AVP ..................................18 4.1.2. EAP-Reissued-Payload AVP .........................18 4.1.3. EAP-Master-Session-Key AVP .......................19 4.1.4. EAP-Key-Name AVP .................................19 4.1.5. Accounting-EAP-Auth-Method AVP ...................19 5. AVP Occurrence Tables .........................................19 5.1. EAP Command AVP Table ...................................20 5.2. Accounting AVP Table ....................................21 6. RADIUS/Diameter Interactions ..................................22 6.1. RADIUS Request Forwarded as Diameter Request ............22 6.2. Diameter Request Forwarded as RADIUS Request ............23 6.3. Accounting Requests .....................................24 7. IANA Considerations ...........................................24 8. Security Considerations .......................................24 8.1. Overview ................................................24 8.2. AVP Editing .............................................26 8.3. Negotiation Attacks .....................................27 8.4. Session Key Distribution ................................28 8.5. Privacy Issues ..........................................28 8.6. Note about EAP and Impersonation ........................29 9. Acknowledgements ..............................................29 10. References ....................................................30 10.1. Normative References ....................................30Show full document text