<?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: New Domain Extensions:  &#8220;Intellectual Property Watch&#8221; Says Not So Fast</title>
	<atom:link href="http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 06:38:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Comment Period For ICANN Closing On Monday: Why You Need To Comment &#38; Here’s Our’s</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-12743</link>
		<dc:creator>Comment Period For ICANN Closing On Monday: Why You Need To Comment &#38; Here’s Our’s</dc:creator>
		<pubDate>Sat, 11 Apr 2009 16:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-12743</guid>
		<description>[...] http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/  [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/" rel="nofollow">http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/</a>  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jothan Frakes</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8103</link>
		<dc:creator>Jothan Frakes</dc:creator>
		<pubDate>Wed, 17 Sep 2008 16:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8103</guid>
		<description>Not suggesting a downside, because brands have their own approaches to what their online strategy.  

As many folks like yourself or I with tenure have seen play out, there are some very progressive brands out there with respect to their online and internet adoption.

And there are still many that have not adopted the internet as a way to grow and expand their presence and keep having to react to the evolution of the market around them.

What I am hearing in the IP world is that the initial reaction to adding more TLDs is that it will massively expand the costs for a brand to enforce their famous marks or trademark strings by the number of new extensions.  

So they&#039;d have to do sunrise if they are proactive or they&#039;d have to ACPA or UDRP if they are reactive and for many this is a daunting workload just with the current count of TLDs.  When the world has a situation of a massive TLD introductions.... 

Can I get an &quot;Oy Vey&quot;?

That said, there are many in the intellectual property space that see the new TLDs instead as opportunity.

If I were Kraft Foods or Johnson and Johnson or one of the brands with more of a hip and savvy strategy I would be looking at saying &quot;screw that process of registering and reacting in these new TLDs, my customer will know me as ., and thus the . will be less dilutive and god bless those that go register them, I&#039;ll just react to the onerous ones as they arise.

But my point in that comment was that it will help to drive and clarify the definitions of PROHIBITIONS in ICANNs MOU with the USDOC if that starts to happen. 

In theory, does that not begin to make ICANN the registry and create a scenario whereby brands are not interacting with a registry or registrar or registrants but simply with ICANN itself?

Is ICANN then competing directly with the incumbent or new to be introduced registries? 

That&#039;s the rhetorical question to ponder that has been posed.  It is worth some thought.</description>
		<content:encoded><![CDATA[<p>Not suggesting a downside, because brands have their own approaches to what their online strategy.  </p>
<p>As many folks like yourself or I with tenure have seen play out, there are some very progressive brands out there with respect to their online and internet adoption.</p>
<p>And there are still many that have not adopted the internet as a way to grow and expand their presence and keep having to react to the evolution of the market around them.</p>
<p>What I am hearing in the IP world is that the initial reaction to adding more TLDs is that it will massively expand the costs for a brand to enforce their famous marks or trademark strings by the number of new extensions.  </p>
<p>So they&#8217;d have to do sunrise if they are proactive or they&#8217;d have to ACPA or UDRP if they are reactive and for many this is a daunting workload just with the current count of TLDs.  When the world has a situation of a massive TLD introductions&#8230;. </p>
<p>Can I get an &#8220;Oy Vey&#8221;?</p>
<p>That said, there are many in the intellectual property space that see the new TLDs instead as opportunity.</p>
<p>If I were Kraft Foods or Johnson and Johnson or one of the brands with more of a hip and savvy strategy I would be looking at saying &#8220;screw that process of registering and reacting in these new TLDs, my customer will know me as ., and thus the . will be less dilutive and god bless those that go register them, I&#8217;ll just react to the onerous ones as they arise.</p>
<p>But my point in that comment was that it will help to drive and clarify the definitions of PROHIBITIONS in ICANNs MOU with the USDOC if that starts to happen. </p>
<p>In theory, does that not begin to make ICANN the registry and create a scenario whereby brands are not interacting with a registry or registrar or registrants but simply with ICANN itself?</p>
<p>Is ICANN then competing directly with the incumbent or new to be introduced registries? </p>
<p>That&#8217;s the rhetorical question to ponder that has been posed.  It is worth some thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MHB</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8087</link>
		<dc:creator>MHB</dc:creator>
		<pubDate>Wed, 17 Sep 2008 05:20:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8087</guid>
		<description>Jothan

I would expect many brands to apply for their own extension.

Afterall its pretty cheap ($100K-$250K) to get

What is the downside?</description>
		<content:encoded><![CDATA[<p>Jothan</p>
<p>I would expect many brands to apply for their own extension.</p>
<p>Afterall its pretty cheap ($100K-$250K) to get</p>
<p>What is the downside?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jothan Frakes</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8084</link>
		<dc:creator>Jothan Frakes</dc:creator>
		<pubDate>Tue, 16 Sep 2008 22:39:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8084</guid>
		<description>Great topic Michael, and I had to step up and comment on this...
(disclaimer: this is made personally, not necessarily an opinion shared by my employer)

Those of you who follow me or know me understand my reach and background in the ICANN and new TLD space, and I have blogged about the numerous extensions or ideas that have been pitched to me.

There&#039;s an interesting rhetorical question that was raised at the ICANN Studenkries as to if some of the TLD proposals for brands, if allowed by ICANN to be used for sole registration purposes (where there would be only one registration, the TLD itself) might hypothetically be in direct conflict with &quot;RESPONSIBILITIES OF THE PARTIES&quot;; &quot;PROHIBITIONS&quot; (V.D.1) of the Memorandum of Understanding with the NTIA/DOC, in which ICANN could not become a registry.

If you noodle on that for a minute, really think about it, and then pause to consider the difference between an ATT.COM or IBM.COM versus a .ATT or .IBM, one begins to recognize that there is a possibility of a large number of brands heading in that direction.

One of the thoughts on new TLDs is that many of the submissions are going to be brands locking down their TLD as sole registrant or as a closed community that would have no registrars or registrants.

Many of the larger brands are looking at new TLDs with a massive pucker factor, because of all the sunrise and other matters that they have to manage and track.

Some Brands have considered embracing the new TLD process, in the manner that if they had a . it would help to reduce the massive costs of proactive brand protection as we take a sip from the firehose of new extensions we may face.  

[http://www.ntia.doc.gov/ntiahome/domainname/icann-memorandum.htm]
Section V, &quot;RESPONSIBILITIES OF THE PARTIES&quot;,
Sub D &quot;PROHIBITIONS&quot;,
Item 1 &quot;ICANN shall not act as a domain name Registry or Registrar or IP Address Registry in competition with entities affected by the plan developed under this Agreement. Nothing, however, in this Agreement is intended to prevent ICANN or the USG from taking reasonable steps that are necessary to protect the operational stability of the Internet in the event of the financial failure of a Registry or Registrar or other emergency. &quot;</description>
		<content:encoded><![CDATA[<p>Great topic Michael, and I had to step up and comment on this&#8230;<br />
(disclaimer: this is made personally, not necessarily an opinion shared by my employer)</p>
<p>Those of you who follow me or know me understand my reach and background in the ICANN and new TLD space, and I have blogged about the numerous extensions or ideas that have been pitched to me.</p>
<p>There&#8217;s an interesting rhetorical question that was raised at the ICANN Studenkries as to if some of the TLD proposals for brands, if allowed by ICANN to be used for sole registration purposes (where there would be only one registration, the TLD itself) might hypothetically be in direct conflict with &#8220;RESPONSIBILITIES OF THE PARTIES&#8221;; &#8220;PROHIBITIONS&#8221; (V.D.1) of the Memorandum of Understanding with the NTIA/DOC, in which ICANN could not become a registry.</p>
<p>If you noodle on that for a minute, really think about it, and then pause to consider the difference between an ATT.COM or IBM.COM versus a .ATT or .IBM, one begins to recognize that there is a possibility of a large number of brands heading in that direction.</p>
<p>One of the thoughts on new TLDs is that many of the submissions are going to be brands locking down their TLD as sole registrant or as a closed community that would have no registrars or registrants.</p>
<p>Many of the larger brands are looking at new TLDs with a massive pucker factor, because of all the sunrise and other matters that they have to manage and track.</p>
<p>Some Brands have considered embracing the new TLD process, in the manner that if they had a . it would help to reduce the massive costs of proactive brand protection as we take a sip from the firehose of new extensions we may face.  </p>
<p>[http://www.ntia.doc.gov/ntiahome/domainname/icann-memorandum.htm]<br />
Section V, &#8220;RESPONSIBILITIES OF THE PARTIES&#8221;,<br />
Sub D &#8220;PROHIBITIONS&#8221;,<br />
Item 1 &#8220;ICANN shall not act as a domain name Registry or Registrar or IP Address Registry in competition with entities affected by the plan developed under this Agreement. Nothing, however, in this Agreement is intended to prevent ICANN or the USG from taking reasonable steps that are necessary to protect the operational stability of the Internet in the event of the financial failure of a Registry or Registrar or other emergency. &#8220;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damir</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8076</link>
		<dc:creator>Damir</dc:creator>
		<pubDate>Tue, 16 Sep 2008 19:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8076</guid>
		<description>Great post - It would be good for many people to change professions and become Lawyers - as a Lawyer you will make a 10 figure income with all the trademark infringement court cases WorldWide once the New domain name extensions come out in the open (Online)</description>
		<content:encoded><![CDATA[<p>Great post &#8211; It would be good for many people to change professions and become Lawyers &#8211; as a Lawyer you will make a 10 figure income with all the trademark infringement court cases WorldWide once the New domain name extensions come out in the open (Online)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MHB</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8074</link>
		<dc:creator>MHB</dc:creator>
		<pubDate>Tue, 16 Sep 2008 16:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8074</guid>
		<description>Mickie

You are correct</description>
		<content:encoded><![CDATA[<p>Mickie</p>
<p>You are correct</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MHB</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8073</link>
		<dc:creator>MHB</dc:creator>
		<pubDate>Tue, 16 Sep 2008 16:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8073</guid>
		<description>John

That is not going to happen</description>
		<content:encoded><![CDATA[<p>John</p>
<p>That is not going to happen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mickie Kennedy</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8071</link>
		<dc:creator>Mickie Kennedy</dc:creator>
		<pubDate>Tue, 16 Sep 2008 14:37:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8071</guid>
		<description>We&#039;re not talking a $7 a year fee, we&#039;re talking a new top-level domain system where an individual or company could pay what will likely be tens or hundreds of thousands of dollars for their rights to domain.trademark like domain.yahoo or domain.apple  No big deal. What happens when when domain.bob decides to park yahoo.bob or google.bob (bad examples as they have the lawyers and resources to fight this). How about the midsized business owner who now sees his trademark.bob and thousands others popping up.</description>
		<content:encoded><![CDATA[<p>We&#8217;re not talking a $7 a year fee, we&#8217;re talking a new top-level domain system where an individual or company could pay what will likely be tens or hundreds of thousands of dollars for their rights to domain.trademark like domain.yahoo or domain.apple  No big deal. What happens when when domain.bob decides to park yahoo.bob or google.bob (bad examples as they have the lawyers and resources to fight this). How about the midsized business owner who now sees his trademark.bob and thousands others popping up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Doe</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8070</link>
		<dc:creator>John Doe</dc:creator>
		<pubDate>Tue, 16 Sep 2008 14:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8070</guid>
		<description>ICANN has become obsolete, look at their paychecks.

The US trade commission needs to take over temporarily while they clean hour and put someone else in charge  to clean house.</description>
		<content:encoded><![CDATA[<p>ICANN has become obsolete, look at their paychecks.</p>
<p>The US trade commission needs to take over temporarily while they clean hour and put someone else in charge  to clean house.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MHB</title>
		<link>http://www.thedomains.com/2008/09/15/new-domain-extensions-intellectual-property-watch-says-no/comment-page-1/#comment-8069</link>
		<dc:creator>MHB</dc:creator>
		<pubDate>Tue, 16 Sep 2008 13:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thedomains.com/?p=1002#comment-8069</guid>
		<description>Daniel

Its more than trademark holders that have concerns about these new extensions.

Say you own newyorkrealestate.com.  Then they allow .realestate as a new extension.  now someone can use newyork.realestate

How many people are going to type in newyork.realestate.com?

What it there is a .newyork

Then you can use realestate.newyork, newyork.realestate 

Talk about confusion.

And if you own the .com you would feel compelled t go for the .newyork and .realestate version which will be aucitoned off and that guy is going to have to spend tens or hundreds of thousands of dollars on what?  Domains they don&#039;t want or need but have to have.</description>
		<content:encoded><![CDATA[<p>Daniel</p>
<p>Its more than trademark holders that have concerns about these new extensions.</p>
<p>Say you own newyorkrealestate.com.  Then they allow .realestate as a new extension.  now someone can use newyork.realestate</p>
<p>How many people are going to type in newyork.realestate.com?</p>
<p>What it there is a .newyork</p>
<p>Then you can use realestate.newyork, newyork.realestate </p>
<p>Talk about confusion.</p>
<p>And if you own the .com you would feel compelled t go for the .newyork and .realestate version which will be aucitoned off and that guy is going to have to spend tens or hundreds of thousands of dollars on what?  Domains they don&#8217;t want or need but have to have.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
