(Sorry, sent to dev-list by mistake)
> Please accept my vote for this to become an issue.
>
> I think the only way an RSP other than the one who registered the domain
> name should be able to renew it is if the domain name is transferred to
that
> RSP. (I think there should be an automated process for this that makes it
> at least as easy to change RSP's as it is to change registrars. This is in
> OpenSRS's best interest, because if an end user wants to leave their RSP,
> and it is difficult to move to another OpenSRS RSP, they will find another
> registrar.)
>
> "Renew Anywhere" is going to cause a lot of problems with recordkeeping.
> For instance, if my customer adds two years with another RSP, how will I
> ever find out about it?
>
> The biggest part of the work is in the initial registration, dns setup,
> hosting or forwarding configuration. A lot of business models count on a
> stream of future renewals to make money. I don't remember this ever being
> discussed on the list.
>
> ----- Original Message -----
> From: "Scott Allan" <[EMAIL PROTECTED]>
> To: "Chuck Hatcher" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 02, 2001 10:44 PM
> Subject: Re: renewals
>
>
> > On Tue, 2 Jan 2001, Chuck Hatcher wrote:
> >
> > > So the cost of the renewal is charged to the RSP running the renewal
> script,
> > > regardless of which RSP registered the domain name?
> >
> > Yes.
> >
> > > If so, what's to stop me from setting up a renewal site charging
$11.00,
> and
> > > soliciting renewal business from all the clients of all the other
RSP's?
> > > And not have to provide any RSP support or value-added services to
those
> > > clients?
> > >
> > > Wow.
> >
> > Well, we could stop you.
> >
> > You would also have to deal with the customers (collect money) as
> > well as try and market to them and assume costs. Not to mention the
> > fact that customers who are well served by their RSPs won't even
consider
> > trading in their RSP for someone who competes strictly on price.
> >
> > Not to mention the fact that a competent RSP will be able to easily
> > contact the registrants, whereas your rogue RSP would need to use some
> > less conventional method (UCE), and likely have some fall out associated
> > with that.
> >
> > What is to stop you from running a transfer promotion to compete
> > with other RSPs today? How do you compete with all those services that
> > sell below cost?
> >
> > Honestly, if this becomes an issue it is not hard to change it. The
> > reasons behind leaving it unrestricted are:
> >
> > - we generally try and engineer processes to be as simple and open as
> > possible
> > - without RSP to RSP transfers automated it simplifies domain renewal
for
> > registrants who are not happy with their current RSP, or whose RSP does
> > not respond
> >
> > Regards,
> >
> > sA
> >
> >
>
