UpdatedINFORMATIONALIETF stream

RFC 5422: Dynamic Provisioning Using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST)

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

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

The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) method enables secure communication between a peer and a server by using Transport Layer Security (TLS) to establish a mutually authenticated tunnel. EAP- FAST also enables the provisioning credentials or other information through this protected tunnel. This document describes the use of EAP-FAST for dynamic provisioning. This memo provides information for the Internet community.

Document record

Document ID
RFC5422
Published
March 2009
Authors
N. Cam-Winget; D. McGrew; J. Salowey; H. Zhou
Status
INFORMATIONAL
Stream
IETF
Area
Pages
39
Also known as
Updated by:
RFC 8996

Referenced by

One later RFC formally updates or obsoletes part of this document.

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/5422-dynamic-provisioning-using-flexible-authentication-via-secure-tunneling-extensib