[Ietf-not43] [Fwd: I-D ACTION:draft-ietf-rescap-rc-01.txt]

[Eric A. Hall]

Eric Brunner-Williams in Portland Maine wrote:

> >> names to be internationalized easily, while RC relies on ASCII
> >> strings which is less straightforward (and internationalization
> >> needs to be added to the requirements doc, btw).
> 
> I wish I knew what "internationalized" means. Is it:

I probably should have said localization. What I am thinking about in
particular is that the not43 "client" uses locale data to present
attribute names to the user in the appropriate language for that user.
Rather than having the server generate "Name:" the client generates "Nom:"
or whatever is appropriate for the local user, and using OIDs for the
identifiers makes this localization simpler for the clients.

The data has to support internationalized values, but that stuff probably
shouldn't be translated on-the-fly. It may be prudent to specify that
things like postal addresses, etc, should be stored in the system in
English so that international mail delivery works, however.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/