Perhaps the problem isn't a bad RSP, but a bad client who
did a charge back on the domain name and is now trying to
transfer the domain name and keep it without paying for it.
The losing RSP should have an input into the transfer prior
to it being approved, but should be required to respond
within a certain time frame. If the RSP does not respond in
that time frame with an answer, assume yes, if the RSP
answers no and provides a valid reason, then block the
transfer.
And yes, I know some on this list will respond that one RSP
out of the thousands with OpenSRS may be a bad apple, so
none of the RSPs should be trusted to have an impact on this
decision. Sorry, but I still do not buy the argument that
some day in the far far future there might be a bad RSP, so
let's punish all RSPs today.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Dave
Warren
Sent: Saturday, September 02, 2000 10:31 PM
To: Southpaw/NINEpm; OpenSRS Discussion List
Subject: Re: Transfers in general
>
> i dont agree with the allowing a transfer without the
approval of the
losing
> RSP, i firmly believe the losing rsp should have control
over this and
> opensrs and tucows shouldnt have last word. There could be
other issues
> involved with the transfer and an approval from the losing
rsp helps
protect
> them.
And if the RSP just doesn't get around to answering? Same
as a registrar,
there must be some mechanism. Give 'em 5 days, if they
haven't rejected it,
then assume it's fine.
Otherwise, if I (As a RSP user) was on bad terms with my RSP
and they didn't
want to transfer it, I'd just find another registrar
altogether and forget
OpenSRS and my bad RSP.
