John:
Yes, you are correct in your description of how a transfer (between
profiles) works, and I tend to agree that a "direct" transfer could be
problematic IF the transfer was for other than convenience reasons (I
maintain several profiles to "group" domains together for changes, so I like
the ability to easily move domains between them).
Here's how I would recommend that people transfer a domain to another owner:
1-Select a new username and password that both people agree to. This will
only be temporary, and is used as a transition point.
2-The current owner transfers the domain to the agreed-upon
username/password and notifies the new owner
3-The new owner logs in with the "transition" username/password and then
transfers the domain to his own profile.
There you have it...nobody has disclosed their personal passwords!
As for transferring to another ICANN member, that's a REGISTRAR transfer,
and must be initiated from the "receiving" Registrar's system. OpenSRS has
kindly provided an automated solution to this. I honestly don't know how
other registrars do it (nor do I care <grin>).
Regards,
Eric Longman
Atl-Connect Internet Services
----- Original Message -----
From: "John Browbill - Fasthosts" <john@fasthosts.co.uk>
To: <dev-list@opensrs.org>
Sent: Thursday, April 20, 2000 5:24 AM
Hi All,
First off.. thanks for a good API for this system. It took me a while to get
to grips with it all, but I am now well underway.
Now for a few questions...
1) Am I right in think that you can only transfer a domain to another
'profile', and that this can only be done if you know the destination
'profile''s username, password, and one domain name.
2) If the above is correct... Is this not a little insecure for other
'profile' holders, havinng to give out their username and password. (I think
I might be missing somethign here.
3) Is there any way (or will there be a way) to transfer a domain to another
ICANN member? I'm not sure if this is possible at all, or even with this
API.
Thanks for looking at these..
A few suggestions...
While I was learning how to use the OpenSRS API it took me a while to get
all the needed information together. It would have been very helpful to have
a single document that included...
A) All the commands that the API supports, along with...
1) All the needed input fields, any validation checking, what they were
for, and in what combinations they would be expected.
2) All the expect output field, what they are, and when they could be
expected.
Some of the above are already included in the current documentation, and
some points are spread across 2 - 3 documents. It would be nice to have
these all in one reference type document.
Once again, thanks to the creators... We hope to do some good deligating on
the back of this!
Best Regards,
John Brownbill.
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:27 EDT