At 9/7/01 5:53 AM, Scott Allan wrote:
>Thanks for this feedback - I have felt for some time we should re-examine
>this issue. I have a couple of further concepts for your consideration
>along these lines...
>
>1. I assume "easy" deletes after 4-5 days would be desired as well - no
>refund, but still useful when a registrant wants to get rid of a name
>(typically for legal reasons) -
Yes, that would be useful. We have had a couple of these where the owner
is being sued by someone for various reasons and wants us to remove it
completely so it can be re-registered by the other party (and they aren't
on good enough terms to do a transfer without expensive lawyers getting
involved).
Also, it'd be nice to get rid of the odd fraudulent order without
cluttering up our records or bugging OpenSRS support.
But that would be a lower priority for us -- I was mostly interested in
being able to fix the odd typographical mistake/fraudulent order that
becomes apparent within 48 hours or so.
>2. Would there be any strong opposition to mandatory (somewhat
>customizable) registrant email notification for deletes?
That sounds like a good idea. In the case of deletion due to typo, the
user wouldn't care and would appreciate the full disclosure.
However, you'd probably have to come up with a policy for disputes: what
if the reseller says he's deleting it because the registration is
fraudulent, but the end-user says it's legitimate and should not be
deleted? A sticky issue. And obviously you'd have only a couple of days
to resolve it before people get charged.
Hmmm. If that would be a sticking point, you could start off by making it
so that the registrant has to confirm deletion, which would at least be
useful in the case of typos.
>3. Reseller trust - I have thought long and hard about implementing some
>sort of preferred trusted status for resellers, with the thinking being
>that some extra functionality (perhaps deletes, manage name for registrant
>or manage nameserver for registrant) could be extended if you qualify. My
>(very preliminary) thinking is something along the lines of:
>
>- demonstrated monthly (over 3 months) volume of 25 name years
>- proof of over 500 sponsored names with any registrar (to allow people who
>are switching the ability to get the status)
That would be be welcome. As long as meeting the criteria requires more
effort than modifying manage.cgi/reg_system.cgi to record passwords, it
won't cause any problems you don't already have.
--
Robert L Mathews, Tiger Technologies
