RE: Single-letter names (was: Re: Update of RFC 2606 based on the recent ICANN changes?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I feel that Edmon's report of the ICANN/GNSO point of view and the positions of James Seng are shared by most of the groups we relate with (Internet @large, open roots, ISO lobbies, Multilinc, MINC, Eurolinc, ISOC France, ccTLDs, etc.). If this WG does not think they are technically adequate there would certainly be a real urgency to document why, to have it confirmed by the IAB, and disseminated. This is due to the constraints a change would introduce outside of the Internet community and the général awareness of this debate after the Paris meeting. This WG needs to speak up now, or status quo will be considered as definitly settled.

I expect one single sign (logo) gcTLDs [geocultural] to be documented this year for multilingual information machines (airports, transports, health, kids, disabled). BTW this is also why I would recommend to refer to the semiotic rather than to the semantic aspects.
jfc

At 01:33 05/07/2008, Edmon Chung wrote:
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

_______________________________________________

Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]