Handling Large Certificates and Long Certificate Chains in TLS-based EAP Methods
draft-ms-emu-eaptlscert-03
| Document | Type |
Replaced Internet-Draft
(emu WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohit Sethi , John Preuß Mattsson , Sean Turner | ||
| Last updated | 2019-08-12 (Latest revision 2019-05-26) | ||
| Replaced by | RFC 9191 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-emu-eaptlscert | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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 memo looks at the this problem in detail and describes the potential solutions available.
Authors
Mohit Sethi
John Preuß Mattsson
Sean Turner
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)