Re: [ietf-provreg] Re: EPP Extensions for IDN

["Tan, William" <William.Tan@Neustar.biz>]

I apologize for coming into this thread late.

I'm not sure how to interpret "IDN deals with scripts", because if IDN 
were to "deal" with anything, it would be a sequence of characters from 
the Unicode character repertoire. Now, that's not saying much either.

If I understand correctly, this is trying to capture a best practice / 
recommendation to restrict label registrations to only contain 
characters from a certain *table*, and that the table in defined in 
terms of scripts instead of languages.

Now, I'm not sure if this WG is really in the business of recommending 
registry policies. There is definitely a need for some form of a tag, 
especially in gTLD registries implementations, to facilitate checking 
for the rule that all characters within the requested label must fall 
within a single table.

IMHO the content of such a tag, if used, should be left up to the 
implementation. One registry might use ISO15924-based script codes, or 
RFC4646 tags, or ISO639-based codes.

=wil


Stephane Bortzmeyer wrote:
> On Fri, Apr 06, 2007 at 02:25:08PM +0200,
>  Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
>  a message of 8 lines which said:
>
>   
>> In the case you mention (chinese characters), yes, but it is not a
>> general rule.
>>     
>
> Joe Abley kindly explained that I could have say it in a better
> way. Here is a new attempt (and I suggest that a similar sentence be
> included in the I-D if someone wants to revive an EPP extension for
> IDN):
>
> ***************
>
> IDN deals with scripts, not with languages. Asking what is the
> language of an IDN domain name is often irrelevant and sometimes
> meaningless (many corporate trademarks are not words in any human
> language, for instance).
>
> In the vast majority of writing systems, knowledge of the language
> being represented is not necessary.
>
> The Chinese/Japanese case described in RFC 3743 is a prominent example
> of where the language may be relevant.
>
>
>