[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [idn] compatibility chars in draft-ietf-idn-nameprep



I think it is more friendly to convert them at entry. But this is no
contradiction: the user agent converts them, afterwards they are not
allowed.

Jony

> -----Original Message-----
> From: owner-idn@ops.ietf.org [mailto:owner-idn@ops.ietf.org]On
> Behalf Of Paul Hoffman / IMC
> Sent: Wednesday, August 16, 2000 6:30 AM
> To: idn@ops.ietf.org
> Subject: Re: [idn] compatibility chars in draft-ietf-idn-nameprep
>
>
> At 8:13 AM +1000 8/16/00, Frank Ernens wrote:
> >I believe that all characters specified by the Unicode
> >standard as compatibility characters should be prohibited.
> >(But not all non-compatibility characters should be allowed.)
>
> These are all very good arguments.
>
> >If the document is amended to say "all Unicode compatibility
> >characters are prohibited", the list of prohibited characters
> >is greatly shortened from what is currently in the document,
> >and may be reducible to a small stable set.
>
> Exactly right. It constrains what users can enter, but this might be
> a Good Thing for stability and manageability.
>
> How do others feel about this proposal?
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>