> -----Original Message----- > From: Bernard Aboba [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 07, 2007 8:12 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [email protected] > Subject: Re: [Emu] RFC4279 support in draft-simon-emu-rfc2716bis? > > Hannes Tschofenig said: > > >We discussed this already several times and this lead me to > work on a > >draft together with Thomas Otto: > > > >http://tools.ietf.org/id/draft-otto-emu-eap-tls-psk-02.txt > > Which begs the question: what is the WG doing with this draft? >
[Joe] The draft is not currently a working group item. The pre-shared key mechanism charter item is covered by EAP-GPSK. There is a charter item for enhanced EAP-TLS which could support TLS-PSK and other enhancements. > >From where I sit, it seems quite likely that EAP-TLS-PSK, if > completed, > >will > be deployed. When TLS 1.2 is done, this method could > eventually benefit from KDF negotiation, and should meet the > criteria for FIPS 140-2 certification. Given the TLS code > base in embedded systems, it should not be hard to add > support for EAP-TLS-PSK within embedded devices. > [Joe] The KDF needs to be looked at, but I do not think it is necessarily a show stopper, it does provide KDF agility. Reports from people who implemented EAP-GPSK indicate that it was simple to implement. I have heard push back from embedded system implementers on EAP-TLS stating that it is too complex, this may be a result of certificate support I am not sure. > I my doubts about EAP-GPSK on several of these dimensions. > > > > _______________________________________________ > Emu mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/emu > _______________________________________________ Emu mailing list [email protected] https://www1.ietf.org/mailman/listinfo/emu
