<story><title>GoDaddy Responds To Namecheap Accusations, Removes “Normal” Rate Limiting Block</title><url>http://techcrunch.com/2011/12/26/godaddy-responds-to-namecheap-accusations-removes-normal-rate-limiting-block/</url></story><parent_chain></parent_chain><comment><author>freejack</author><text>These types of things happen all the time behind the scenes. The entire domain registration system is very loosely coupled as it relates to transfers - too loose imo, and breakage is really easy. We had a situation last week where a registrar made a small change to their registrar name and it threw our whois parsers for a loop. From a casual view, it looked like the other end had cut us off, and a quick deep dive made the parsing issue immediately apparent.&lt;p&gt;Domain transfers was an afterthought to the multi-registrar model and was designed and implemented as policy (i.e. ICANN), not as a technical process (i.e. IETF). I wish we&apos;d done a better job in 1999.</text></comment>
<story><title>GoDaddy Responds To Namecheap Accusations, Removes “Normal” Rate Limiting Block</title><url>http://techcrunch.com/2011/12/26/godaddy-responds-to-namecheap-accusations-removes-normal-rate-limiting-block/</url></story><parent_chain></parent_chain><comment><author>hamax</author><text>A namecheap employee claims that they did contact goDaddy and that they resorted to the PR release only after they couldn&apos;t resolve the issue directly with them: &lt;a href=&quot;http://community.namecheap.com/blog/2011/12/26/godaddy-transfer-update/#comment-1709&quot; rel=&quot;nofollow&quot;&gt;http://community.namecheap.com/blog/2011/12/26/godaddy-trans...&lt;/a&gt;</text></comment>