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, sounds good.
> 2. Would there be any strong opposition to mandatory (somewhat
> customizable) registrant email notification for deletes?
I'm ok with that. If this is part of what you need to do to put deletes into
my hand, so be it. Please keep ICANN happy so we can all continue to get
service from you. :-)
> 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)
>
> Is this a silly idea?
Curious. Because of how the client scripts, you give "manage name for
registrant" privileges to anyone who sets up a local password database. This
looked like a funny legal maneuver so that we could have this ability
without OpenSRS endorsing it or providing tools.
I'm not sure that having more domain registrations proves an RSP more
trustworthy. Many scummy business practices have come from large companies.
How does the RSP's size make a difference in the ICANN legal agreements? But
if this will satisfy ICANN, go for it. I'm sure some RSPs would enjoy being
freed from maintaining password databases.
I'm surprised that you placed "delete name" in the same category as "manage
name for registrant"... well, that does make sense if the RSP deletes the
name instead of the client. BUT! What if the client deletes the name through
a button on manage.cgi? This is then a client-initiated action and perhaps
not needing RSP trust.
When a name is deleted by the client, the RSP would be notified of the
change. If inside the grace period, the RSP can refund the money or let the
client register another name. If outside the grace period, then the RSP
doesn't need to do anything.
Then, RSP's with password databases can use the delete feature without being
certified as "trusted". And all other RSP's simply have the registrant
perform the delete.
> Thanks again for your feedback -
Welcome!
David
