ICANN/GNSO GNSO Email List Archives

[council]

<<< Chronological Index >>>    <<< Thread Index >>>

[council] Re: Regarding issues report on IDNs

  • To: GNSO Council <council@xxxxxxxxxxxxxx>
  • Subject: [council] Re: Regarding issues report on IDNs
  • From: Cary Karp <ck@nic.museum>
  • Date: Mon, 06 Feb 2006 10:47:06 +0100
  • Cc: John C Klensin <klensin@xxxxxxx>, Patrik Fältstrom <paf@xxxxxxxxx>, Tina Dam <dam@xxxxxxxxx>
  • In-reply-to: <43E712F0.40402@nic.museum>
  • References: <355313303-1139066387-cardhu_blackberry.rim.net-8820-@engine88> <EABA9ABB250C96DD0D778699@7AD4D3FB4841A5E367CCF211> <fdcd4ef30602052323u1b145dban@mail.gmail.com> <43E712F0.40402@nic.museum>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • User-agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
This is a brief P.S. to my previous message, saving someone else the
trouble of pointing it out :-)

> However, very few TLD labels are words in specific languages. The
> ccTLD labels are deliberately restricted to a list of codes, and of
> the few labels in the gTLD 'vocabulary' that actually appear in the
> English dictionary, not all are defined there in the sense that the
> label is being presented to users.

A few of the ccTLD labels also happen to be words in one or another
language. Similarly, others have strong mnemonic associations external
to their intended purpose. These generate TLD policy considerations
all of their own which (as should surprise nobody) will become
massively more complex when the TLD space is IDNified.

/Cary
<<< Chronological Index >>>    <<< Thread Index >>>