<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [ga] Care needed over the .travel Registry Agreement
- To: Richard Henderson <richardhenderson@xxxxxxxxxxxx>, General Assembly of the DNSO <ga@xxxxxxxxxxxxxx>
- Subject: Re: [ga] Care needed over the .travel Registry Agreement
- From: Hugh Dierker <hdierker2204@xxxxxxxxx>
- Date: Sun, 3 Apr 2005 00:39:18 -0800 (PST)
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=KD4gp5H6B8Rx5MgvoX1Wg/iyPbSM2M49+AFtZoQEto5e9M+joBJ22lMBJRxNRYabpZisu5t/1alO6e0bZOokzVT+KhrZKTUYsbo4sRmDA5CvOQdo2hmMCi+Lv+XSUUARS9A+WT4qYYVkSgal7hkhJA6KIHYwjMTb57OEoXCvfqo= ;
- In-reply-to: 6667
- Sender: owner-ga@xxxxxxxxxxxxxx
Richard,
Let me ask it simply, who cares?
I mean I do, but who cares? if I do? What impact does this have. Certainly all who spend money in these spaces know that the rules are funny and who cares?
e
Richard Henderson <richardhenderson@xxxxxxxxxxxx> wrote:
I wonder what provisions ICANN propose to make to ensure that a restricted TLD like .travel does not get "invaded" by uncertified "gatecrashers" like the thousands who have obtained domains in recent weeks from another restricted TLD: .pro?
The registrar EnCirca used a loophole in the ICANN Registry Agreement to act as "proxy registrant" for thousands of customers, so that the applicants could avoid the rigorous checks and authorisations which were meant to "restrict" the TLD to certain categories of users.
Now we have the prospect of .travel, also intended to be restricted to authorised categories of people, but what is there to stop the same device being used to get round the "roadblock", with one eligible entity using their eligibility to act as "proxy registrant" to thousands of unchecked and unauthorised domain speculators and, in theory, the entire human race?
This seems a matter which needs urgent attention over the drafting of the agreement, or history may repeat itself, and the whole concept of "restricted TLDs" will be called into question.
I would also argue that ICANN should reserve the right, in the wording of the Agreement, to enforce amendments to this Agreement, where it considers that the integrity and stability of the registry is threatened - see, for example, the wording for the .us TLD:
http://www.nic.us/registrars/accreditation/usTLD_AdministratorRegistrar_Agreement.pdf
"usTLD Administrator reserves the right to deny, cancel or transfer any registration that it deems necessary, in its discretion; (1) to protect the integrity and stability of the registry" (my thanks to the ICANN director who pointed this up to me earlier this week, stressing the word "Integrity")
I would argue that ICANN should reserve the right, not only to cancel registrations that undermine the integrity of the TLD and its Agreement, but also the right to intervene and amend the Registry Agreement itself, where blatant loopholes are discovered and exploited. This right of intervention and amendment should be a unilateral right, if the TLD itself will not co-operate.
Yrs,
Richard Henderson
---------------------------------
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|