At 11:58 AM 12/20/01 -0800, George Kirikos wrote: >I guess it's evident that all the OpenSRS dropping names are now going >to be skimmed for the quality names.
It is evident that we are considering developing a product for our channel that addresses the demand for the "secondary name" market. >In particular, note that it never dropped (it was expired, but directly >transferred to the new registrant). If you are referring to the fact that the "record created" date has not changed, it is possible that this happens for other reasons. I will investigate. >This is going to set a *bad* precedent. What if NSI starts doing this? NSI registrar already does this in a big way. NSI registry is specifically prevented from doing this. >This opens up a can of worms due to short-sightedness. Grrrrr. :( > >What's worse is that OpenSRS/Tucows advocated a quite different >position in the discussion a few months ago. See: > >http://www.byte.org/rc-deletes/ > >And I quote: > >"It is the recommendation of this document that Verisign Global >Registry Services (VGRS) immediately: > >1. Eliminate the "batch pool" methodology and infrastructure currently >in place as an "interim" measure. >2. Reinstate the previous "first-come, first-served" re-registration >processes. >3. Require that all registrars immediately cease "batch-delete" >processes. >4. Require that all registrars adhere to the 45-day post-expiry >registered name deletion requirements of the Verisign >Registrar/Registry agreements. >5. Police denial of service and other abusive practices by registrars >as required by the Verisign/ICANN registry services agreement." > >Allowing certain parties to cherry-pick the best names is hardly >consistent with the above. I disagree. The points above refer specifically to the "registry" practices wrt names explicitly deleted by registrars. The allegations today stem from the fact that we are "lighting up" (putting in the zone files) expired names at day 40 for names that we have not yet deleted, but intend to. I can also add that we will cease to do this once our testing is complete, which will be in early January (as per our plan). Regards, sA
