ICANN/GNSO GNSO Email List Archives

[council]


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

RE: [council] Issue for IDN discussion

  • To: "'Council GNSO'" <council@xxxxxxxxxxxxxx>
  • Subject: RE: [council] Issue for IDN discussion
  • From: "Edmon Chung" <edmon@xxxxxxxxxxx>
  • Date: Thu, 6 Dec 2007 08:19:34 +0800
  • In-reply-to: <41C2559F-C0D4-40BD-A292-5BB120FA37E6@psg.com>
  • List-id: council@xxxxxxxxxxxxxx
  • Organization: DotAsia Organisation
  • References: <41C2559F-C0D4-40BD-A292-5BB120FA37E6@psg.com>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: Acg3kPXgqlCD9N/jTd+tZfVHdkjdWwAAISyQ

> To what extent is there support within the council for the allocation
> of at most 1 IDN in 1 Script per 3166-1 based ccTLD by methods chosen
> by the IDNC fast track WG, so long as it is clearly understood  that
> no other allocations may be made until such time as there is a
> community wide discussion and agreement of any further re-allocation
> of gNSO namespace to the ccNSO?

The question itself may be problematic I think.  And is one which the ccTLDs 
themselves are avoiding.  I do not think specifying "at most 1 IDN in 1 Script 
per 3166" is a good idea.  It may appear that we have not heard some of the 
sensitivities and concerns from the local communities.  i.e. I worry it would 
not be seen as supportive for the fast track (which I think is the original 
intent).

I feel that simply indicating that we are supportive of a fast track concept 
given that it is a more contained "experimental" process would be more 
appropriate than specifying 1-IDN-1-cc.

Edmon







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