On Tue, 12 May 2026, at 12:12, Peter Yee via Datatracker wrote: > This message starts a emu WG Call for Adoption of: > draft-dekok-emu-teapv2-03 > > This Working Group Call for Adoption ends on 2026-05-26 > > Abstract: > This document defines the Tunnel Extensible Authentication Protocol > (TEAP) version 2. It addresses a number of security and > interoperability issues which were found during the publication of > TEAPv1 ([I-D.ietf-emu-rfc7170bis]). > > Please reply to this message and indicate whether or not you support adoption > of this Internet-Draft by the emu WG. Comments to explain your preference are > greatly appreciated. Please reply to all recipients of this message and > include this message in your response.
I support adoption. TEAP version one is an EAP method (the only one?) that describes chained authentication, crypto-bindings and provisioning. Unfortunately that extra functionality is not usable in its current form for various reasons and as such implementations today offer little materially beyond what EAP-(T)TLS and PEAP already do. I would like to see a 'working' TEAP that offers this promised functionality and see that a TEAPv2 is one of the better options to realise this; other than creating a new EAP method from scratch. Crucially, a TEAPv2 would expand on already existing TEAPv1 implementations which (hopefully) will make adoption by the supplicant vendors more likely. Cheers Alex _______________________________________________ Emu mailing list -- [email protected] To unsubscribe send an email to [email protected]
