[ALAC] Verisign Service Request - Malware monitoring and Malicious site takedown

Jean-Jacques Subrenat jj.subrenat at welho.com
Wed Oct 12 03:46:55 UTC 2011

*Thank you Alan for pointing this out. *
*The proposal under consideration illustrates the approach of many large
companies today, calling for self-regulation to replace a proper regulatory
body acting in the public interest. We've seen how Greenspan, Paulson and
others, by playing down the regulatory duties of the US federal government
over the years, have allowed widespread disaster in the financial sector,
with incalculable consequences for taxpayers worldwide.*
*Verisign's proposal brings up questions which have been well formulated by
the commentators Alan has pointed to (Kirikos, Jeftovic) and which should
also be looked at from a (higher) policy standpoint: *
*- to what extent can a private company be allowed to exercise regulatory
duties, against payment?*
*- the proposed mechanism carries the risk of collateral damage to
legitimate entities and users.
*Alan, I support your call for ALAC to adopt and make known its position on

On 12 October 2011 03:20, Alan Greenberg <alan.greenberg at mcgill.ca> wrote:

> Verisign has requested ICANN permission to offer a new service under
> the Registry Service Evaluation Process (RSTEP).
> There are two services described within the proposed Verisign
> Anti-Abuse Domain Use Policy.
> - Periodic scans of websites to identify possible malware
> - An anti-abuse policy and procedures to take down sites that violate
> the policy.
> They would be applicable to the .com, .net and .name TLDs managed by
> Verisgin.
> The full request can be seen at
> http://www.icann.org/en/registries/rsep/verisign-com-net-name-request-10oct11-en.pdf
> ,
> and there are articles about the request at
> http://www.theregister.co.uk/2011/10/11/verisign_asks_for_web_takedown_powers/
> and
> http://domainnamewire.com/2011/10/11/verisign-proposes-takedown-procedures-and-malware-scanning-for-com/
> .
> There are already a few comments on the service - see
> http://forum.icann.org/lists/registryservice/.
> In theory, ICANN could approve the service in as little as two weeks
> from today. However, in this case I suspect that a longer time will
> be allowed, and perhaps a formal Public Comment period will also be opened.
> As you will see from the news articles and the early comments, there
> are a number of issues involved here and the ALAC may well want to
> comment on this Service Request.
> Alan
> _______________________________________________
> 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