At 4/24/01 5:57 AM, Scott Allan wrote:

>At 08:33 AM 4/24/01 -0400, OpenSRS wrote:
>>Can't find this in the docs ...
>>
>>End-user A owns blah.com (registered with opensrs) and would like to give
>>it to end-user B.  B owns no domains and therefore has no opensrs profile.
>>How does A give blah.com to B?
>
>Hi Cliff!
>
>Log into manage - click on "manage profile" - click on "Change Ownership of 
>Domain"  - page 37 of the latest guide 
>(http://www.opensrs.org/docs/OpenSRS_v2.33_New_User_Guide.PDF) section 6.25 
>should be beefed up to provide this info.

Hmmm, what about the contract requirement that OpenSRS be given written 
notice? From Exhibit A of the gTLD contract:

>14. TRANSFER OF OWNERSHIP. The person named as administrative contact at 
>the time the controlling user name and password are secured shall be the 
>owner of the domain name. You agree that prior to transferring ownership 
>of your domain name to another person (the Transferee") you shall require 
>the Transferee to agree, in writing to be bound by all the terms and 
>conditions of this Agreement. Your domain name will not be transferred 
>until we receive such written assurances or other reasonable assurance 
>that the Transferee has been bound by the contractual terms of this 
>Agreement (such reasonable assurance as determined by us in our sole 
>discretion) along with the applicable transfer fee. If the Transferee 
>fails to be bound in a reasonable fashion (as determine by us in our sole 
>discretion) to the terms and conditions in this Agreement, any such 
>transfer will be null and void.

If this is no longer the case, can we remove this from the contract? I 
had another person complain the other day about how long the contract is 
compared to most other registrars'. In addition, there's no "applicable 
transfer fee" that I'm aware of, so that should be removed in any case, 
shouldn't it?

While I'm thinking of it, the whole thing could use a bit of a cleanup to 
remove misplaced quotation marks and the like (as in the fourth line 
above) as well.

--
Robert L Mathews, Tiger Technologies

Reply via email to