Honestly, we have not committed to an approach yet. However, what you
suggest is certainly the easiest most logical way for us to implement it,
and what I had in mind. I hope to have this locked down early next week.
Regards,
sA
At 01:07 PM 1/10/01 -0800, Tiger Technologies wrote:
>I'm a little concerned that OpenSRS has said that they plan to have RSP
>transfers working within 30 days, but that there has been no discussion
>of exactly how it will work.
>
>I'd like to suggest that the mechanism NOT be offered as a separate
>client option, but that OpenSRS simply integrate the changes into the
>server-side process.
>
>For example, I should be able to use the existing domain transfer client
>functionality to transfer (and add a year to) any domain, whether it's
>registered through NSI or another OpenSRS RSP. That is, as an RSP trying
>to acquire the domain as a transfer, I should not have to know or care
>whether it was originally registered with OpenSRS or another registrar.
>
>In addition, the end-user approval process should look exactly the same,
>so I can have one set of instructions that tell them what to expect.
>
>Ideally, the transfer rules would be the same, too: no transfer within
>the first 60 days, etc. This would be helpful to communicate the rules to
>customers. (Without exception, my customers who originally registered
>their domain with another OpenSRS RSP weren't aware of it, so asking them
>to follow two sets of rules based on their status isn't going to work.)
>
>Perhaps what I've described is exactly what's being planned; if so, it
>would be nice if OpenSRS could tell us that. If this isn't what's being
>planned, can you tell us the details of how it will work so that we can
>discuss it and avoid a repeat of the surprises regarding renewals?
>
>Thanks!
>
>--
>Robert L Mathews, Tiger Technologies
Scott Allan
Director OpenSRS
[EMAIL PROTECTED]
