ICANN ICANN Email List Archives


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

[bc-gnso] Public Comment: One & Two-Character Names in dot-travel

  • To: "BC gnso" <bc-gnso@xxxxxxxxx>
  • Subject: [bc-gnso] Public Comment: One & Two-Character Names in dot-travel
  • From: "BC Secretariat" <secretariat@xxxxxxxxxxxx>
  • Date: Fri, 12 Jun 2009 15:37:47 +0200

News Alert

Public Comment: One & Two-Character Names in dot-travel
10 June 2008

A new public comment period opens today for 30 days on a proposed amendment 
from Tralliance to Appendix 6 and 7 of the dot-travel Registry Agreement.
On 18 May 2009, ICANN posted for public information a request submitted by 
Tralliance through the Registry Services Evaluation Process (RSEP). The 
request calls for a phased allocation process for one and two-character 
names in dot-travel.

The Tralliance proposal is available at 
As provided for by existing consensus policy 
(http://www.icann.org/en/registries/rsep/rsep.html), ICANN performed a 
preliminary review to determine whether the proposal might raise significant 
security, stability, or competition issues. ICANN's determination is that 
the proposal does not raise such issues.
[Note that, from 13 June to 13 July 2008, ICANN conducted a public comment 
forum on a proposed single-character second-level domain names allocation 
which supported the allocation single-character second-level domain names in 
existing registries and reviewed various allocation methods.]

The proposal requires an amendment to the dot-travel Schedule of Reserved 
Names (Appendix 6) and a description of the phased allocation program is 
proposed to be inserted in Section 9 of Appendix 7. A copy of the proposed 
contract amendment is available here [PDF, 20K]. Comments on the proposed 
amendment may be submitted to tralliance-amendment at icann.org through 10 
July 2009 23:59 UTC. Comments may be viewed at 

All documentation related to the Tralliance proposal is available at 
Glen de Saint Géry
GNSO Secretariat


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

Privacy Policy | Terms of Service | Cookies Policy