<?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: Closed gTLD debate threatens Google and Amazon</title>
	<atom:link href="http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/feed" rel="self" type="application/rss+xml" />
	<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon</link>
	<description>Domain Name News And Opinion</description>
	<lastBuildDate>Sat, 25 May 2013 18:00:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Rubens Kuhl</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24307</link>
		<dc:creator>Rubens Kuhl</dc:creator>
		<pubDate>Tue, 12 Feb 2013 11:23:17 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24307</guid>
		<description><![CDATA[Caterpillars turn into Butterflies. Spammers turn into Patent Trolls.]]></description>
		<content:encoded><![CDATA[<p>Caterpillars turn into Butterflies. Spammers turn into Patent Trolls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Brunner-Williams</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24226</link>
		<dc:creator>Eric Brunner-Williams</dc:creator>
		<pubDate>Sat, 09 Feb 2013 17:05:23 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24226</guid>
		<description><![CDATA[Michael,

First mention(1) may qualify as &quot;acknowledged&quot;, but not as &quot;heavily debated&quot;. I suppose the thing to do is to write to the participants at the Bruxelles VI meeting -- particularly those committed to the no-cap positions -- the one lead by Volker and the one lead by Milton -- and ask if they thought before that meeting that they were proposing policy for {.brand/single-registrant/...} registry-registrar integration.

It is my impression, having been part of the Bruxelles and subsequent attempts to find a common position among the pro-cap proposals (James and Johnathan lead, resp.), that the only exception to the separation rule then contemplated, at least by those in favor of the 15% cross ownership cap, was for community-based proposals.

It is also my impression, having corresponded at some length with Volker and others, that many opposed to any cap were not motivated by a preference for a type of application that did not then, and does not now, exist in the published rules, but were positing the application of a competition authority or internal separation to prevent self-dealing where two or more registrars, only one of which is owned or controlled by the registry, offered competitive registration services to an unrestricted, or community registration eligibility restricted, pool of third-party registrants.

You will have made the case that I&#039;ve substantially misrepresented the sub-issue in the course of the VI WG policy development process if you can show that substantive debate on a proposal for {.brand/single-registrant/...} took place earlier than I wrote above, better still, in the instructions from the Board, post-Nairobi, to the Community, to address cross ownership policy, explicitly including the novelty of registries for single registrants, and the better informed world will of course thank you for your careful effort to &quot;make sure that the facts are on the table&quot;.

You can do that, can&#039;t you?

(1) The hypo came up during Working Group C, circa 1999.]]></description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>First mention(1) may qualify as &#8220;acknowledged&#8221;, but not as &#8220;heavily debated&#8221;. I suppose the thing to do is to write to the participants at the Bruxelles VI meeting &#8212; particularly those committed to the no-cap positions &#8212; the one lead by Volker and the one lead by Milton &#8212; and ask if they thought before that meeting that they were proposing policy for {.brand/single-registrant/&#8230;} registry-registrar integration.</p>
<p>It is my impression, having been part of the Bruxelles and subsequent attempts to find a common position among the pro-cap proposals (James and Johnathan lead, resp.), that the only exception to the separation rule then contemplated, at least by those in favor of the 15% cross ownership cap, was for community-based proposals.</p>
<p>It is also my impression, having corresponded at some length with Volker and others, that many opposed to any cap were not motivated by a preference for a type of application that did not then, and does not now, exist in the published rules, but were positing the application of a competition authority or internal separation to prevent self-dealing where two or more registrars, only one of which is owned or controlled by the registry, offered competitive registration services to an unrestricted, or community registration eligibility restricted, pool of third-party registrants.</p>
<p>You will have made the case that I&#8217;ve substantially misrepresented the sub-issue in the course of the VI WG policy development process if you can show that substantive debate on a proposal for {.brand/single-registrant/&#8230;} took place earlier than I wrote above, better still, in the instructions from the Board, post-Nairobi, to the Community, to address cross ownership policy, explicitly including the novelty of registries for single registrants, and the better informed world will of course thank you for your careful effort to &#8220;make sure that the facts are on the table&#8221;.</p>
<p>You can do that, can&#8217;t you?</p>
<p>(1) The hypo came up during Working Group C, circa 1999.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Palage</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24223</link>
		<dc:creator>Michael Palage</dc:creator>
		<pubDate>Sat, 09 Feb 2013 13:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24223</guid>
		<description><![CDATA[Eric,

Let me begin by disclosing that I worked on several &quot;closed generic&quot; applications in connection with the over 150+ applications I worked on.

I also participated in the VI Working and I would respectfully disagree with your assessment that &quot;closed generics&quot; were slipped in late in the game.  Please refer to the following email including a list of hypotheticals predicting many of the very type of gTLD business models we currently have in the 1900+ applications, see http://forum.icann.org/lists/gnso-vi-feb10/msg00560.html  That list of hypotheticals was posted in March 2010, approximately one month after the WG was formed. 

Google, Amazon and others merely filed applications which conformed with the much maligned/debated Applicant Guidebook and are now being vilified, and no I did not work on Google or Amazon&#039;s application.  Google and Amazon just chose to keep their intentions private not unlike other large portfolio applicants.

While I hope/trust ICANN will do the right thing, I just want to make sure that the facts are on the table that &quot;closed generics&quot; did not just happen out of thin air, they were well known.]]></description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>Let me begin by disclosing that I worked on several &#8220;closed generic&#8221; applications in connection with the over 150+ applications I worked on.</p>
<p>I also participated in the VI Working and I would respectfully disagree with your assessment that &#8220;closed generics&#8221; were slipped in late in the game.  Please refer to the following email including a list of hypotheticals predicting many of the very type of gTLD business models we currently have in the 1900+ applications, see <a href="http://forum.icann.org/lists/gnso-vi-feb10/msg00560.html" rel="nofollow">http://forum.icann.org/lists/gnso-vi-feb10/msg00560.html</a>  That list of hypotheticals was posted in March 2010, approximately one month after the WG was formed. </p>
<p>Google, Amazon and others merely filed applications which conformed with the much maligned/debated Applicant Guidebook and are now being vilified, and no I did not work on Google or Amazon&#8217;s application.  Google and Amazon just chose to keep their intentions private not unlike other large portfolio applicants.</p>
<p>While I hope/trust ICANN will do the right thing, I just want to make sure that the facts are on the table that &#8220;closed generics&#8221; did not just happen out of thin air, they were well known.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Tyrer</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24216</link>
		<dc:creator>Dave Tyrer</dc:creator>
		<pubDate>Sat, 09 Feb 2013 01:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24216</guid>
		<description><![CDATA[An excellent article, thanks for the info about the public comment period.
----------------------------------------
ICANN could consider enforcing the claims already made in some of the applications:

&quot;Charleston Road Registry intends to operate the proposed gTLD as a closed registry with Google as the sole registrar and registrant... This will promote competition in the gTLD space by inciting competitors to respond with improved gTLD operations, greater range and higher quality products and services, and/or the creation of their own respective gTLDs, to the benefit of all Internet users.&quot;

(Edited excerpt, Google application for the .SEARCH string)

Google should simply be required to demonstrate on an annual basis precisely how being given a monopoly over all .SEARCH domains promotes competition. For example, they could provide ICANN with testimonials from Bing and Yahoo describing how this incitement assisted them to compete and increase market share.
----------------------------------------
@DI: &quot;First, the .beauty scenario: L’Oreal keeps all the second-level .beauty domains to itself, essentially converting the word “beauty” into a brand name as far as the DNS is concerned.&quot;

L’Oréal&#039;s application for .BEAUTY has been beautifully expressed by Parminder Jeet Singh in TheHindu.com:

&quot;How L’Oréal will leverage this privileged association with a key symbolic term of our culture will be an interesting exercise to follow. But the goldmine is there for anyone to see. It can certainly begin by propagating the term “.beauty” in all its communications and expressions. With time, demonstrating the long association, it could also seek trademark rights on “.beauty,” and so will go on the saga of how L’Oréal became beauty, and beauty, L’Oréal!&quot;

http://www.thehindu.com/opinion/op-ed/beauty-lies-in-the-domain-of-the-highest-bidder/article3929612.ece
----------------------------------------
I&#039;ve built a big resource about the proposed closed registries at SuperMonopolies.com
----------------------------------------
Tom Gilles has organized an important petition at Change.org about this issue:

http://www.change.org/petitions/icann-stop-corporate-takeover-of-new-internet-names]]></description>
		<content:encoded><![CDATA[<p>An excellent article, thanks for the info about the public comment period.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
ICANN could consider enforcing the claims already made in some of the applications:</p>
<p>&#8220;Charleston Road Registry intends to operate the proposed gTLD as a closed registry with Google as the sole registrar and registrant&#8230; This will promote competition in the gTLD space by inciting competitors to respond with improved gTLD operations, greater range and higher quality products and services, and/or the creation of their own respective gTLDs, to the benefit of all Internet users.&#8221;</p>
<p>(Edited excerpt, Google application for the .SEARCH string)</p>
<p>Google should simply be required to demonstrate on an annual basis precisely how being given a monopoly over all .SEARCH domains promotes competition. For example, they could provide ICANN with testimonials from Bing and Yahoo describing how this incitement assisted them to compete and increase market share.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
@DI: &#8220;First, the .beauty scenario: L’Oreal keeps all the second-level .beauty domains to itself, essentially converting the word “beauty” into a brand name as far as the DNS is concerned.&#8221;</p>
<p>L’Oréal&#8217;s application for .BEAUTY has been beautifully expressed by Parminder Jeet Singh in TheHindu.com:</p>
<p>&#8220;How L’Oréal will leverage this privileged association with a key symbolic term of our culture will be an interesting exercise to follow. But the goldmine is there for anyone to see. It can certainly begin by propagating the term “.beauty” in all its communications and expressions. With time, demonstrating the long association, it could also seek trademark rights on “.beauty,” and so will go on the saga of how L’Oréal became beauty, and beauty, L’Oréal!&#8221;</p>
<p><a href="http://www.thehindu.com/opinion/op-ed/beauty-lies-in-the-domain-of-the-highest-bidder/article3929612.ece" rel="nofollow">http://www.thehindu.com/opinion/op-ed/beauty-lies-in-the-domain-of-the-highest-bidder/article3929612.ece</a><br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
I&#8217;ve built a big resource about the proposed closed registries at SuperMonopolies.com<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
Tom Gilles has organized an important petition at Change.org about this issue:</p>
<p><a href="http://www.change.org/petitions/icann-stop-corporate-takeover-of-new-internet-names" rel="nofollow">http://www.change.org/petitions/icann-stop-corporate-takeover-of-new-internet-names</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Pace</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24211</link>
		<dc:creator>Aaron Pace</dc:creator>
		<pubDate>Fri, 08 Feb 2013 19:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24211</guid>
		<description><![CDATA[Google and Amazon are going to do well with new TLD&#039;s. However you have to ask yourself, what would people actually &quot;want&quot; to name their website? Do you think the TLD&#039;s that they applied for are going to be big sellers? Example: MyWebsite.GOOGLE . I would not put that on my business card, would you? 

If ICANN wants to make this TLD expansion into a &quot;great success&quot; they should talk to me about my intellectual property, brand name and help me figure out a way to get it into the marketplace. My development is really what the world wants, plus it would be a huge seller. Read my technology investor page for more info.]]></description>
		<content:encoded><![CDATA[<p>Google and Amazon are going to do well with new TLD&#8217;s. However you have to ask yourself, what would people actually &#8220;want&#8221; to name their website? Do you think the TLD&#8217;s that they applied for are going to be big sellers? Example: MyWebsite.GOOGLE . I would not put that on my business card, would you? </p>
<p>If ICANN wants to make this TLD expansion into a &#8220;great success&#8221; they should talk to me about my intellectual property, brand name and help me figure out a way to get it into the marketplace. My development is really what the world wants, plus it would be a huge seller. Read my technology investor page for more info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Brunner-Williams</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24209</link>
		<dc:creator>Eric Brunner-Williams</dc:creator>
		<pubDate>Fri, 08 Feb 2013 18:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24209</guid>
		<description><![CDATA[Kevin,

I think you could do better than this:

&quot;During the year-long community discussion about registry-registrar vertical integration, the possibility of closed generics was acknowledged and heavily debated.&quot;

These were snuck in very late in the game, piggybacked on the notion that small community registries would benefit if offered what the 2000 round sTLD applicants sought, the right to register their community members.

You should acknowledge the skill of Kristina slipping the &quot;.brand&quot; exemption into the attempt to find agreement between the proposals advanced by James (one conditional cross ownership cap) and by Johnathan (another conditional cross ownership cap), and the no-cap proposal advanced by milton, and the other no-cap proposal advanced by Volker.

You are correct pointing out that &quot;currently no such thing as a dot-brand [exists] under ICANN’s rules&quot;. Of course, had you done so with any persistence as a member of the Vertical Integration Working Group you might have the subject of a censure note by the co-chairs for ... pointing that out.

The present issue then is whether a &quot;public comment period&quot; in 2013 immunizes the department and its agent, the corporation, for rule making made in 2011 for which no notice and comment exists in the public record.

I participated in the VI WG.]]></description>
		<content:encoded><![CDATA[<p>Kevin,</p>
<p>I think you could do better than this:</p>
<p>&#8220;During the year-long community discussion about registry-registrar vertical integration, the possibility of closed generics was acknowledged and heavily debated.&#8221;</p>
<p>These were snuck in very late in the game, piggybacked on the notion that small community registries would benefit if offered what the 2000 round sTLD applicants sought, the right to register their community members.</p>
<p>You should acknowledge the skill of Kristina slipping the &#8220;.brand&#8221; exemption into the attempt to find agreement between the proposals advanced by James (one conditional cross ownership cap) and by Johnathan (another conditional cross ownership cap), and the no-cap proposal advanced by milton, and the other no-cap proposal advanced by Volker.</p>
<p>You are correct pointing out that &#8220;currently no such thing as a dot-brand [exists] under ICANN’s rules&#8221;. Of course, had you done so with any persistence as a member of the Vertical Integration Working Group you might have the subject of a censure note by the co-chairs for &#8230; pointing that out.</p>
<p>The present issue then is whether a &#8220;public comment period&#8221; in 2013 immunizes the department and its agent, the corporation, for rule making made in 2011 for which no notice and comment exists in the public record.</p>
<p>I participated in the VI WG.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom G</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24208</link>
		<dc:creator>Tom G</dc:creator>
		<pubDate>Fri, 08 Feb 2013 18:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24208</guid>
		<description><![CDATA[Aside from the fact that it&#039;s really just the right thing to do.]]></description>
		<content:encoded><![CDATA[<p>Aside from the fact that it&#8217;s really just the right thing to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom G</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24207</link>
		<dc:creator>Tom G</dc:creator>
		<pubDate>Fri, 08 Feb 2013 17:47:30 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24207</guid>
		<description><![CDATA[They are cutting them a deal, giving the closed applicants a break here. All of this is just being done so those applicants can stay in the game. Otherwise they would go down to GAC Advice. 

Early Warning means problematic if not amended. This means you&#039;re going to be subject to the strongest GAC advice possible, presumed rejected unless rationale provided by the Board. Which, is not likely to happen.

They&#039;re not getting screwed, they&#039;re catching a break.

Just like the applicants who can now add &quot;Public Interest Commitments&quot; to their applications. It&#039;s giving them a huge break and keeping them in the game. Many of these are potential GAC issues.

How would you feel if you were an applicant that already included those commitments, in the original application?

So, applications will be amended, allowing deep pockets to stay in contention sets.

But not likely any closed model .book, or .app, or .shop.

Which is pretty much what I predicted months ago.

I&#039;m just trying to make sure all those potential .app, .book, .shop users can buy websites. 

But that&#039;s probably obvious

Thanks for the shout out.

Cheers]]></description>
		<content:encoded><![CDATA[<p>They are cutting them a deal, giving the closed applicants a break here. All of this is just being done so those applicants can stay in the game. Otherwise they would go down to GAC Advice. </p>
<p>Early Warning means problematic if not amended. This means you&#8217;re going to be subject to the strongest GAC advice possible, presumed rejected unless rationale provided by the Board. Which, is not likely to happen.</p>
<p>They&#8217;re not getting screwed, they&#8217;re catching a break.</p>
<p>Just like the applicants who can now add &#8220;Public Interest Commitments&#8221; to their applications. It&#8217;s giving them a huge break and keeping them in the game. Many of these are potential GAC issues.</p>
<p>How would you feel if you were an applicant that already included those commitments, in the original application?</p>
<p>So, applications will be amended, allowing deep pockets to stay in contention sets.</p>
<p>But not likely any closed model .book, or .app, or .shop.</p>
<p>Which is pretty much what I predicted months ago.</p>
<p>I&#8217;m just trying to make sure all those potential .app, .book, .shop users can buy websites. </p>
<p>But that&#8217;s probably obvious</p>
<p>Thanks for the shout out.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikey O'Connor</title>
		<link>http://domainincite.com/11785-closed-gtld-debate-threatens-google-and-amazon/comment-page-1#comment-24206</link>
		<dc:creator>Mikey O'Connor</dc:creator>
		<pubDate>Fri, 08 Feb 2013 14:31:34 +0000</pubDate>
		<guid isPermaLink="false">http://domainincite.com/?p=11785#comment-24206</guid>
		<description><![CDATA[As one of the co-chairs of the vertical integration working group, which got pretty badly manhandled by the Board, I&#039;d like to propose an alternate headline for your article:

       Decide in haste, repent at leisure.

One of the problems the Board created for itself by  cutting the VI working group short was that it lost the very deep pool of knowledge that had been building during the discussion.  

VI couldn&#039;t reach consensus.  But another way to phrase that would be VI couldn&#039;t reach consensus on the schedule imposed by the Board.  And thus an opportunity for more-nuanced Guidebook language was lost.  

You&#039;re also right in pointing out that categorizing TLDs is likely to open up huge kettle of issues.

T&#039;will be interesting to see how this plays out.  Thanks for the summary.  Nicely done.]]></description>
		<content:encoded><![CDATA[<p>As one of the co-chairs of the vertical integration working group, which got pretty badly manhandled by the Board, I&#8217;d like to propose an alternate headline for your article:</p>
<p>       Decide in haste, repent at leisure.</p>
<p>One of the problems the Board created for itself by  cutting the VI working group short was that it lost the very deep pool of knowledge that had been building during the discussion.  </p>
<p>VI couldn&#8217;t reach consensus.  But another way to phrase that would be VI couldn&#8217;t reach consensus on the schedule imposed by the Board.  And thus an opportunity for more-nuanced Guidebook language was lost.  </p>
<p>You&#8217;re also right in pointing out that categorizing TLDs is likely to open up huge kettle of issues.</p>
<p>T&#8217;will be interesting to see how this plays out.  Thanks for the summary.  Nicely done.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
