----- Original Message -----
From: "Don Brown" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 05, 2001 7:29 PM
Subject: Re: renewals
> At 05:00 PM 1/5/01 -0500, you wrote:
>
> >>(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.
> >
> >Fine - but (as mentioned before) I do think we should wait until we have
> >the RSP to RSP transfers automated...
>
> Why wait? We're in favor of being consistent with this from the start. A
> customer can follow the current procedure for transfers until the
automated
> transfer system is in place. After all, that's the best transfer system
we
> have right now.
>
> There is no downside to the customer or OSRS to implement the renewal
> procedure now. The only potential downside is to the RSPs, if we wait.
If renewing through another RSP does not effect an actual transfer of the
domain, then it probably makes little difference. However, this still isn't
100% clear to me what happens to a domain if a cusomer _happens_ to renew it
through some other RSP. I think Scott's assessment that this will be a very
very rare occurence is accurate. If we're talking two or three months,
fine, however if longer, then it needs to be implemented ASAP.
I think the OpenSRS approach to software releases needs a bit of
reexamination. Why go to the trouble of doing things one way, only to have
RSP's tell you it's not what _they_ had in mind? This surely must end up
requiring more work in the long run, leading to more delays in feature
releases. Why not lay your cards on the table and publish timelines and
planned features? Missing release deadlines isn't so bad as keeping RSP's
guessing as to when features will happen and then surprising them with the
results.
Jim
