File formats:

Also available: XML file for editing

 

Status:

INFORMATIONAL

Authors:

M. Sethi
J. Preuß Mattsson
S. Turner

Stream:

IETF

Source:

emu (sec)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9191

Discuss this RFC: Send questions or comments to the mailing list emu@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9191

Abstract

The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides a standard mechanism for support of multiple authentication methods. EAP-TLS and other TLS-based EAP methods are widely deployed and used for network access authentication. Large certificates and long certificate chains combined with authenticators that drop an EAP session after only 40 - 50 round trips is a major deployment problem. This document looks at this problem in detail and describes the potential solutions available.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.