[Ietf-not43] l10n/i18n issues

[Andrew Newton]

Eric A. Hall wrote:
> 
> Z.n The service MUST conform to RFC 2277 rules regarding textual data. In
> particular, the protocol and/or schema MUST be able to indicate the
> charset and language in use with unstructured textual data.
> 
> Z.m The service MUST be able to support multiple representations of
> contact data, with these representations complying with the requirements
> in section Z.n. The service SHOULD be able to provide non-ASCII contact
> data in its natural form as well as in US-ASCII.
> 

My stab:

   The schema defining domain related resources MUST conform to RFC 2277
   regarding textual data.  In particular, the schema MUST be able to
   indicate the charset and language in use with unstructured textual
   data.

   The protocol MUST be able to support multiple representations of
   contact data, with these representations complying with the
   requirements in Section XX.  The protocol MUST be able to provide
   contact data in UTF-8 and SHOULD be able to provide contact data in
   US-ASCII and other character sets.

After just re-reading 2277, it says that UTF-8 is a MUST unless a 
variance is provided.

-andy