Cатсн²² (in)sесuяitу / ChrisJohnRiley

In an update to my earlier post on the EstDomains revocation, it seems that despite an attempt by EstDomains to clear up the issue, ICANN is going ahead with the revocation of the contract. Copies of the discussion between ICANN and EstDomains can be found on the ICANN website.

As much as I support the revocation, ICANN appear to be hiding behind the technical inaccuracies of filings from EstDomains to push through the revocation. I guess bad things happen to bad people, but still, it would be nice to see it spelled out for all to see, instead of saying that .:

The notice of primary contact change recently sent to ICANN’s Brussels office is not compliant with the requirements of the RAA and is not an effective notice of primary contact change.

Still, we can’t always have our cake and eat it