[Ietf-not43] off-list comments on requirements

[Eric A. Hall]

Eric Brunner-Williams in Portland Maine wrote:

> > 1) The internationalization considerations section should
> > state that names of attributes or tags (or whatever you wish
> > to call them, and this will probably vary depending on the
> > final set of technologies used) should be displayed according
> > to a users locale and the values must be able to support
> > internationalized content.  (why start with an easy one :) )
> 
> This is posing i18n as a presentation probem. You may. I prefer to ask
> "what does this mean if the encoding is EBCDIC?" to help me through to
> the perfection of blindness. Characters can be distracting. If you are
> going down the UNICODE path, don't indicate it by design indirection.

There shouldn't be a requirement for any specific encoding or repertoir,
and none is given, although there should be a nod to the existing IAB
guidelines on the matter. That's pretty much what the drafts requirement
currently does. My request is to define the expected functionality, rather
than the implementation methodology.

I suppose the logical extended verbiage for this would include "specify
how the proposal provides for the necessary i18n and l10n functionality"

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