<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Valideus</title>
	<atom:link href="http://valideus.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://valideus.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 27 Jul 2010 12:15:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on DAG4 issues &#8211; Malicious conduct by david</title>
		<link>http://valideus.com/dag4-issues-malicious-conduct/comment-page-1/#comment-83</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 27 Jul 2010 12:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://valideus.com/?p=711#comment-83</guid>
		<description>Elaine: ICANN registrars may have a contract with ICANN but disappointingly there are a significant number of them who are less than rigorous at meeting their obligations. In the past two years we have seen the rise of Bad Actor registrars such as Lead Networks (now de-accredited) who conspire to infringe rights owners. We therefore agree with the law enforcement specialists who deal with the consequences of malicious behaviours every day. We think that ICANN should impose greater requirements on registry operators to eliminate malicious behaviours higher up the chain. Of course ICANN could also impose greater requirements on registrars too. The sad fact is that ICANN&#039;s investment in contract compliance has been woefully inadequate so far.</description>
		<content:encoded><![CDATA[<p>Elaine: ICANN registrars may have a contract with ICANN but disappointingly there are a significant number of them who are less than rigorous at meeting their obligations. In the past two years we have seen the rise of Bad Actor registrars such as Lead Networks (now de-accredited) who conspire to infringe rights owners. We therefore agree with the law enforcement specialists who deal with the consequences of malicious behaviours every day. We think that ICANN should impose greater requirements on registry operators to eliminate malicious behaviours higher up the chain. Of course ICANN could also impose greater requirements on registrars too. The sad fact is that ICANN&#8217;s investment in contract compliance has been woefully inadequate so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DAG4 issues &#8211; Malicious conduct by Elaine</title>
		<link>http://valideus.com/dag4-issues-malicious-conduct/comment-page-1/#comment-28</link>
		<dc:creator>Elaine</dc:creator>
		<pubDate>Sun, 18 Jul 2010 22:39:38 +0000</pubDate>
		<guid isPermaLink="false">http://valideus.com/?p=711#comment-28</guid>
		<description>&quot; there is currently no requirement on registry operators to validate information provided by registrants in whois, to use CAPTCHA to prevent domains being registered by BOTS, to maintain a list of fraudulent IP addresses&quot;...
Because this is the registrar&#039;s responsibility according to ICANN contracts.  Don&#039;t forget there is a party between (miscreant) applicants and registry operators.</description>
		<content:encoded><![CDATA[<p>&#8221; there is currently no requirement on registry operators to validate information provided by registrants in whois, to use CAPTCHA to prevent domains being registered by BOTS, to maintain a list of fraudulent IP addresses&#8221;&#8230;<br />
Because this is the registrar&#8217;s responsibility according to ICANN contracts.  Don&#8217;t forget there is a party between (miscreant) applicants and registry operators.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

