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.
