ICANN rules be damned. They're only mildly relevant actually.
I paid Tucows money for a domain for 'x' years. Under the UCC [1] I would
be the customer of Tucows, not my client. Therefore, they SHOULD be
transferring the ownership (or license to use) to ME, and not to anyone
else. If I choose to resell that domain, or sublet it out annually, that's
between me and my client.
You're right that ICANN see's no "reseller" position, thus "I" am the
domain-purchaser, since I am "the person who bought the domain from the
ICANN-accredited-registrar" ...
Thus, I'm not sure how Tucows can, under ICANN, _EVER_ give the domain to
anyone but the RSP, since the RSP is the only "customer of the registrar".
They should basically be required to assign it "our name and address" until
such time as we initiate (through some means) a transfer into the
end-customer's name/address/orgname.
Now, an RSP _MIGHT_ elect (as I might, given my circumstances) to just do
that automatically. But the answer is that there probably should be some
means in the system (an option to enable) which says:
[ ] Always register my domains as RSP / 12 Main St. / Anytown NY 10001, but
keep the requested name/address info available for future assignment.
and until that assignment is DONE, the username/password requested by the
user is not active, and only the RSP's username/password is active.
So to follow this logic:
1.) Customer requests foo.com, gives credit card number.
2.) Card approved, request processed
3.) Domain name completed. Assigned to {RSP_INFO} as above. All contacts
are the RSP's, and the customer's requested username/password do not yet
work (perhaps even giving a message saying "Your RSP has not yet
transferred the domain permanently to you."
4.) RSP is satisfied with payment terms being satisfied, 30 days have
passed or whatever they elect to choose.
5.) RSP signs on and finally delegates domain to customer. RSP's password
no longer functions to access the domain (unless he's one of the contacts)
and all customer-requested logins/passwords work. Contacts and owner info
become the information requested and stored in the DB.
Theoretically, I can't understand how SRS could NOT do that, as I said,
since WE are their customer, not the end-user.
D
[1] Admittedly the user agreement between me and Tucows is under CanaDuh
law, but I suspect it will behave similarly.
At 3:58 PM -0800 12/8/00, William X. Walsh wrote:
>Hello Derek,
>
>ICANN is the controlling factor here, and their rules do not support
>this type of position.
>
>Friday, December 08, 2000, 1:19:51 PM, you wrote:
