Joe Salowey said: "#18: Internationalization
Is the use of UTF-8 sufficient or is other tagging necessary. The following cases need to be considered: 1. Usernames and passwords 2. Prompts and error associated with username and password authentication 3. Other textual data " It's important to keep in mind that this is a tunnel method requirements document. The tunnel method will use TLS, so as far as bringing up the tunnel is concerned, it is TLS internationalization that is relevant here. With respect to inner authentication methods, it is the internationalization support of the inner method that matters. Given this, what exactly is within the purview of the tunnel method with respect to internationalization? Clearly, the EMU WG is not chartered to change EAP itself, TLS or existing EAP methods. Given that, what *exactly* does this requirement refer to? While it's certainly possible for a tunnel method to do language negotiation, given that such a negotiation wouldn't affect most of what goes on in the method (e.g. TLS or the inner method), I don't see what good it would do.
_______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
