Sam also suggested to add channel bindings and to address internalization support in a proper way.
Do you mean internationalization?
If so, I'm not quite sure what this means. RFC 4282 supports internationalization of the NAI. Are we talking about internationalization of error messages? For TLS-based EAP methods this will often depend on TLS internationalization support.
With respect to Channel Bindings, it should be understood that no proposals for this have ever been implemented, as far as I am aware. So a first step would be for a method to choose one of the approaches to Channel Bindings and support it (probably as an experimental extension), and then to evaluate the experiment so we can understand how well (or badly) the chosen approach works. At that point we might be ready to support Channel Bindings in other methods.
_______________________________________________ Emu mailing list [email protected] https://www1.ietf.org/mailman/listinfo/emu
