Zeljko,
>Hi Fagyal,
>
>Domain ownership is determined by owner contact, but access to domain is
>determined by access to profile, and its' username/password information. For
>that reason, profile should closely resemble ownership, and best practice is
>to use profile for all domains that belong to one user, and one user only.
>
>
That's correct.
>It's really not a good practice to throw different people's domains into the
>same profile.
>
Well, it's not about different people. User B *buys* the domain from
user A, so he issues a transfer.
>This is actually impossible for end-users to do on their own;
>
>
See above: user B issues the transfer, which is then acknowledged by
user A. We do not even see the process here, it just takes place via our
website.
As I mentioned earlier, the problem here is that user B thinks that
because he has provided his own contact data when he submitted the
order, these contact data will actually be associated with the domain,
and not only with the order. If these contact data are not used, then
why are they here? if they are used to associate data with the order,
and not the domain, then why aren't there similar fields when a renewal
order is placed?
>when placing an order, if one want to assign it to the existing profile, one
>needs to know username and password of that profile; end-user would not have
>that information, unless it's the owner of the profile.
>
It's the owner's profile.
> It's only service
>providers that may do that, if they have u/p of their customers. Once again,
>please don't do it, it's not a good practice, even if you manage domains of
>all your customers. One example of the possible problems is the one you
>described.
>
I understand, but I hope you see our problem now. Everything boils down
to that nothing happens with the contact data provided for transfer orders.
- Csongor
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:59 EDT