TLS-Based Extensible Authentication Protocol (EAP) Types for Use with TLS 1.3
draft-ietf-emu-tls-eap-types-13

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-emu-tls-eap-types@ietf.org, emu-chairs@ietf.org, emu@ietf.org, jsalowey@gmail.com, paul.wouters@aiven.io, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'TLS-based EAP types and TLS 1.3' to Proposed Standard (draft-ietf-emu-tls-eap-types-13.txt)

The IESG has approved the following document:
- 'TLS-based EAP types and TLS 1.3'
  (draft-ietf-emu-tls-eap-types-13.txt) as Proposed Standard

This document is the product of the EAP Method Update Working Group.

The IESG contact persons are Paul Wouters and Roman Danyliw.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-tls-eap-types/

Ballot Text

Technical Summary

   EAP-TLS (RFC 5216) has been updated for TLS 1.3 in RFC 9190.  Many
   other EAP types also depend on TLS, such as EAP-FAST (RFC 4851), EAP-
   TTLS (RFC 5281), TEAP (RFC 7170), 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.

Working Group Summary

   This document reflects strong consensus from members of the working group
   interested in TLS EAP types. Consensus was in general strong. There are
   areas where there is less implementation experience, but no objection to
   moving forward

   During IETF LC, it was noted an update was needed to the TEAP text to match
   RFC7170bis. This was announced to the WG list to verify no one objects to this
   late change.
   
Document Quality

   A number of vendors are looking to implement this specification. There have
   already been interoperable implementations for most of the methods in the
   document.   EAP-FAST and TEAP are a little behind in implementation.

  
Personnel

   Document Shepherd: Joseph A. Salowey
   Responsible Area Director: Paul Wouters

   The IANA Expert(s) for the registries in this document are Yoav Nir, Rich Salz, Nick Sullivan

RFC Editor Note