Re: renewals

From: Don Brown (donbrown_l@inetconcepts.net)
Date: Wed Jan 03 2001 - 15:28:02 EST


At 12:39 PM 1/3/01 -0500, you wrote:
>At 11:06 PM 1/2/01 -0500, Chuck Hatcher wrote:
>>Please accept my vote for this to become an issue.
>
>Accepted.
>
>>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.)
>
>Agreed.
>
>Again, as I think back as to why this approach was taken, it probably had
>a lot to do with not having automated RSP to RSP transfers. So, it was
>certainly a compromise based on missing functionality. Not a good thing.
>
>While I have no problem adding in the restriction, I think it might be
>best to wait until RSP to RSP transfers are automated, which is near the
>top of list of things we are to work on next. Fair?
>
>Personally, I do not see the *real* threat in keeping this open,
[SNIP]

Hi Scott,

I don't think anyone is really advocating a closed system or anything the
least bit nefarious. Certainly, I don't think any of us (or OSRS/TUCOWS)
wish the perception of doing business in any way similar to those *other*
guys, either.

The concerns expressed are primarily associated with credit risk,
accounting, record keeping and knowing when to discontinue ancillary
services and some degree of protection.

We think the solution is:

(1) An RSP transfer system which notifies the losing and receiving RSP,
allows the losing RSP to mitigate its credit risk, to discontinue ancillary
services and to keep his customer and accounting records current. We think
this process should be similar to the current process for transfers between
Registrars for the protection of the customer and the losing Registrar/RSP.

We agree that the ability to transfer should be easy for the
customer. But, our perception is that this will be Even More Open, since
the respective RSP's will know what is going on with its business and
customers. The complaint repeatedly voiced on this list is that the RSP is
kept in the dark. This will fix it, without any downside and make some of
us a bit less nervous.

(2) Allow Renewals only through the current RSP, as opposed to allowing a
renewal with any RSP. If the customer wants to transfer, then he can
transfer via the transfer system discussed above.

This concept is no different than current concept embraced by
Registrars. For instance, I can't renew my domain name at OSRS/TUCOWS,
when my current Registrar is NSI. But, I can transfer it to OSRS/TUCOWS
and then . . .

This does not make the process any more closed, either. In contrast, it
gives the process structure and addresses the concerns voiced by several
RSPs, without any downside for the customer or for OSRS/TUCOWS.

FWIW

Thanks,

----
Don Brown - Dallas, Texas USA       Internet Concepts, Inc.
donbrown@inetconcepts.net            http://www.inetconcepts.net
PGP Key ID: 04C99A55                  (972) 788-2364  Fax: (972) 788-5049
Providing Internet Solutions Worldwide - An eDataWeb Affiliate
----



This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:36:12 EDT