The _procedure_ should not be transparent to the end user, only the
_difference_ between the RSP-to-RSP procedure and the registrar-to-registrar
procedure. In either case, it should be obvious to the end user that a
substantive change is taking place, and they must authorize the change
deliberately after receiving an email verification. It should be an easy
process, but an obvious and unambiguous one.
In my view, the process should not be designed to eliminate competition, but
to make it just as easy to switch RSP's as it already is to switch
registrars. At least then when an end user is dissatisfied with one OpenSRS
RSP, the others still have a chance. It certainly can't eliminate lowball
pricing, sleazy marketing tactics, spam, or any number of other evils.
For me personally, the #1 most important feature is to be informed when a
customer is leaving (assuming such a thing could *ever* happen!)
----- Original Message -----
From: "Jim McAtee" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 10, 2001 9:43 PM
Subject: Re: Plans for Automated RSP Transfers?
> With the "renew anywhere" implementation, someone brought up the
possibility
> of an RSP offering cheap renewals, maybe $11 per year, and then marketing
> directly to your registration customers. If the RSP to RSP procedure is
> made totally transparent to the end user, and truly no different from
> registrar to registrar transfers, what's to prevent exactly the same
> situation?
>
> Then again, is this situation any different than someone that
sells/resells
> registrations from another registrar contacting those same customers when
> their domain registration comes due?
>
> I'm not arguing one way or the other, just trying to get a better idea of
> the implications of such a system.
>
> Jim
>
>
> ----- Original Message -----
> From: "Chuck Hatcher" <[EMAIL PROTECTED]>
> To: "Tiger Technologies" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, January 10, 2001 4:02 PM
> Subject: Re: Plans for Automated RSP Transfers?
>
>
> > I agree - let the OpenSRS server decide whether it's a registrar
transfer
> or
> > an RSP transfer. That would be the best solution from an RSP's point of
> > view, as well as for the end user. More choices, less hassles. I would
> add
> > one very important feature - notification to the losing RSP when the
> > transfer occurs. I will leave it to others to decide whether or not the
> > losing RSP should be able to prevent a transfer for any reason.
> >
> > A server-side process has the added benefit of being "bug-fixable"
without
> > releasing a new client.
>
>
>
