I understand the desire to delay/block the transfer to make sure the registrant knows that, in addition to transferring the domain registration, they are about to loose other services as well. Imagine someone tricked into transferring a domain by DRoA and having their website and e-mail suddenly disappear because the original registrar removed DNS entries, etc. as part of the transfer out process.
On the other hand, we don't want to needlessly (from the customer's perspective) block transfers -- that's the whole problem the new transfer policy was trying to address.
How about this? GoDaddy (or whomever) automatically locks any domain with "special" services attached to them. Domain locked is a valid reason to reject the transfer, right? To unlock the domain, you have to
turn off the proxy registration service first. Is there anything preventing a prerequisite to the "unlock" command?
BTW, in this specific case... it could be argued that the transfer request was rejected by the registrant not the losing registrar. After all, isn't "Domains by Proxy, Inc." the official registrant of the domain? The only thing giving the "real" registrant rights to the domain is the contract they have with Domains by Proxy, not the ICANN registration agreement.
-- Apu <[EMAIL PROTECTED]> NOC Services Corp. www.nocservices.com _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
