(sorry for the duplicate; I sent this first with incorrect email address which did not go through to the mailing list)
On Sat, Nov 18, 2006 at 09:43:40AM -0800, Bernard Aboba wrote: > While I would expect that RFC 3748-compliant implementations will take less > than 7 years to appear, we are still only at the beginning of the road. > For example, there are no RFC 3748-compliant implementations shipping yet; > we have not had an RFC 3748 bakeoff demonstrating interoperability between > two distinct implementations with respect to new RFC 3748 features > (including the EMSK); no open source RFC 3748-compliant implementations > exist yet. The current development branch for wpa_supplicant (EAP peer) and hostapd (EAP server) includes support for most of RFC 3748, including EMSK derivation in many of the EAP methods and use of expanded types. Sure, EMSK is not currently used for anything, but at least it is included in the EAP method interface and the programs are ready to start using it once suitable use of EMSK is specified. I would be interested in running interoperability tests for RFC 3748 features with other implementations. I haven't tested EMSK derivation with another implementation, but expanded types have been tested with other implementations. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Emu mailing list [email protected] https://www1.ietf.org/mailman/listinfo/emu
