ICANN/GNSO GNSO Email List Archives

[registrars]


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

RE: [registrars] Verisign batch pool advisory

  • To: "'Bhavin Turakhia'" <bhavin.t@xxxxxxxxxxxxxx>, "'Bhavin Turakhia'" <bhavin.t@xxxxxxxxxxx>, "'Registrars Constituency'" <registrars@xxxxxxxx>
  • Subject: RE: [registrars] Verisign batch pool advisory
  • From: "Tim Ruiz" <tim@xxxxxxxxxxx>
  • Date: Wed, 6 Oct 2004 10:22:02 -0500
  • Importance: Normal
  • In-reply-to: <200410061312.i96DCY6A000509@smtp-mtc05.proxy.aol.com>
  • Sender: owner-registrars@xxxxxxxxxxxxxx

Bhavin,

The forgiveness component consists of two criteria:

1. Fewer than 350,000 names under management, and 

2. A ratio of attempted add commands to successful add commands of less than
200 to 1.

So at least the top 20 or so registrars will still not qualify for
forgiveness.

Tim


-----Original Message-----
From: Bhavin Turakhia [mailto:bhavin.t@xxxxxxxxxxxxxx] 
Sent: Tuesday, October 05, 2004 10:43 PM
To: 'Tim Ruiz'; 'Bhavin Turakhia'; 'Registrars Constituency'
Subject: RE: [registrars] Verisign batch pool advisory


> So while option 1 may not be ideal either, for now, it will 
> make the usefulness of the *phantom* registrars pretty much nil.
> 
> Also, with Network Solutions' and Tucows' intention to offer 
> a secondary market service to registrants with 
> expiring/deleting names, far less valuable names are going to 
> actually hit the drop list anyway. So I think the future 
> value of the batch pool is going to change dramatically.

My greater concern is that implementing 1 will result in a situation where
icann will not meet its budget sinc everyone will match the forgiveness
criteria.

Im still out on the road all of this week and will only be back in office
after 2 weeks ..... And therefore will be a lil quiet :)

-B





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