<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.thestandard.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The Industry Standard - ICANN slaps wrists and sends emails to spammers&amp;#039; registrars - Comments</title>
 <link>http://www.thestandard.com/news/2008/10/07/icann-slaps-wrists-and-sends-emails-spammers-registrars</link>
 <description>Comments for &quot;ICANN slaps wrists and sends emails to spammers&#039; registrars&quot;</description>
 <language>en</language>
<item>
 <title>Hi Cyndy,
I think you&#039;ve</title>
 <link>http://www.thestandard.com/news/2008/10/07/icann-slaps-wrists-and-sends-emails-spammers-registrars#comment-6972</link>
 <description>&lt;p&gt;&lt;!--paging_filter--&gt;Hi Cyndy,&lt;/p&gt;
&lt;p&gt;I think you&#039;ve overlooked some pretty clear indications over the past four months that there is much more going on that just &quot;wrist-slapping&quot;, as you argue.&lt;/p&gt;
&lt;p&gt;There is a very clear process now in place where registrars that do not comply with their contractual obligations are sent notices warning them. If they do not act within 15 days, that is escalated up to the point where they are de-accredited. And there are a number of registrars who can testify to precisely that. I can name three of them right now as ICANN has put out public announcements concerning their cases: 1dni.com, DotForce and Esoftwiz.&lt;/p&gt;
&lt;p&gt;What happens then? Again, look at the announcements ICANN has made. They are deaccredited and then ICANN asks if other registrars are interested in assuming the domain registrations they have. And then, shortly afterwards, those domains are transferred to a new registrar.&lt;/p&gt;
&lt;p&gt;That&#039;s the process and you can see it in these two announcements:&lt;br /&gt;
&lt;a href=&quot;http://www.icann.org/en/announcements/announcement-2-30jul08-en.htm&quot; title=&quot;http://www.icann.org/en/announcements/announcement-2-30jul08-en.htm&quot; rel=&quot;nofollow&quot;&gt;http://www.icann.org/en/announcements/announcement-2-30jul08-en.htm&lt;/a&gt;&lt;br /&gt;
&lt;a href=&quot;http://www.icann.org/en/announcements/announcement-18sep08-en.htm&quot; title=&quot;http://www.icann.org/en/announcements/announcement-18sep08-en.htm&quot; rel=&quot;nofollow&quot;&gt;http://www.icann.org/en/announcements/announcement-18sep08-en.htm&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is all ongoing as we speak, and if you subscribe to the Compliance newsletter (&lt;a href=&quot;http://www.icann.org/en/newsletter/&quot; title=&quot;http://www.icann.org/en/newsletter/&quot; rel=&quot;nofollow&quot;&gt;http://www.icann.org/en/newsletter/&lt;/a&gt;), each month you can see the work that is being done is chasing registrars. You will also see that most registrars do comply and that those that don&#039;t are chased until they do, Or they are deaccredited and they lose their domains.&lt;/p&gt;
&lt;p&gt;As to the question &quot;why isn&#039;t ICANN doing this... why isn&#039;t ICANN doing that?&quot; - the answer in nearly all cases will be because ICANN does not have the right to do so. ICANN can only use the terms in its contract with registrars to enforce compliance. It is a very clear line that the Internet community decided upon around eight years ago.&lt;/p&gt;
&lt;p&gt;If you believe that needs to change, if you think ICANN should be granted greater powers, if you believe the Registrar Accreditation Agreement needs to change so ICANN can manage registrar issues more effectively, then it is YOU that has to change it. And the only way to do that is to get involved in ICANN&#039;s process and persuade others of your argument.&lt;/p&gt;
&lt;p&gt;ICANN is a multistakeholder process. ICANN staff - and in this area compliance staff - do what they are able to do with the boundaries agreed by the community. If you don&#039;t like it, it&#039;s up to you to fix it.&lt;/p&gt;
&lt;p&gt;Let me give this link as a direct route to doing precisely that: &lt;a href=&quot;http://www.icann.org/en/public-comment/#new-irtp&quot; title=&quot;http://www.icann.org/en/public-comment/#new-irtp&quot; rel=&quot;nofollow&quot;&gt;http://www.icann.org/en/public-comment/#new-irtp&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The comment period is closed but you can see what people have said, what is under discussion, who in ICANN is in charge of aiding the process, and so on. It&#039;s the start point.&lt;/p&gt;
&lt;p&gt;Kieren McCarthy&lt;br /&gt;
General manager of public participation, ICANN&lt;/p&gt;
</description>
 <pubDate>Mon, 13 Oct 2008 14:55:05 -0400</pubDate>
 <dc:creator>Kieren McCarthy</dc:creator>
 <guid isPermaLink="false">comment 6972 at http://www.thestandard.com</guid>
</item>
<item>
 <title>Alas, you are correct - too</title>
 <link>http://www.thestandard.com/news/2008/10/07/icann-slaps-wrists-and-sends-emails-spammers-registrars#comment-6888</link>
 <description>&lt;p&gt;&lt;!--paging_filter--&gt;Alas, you are correct - too little and way too late. &lt;/p&gt;
&lt;p&gt;But it goes beyond that. WDPRS who-is is a false metric that does not even cover all TLDs.&lt;br /&gt;
Even if it did, is that the best we can do --INCOMPLETE whois ??? Breech of contract ???&lt;/p&gt;
&lt;p&gt;We saw how effective govt regulation of the mortgage business was-- the toothlessness of ICANN is much worse ...&lt;/p&gt;
</description>
 <pubDate>Thu, 09 Oct 2008 19:54:49 -0400</pubDate>
 <dc:creator>Howard Hoyt</dc:creator>
 <guid isPermaLink="false">comment 6888 at http://www.thestandard.com</guid>
</item>
<item>
 <title>ICANN slaps wrists and sends emails to spammers&#039; registrars</title>
 <link>http://www.thestandard.com/news/2008/10/07/icann-slaps-wrists-and-sends-emails-spammers-registrars</link>
 <description>&lt;!--paging_filter--&gt;&lt;p&gt;&lt;!--paging_filter--&gt;
&lt;p&gt;&lt;!--paging_filter--&gt; &lt;/p&gt;
&lt;p&gt;In what KnujOn claims is a &amp;quot;victory,&amp;quot; &lt;a href=&quot;http://www.icann.org/en/announcements/announcement-01oct08-en.htm&quot;&gt;ICANN sent two breach notices&lt;/a&gt; to domain registrars Joker.com and DNS.com.cn, stating that the two companies had&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&lt;i&gt;&amp;quot;failed to comply with Section 3.7.8 of the Registrar Accreditation Agreement (RAA) which requires registrars to take &amp;quot;reasonable steps to investigate&amp;quot; Whois inaccuracy claims.&amp;quot;&lt;/i&gt;&lt;/p&gt;
&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;The two registrars, with nearly one million domains registered between them, have both been accused of allowing domains to be registered with incomplete or false WHOIS information, a clear violation of ICANN policy. &lt;/p&gt;
&lt;p&gt;Of course, in &lt;a href=&quot;http://www.thestandard.com/news/2008/07/24/icann-admits-its-toothless&quot;&gt;typical ICANN fashion&lt;/a&gt;, violators take a long time to get their wrist slap. According to the ICANN link, violations were first discovered last November, with &amp;quot;Notices of Concern&amp;quot; sent in May, and now a &amp;quot;Breach Notice&amp;quot; was sent giving the registrars 15 additional days before &amp;quot;termination proceedings begin.&amp;quot;&lt;/p&gt;
&lt;p&gt;Joker.com already replied to the Breach Notice, claiming that the domains with false or missing information had been suspended, and &lt;a href=&quot;http://www.icann.org/correspondence/burnette-to-legenhauseny-03oct08.htm&quot;&gt;ICANN&#039;s response indicated&lt;/a&gt; that as long as the company can show that it attempted to get the registrants to correct the information and received no response, then Joker.com is cleared. DNS.com.cn has not yet responded to the Breach Notice, but has until 15 October to do so. &lt;/p&gt;
&lt;p&gt;ICANN may wonder why organizations like KnujOn exist and &lt;a href=&quot;http://www.thestandard.com/news/2008/09/09/court-public-opinion-replacing-icann&quot;&gt;regularly publish reports about registrars who fail to comply with even the regulations ICANN can enforce&lt;/a&gt;, and so much criticism is directed at the organization for being &amp;quot;toothless.&amp;quot; Looking at a year-long process to levy what is essentially wrist-slap for allowing spammers to register domains with false or missing information and then backing down might be a good place to start. A year is far too long to deal with the problem of spammers, who have usually moved on well before ICANN even begins their process to register other domains. &lt;/p&gt;
</description>
 <comments>http://www.thestandard.com/news/2008/10/07/icann-slaps-wrists-and-sends-emails-spammers-registrars#comments</comments>
 <category domain="http://www.thestandard.com/taxonomy/term/11332">co:DNS.com.cn</category>
 <category domain="http://www.thestandard.com/taxonomy/term/5846">co:icann</category>
 <category domain="http://www.thestandard.com/taxonomy/term/11331">co:Joker.com</category>
 <category domain="http://www.thestandard.com/taxonomy/term/5823">co:knujon</category>
 <category domain="http://www.thestandard.com/taxonomy/term/5668">Standards &amp;amp; Legal</category>
 <category domain="http://www.thestandard.com/taxonomy/term/2514">The Industry Standard</category>
 <pubDate>Tue, 07 Oct 2008 19:19:52 -0400</pubDate>
 <dc:creator>Cyndy Aleo-Carreira</dc:creator>
 <guid isPermaLink="false">119590 at http://www.thestandard.com</guid>
</item>
</channel>
</rss>
