How about a "hold" flag for RSP's to set? If the flag is not set,
automatically process any transfer (to another registrar or to another RSP)
as usual, contacting the admin contact for authorization. If the flag is
set, contact the RSP for details of why the domain name should not be
transferred.
----- Original Message -----
From: "easygoing" <[EMAIL PROTECTED]>
To: "Jim McAtee" <[EMAIL PROTECTED]>; "OpenSRS Discussion List"
<[EMAIL PROTECTED]>
Sent: Thursday, November 23, 2000 10:41 PM
Subject: RE: transfer a domany registered under opensrs
> I totaly disagree that the current RSP should have no say in transfers,
> whether to another RSP or to another Registrar.
>
> What happens if a client registers the domain, charges it back through his
> bank and then has the domain transferred to another RSP or Registrar?
>
> OpenSRS should check with the current RSP prior to approving transfers
away
> from OpenSRS by a RSP's client. And all clients are RSP clients, as
OpenSRS
> states that they do not sell directly to the retail public.
>
> Given the quality of service at OpenSRS, with the excellent method of
> allowing retail clients to manage their domain names, why would a client
> attempt to go to another Registrar unless there was a problem with the
RSP?
> Given that, OpenSRS should check with the RSP to determine the problem
> before taking action.
>
> If the RSP is the problem, then OpenSRS should take steps to remove the
RSP
> from the system. But I suspect 99% of the problems will be the client,
not
> the RSP.
