At 10:50 AM 9/29/00 -0500, you wrote:
- allowing RSPs to perform renewals from the client scripts
>>- allowing RSPs to query our systems for names coming up for renewal in
>>the next 60 days from the client scripts
>
>Make this an input field, in case 90 days in advance is needed for some
>reason.
This applies to all of your "variable term" requests....
Essentially, the more flexible we make the system, the more confusing it
will be. It will also add an additional load on our systems. We are trying
to find a balance between functionality and managing resources.; it is hard
to do.
Nothing stops any RSP form building their own renewal system that works
precisely the way they want it to.
However, we will evaluate this suggestion in depth, and if we can do it, we
will.
>>At the renewal date, if the name has not been renewed, Tucows will send
>>an email message to the admin and billing contacts, advising them that
>>this is their final notice, and that if they do not renew the name within
>>15 days, they risk losing it. This message will refer them to their RSP
>>for renewal. RSPs will be allowed to manually stop this message from
>>going out on a "per name" basis.
>
>Why from Tucows? Why not from the RSP?
Theoretically to promote sanity in cases where the RSP in not responding.
The RSP has had at least two chances to capture the renewal. Again, we can
be flexible if enough RSP's care. It would certainly include current RSP
contact info. We do not want your customers calling us, *really*, it's
true!. :)
Thanks for your feedback -
Regards,
sA
Scott Allan
Director OpenSRS
[EMAIL PROTECTED]
