[ALAC] ICANN Compliance serves breach notice on BizCN registrar
Holly Raiche
h.raiche at internode.on.net
Sat May 10 04:46:46 UTC 2014
First - to Dev and Alan - well done.
Yes, Alan, if we ever get beyond square One in the P/P discussions, it is absolutely on point. I”ll pass it on and a rather alarming example of the use of P/P. It is also an issue for Carlton and the EWG - who validates what and in what circumstances.
Thanks to you all
Holly
(and why one should never trust anything from .ru (whether ccTLD or gTLD)
On 9 May 2014, at 1:44 pm, Alan Greenberg <alan.greenberg at mcgill.ca> wrote:
> Note that the non-compliant issues 1, 2 and 3 are all associated with an audit to ensure that registries comply with the Expired Registration Recovery Policy, the result of the PEDNR PDP that ALAC initiated and saw through.
>
> Compliance has been citing a number of registrars in recent days over these issues.
>
> It is worthy of note that for some of the Whois accuracy issues that we raised, they fixed these by moving the "proxy service" from non-existent French addresses and non-existent e-mail addresses to a new address is Moscow (probably valid based on Google) and a new e-mail address that at least has a valif domain name. All "interesting" to say the least.
>
> One thing I noted that we may want to act on. The e-mail domain address associated with this Russian proxy service is registered via the same proxy service.
>
> Holly: Should this be allowed under the new P/P rules being developed. Or even registering their contact address via ANOTHER P/P service. Shoe we make an additional statement to the WG?
>
> Alan
>
> At 08/05/2014 10:06 PM, Dev Anand Teelucksingh wrote:
>> Dear All,
>>
>> BizCN registrar, the focus of many of the compliance related issues raised
>> by the ALAC in the past few months has been served with a breach notice.
>> See
>> http://www.icann.org/en/news/correspondence/serad-to-guanghui-08may14-en.pdf
>>
>> Many of the concerns raised by the ALAC regarding this particular registrar
>> appear to have been included in the breach notice, including the systemic
>> Whois inaccuracy complaints.
>>
>> Kudos to all those involved that worked hard on this to get some results.
>>
>> Kind Regards,
>>
>> Dev Anand Teelucksingh
>> _______________________________________________
>> ALAC mailing list
>> ALAC at atlarge-lists.icann.org
>> https://atlarge-lists.icann.org/mailman/listinfo/alac
>>
>> At-Large Online: http://www.atlarge.icann.org
>> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>
> _______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
More information about the ALAC
mailing list