<?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 on: Project.me Domain Dispute Sets Dangerous Precedent</title>
	<atom:link href="http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/feed/" rel="self" type="application/rss+xml" />
	<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/</link>
	<description>News and Views for the Domain Name Industry</description>
	<lastBuildDate>Thu, 11 Mar 2010 19:36:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Shhit</title>
		<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/comment-page-1/#comment-538190</link>
		<dc:creator>The Shhit</dc:creator>
		<pubDate>Fri, 08 Jan 2010 06:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9323#comment-538190</guid>
		<description>I personally hope that the .me domain value remains low so that normal people like myself can get some very brandable and recognizable names for cheap and make fun websites like you could at the dawn of the internet. Everyday peeps! register .me domains and make fun websites before domainers start making it harder by sitting on them! Their are tons of great ones left!</description>
		<content:encoded><![CDATA[<p>I personally hope that the .me domain value remains low so that normal people like myself can get some very brandable and recognizable names for cheap and make fun websites like you could at the dawn of the internet. Everyday peeps! register .me domains and make fun websites before domainers start making it harder by sitting on them! Their are tons of great ones left!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domain Name Wire &#187; News &#187; Paris Wins Parvi.org in Disturbing Domain Name Arbitration Decision - The Domain Industry's News Source</title>
		<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/comment-page-1/#comment-519412</link>
		<dc:creator>Domain Name Wire &#187; News &#187; Paris Wins Parvi.org in Disturbing Domain Name Arbitration Decision - The Domain Industry's News Source</dc:creator>
		<pubDate>Tue, 01 Dec 2009 02:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9323#comment-519412</guid>
		<description>[...] Christie is on a crusade to implement his vision on UDRP. He was also the presiding panelist on the Project.me case, which broke with precedent by suggesting that the top level domain should be considered part of [...]</description>
		<content:encoded><![CDATA[<div style="background-color: #FFfbd0">
<p>[...] Christie is on a crusade to implement his vision on UDRP. He was also the presiding panelist on the Project.me case, which broke with precedent by suggesting that the top level domain should be considered part of [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Douglas</title>
		<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/comment-page-1/#comment-514665</link>
		<dc:creator>Stephen Douglas</dc:creator>
		<pubDate>Mon, 23 Nov 2009 08:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9323#comment-514665</guid>
		<description>Johnny-B

Thanks for making that more clear.  It says a lot about domainers walking through a minefield with their investments in any particular domain. My own domain investments never took the extension into consideration for TM issues. I reviewed my list and I don&#039;t think I&#039;ve crossed that lake of thin ice, but I&#039;d suggest that this topic be considered as one of the many legal issues to consider in purchasing a domain name.

I appreciate your answer. Cheers</description>
		<content:encoded><![CDATA[<p>Johnny-B</p>
<p>Thanks for making that more clear.  It says a lot about domainers walking through a minefield with their investments in any particular domain. My own domain investments never took the extension into consideration for TM issues. I reviewed my list and I don&#8217;t think I&#8217;ve crossed that lake of thin ice, but I&#8217;d suggest that this topic be considered as one of the many legal issues to consider in purchasing a domain name.</p>
<p>I appreciate your answer. Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Berryhill</title>
		<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/comment-page-1/#comment-514601</link>
		<dc:creator>John Berryhill</dc:creator>
		<pubDate>Mon, 23 Nov 2009 05:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9323#comment-514601</guid>
		<description>Stephen,

Karen&#039;s been around for a while and has long been a good attorney.

The point is not whether the Respondent won on legitimate interests or on bad faith, since in both cases the Respondent won.  The point is that confusing similarity was found in both instances on the basis of including the TLD.  

Yes, subsequent panels do cite it for a proposition that wasn&#039;t found in the actual decision, as the panel did decide that &quot;six.net&quot; was identical or confusingly similar to &quot;SIXNET&quot;.</description>
		<content:encoded><![CDATA[<p>Stephen,</p>
<p>Karen&#8217;s been around for a while and has long been a good attorney.</p>
<p>The point is not whether the Respondent won on legitimate interests or on bad faith, since in both cases the Respondent won.  The point is that confusing similarity was found in both instances on the basis of including the TLD.  </p>
<p>Yes, subsequent panels do cite it for a proposition that wasn&#8217;t found in the actual decision, as the panel did decide that &#8220;six.net&#8221; was identical or confusingly similar to &#8220;SIXNET&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Douglas</title>
		<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/comment-page-1/#comment-514047</link>
		<dc:creator>Stephen Douglas</dc:creator>
		<pubDate>Sun, 22 Nov 2009 12:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9323#comment-514047</guid>
		<description>@ Karen

Where did you learn to box so well? You just knocked Berryhill out with your reply.  Watch out, there&#039;s a new legal voice making some good sense here. Name: Karen Bernstein

Berryhill&#039;s comment: &quot;Ahh… Everything old is new again.&quot; is moot... his report proved the point that the RESPONDENT WON, but the &quot;recent&quot; approach by ICANN is NEW.  But maybe John  was right in saying &quot;everything old is NEW again&quot; which is what Ms Bernstein was saying originally.</description>
		<content:encoded><![CDATA[<p>@ Karen</p>
<p>Where did you learn to box so well? You just knocked Berryhill out with your reply.  Watch out, there&#8217;s a new legal voice making some good sense here. Name: Karen Bernstein</p>
<p>Berryhill&#8217;s comment: &#8220;Ahh… Everything old is new again.&#8221; is moot&#8230; his report proved the point that the RESPONDENT WON, but the &#8220;recent&#8221; approach by ICANN is NEW.  But maybe John  was right in saying &#8220;everything old is NEW again&#8221; which is what Ms Bernstein was saying originally.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen Bernstein</title>
		<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/comment-page-1/#comment-513567</link>
		<dc:creator>Karen Bernstein</dc:creator>
		<pubDate>Sat, 21 Nov 2009 16:53:51 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9323#comment-513567</guid>
		<description>That&#039;s very interesting, John, but subsequent Panels cite this case for the old proposition that identical/confusing similarity looks to the left of the dot.  This most recent decision is quite disturbing because it explicitly acknowledges the departure from the long-standing rule and the decision is written as if the Panel wants to set new precedent here.  With the advent of the gTLDs the prospect of this new approach to analyzing the first prong has the potential of wreaking havoc on lawyers and domainers alike.  Not pretty.</description>
		<content:encoded><![CDATA[<p>That&#8217;s very interesting, John, but subsequent Panels cite this case for the old proposition that identical/confusing similarity looks to the left of the dot.  This most recent decision is quite disturbing because it explicitly acknowledges the departure from the long-standing rule and the decision is written as if the Panel wants to set new precedent here.  With the advent of the gTLDs the prospect of this new approach to analyzing the first prong has the potential of wreaking havoc on lawyers and domainers alike.  Not pretty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Douglas</title>
		<link>http://domainnamewire.com/2009/11/20/project-me-domain-dispute-sets-dangerous-precedent/comment-page-1/#comment-513419</link>
		<dc:creator>Stephen Douglas</dc:creator>
		<pubDate>Sat, 21 Nov 2009 09:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/?p=9323#comment-513419</guid>
		<description>Great to see a guest writer on DNW. Good article.

@David, I usually agree with you, but that&#039;s a poor excuse not to &quot;entertain&quot; the idea of using SLD&#039;s. No disrespect intended.</description>
		<content:encoded><![CDATA[<p>Great to see a guest writer on DNW. Good article.</p>
<p>@David, I usually agree with you, but that&#8217;s a poor excuse not to &#8220;entertain&#8221; the idea of using SLD&#8217;s. No disrespect intended.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
