RFC 4072: Diameter Extensible Authentication Protocol (EAP) Application
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4072
- Published
- August 2005
- Authors
- P. Eronen; T. Hiller; G. Zorn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 33
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2867RADIUS Accounting Modifications for Tunnel Protocol SupportCurrent
June 2000
- RFC 2865Remote Authentication Dial In User Service (RADIUS)Updated
June 2000
- RFC 4005Diameter Network Access Server ApplicationObsoleted
August 2005
- RFC 3576Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)Obsoleted
July 2003
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
- RFC 2882Network Access Servers Requirements: Extended RADIUS PracticesCurrent
July 2000
- RFC 2869RADIUS ExtensionsUpdated
June 2000
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?