[Simple] Re: [Geopriv] Domain identifier in common policy

[Henning Schulzrinne <hgs at cs.columbia.edu>]

I don't feel strongly about this; my only gut feeling is that it is a 
good thing to reduce options that don't add value. As far as I know, the 
set of strings representable by UTF-8 is exactly the same as the one 
representable in UTF-16. What is the advantage of allowing UTF-16?

(One disadvantage is that any comparison would have to convert to a 
common format if both are allowed.)

> > Common policy MUST use UTF-8 to store domain names in 'id' domain 
> > attributes. For non-IDNs, lower-case ASCII SHOULD be used.

> Is "MUST use UTF-8" intended to purposefully rule out UTF-16, which all 
> XML parsers are required to understand?  That is fine if it is, but this 
> would seem to then restrict the document to UTF-8.  If this is a 
> protocol requirement, it needs to be stated.
>
> -andy


_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple