TLS-based EAP types and TLS 1.3
draft-ietf-emu-tls-eap-types-01
The information below is for an old version of the document.
| Document | Type | Expired Internet-Draft (emu WG) | |
|---|---|---|---|
| Author | Alan DeKok | ||
| Last updated | 2021-01-30 (Latest revision 2020-07-29) | ||
| Replaces | draft-dekok-emu-tls-eap-types | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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 can be found at:
https://www.ietf.org/archive/id/draft-ietf-emu-tls-eap-types-01.txt
https://www.ietf.org/archive/id/draft-ietf-emu-tls-eap-types-01.txt
Abstract
EAP-TLS [RFC5216] is being updated for TLS 1.3 in [EAPTLS]. Many other EAP [RFC3748] and [RFC5247] types also depend on TLS, such as FAST [RFC4851], TTLS [RFC5281], TEAP [RFC7170], and possibly many vendor specific EAP methods. This document updates those methods in order to use the new key derivation methods available in TLS 1.3. Additional changes necessitated by TLS 1.3 are also discussed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)