ICANN related question...

Sat Dec 7 03:40:21 UTC 2013

On Fri, Dec 6, 2013 at 4:34 PM, Robert L Mathews <lists at tigertech.com>wrote:

> > now you know the (gaining) r-of-r, and the (gaining) reseller (if any),
> > and you're free to do whatever else you want.
>

ICANN is one potential recourse against the registrar, if non-cooperative
with the registrant;  another one is the courts,  and finally: there is the
court of public opinion.

> Unfortunately, that won't work, because:
> >Status:CLIENT TRANSFER PROHIBITED
>
> ... means that the domain name is locked against transfers, and someone
> will first need to login at the existing reseller to unlock it (and
> probably to get the transfer authorization code, too).
>

This is a technical block against transfer, that the losing registrar must
not refuse to allow the registrant to remove.

http://archive.icann.org/en/transfers/policy-12jul04.htm

"Instances when the requested change of Registrar may not be denied
include, but are not limited to:

...
  * Domain name in Registrar Lock Status, unless the Registered Name Holder
is provided with the reasonable opportunity and ability to unlock the
domain name prior to the Transfer Request.
"

Sadly, ICANN compliance will not do a thing for any individual domain
> name incident. Their mechanism for such things is to pass complaints on
> to the registrar, even when the registrar IS the problem, as if they're
> the Better Business Bureau. I've never seen them intervene in an
> individual domain name case

Perhaps, there need to be some complaints to ICANN about ICANN then.

Or to other community entities about an apparent lack of competent
authority by ICANN,
to even successfully implement their own policies.

> Robert L Mathews, Tiger Technologies, http://www.tigertech.net/
>
--
-JH