UpdatedINFORMATIONALIETF stream

RFC 4851: The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST)

Still current, but amended. Parts of this document are changed or extended by RFC 8996, RFC 9427. Read both.

In plain English — editorial summary, not part of the RFC

This document defines the Extensible Authentication Protocol (EAP) based Flexible Authentication via Secure Tunneling (EAP-FAST) protocol. EAP-FAST is an EAP method that enables secure communication between a peer and a server by using the Transport Layer Security (TLS) to establish a mutually authenticated tunnel. Within the tunnel, Type-Length-Value (TLV) objects are used to convey authentication related data between the peer and the EAP server. This memo provides information for the Internet community.

Document record

Document ID
RFC4851
Published
May 2007
Authors
N. Cam-Winget; D. McGrew; J. Salowey; H. Zhou
Status
INFORMATIONAL
Stream
IETF
Area
Pages
64
Also known as
Updated by:
RFC 8996, RFC 9427

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.

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?

canonical URL: /rfc/4851-the-flexible-authentication-via-secure-tunneling-extensible-authentication-proto