ICANN ICANN Email List Archives

[tralliance-amendment]


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

Summary & Analysis of Comments

  • To: "tralliance-amendment@xxxxxxxxx" <tralliance-amendment@xxxxxxxxx>
  • Subject: Summary & Analysis of Comments
  • From: Patrick Jones <patrick.jones@xxxxxxxxx>
  • Date: Tue, 14 Jul 2009 14:14:09 -0700

Summary & Analysis of Comments for:
One and Two-Character Domain Names in dot-travel

The comment period ran from 10 June to 10 July 2009. Two comments were received 
during the comment period - one from Cristian Hernan Casas and one from Danny 
Younger. The comment from Cristian Hernan Casas was related to the allocation 
of tur.ar by Argentina's ccTLD manager, and staff replied directly to his 
comment on 26 June 2009 encouraging him to consult with the ccTLD manager. The 
comments on the proposed contract amendment can be found at 
http://forum.icann.org/lists/tralliance-amendment/.

Danny Younger directed his comment to the ICANN Board, noting that caution on 
the Tralliance amendment is strongly advised. See 
http://forum.icann.org/lists/tralliance-amendment/msg00001.html. The comment 
noted previous correspondence to ICANN staff and the Chair of ALAC on 
registration practices by Tralliance and related entities, and cited to UDRP 
decisions involving dot-travel domain names by an entity utilizing dot-travel's 
bulk registration program.

Younger requested that ICANN freeze consideration of Tralliance's request to 
offer single and two-character dot-travel domain names "until such time as its 
officers and their activities pursuant to dot-travel have been thoroughly 
scrutinized." Further, he suggested six steps that ICANN Compliance must 
undertake before the Board makes a determination on the proposed contract 
amendment. He also recommended that ICANN consider Tralliance's activity in 
light of the Post-Delegation Dispute Mechanism proposal in the new gTLD 
Implementation Recommendation Team (IRT) report.

Younger noted "When contracted parties use their registry operations for 
personal gain, rather than for the benefit of the community they represent, 
ICANN needs to step up so that the community may be protected. The history of 
the operation of the dot travel registry is such that a strong case for 
redelegation to another operator could well be made. Do not reward this 
operator any further."

--
Patrick L. Jones
Registry Liaison Manager &
Support to ICANN Nominating Committee
Internet Corporation for Assigned Names & Numbers
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1 310 301 3861
patrick.jones@xxxxxxxxx
patrickjones.tel






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

Privacy Policy | Terms of Service | Cookies Policy