<?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: Board discussion over RegisterFly</title>
	<atom:link href="http://blog.icann.org/2007/04/board-discussion-over-registerfly/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/</link>
	<description>Internet Corporation for Assigned Names and Numbers</description>
	<lastBuildDate>Mon, 23 Nov 2009 02:20:28 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scott Reese</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-3969</link>
		<dc:creator>Scott Reese</dc:creator>
		<pubDate>Thu, 20 Sep 2007 23:11:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-3969</guid>
		<description>ICANN does have it&#039;s work cut out for it, these are complex issues and every scenario can&#039;t be thought of and protected from in advance of it actually happening.  Also rules can&#039;t prevent crime, but systems can be put in place to protect the end user I think similar to how the banking industry is regulated. It is also important to keep to the forefront that the value of a domain is not it&#039;s purchase price... as an example my father has invested $15,000 in advertising on a product whose domain is currently in enom&#039;s no man&#039;s land.

As this process proceeds I feel it is important to keep in mind two simple truths:

1) Whatever &quot;rules or regulations&quot; ICANN comes up with must be enforceable - everyone goes into the agreement knowing this.

2) When the rules are broken, aggressively carry out the consequences.  I know ICANN is not staffed to chase down every complaint, but when hundreds of thousands of people are affected decisive action is needed. 

I do wish you guys the best and that it is easy for people with no knowledge of International laws to give advice. I hope though that this &quot;REGISTERFLY MESS&quot; won&#039;t be swept under the table so quickly that the affected parties aren&#039;t properly helped...</description>
		<content:encoded><![CDATA[<p>ICANN does have it&#8217;s work cut out for it, these are complex issues and every scenario can&#8217;t be thought of and protected from in advance of it actually happening.  Also rules can&#8217;t prevent crime, but systems can be put in place to protect the end user I think similar to how the banking industry is regulated. It is also important to keep to the forefront that the value of a domain is not it&#8217;s purchase price&#8230; as an example my father has invested $15,000 in advertising on a product whose domain is currently in enom&#8217;s no man&#8217;s land.</p>
<p>As this process proceeds I feel it is important to keep in mind two simple truths:</p>
<p>1) Whatever &#8220;rules or regulations&#8221; ICANN comes up with must be enforceable &#8211; everyone goes into the agreement knowing this.</p>
<p>2) When the rules are broken, aggressively carry out the consequences.  I know ICANN is not staffed to chase down every complaint, but when hundreds of thousands of people are affected decisive action is needed. </p>
<p>I do wish you guys the best and that it is easy for people with no knowledge of International laws to give advice. I hope though that this &#8220;REGISTERFLY MESS&#8221; won&#8217;t be swept under the table so quickly that the affected parties aren&#8217;t properly helped&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Reese</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-3966</link>
		<dc:creator>Scott Reese</dc:creator>
		<pubDate>Thu, 20 Sep 2007 22:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-3966</guid>
		<description>I&#039;ve lost at least 75 domains due to this registerfly fiasco. I wll not recount my story because because it&#039;s similar to what everyone else went through. It was absolutely impossible to renew domain names. It was slow and painful deaths as you would see the domain expire and someone else (usually an unknown protected person) buy the domains. Other domains are still being held hostage by enom because I am unable to pay their outrageously high fees. A few very valuable domains were in enom&#039;s possession when I pleaded with them not to sell/drop them (I have it in print through the &quot;help&quot; tickets) telling them that I would pay any price, but they still let them drop and they were snached up by others.

I am still trying to get the domains back that I legally bought and were illegally dropped &amp; purchased by others and also figure out which ones still in enom&#039;s system I can afford to get back.

&lt;b&gt; Anyway, as I attempt to do this is there a page on ICANN&#039;s site that is designed for the purpose of helping us get our domains back.
I.E. a brief description of the registerfly debacle, that ICANN is committed to getting the affected domains to the rightful owners, and that the ethical and legal course of action is to return the domains to the rightful owners at a fair compensation level. This would also be helpful when I deal with a foriegn registra when I try to get www.shopchina.cn back.&lt;/b&gt;

Thank you,
Scott Reese
webevangelist@gmail.com</description>
		<content:encoded><![CDATA[<p>I&#8217;ve lost at least 75 domains due to this registerfly fiasco. I wll not recount my story because because it&#8217;s similar to what everyone else went through. It was absolutely impossible to renew domain names. It was slow and painful deaths as you would see the domain expire and someone else (usually an unknown protected person) buy the domains. Other domains are still being held hostage by enom because I am unable to pay their outrageously high fees. A few very valuable domains were in enom&#8217;s possession when I pleaded with them not to sell/drop them (I have it in print through the &#8220;help&#8221; tickets) telling them that I would pay any price, but they still let them drop and they were snached up by others.</p>
<p>I am still trying to get the domains back that I legally bought and were illegally dropped &amp; purchased by others and also figure out which ones still in enom&#8217;s system I can afford to get back.</p>
<p><b> Anyway, as I attempt to do this is there a page on ICANN&#8217;s site that is designed for the purpose of helping us get our domains back.<br />
I.E. a brief description of the registerfly debacle, that ICANN is committed to getting the affected domains to the rightful owners, and that the ethical and legal course of action is to return the domains to the rightful owners at a fair compensation level. This would also be helpful when I deal with a foriegn registra when I try to get <a href="http://www.shopchina.cn" rel="nofollow">http://www.shopchina.cn</a> back.</b></p>
<p>Thank you,<br />
Scott Reese<br />
<a href="mailto:webevangelist@gmail.com">webevangelist@gmail.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kieren McCarthy</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-2420</link>
		<dc:creator>Kieren McCarthy</dc:creator>
		<pubDate>Thu, 19 Jul 2007 11:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-2420</guid>
		<description>Hindsight is a wonderful thing, Jackee. 

And it can be very easily demonstrated why this apparent lack of &quot;imagination&quot; is a red herring.

At some point in the next five to ten years, there will be another issue just like RegisterFly - where domain owners are up in arms and ICANN finds its current policies are not sufficient and it will have to deal with it and then change the policies to fix the problem for the future. And when that happens someone else will complain that ICANN should have foreseen the problem.

So, here&#039;s the question: what changes does ICANN make now for that not to happen? We don&#039;t want it to happen, no one wants it to happen, so come up with the changes now and we&#039;ll do it.

As a quick indication of where the problem is going to come from, bear in mind these following changes to the domain name system that will happen in the next few years:

* A range - potentially a very large range - of new top-level domains will be approved and appear on the Internet. It will no longer be dotcom domains but dot-coffee, dot-hotel, dot-tree, dot-whatever.

* With a larger number of TLDs, it is inevitable that at some point an entire registry will fail, rather that just a single registrar. That will mean that all domains under that registry will be at risk - and they will have been bought through dozens of different registrars. Could you draw up the rules for this scenario please - and make sure there are no loopholes?

* It will not only be English TLDs. Very soon, there will hundreds perhaps thousands of new top-level domains in a range of scripts so people all over the world will be able to represent their language. This in turn will mean new registrars situated all over the world. Registrars operating in different countries, under different laws, who may never sell a dotcom in their life but only Chinese scripts or Arabic scripts. Do you think the rules are currently sufficient to cover companies right across the world? If not, could you please provide the wording - and then accurate translations of those rules in 25 languages?

* Are the rules in place sufficient to allow someone based in the US, who registered a domain in the Arabic script to get it back off a registrar based in Russia? If not, could you please provide the watertight wording that will mean ICANN can protect the registrant? And not just that registrant but the hundreds of millions of new registrants all over the world that will buy domains for the first time - very few of whom will understand how the system actually works?

* How many staff do you think ICANN would need to adequately protect 100 million people? Has there ever been an organisation in the world that has been able to protect that number of people? So if ICANN can&#039;t do that, how can registrants be protected? Would people be willing to pay an extra $5 right across the world for every domain because of the one-in-a-million chance that they might lose their domain? Or should it be left to market forces? Allow companies to offer protection services and promote their stability? What if people buy a domain from an unscrupulous registrar in Taiwan anyway just because it&#039;s 30 cents cheaper? How does ICANN decide what is a good and what is a bad registrar? What if a previously good registrar turns bad?

* What if a new registry sues a new registrar and the domains are put in limbo?

* What if a new registrar sues its own customers, pointing out an obscure clause in its Indian contract, and takes control over thousands of valuable domains? Do you have the wording for this scenario?

* What if a registrar declares bankruptcy but starts the next day with all its previous domains under a different company name with a different contract - which is then enforces to get everyone to pay an extra $30 or lose the domain?


I would say that was a fairly imaginative set of scenarios. Now all we need to do in produce the rules and guidelines that mean there will never be another problem like RegisterFly.


Incidentally, if you *do* have some ideas that you think have been overlooked or would make matters easier, please do get involved and put them in front of either ALAC or the GNSO. If they solve a problem they *will* get through - that&#039;s how the ICANN model works.


Kieren McCarthy
General manager of public participation, ICANN</description>
		<content:encoded><![CDATA[<p>Hindsight is a wonderful thing, Jackee. </p>
<p>And it can be very easily demonstrated why this apparent lack of &#8220;imagination&#8221; is a red herring.</p>
<p>At some point in the next five to ten years, there will be another issue just like RegisterFly &#8211; where domain owners are up in arms and ICANN finds its current policies are not sufficient and it will have to deal with it and then change the policies to fix the problem for the future. And when that happens someone else will complain that ICANN should have foreseen the problem.</p>
<p>So, here&#8217;s the question: what changes does ICANN make now for that not to happen? We don&#8217;t want it to happen, no one wants it to happen, so come up with the changes now and we&#8217;ll do it.</p>
<p>As a quick indication of where the problem is going to come from, bear in mind these following changes to the domain name system that will happen in the next few years:</p>
<p>* A range &#8211; potentially a very large range &#8211; of new top-level domains will be approved and appear on the Internet. It will no longer be dotcom domains but dot-coffee, dot-hotel, dot-tree, dot-whatever.</p>
<p>* With a larger number of TLDs, it is inevitable that at some point an entire registry will fail, rather that just a single registrar. That will mean that all domains under that registry will be at risk &#8211; and they will have been bought through dozens of different registrars. Could you draw up the rules for this scenario please &#8211; and make sure there are no loopholes?</p>
<p>* It will not only be English TLDs. Very soon, there will hundreds perhaps thousands of new top-level domains in a range of scripts so people all over the world will be able to represent their language. This in turn will mean new registrars situated all over the world. Registrars operating in different countries, under different laws, who may never sell a dotcom in their life but only Chinese scripts or Arabic scripts. Do you think the rules are currently sufficient to cover companies right across the world? If not, could you please provide the wording &#8211; and then accurate translations of those rules in 25 languages?</p>
<p>* Are the rules in place sufficient to allow someone based in the US, who registered a domain in the Arabic script to get it back off a registrar based in Russia? If not, could you please provide the watertight wording that will mean ICANN can protect the registrant? And not just that registrant but the hundreds of millions of new registrants all over the world that will buy domains for the first time &#8211; very few of whom will understand how the system actually works?</p>
<p>* How many staff do you think ICANN would need to adequately protect 100 million people? Has there ever been an organisation in the world that has been able to protect that number of people? So if ICANN can&#8217;t do that, how can registrants be protected? Would people be willing to pay an extra $5 right across the world for every domain because of the one-in-a-million chance that they might lose their domain? Or should it be left to market forces? Allow companies to offer protection services and promote their stability? What if people buy a domain from an unscrupulous registrar in Taiwan anyway just because it&#8217;s 30 cents cheaper? How does ICANN decide what is a good and what is a bad registrar? What if a previously good registrar turns bad?</p>
<p>* What if a new registry sues a new registrar and the domains are put in limbo?</p>
<p>* What if a new registrar sues its own customers, pointing out an obscure clause in its Indian contract, and takes control over thousands of valuable domains? Do you have the wording for this scenario?</p>
<p>* What if a registrar declares bankruptcy but starts the next day with all its previous domains under a different company name with a different contract &#8211; which is then enforces to get everyone to pay an extra $30 or lose the domain?</p>
<p>I would say that was a fairly imaginative set of scenarios. Now all we need to do in produce the rules and guidelines that mean there will never be another problem like RegisterFly.</p>
<p>Incidentally, if you *do* have some ideas that you think have been overlooked or would make matters easier, please do get involved and put them in front of either ALAC or the GNSO. If they solve a problem they *will* get through &#8211; that&#8217;s how the ICANN model works.</p>
<p>Kieren McCarthy<br />
General manager of public participation, ICANN</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jackee</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-2418</link>
		<dc:creator>jackee</dc:creator>
		<pubDate>Thu, 19 Jul 2007 02:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-2418</guid>
		<description>i also have to disagree. ICANN’s lack of of imagination and not having in place mechanisms for dealing with a Registerfly type scenario is glaring. i just want to say it there is waste of time so i go and take few glasess of wine and sleep.</description>
		<content:encoded><![CDATA[<p>i also have to disagree. ICANN’s lack of of imagination and not having in place mechanisms for dealing with a Registerfly type scenario is glaring. i just want to say it there is waste of time so i go and take few glasess of wine and sleep.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-2256</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Tue, 12 Jun 2007 17:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-2256</guid>
		<description>Godaddy isn&#039;t honoring the domain expiration dates that Registerfly had.  Registerfly still shows 2008 on the domain name expiration and godaddy won&#039;t honor it:


&quot;Thank you for contacting Online Support.

Unfortunately, we are unable to assist you with your issue. When your domain names were migrated from Registerfly, we received them exactly as they were including all of your original account information. If you renewed your domain name through Registerfly and it was not showing the correct expiration date before your recent renewal with our company, you will need to contact Registerfly or ICANN for assistance. We apologize for any inconvenience regarding this issue.&quot;</description>
		<content:encoded><![CDATA[<p>Godaddy isn&#8217;t honoring the domain expiration dates that Registerfly had.  Registerfly still shows 2008 on the domain name expiration and godaddy won&#8217;t honor it:</p>
<p>&#8220;Thank you for contacting Online Support.</p>
<p>Unfortunately, we are unable to assist you with your issue. When your domain names were migrated from Registerfly, we received them exactly as they were including all of your original account information. If you renewed your domain name through Registerfly and it was not showing the correct expiration date before your recent renewal with our company, you will need to contact Registerfly or ICANN for assistance. We apologize for any inconvenience regarding this issue.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-2255</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Tue, 12 Jun 2007 17:34:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-2255</guid>
		<description>1) One of my customer&#039;s domain names have been taken over by an ad company.  I though that we weren&#039;t going to loose domain names?
Ouch!!

2) Also- godaddy isn&#039;t allowing me to transfer out... holding me hostage to renewing with them because they hold for a 60 day period.</description>
		<content:encoded><![CDATA[<p>1) One of my customer&#8217;s domain names have been taken over by an ad company.  I though that we weren&#8217;t going to loose domain names?<br />
Ouch!!</p>
<p>2) Also- godaddy isn&#8217;t allowing me to transfer out&#8230; holding me hostage to renewing with them because they hold for a 60 day period.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mehdi Alidoost</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-2185</link>
		<dc:creator>Mehdi Alidoost</dc:creator>
		<pubDate>Mon, 04 Jun 2007 00:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-2185</guid>
		<description>There is a big problem after moving domain names to Godaddy.com , becuase this site block Iranina IP Address and limit access from this country , we can not reach ( update or transfer ) our domains at all now.

Before,When I had registered domain by Godaddy from Iranian IP address or domain owner address , they inform me thet I have 48 hours to transfer domain to another registrant.

now What can we do? from here we can not access godaddy and all domains move to this , and until now we dont receive any information about our account on Godaddy ?</description>
		<content:encoded><![CDATA[<p>There is a big problem after moving domain names to Godaddy.com , becuase this site block Iranina IP Address and limit access from this country , we can not reach ( update or transfer ) our domains at all now.</p>
<p>Before,When I had registered domain by Godaddy from Iranian IP address or domain owner address , they inform me thet I have 48 hours to transfer domain to another registrant.</p>
<p>now What can we do? from here we can not access godaddy and all domains move to this , and until now we dont receive any information about our account on Godaddy ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Orson</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-2163</link>
		<dc:creator>Orson</dc:creator>
		<pubDate>Sat, 02 Jun 2007 09:43:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-2163</guid>
		<description>I had several domain names registered at registerfly.com. And now I learn that this registrar&#039;s accreditation has been removed by your organization. In due time some of my domains have expired and been registered by someone else.  I didn&#039;t receive any email regarding this situation neither by Registerfly.com or by ICANN. 

And now I learn by chance that all domains under registerfly.com will going to be transferred to godaddy.com. But when I go this new registrar&#039;s site, I need to complete a bunch of complex procedures in order to access my domain accounts. 

I think ICANN is liable of making this transfer as smooth as possible in order keep up the satisfaction of previous customers of Registerfly.com. And I am asking from you to retrieve all of the rights of my domains regisgtered in Registerfly.com since you accredited this firm beforehand and you are liable of keeping the security of the customers. 

THus I declare that I won&#039;t take any action or procedure to collect all my domains into GoDaddy.com (or some other site). THis is YOUR TASK! 

If I don&#039;t find all of my domains control in order and working smoothly in two weeks time, or if any of my domains registered before in Registerfly.com has been captivated by someone else, I will use my international rights to sue you in international courts and demand my financial loss. 



2.6.07</description>
		<content:encoded><![CDATA[<p>I had several domain names registered at registerfly.com. And now I learn that this registrar&#8217;s accreditation has been removed by your organization. In due time some of my domains have expired and been registered by someone else.  I didn&#8217;t receive any email regarding this situation neither by Registerfly.com or by ICANN. </p>
<p>And now I learn by chance that all domains under registerfly.com will going to be transferred to godaddy.com. But when I go this new registrar&#8217;s site, I need to complete a bunch of complex procedures in order to access my domain accounts. </p>
<p>I think ICANN is liable of making this transfer as smooth as possible in order keep up the satisfaction of previous customers of Registerfly.com. And I am asking from you to retrieve all of the rights of my domains regisgtered in Registerfly.com since you accredited this firm beforehand and you are liable of keeping the security of the customers. </p>
<p>THus I declare that I won&#8217;t take any action or procedure to collect all my domains into GoDaddy.com (or some other site). THis is YOUR TASK! </p>
<p>If I don&#8217;t find all of my domains control in order and working smoothly in two weeks time, or if any of my domains registered before in Registerfly.com has been captivated by someone else, I will use my international rights to sue you in international courts and demand my financial loss. </p>
<p>2.6.07</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shirl Rose</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-2156</link>
		<dc:creator>Shirl Rose</dc:creator>
		<pubDate>Sat, 02 Jun 2007 06:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-2156</guid>
		<description>Now that our domain names have moved from Registerfly to Godaddy it has come to our attention that Godaddy is imposing a 60 prohibition on transferring them out to registrars. All requests for such transfers are automatically rejected by Godaddy and will continue to be so for 60 days.
 
This seems improper since the automatic transfer from Registerfly to Godaddy does not constitute a customary transfer (payment to Godaddy, acceptance of their TOS, extension of expiration date, an explicit and willful action by the registrant to use Godaddy, etc.)

While the registry requirement for transferring out are met (lock status can be removed and the AuthCode obtained from Godaddy) Godaddy is unilaterally and automatically rejecting transfer out requests. I maintain Godaddy does not have such authority - whether based on its agreements with ICANN (which has not been posted at ICANN’s website) or based on a user agreement (which has never been established with the registrant due to the ICANN sanctioned automatic transfers).
 
On its website Godaddy states: “ICANN named GoDaddy.com the new custodian of the .COM, .NET, .ORG, .INFO, .BIZ, and .NAME domain names that were previously registered at RegisterFly. ”

If Godaddy is the &quot;custodian&quot; of these transferred domain names it should not have the authority to place constraints on the domain names over and above that what existed while the domain names were at Registerfly. This would not include an additional 60 day prohibition on transferring out and imposing mandatory renewals on expiring domain names.
 
If Godaddy is allowed to forcefully place this 60 day hold not only will expired registrations have to be renewed at Godaddy and no other registrar but also those registrations that will expire in the next 60 days will have to be registered at Godaddy!
 
In effect Godaddy will not be the &quot;custodian&quot; of these domain names but rather the new registrar imposed for an additional year - under its own terms and conditions and its own fee structure - without such authority by the current registrant.
 
One would hope ICANN&#039;s agreement with Godaddy was not supposed to impose such a huge windfall for Godaddy by forcing a long term relationship by the Registerfly registrants with Godaddy.

According to Godaddy’s website “more than 850,000 domain names will have been moved.” Assuming 2/12 of these expired during the past two months at Registerfly due to the acknowledged problems and 2/12 will expire in the next two months a total of 1/3 of the automatically transferred domain names (280,000) will be forced to be renewed at Godaddy for an additional year - without any such consent currently existing by the registrant. This constitutes a windfall of some $2,800,000 in sales for Godaddy simply for entering into the agreement with ICANN, and a sizable profit based on its $9.17 price. Adding insult to injury Godaddy will charge these domain names at its renewal fee of $9.17 instead of its transfer fee of $7.17.
 
If Godaddy is allowed to enforce this 60 day hold policy this arrangement would not by definition constitute a “custodial” and interim relationship with Godaddy but rather a forceful acceptance of a third party registrar with its own TOS (which we never agreed to) and an ICANN sanctioned unilateral and coerced acceptance of Godaddy as our registrar for one more year.</description>
		<content:encoded><![CDATA[<p>Now that our domain names have moved from Registerfly to Godaddy it has come to our attention that Godaddy is imposing a 60 prohibition on transferring them out to registrars. All requests for such transfers are automatically rejected by Godaddy and will continue to be so for 60 days.</p>
<p>This seems improper since the automatic transfer from Registerfly to Godaddy does not constitute a customary transfer (payment to Godaddy, acceptance of their TOS, extension of expiration date, an explicit and willful action by the registrant to use Godaddy, etc.)</p>
<p>While the registry requirement for transferring out are met (lock status can be removed and the AuthCode obtained from Godaddy) Godaddy is unilaterally and automatically rejecting transfer out requests. I maintain Godaddy does not have such authority &#8211; whether based on its agreements with ICANN (which has not been posted at ICANN’s website) or based on a user agreement (which has never been established with the registrant due to the ICANN sanctioned automatic transfers).</p>
<p>On its website Godaddy states: “ICANN named GoDaddy.com the new custodian of the .COM, .NET, .ORG, .INFO, .BIZ, and .NAME domain names that were previously registered at RegisterFly. ”</p>
<p>If Godaddy is the &#8220;custodian&#8221; of these transferred domain names it should not have the authority to place constraints on the domain names over and above that what existed while the domain names were at Registerfly. This would not include an additional 60 day prohibition on transferring out and imposing mandatory renewals on expiring domain names.</p>
<p>If Godaddy is allowed to forcefully place this 60 day hold not only will expired registrations have to be renewed at Godaddy and no other registrar but also those registrations that will expire in the next 60 days will have to be registered at Godaddy!</p>
<p>In effect Godaddy will not be the &#8220;custodian&#8221; of these domain names but rather the new registrar imposed for an additional year &#8211; under its own terms and conditions and its own fee structure &#8211; without such authority by the current registrant.</p>
<p>One would hope ICANN&#8217;s agreement with Godaddy was not supposed to impose such a huge windfall for Godaddy by forcing a long term relationship by the Registerfly registrants with Godaddy.</p>
<p>According to Godaddy’s website “more than 850,000 domain names will have been moved.” Assuming 2/12 of these expired during the past two months at Registerfly due to the acknowledged problems and 2/12 will expire in the next two months a total of 1/3 of the automatically transferred domain names (280,000) will be forced to be renewed at Godaddy for an additional year &#8211; without any such consent currently existing by the registrant. This constitutes a windfall of some $2,800,000 in sales for Godaddy simply for entering into the agreement with ICANN, and a sizable profit based on its $9.17 price. Adding insult to injury Godaddy will charge these domain names at its renewal fee of $9.17 instead of its transfer fee of $7.17.</p>
<p>If Godaddy is allowed to enforce this 60 day hold policy this arrangement would not by definition constitute a “custodial” and interim relationship with Godaddy but rather a forceful acceptance of a third party registrar with its own TOS (which we never agreed to) and an ICANN sanctioned unilateral and coerced acceptance of Godaddy as our registrar for one more year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Coble</title>
		<link>http://blog.icann.org/2007/04/board-discussion-over-registerfly/comment-page-1/#comment-1877</link>
		<dc:creator>David Coble</dc:creator>
		<pubDate>Mon, 21 May 2007 02:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.icann.org/?p=86#comment-1877</guid>
		<description>I absolutely agree.  All that need happen for evil to flourish is for good men to do nothing.  It&#039;s time for ICANN to do something.  I have not been able to log in to my RF account since late February, so all the advice about how to unlock domains and acquire auth codes feels like mockery to me.

I have called and emailed RF many times.

When are we going to see something from the good guys?</description>
		<content:encoded><![CDATA[<p>I absolutely agree.  All that need happen for evil to flourish is for good men to do nothing.  It&#8217;s time for ICANN to do something.  I have not been able to log in to my RF account since late February, so all the advice about how to unlock domains and acquire auth codes feels like mockery to me.</p>
<p>I have called and emailed RF many times.</p>
<p>When are we going to see something from the good guys?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
