The core chartered requirements also include the use of the tunnel
method for password authentication, so it is important to consider this
case.   

In addition, there is a proposal for defining conventions for defining
generic textual attributes within the tunnel.  I think the main
advantage of doing this would be to have a consistent approach to
internationalization.   If this is too difficult, perhaps it should be
dropped, although I'm not sure these requirements would be too different
form what is needed for password authentication.  

Joe

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On 
> Behalf Of Bernard Aboba
> Sent: Monday, August 10, 2009 12:09 AM
> To: [email protected]
> Subject: Re: [Emu] #18 Internationalization
> 
> 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. 
> 
> 
> 
> 
> <http://im.live.com/Messenger/IM/Home/?source=EML_WLHM_GreaterGood> 
>       
> 
_______________________________________________
Emu mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/emu

Reply via email to