This basically means that instead of the usual
"https://rr-n1-tor.opensrs.net/transfers/index.cgi?rid=xxxx"; URL that
shows up in the customer's confirmation message, they'll see
"http://transfers.yourdomain.com";, and you'll be able to pass the
parameters for the transfer approval to OpenSRS via the system (documented
tomorrow - I *personally* don't know how it works yet).
You won't be able to ACK/NAC transfers (not having the appropriate codes),
but aesthetically it will be more desirable for your customers to appear
to be dealing with you, instead of this "opensrs.net" thingy :)
Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]
On Tue, 19 Jun 2001, David Harris wrote:
>
> On page 36 of:
> http://www.opensrs.org/docs/opensrs_client_protocol_spec24.PDF
> the following text appears:
>
> }} Customizing the Transfer Approval URL
> }} By default, a domain's admin contact will be directed to the OpenSRS
> transfer approval
> }} URL, but a reseller can choose to instead direct clients to their own URL
> for approvals.
> }} Details regarding this process will be added to this document on June 20,
> 2001.
>
> Does this mean that we can run the transfer approval process ourselves and
> then report the information back to OpenSRS? How would this work, exactly?
>
> David Harris
> President, DRH Internet Inc.
> [EMAIL PROTECTED]
> http://www.drh.net/
>
>
>
