> On UTF-8:
>
>> The other question is whether there are any restrictions on what
>> Unicode characters can be represented.  You make the colon a special
>> character but give no other restrictions, so an objective name could
>> include space characters (and various related Unicode characters such
>> as tab, EN SPACE, ZERO WIDTH SPACE, and ZERO WIDTH NON-JOINER),
>> control characters (FORM FEED, CARRIAGE RETURN, and the like),
>
> Once we specify byte-by-byte comparison, do we need to worry about
> this in a protocol document? If someone is silly enough to
> specify an objective called 'example.org:Недостаточно握 déjà     vu
> ' do we care, in the protocol design?
>
> Personal opinion: we don't need to say anything.

That's probably correct, and I just wanted to be sure y'all had
thought about it -- more whether there'd be an issue with
space-related characters or confusibles than about real non-Latin
languages or pile-of-poo icons.

Thanks for addressing my comments!

Barry

_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima

Reply via email to