I support adopting TEAPv2. While 7170bis clarifies a number of topics, there are still different views on how TEAPv1 should work.
For example, wpa_supplicant has a flag that changes how it uses EMSK with calculations when acting as a TEAP client (peer). https://git.w1.fi/cgit/hostap/commit/?id=795075444fe847e11a04de541c95613335aad7a5 At the moment this doesn't seem to be a problem because there's only one widely used TEAP client (peer) and this client does not have EMSK with the EAP methods it supports. To summarise: even if we have a fresh 7110bis document, I think there's still room for more work which would much help TEAP, its current and future implementations, and ways it can be used. On Mon, 8 Jun 2026 at 05:07, Peter Yee <[email protected]> wrote: > So far, I've only heard two strong statements of support and nothing > against adoption. However, I'd really like to see more than two people > noting their support before I'm comfortable saying we have consensus > to work on TEAPv2. Thus, I've not yet closed the call for adoption. Please, > if you support this work, make your voice heard and post a statement to > the EMU WG mailing list. > > Thanks. > > -Peter > > On 5/12/26, 7:23 PM, "Peter Yee" <[email protected]> wrote: > > TEAP v1 was originally specified in RFC 7170. RFC 7170bis (RFC 9930) > specifies > how TEAP v1 actually was implemented and fielded. Here's our next shot at > TEAP, TEAP v2, which specifies how TEAP ought to work, based on many > learnings from our experiences with TEAP v1. > > As currently given, Alan's I-D is not written as a standalone document. The > expectation is that at some point it will incorporate the text from TEAP v1 > that carries over to v2. > > If you would like to see this document adopted, please reply to the call > for > adoption with your thoughts. Expressions of willingness to review the work > would also be appreciated. Of course, if you think there shouldn't be a > TEAP > v2, you're welcome to say that too! > > -Peter and Joe > > On 5/12/26, 1:12 PM, "Peter Yee via Datatracker" <[email protected]> > 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. > > Authors, and WG participants in general, are reminded of the Intellectual > Property Rights (IPR) disclosure obligations described in BCP 79 [2]. > Appropriate IPR disclosures required for full conformance with the > provisions > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. > Sanctions available for application to violators of IETF IPR Policy can be > found at [3]. > > Thank you. > [1] https://datatracker.ietf.org/doc/bcp78/ > [2] https://datatracker.ietf.org/doc/bcp79/ > [3] https://datatracker.ietf.org/doc/rfc6701/ > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-dekok-emu-teapv2/ > > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-dekok-emu-teapv2-03.html > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-dekok-emu-teapv2-03 > > _______________________________________________ > Emu mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > > > > > > > > _______________________________________________ > Emu mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- Heikki Vatiainen [email protected]
_______________________________________________ Emu mailing list -- [email protected] To unsubscribe send an email to [email protected]
