At 11:15 AM 9/7/01 -0400, David Harris wrote:
> > 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. :-)
Thanks for acknowledging our efforts to stay "in bounds". We do take these
issues seriously, as we are somewhat motivated to continue to provide
service to you... :)
>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.
Well, not entirely true, it would be possible for a registrant to change
hie U:P through the public manage interface, therefore locking the reseller
out of any control.
It is also a case of facilitation, not many resellers keep local copies of
the passwords as it requires extra work. It has it's own barriers to entry.
>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.
Well, the theory is that in order you to have lots of registrations, you
must conduct yourself in a responsible manner. I certainly concede that
this is not bullet proof. None of these requirements is ICANN mandated or
sanctioned, in fact most of these challenges exist as a result of ICANN not
understanding the market.
>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.
Reseller deletes are different from end user deletions indeed.
>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.
Well, if he provided name service he might want to update that.
Thanks for your comments - still working on my approach - good stuff though!
sA
