ICANN ICANN Email List Archives

[gnso-idng]


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

[gnso-idng] rethinking IDN gTLDs

  • To: <gnso-idng@xxxxxxxxx>
  • Subject: [gnso-idng] rethinking IDN gTLDs
  • From: "Edmon Chung" <edmon@xxxxxxxxxxxxx>
  • Date: Mon, 30 Nov 2009 06:20:55 +0800

Seems like there are a few important things to clarify/identify to move towards 
a constructive discussion on this.  Most importantly, "timing" seems to be a 
key cause for concern.

Two clarifications which may be useful:

1. Not talk about "FAST" track but rather talk about IDN gTLDs in general and 
whether the DAG (so far) is sufficient

2. Not talk about "TRACKs" in the sense that they may be launched at different 
times, but just that certain processes would be conducted differently

And some observations:

A. Currently the DAG only contemplates completely new IDN gTLDs which are 
unassociated with existing (or future gTLDs)

B. There is clear interest (including from the user community and the 
registries admittedly) to offer a consistent continuum for full IDN experience 
with tightly integrated IDN gTLDs (e.g. that an IDN gTLD would run the same 
zonefile as another gTLD, OR that an IDN gTLD would offer 2LDs only to the same 
registrant as another bundled gTLD)

- Is it possible to distinguish between A and B?
- Would the implementation process look different between A and B?
- It seems clear that for A, confusingly similar strings should not be 
acceptable, but for B, it may be entirely the opposite
- Can an implementation for B be added alongside A?

Edmon


PS. Both A and B can be ongoing and B would apply to future new gTLDs as well 
as existing gTLDs.






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

Privacy Policy | Terms of Service | Cookies Policy