<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel>
	<title>MetaFilter posts tagged with domains and VeriSign</title>
	<link>http://www.metafilter.com/tags/domains+VeriSign</link>
	<description>Posts tagged with 'domains' and 'VeriSign' at MetaFilter.</description>
	<pubDate>Mon, 20 Feb 2006 19:18:27 -0800</pubDate> <lastBuildDate>Mon, 20 Feb 2006 19:18:27 -0800</lastBuildDate>

	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>
	<item>
		<title>Verisign and ICANN</title>
		<link>http://www.metafilter.com/49358/Verisign%2Dand%2DICANN</link>
		<description> Bob Parsons of Go Daddy &lt;a href=&quot;http://www.bobparsons.com/dotcomscam.html&quot;&gt;warns &lt;/a&gt;about the proposed contract between VeriSign and ICANN, allowing VeriSign a permanent monopoly on .COM and price increases without regulation.  </description>
		<guid isPermaLink="false">tag:metafilter.com,2006:site.49358</guid>
		<pubDate>Mon, 20 Feb 2006 19:18:27 -0800</pubDate>
		<category>.com</category>
		<category>domains</category>
		<category>GoDaddy</category>
		<category>ICANN</category>
		<category>Internet</category>
		<category>technology</category>
		<category>VeriSign</category>
		<dc:creator>Protocols of the Elders of Awesome</dc:creator>
	</item>
      <item>
		<title>No redirects! Bad Verisign! No biscuit!</title>
		<link>http://www.metafilter.com/28488/No%2Dredirects%2DBad%2DVerisign%2DNo%2Dbiscuit</link>
		<description>&lt;a href="http://icann.org/announcements/advisory-19sep03.htm"&gt;ICANN requests Verisign to stop wildcard redirects.&lt;/a&gt; The &lt;a href=&quot;http://www.iab.org/documents/docs/2003-09-20-dns-wildcards.html&quot;&gt;Internet Architecture Board &lt;/a&gt;posts many reasons why wildcards are a very bad thing in root servers.  Verisign responds by saying &quot;&lt;a href=&quot;http://www.icann.org/correspondence/lewis-to-twomey-21sep03.htm&quot;&gt;We don&apos;t care and you can&apos;t make us&lt;/a&gt;.&quot;   (This is a follow-up to &lt;a href=&quot;http://www.metafilter.com/mefi/28324&quot;&gt;this thread&lt;/a&gt;.)  </description>
		<guid isPermaLink="false">tag:metafilter.com,2003:site.28488</guid>
		<pubDate>Mon, 22 Sep 2003 15:44:07 -0800</pubDate>
		<category>domains</category>
		<category>iab</category>
		<category>icann</category>
		<category>redirects</category>
		<category>verisign</category>
		<category>wildcards</category>
		<dc:creator>dejah420</dc:creator>
	</item>
      <item>
		<title>Feel our awesome naming fu</title>
		<link>http://www.metafilter.com/28324/Feel%2Dour%2Dawesome%2Dnaming%2Dfu</link>
		<description>&lt;a href="http://slashdot.org/articles/03/09/16/0034210.shtml?tid=126&amp;amp;tid=95&amp;amp;tid=98&amp;amp;tid=99"&gt;Verisign modifies the infrastructure of the net to point back to themselves.&lt;/a&gt; Verisign has rigged all .com and .net mistyped domains to reroute to their &lt;a href=&quot;http://sitefinder.verisign.com/&quot;&gt;branded search page&lt;/a&gt;.  This makes them effectively the &lt;a href=&quot;http://www.verisign.com/resources/gd/sitefinder/implementation.pdf&quot;&gt;biggest cybersquatter&lt;/a&gt; on the net, and will make it impossible for most spam filters at the network level to operate as well as seriously &lt;a href=&quot;http://www.verisign.com/resources/gd/sitefinder/bestpractices.pdf&quot;&gt;complicating&lt;/a&gt; the lives of network administrators everywhere.  </description>
		<guid isPermaLink="false">tag:metafilter.com,2003:site.28324</guid>
		<pubDate>Mon, 15 Sep 2003 20:07:52 -0800</pubDate>
		<category>advertising</category>
		<category>branding</category>
		<category>domains</category>
		<category>squatting</category>
		<category>urls</category>
		<category>verisign</category>
		<dc:creator>dejah420</dc:creator>
	</item>
      <item>
		<title>VeriSign Can Be Sued for Losing Your Domain Name</title>
		<link>http://www.metafilter.com/27268/VeriSign%2DCan%2DBe%2DSued%2Dfor%2DLosing%2DYour%2DDomain%2DName</link>
		<description>&lt;a href="http://www.wired.com/news/business/0,1367,59788,00.html"&gt;VeriSign Can Be Sued for Losing Your Domain Name&lt;/a&gt; A Federal appeals court (Ninth Circuit) has ruled that the owner of the sex.com domain, who lost the domain when VeriSgin transferred it on the basis of a forged letter, can sue VeriSign for damages resulting from VeriSign&apos;s mistake.  The sex.com case is worth millions, but anyone who has lost a domain name due to VeriSign&apos;s incompetence may now be able to draw their pound of flesh straight from those entrusted with making sure the registry process works.  </description>
		<guid isPermaLink="false">tag:metafilter.com,2003:site.27268</guid>
		<pubDate>Sun, 27 Jul 2003 14:33:13 -0800</pubDate>
		<category>domains</category>
		<category>legal</category>
		<category>legislation</category>
		<category>sex</category>
		<category>urls</category>
		<category>verisign</category>
		<dc:creator>mikewas</dc:creator>
	</item>
      <item>
		<title></title>
		<link>http://www.metafilter.com/19680/</link>
		<description>&lt;a href="http://www.icann.org/correspondence/touton-letter-to-beckwith-03sep02.htm"&gt;&quot;VeriSign got in trouble,&lt;/a&gt; &lt;a href=&quot;http://www.icann.org/announcements/announcement-03sep02.htm&quot;&gt;VeriSign got in trouble!&quot;&lt;/a&gt; ICANN serves VeriSign with a formal notice of breach of its accreditation agreement for its mishandling of WHOIS data under its control (.com addresses). VeriSign has 15 days to smarten up or it could lose the .com registry.  (&lt;i&gt;via &lt;a href=&quot;http://boingboing.net/2002_09_01_archive.html#85410597&quot;&gt;Boing Boing&lt;/a&gt;&lt;/i&gt;)  </description>
		<guid isPermaLink="false">tag:metafilter.com,2002:site.19680</guid>
		<pubDate>Tue, 03 Sep 2002 17:50:55 -0800</pubDate>
		<category>domains</category>
		<category>icann</category>
		<category>registrar</category>
		<category>verisign</category>
		<category>whois</category>
		<dc:creator>mcwetboy</dc:creator>
	</item>
      <item>
		<title></title>
		<link>http://www.metafilter.com/18077/</link>
		<description> &lt;a href=&quot;http://www.verisign.com/&quot;&gt;Verisign&lt;/a&gt; (aka &lt;a href=&quot;http://www.verisignoff.org/&quot;&gt;Satan&lt;/a&gt;) is set to &lt;a href=&quot;http://www.nytimes.com/2002/06/15/technology/15NET.html&quot;&gt;relinquish the management of the .org domain&lt;/a&gt; pool this week, after agreeing to drop both the .org and .net registries to keep the .com one until 2007. &lt;a href=&quot;http://videolab.uoregon.edu/events/ICANN/icann_bucharest.html&quot;&gt;ICANN is meeting on it this week &lt;/a&gt; (webcast). The &lt;a href=&quot;http://www.icann.org/tlds/org/applications/&quot;&gt;list of all interested parties with competing applications is here&lt;/a&gt;, but personally I&apos;m pulling for Carl from &lt;a href=&quot;http://media.org/&quot;&gt;media.org&lt;/a&gt;&apos;s proposal for &lt;a href=&quot;http://not.invisible.net/MT/mt-comments.cgi?entry_id=55&quot;&gt;a public trust&lt;/a&gt;. For anyone that owns a .org domain, this is one to watch.  </description>
		<guid isPermaLink="false">tag:metafilter.com,2002:site.18077</guid>
		<pubDate>Wed, 26 Jun 2002 16:06:49 -0800</pubDate>
		<category>.org</category>
		<category>DNS</category>
		<category>domains</category>
		<category>ICANN</category>
		<category>internet</category>
		<category>topleveldomains</category>
		<category>verisign</category>
		<category>www</category>
		<dc:creator>mathowie</dc:creator>
	</item>
      
	</channel>
</rss>


