> I totaly disagree that the current RSP should have no say in transfers,
> whether to another RSP or to another Registrar.
But this should be consistant, reguardless of who it's being transferred to,
right?
>
> 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?
True. but we have no say when it's transferred to another registrar, so why
should the "new" RSP be placed at a disadvantage just because the previous
registrar is an RSP?
> 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.
As a customer, if I am annoyed at my current RSP, I do not want to go
through extra hassle to transfer to another RSP. If that's the case, I'll
just go to another registrar altogether. The RSP loses, OpenSRS loses, and
ultimately, the customer loses.
> 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.
And if a problem client decides to leave, as far as I'm concerned, all power
to them. Regardless of what the problem is (RSP, RSP's service, personal
problems with the RSP, or the customer), why place obstacles in the way of
keeping the client? Why make it harder for the client to stay with OpenSRS
RSPs? As soon as it's easier to go somewhere else altogether, most
customers will.
