Update of RFC 2606 based on the recent ICANN changes?

Edmon Chung mail at edmon.asia
Fri Jul 4 02:46:40 CEST 2008


Regarding single Unicode code-point labels at the TLD level, there was quite
some discussion on this topic at the GNSO Reserved Names working group and
then at the new gTLD discussion.  The final recommendation from the GNSO
was:

"Single and two-character U-labels on the top level and second level of a
domain name should not be restricted in general. At the top level, requested
strings should be analyzed on a case-by-case basis in the new gTLD process
depending on the script and language used in order to determine whether the
string should be granted for allocation in the DNS. Single and two character
labels at the second level and the third level if applicable should be
available for registration, provided they are consistent with the IDN
Guidelines."

As for ASCII, the recommendation was:
"We recommend reservation of single letters at the top level based on
technical questions raised. If sufficient research at a later date
demonstrates that the technical issues and concerns are addressed, the topic
of releasing reservation status can be reconsidered."

Edmon



> -----Original Message-----
> From: idna-update-bounces at alvestrand.no [mailto:idna-update-
> bounces at alvestrand.no] On Behalf Of Vint Cerf
> Sent: Friday, July 04, 2008 7:05 AM
> To: James Seng
> Cc: John C Klensin; idna-update at alvestrand.no; ietf at ietf.org; Lyman Chapin
> Subject: Re: Update of RFC 2606 based on the recent ICANN changes?
> 
> seems odd to me too, James.
> 
> vint
> 
> 
> On Jul 3, 2008, at 6:14 PM, James Seng wrote:
> 
> >> At the moment, the condition is "no single Unicode code point." To
> >> the extent that a single CJK ideograph can be expressed using a
> >> single Unicode code point, this would represent the situation to
> >> which you say you would object. I will dig through my notes to find
> >> out why the "single character" condition was adopted -
> >
> > Would you be able to explain why the condition is "no single Unicode
> > code point"? Whats the technical basis for that?
> >
> > -James Seng
> > _______________________________________________
> > Idna-update mailing list
> > Idna-update at alvestrand.no
> > http://www.alvestrand.no/mailman/listinfo/idna-update
> 
> _______________________________________________
> Idna-update mailing list
> Idna-update at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/idna-update



More information about the Idna-update mailing list